Segment Routing Architecture
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 32
- Abstract
- Segment Routing (SR) leverages the source routing paradigm. A node steers a packet through an ordered list of instructions, called "segments". A segment can represent any instruction, topological or service based. A segment can have a semantic local to an SR node or global within an SR domain. SR provides a mechanism that allows a flow to be restricted to a specific topological path, while maintaining per-flow state only at the ingress node(s) to the SR domain. SR can be directly applied to the MPLS architecture with no change to the forwarding plane. A segment is encoded as an MPLS label. An ordered list of segments is encoded as a stack of labels. The segment to process is on the top of the stack. Upon completion of a segment, the related label is popped from the stack. SR can be applied to the IPv6 architecture, with a new type of routing header. A segment is encoded as an IPv6 address. An ordered list of segments is encoded as an ordered list of IPv6 addresses in the routing header. The active segment is indicated by the Destination Address (DA) of the packet. The next active segment is indicated by a pointer in the new routing header.
- Publication Date
- 2018-07-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC8402- Link
- https://doi.org/10.17487/RFC8402
- Author(s)
- Clarence FilsfilsStefano PrevidiLes GinsbergBruno DecraeneStephane LitkowskiRob Shakir
Latest version of IETF RFC 8402
Document Versions — IETF RFC 8402
-
▶ IETF RFC 8402 (2018-07-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 3031 [Active*]
- IETF RFC 8174 [Active*]
- IETF RFC 8200 [Active*]
Bibliographic Reference(s)
- IETF.draft-ietf-6man-segment-routing-header-14 — IPv6-SRH EXTERNAL
- IETF.draft-ietf-idr-bgpls-segment-routing-epe-15 — BGPLS-SR-EPE EXTERNAL
- IETF.draft-ietf-isis-segment-routing-extensions-19 — ISIS-SR-EXT EXTERNAL
- IETF.draft-ietf-ospf-ospfv3-segment-routing-extensions-13 — OSPFv3-SR-EXT EXTERNAL
- IETF.draft-ietf-ospf-segment-routing-extensions-25 — OSPF-SR-EXT EXTERNAL
- IETF.draft-ietf-pce-segment-routing-12 — PCEP-SR-EXT EXTERNAL
- IETF.draft-ietf-spring-segment-routing-central-epe-10 — SR-CENTRAL-EPE EXTERNAL
- IETF.draft-ietf-spring-segment-routing-mpls-14 — SR-MPLS EXTERNAL
- IETF.draft-ietf-spring-sr-yang-09 — SR-YANG EXTERNAL
- IETF RFC 3209 [Active*]
- IETF RFC 4206 [Active*]
- IETF RFC 4381 [Active*]
- IETF RFC 4915 [Active*]
- IETF RFC 5095 [Active*]
- IETF RFC 5120 [Active*]
- IETF RFC 5440 [Active*]
- IETF RFC 5714 [Active*]
- IETF RFC 5920 [Active*]
- IETF RFC 6020 [Active*]
- IETF RFC 6241 [Active*]
- IETF RFC 6549 [Active*]
- IETF RFC 7938 [Active*]
- IETF RFC 8084 [Active*]
- IETF RFC 8202 [Active*]
- IETF RFC 8287 [Active*]
- IETF RFC 8355 [Active*]
- IETF RFC 8403 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC8402.json
Amended by:
IETF RFC 9256 [Active*]
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 8402, Segment Routing Architecture. Available at https://doi.org/10.17487/RFC8402
Snippet:
IETF RFC 8402, Segment Routing Architecture. Available at https://doi.org/10.17487/RFC8402
HTML (ISO 690 compliant)
Preview:
IETF RFC 8402, Segment Routing Architecture. Available at https://doi.org/10.17487/RFC8402
Snippet:
<span class="citation"><cite>IETF RFC 8402</cite>, Segment Routing Architecture. Available at <a href="https://doi.org/10.17487/RFC8402" target="_blank" rel="noopener">https://doi.org/10.17487/RFC8402</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 8402, Segment Routing Architecture
doi: 10.17487/RFC8402
url: https://doi.org/10.17487/RFC8402
doi: 10.17487/RFC8402
url: https://doi.org/10.17487/RFC8402
Snippet:
<li> <cite id="bib-rfc8402">IETF RFC 8402</cite>, Segment Routing Architecture <span class="doi">10.17487/RFC8402</span> </li>
Referenced By
- IETF RFC 10018 [Active*]
- IETF RFC 8403 [Active*]
- IETF RFC 8595 [Active*]
- IETF RFC 8655 [Active*]
- IETF RFC 8660 [Active*]
- IETF RFC 8664 [Active*]
- IETF RFC 8669 [Active*]
- IETF RFC 8754 [Active*]
- IETF RFC 8799 [Active*]
- IETF RFC 8934 [Active*]
- IETF RFC 8986 [Active*]
- IETF RFC 8994 [Active*]
- IETF RFC 9012 [Active*]
- IETF RFC 9085 [Active*]
- IETF RFC 9252 [Active*]
- IETF RFC 9256 [Active*]
- IETF RFC 9262 [Active*]
- IETF RFC 9301 [Active*]
- IETF RFC 9502 [Active*]
- IETF RFC 9522 [Active*]
- IETF RFC 9524 [Active*]
- IETF RFC 9573 [Active*]
- IETF RFC 9603 [Active*]
- IETF RFC 9604 [Active*]
- IETF RFC 9746 [Active*]
- IETF RFC 9789 [Active*]
- IETF RFC 9819 [Active*]
- IETF RFC 9830 [Active*]
- IETF RFC 9914 [Active*]
- IETF RFC 9960 [Active*]