SPRING IPv6 ListID Encapsulation
draft-lt-6man-sr-listid-encapsulation-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Ting Liao , Ting Ao | ||
| Last updated | 2016-04-21 (Latest revision 2015-10-19) | ||
| 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. Segment Routing can be applied to the IPv6 architecture, with a new type of routing extension 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 extension header. The segment to process is indicated by a pointer in the routing extension header. Upon completion of a segment, the pointer is incremented. This document describes how to decrease the length of the IPv6 list with ListID carried.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)