Spring Segment List ID
draft-chen-spring-segment-list-id-01
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Ran Chen , Ting Liao | ||
Last updated | 2016-04-14 (Latest revision 2015-10-12) | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
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 allows a node to steer a packet through an ordered list of instructions, called segments. The ingress node prepends a SR header to a packet containing a set of "segments". A segment can represent any instruction topological or service-based. The Segment Routing architecture can be implemented using MPLS 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, but it has implications on label stack depth. This document describes how to decrease the depth of the label stack in order to do effective Segment Routing operation.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)