CARVIEW |
Select Language
HTTP/2 200
date: Fri, 10 Oct 2025 11:51:27 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=LgGgYDW4Y3A2ueLhUxnj4u7i2tmNCTpoLCFnkRJzV1s-1760097087-1.0.1.1-d_v5PaB4ltggU9PAS68UJpp3Aqnx11g7CJe2jz15V1hYHkTqct.juRWE7N2kTlB4WHTD92Bkjp1Xzm1r4T4lZTCyaHv_ITPzG.GVNxER_ko; path=/; expires=Fri, 10-Oct-25 12:21:27 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98c5e7e90e309ac4-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 8754 » RFC Editor
Search RFCs
RFC 8754
IPv6 Segment Routing Header (SRH), March 2020
- File formats:
- Also available: XML file for editing
- Status:
- PROPOSED STANDARD
- Updated by:
- RFC 9800
- Authors:
- C. Filsfils, Ed.
D. Dukes, Ed.
S. Previdi
J. Leddy
S. Matsushima
D. Voyer - Stream:
- IETF
- Source:
- 6man (int)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC8754
Discuss this RFC: Send questions or comments to the mailing list ipv6@ietf.org
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 8754
Abstract
Segment Routing can be applied to the IPv6 data plane using a new type of Routing Extension Header called the Segment Routing Header (SRH). This document describes the SRH and how it is used by nodes that are Segment Routing (SR) capable.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us