Unified Identifier in IPv6 Segment Routing Networks
draft-mirsky-6man-unified-id-sr-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Greg Mirsky , Shaofu Peng | ||
| Last updated | 2018-08-30 (Latest revision 2018-02-26) | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Segment Routing architecture leverages the paradigm of source routing. It can be realized in a network data plane by prepending the packet with a list of instructions, a.k.a. segments. A segment can be encoded as an Multi-Protocol Label Switching (MPLS) label, IPv4 address or IPv6 address. Segment Routing can be applied in MPLS data plane by encoding segments in MPLS label stack. It also can be applied to IPv6 data plane by encoding list of segment identifiers in IPv6 Segment Routing Extension Header (SRH). This document extends the use of the SRH to segment identifiers encoded as MPLS label and IPv4 address.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)