Extensions to ISIS for Source Label Distribution
draft-chen-isis-source-label-distribution-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Mach Chen , Greg Mirsky | ||
| Last updated | 2014-08-17 (Latest revision 2014-02-13) | ||
| 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
An MPLS Source Label (SL) is defined to identify a node that is (one of) the ingress LSRs to a specific LSP. This document defines extensions to ISIS protocol for distribution of the mapping of an MPLS Source Label to an specific LSR. Therefore, the egress and intermediate LSRs can 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 process the Source Label. With the SLC, an ingress LSR can determine whether it is allowed to insert a Source Label 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.)