Unified Identifier in IPv6 Segment Routing Networks
draft-mirsky-6man-unified-id-sr-00

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Last updated 2018-08-30 (latest revision 2018-02-26)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-mirsky-6man-unified-id-sr-00.txt

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

Gregory Mirsky (gregimirsky@gmail.com)
Shaofu Peng (peng.shaofu@zte.com.cn)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)