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

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Authors Weiqiang Cheng  , Greg Mirsky  , Shaofu Peng  , Aihua Liu  , Gyan Mishra 
Last updated 2021-01-03 (latest revision 2020-07-02)
Stream (None)
Formats
Expired & archived
plain text xml pdf htmlized 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-07.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 a Multi-Protocol Label Switching (MPLS) label, IPv4 address, or IPv6 address. Segment Routing can be applied in MPLS data plane by encoding segments in the MPLS label stack. It also can be applied to IPv6 data plane by encoding a list of segment identifiers in IPv6 Segment Routing Extension Header (SRH). This document extends the use of the SRH to unified segment identifiers encoded, for example, as MPLS label or IPv4 address, to compress the SRH, and support more detailed network programming and interworking between SR-MPLS and SRv6 domains.

Authors

Weiqiang Cheng (chengweiqiang@chinamobile.com)
Greg Mirsky (gregimirsky@gmail.com)
Shaofu Peng (peng.shaofu@zte.com.cn)
Aihua Liu (liu.aihua@zte.com.cn)
Gyan Mishra (gyan.s.mishra@verizon.com)

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