Controlling State Advertisements of Non-negotiated LDP Applications, March 2015
- File formats:
- PROPOSED STANDARD
- Updated by:
- RFC 8223
- K. Raza
- mpls (rtg)
Discuss this RFC: Send questions or comments to the mailing list [email protected]
There is no capability negotiation done for Label Distribution Protocol (LDP) applications that set up Label Switched Paths (LSPs) for IP prefixes or that signal point-to-point (P2P) Pseudowires (PWs) for Layer 2 Virtual Private Networks (L2VPNs). When an LDP session comes up, an LDP speaker may unnecessarily advertise its local state for such LDP applications even when the peer session is established for some other applications like Multipoint LDP (mLDP) or the Inter-Chassis Communication Protocol (ICCP). This document defines a solution by which an LDP speaker announces to its peer its disinterest in such non-negotiated applications, thus disabling the unnecessary advertisement of corresponding application state, which would have otherwise been advertised over the established LDP session.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.