Applicability of LDP Label Advertisement Mode
draft-raza-mpls-ldp-applicability-label-adv-02

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Authors Kamran Raza  , Sami Boutros  , Luca Martini  , Nicolai Leymann 
Last updated 2012-07-16 (latest revision 2012-01-13)
Replaced by RFC 7358, RFC 7358
Stream (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 Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-raza-mpls-ldp-applicability-label-adv-02.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 RFC5036 and RFC4447 to remove any ambiguity and conflict in the area of using correct label advertisement mode for a given application.

Authors

Kamran Raza (skraza@cisco.com)
Sami Boutros (sboutros@cisco.com)
Luca Martini (lmartini@cisco.com)
Nicolai Leymann (n.leymann@telekom.de)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)