LDP Specification
draft-ijln-mpls-rfc5036bis-04
| Document | Type | Expired Internet-Draft (mpls WG) | |
|---|---|---|---|
| Last updated | 2017-10-28 (latest revision 2017-04-26) | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | WG state | Candidate for WG Adoption | |
| Document shepherd | Andrew Malis | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | "Ross Callon" <rcallon@juniper.net>, "Andrew G. Malis" <agmalis@gmail.com>, loa@pi.nu | ||
https://www.ietf.org/archive/id/draft-ijln-mpls-rfc5036bis-04.txt
Abstract
The architecture for Multiprotocol Label Switching (MPLS) is described in RFC 3031. A fundamental concept in MPLS is that two Label Switching Routers (LSRs) must agree on the meaning of the labels used to forward traffic between and through them. This common understanding is achieved by using a set of procedures, called a label distribution protocol, by which one LSR informs another of label bindings it has made. This document defines a set of such procedures called LDP (for Label Distribution Protocol) by which LSRs distribute labels to support MPLS forwarding along normally routed paths.
Authors
Xia Chen
(jescia.chenxia@huawei.com)
Loa Andersson
(loa@pi.nu)
Nicolai Leymann
(n.leymann@telekom.de)
Ina Minei
(inaminei@google.com)
Kamran Raza
(skraza@cisco.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)