Extensions to ISIS for Source Identifier Distribution
draft-chen-isis-source-identifier-distribution-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Mach Chen , Greg Mirsky | ||
Last updated | 2015-04-15 (Latest revision 2014-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
A Source Identifier (SI) is carried in an MPLS Source Label and used to identify (one of) the ingress LSR(s) to a specific LSP. This document defines extensions to ISIS protocol for distribution of the mapping of a Source Identifier to an specific LSR. Therefore, the egress and intermediate LSRs can use the SI to determine from which LSR an MPLS packet is sent. This document also defines ISIS extensions to advertise the Source Label Capability (SLC) of each LSR that indicates whether an LSR can properly process the Source Label Indicator (SLI) special purpose label and Source Label (SL). With the SLC, an ingress LSR can determine whether it is allowed to insert a SL into the label stack for a specific LSP.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)