Applicability of LDP Label Advertisement Mode
draft-raza-mpls-ldp-applicability-label-adv-03
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Kamran Raza , Luca Martini , Nicolai Leymann , Sami Boutros | ||
| Last updated | 2012-10-10 (latest revision 2012-07-17) | ||
| Replaced by | RFC 7358 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-mpls-ldp-applicability-label-adv | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-raza-mpls-ldp-applicability-label-adv-03.txt
Abstract
An LDP speaker negotiates the label advertisement mode with its LDP peer at the time of session establishment. Although different applications sharing the same LDP session may need different modes of label distribution and advertisement, there is only one type of label advertisement mode that is negotiated and used per LDP session. This document clarifies the use and the applicability of session's negotiated label advertisement mode, and categorizes LDP applications into two broad categories of negotiated mode-bound and mode-independent applications. The document also suggests an update to RFC 5036 and RFC 4447 to remove any ambiquity and conflict in the area of using correct label advertisement mode for a given application.
Authors
Kamran Raza
(skraza@cisco.com)
Luca Martini
(lmartini@cisco.com)
Nicolai Leymann
(n.leymann@telekom.de)
Sami Boutros
(sboutros@cisco.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)