Non-Penultimate Hop Popping Behavior and Out-of-Band Mapping for RSVP-TE Label Switched Paths

Multicast in Virtual Private LAN Service (VPLS)

“…In order for the egress PE to be able to discard such traffic, it needs to know that the LSP is associated with one or more VPLS instances and that the VPLS A-D route that binds the LSP to a VPLS has not yet been received. This is provided by extending [RFC4875] with [RFC6511].…”

A Survey on the Evolution of RSVP

“…Using the LSP Attributes object defined in [61] two flags were defined by [74]. The Non-PHP behaviour flag and the OOB mapping flag were introduced.…”

“…When an egress LSR recognizes the LSP attributes object and the Non-PHP behaviour flag in the Attribute Flags TLV, it must allocate a non-Null local label to that LSP. The OOB mapping flag is used by the ingress LSR to signal to the egress LSR that the binding of an RSVP-TE LSP to an application and payload identifier is being signalled out of band [74].…”

Resource Reservation Protocol (RSVP) Message Formats for Label Switched Path (LSP) Attributes Objects

“…RFC5420], but not this document, will interpret the first LSP Attributes object present in a received message, which is formatted as described in this document, as representing LSP operational status rather than S2L sub-LSP status. It is unclear if this is a significant issue as the LSP Attributes object is currently considered to be an unsuitable mechanism for reporting operational status of P2MP LSPs, for example, see Section 2.1 of [RFC6511]. The intent of this document is to correct this limitation; it is expected that networks that wish to make use of such operational reporting will deploy this extension.…”

“…Unmodified formats are not listed. An example of a case where the modified formats are applicable is described in [RFC6511].…”