Node Behavior upon Originating and Receiving Resource Reservation Protocol (RSVP) Path Error Messages, January 2010
- Canonical URL:
- File formats:
- PROPOSED STANDARD
- RFC 3209
- JP. Vasseur, Ed.
- mpls (rtg)
Discuss this RFC: Send questions or comments to email@example.com
The aim of this document is to describe a common practice with regard to the behavior of nodes that send and receive a Resource Reservation Protocol (RSVP) Traffic Engineering (TE) Path Error messages for a preempted Multiprotocol Label Switching (MPLS) or Generalized MPLS (GMPLS) Traffic Engineering Label Switched Path (TE LSP). (For reference to the notion of TE LSP preemption, see RFC 3209.) This document does not define any new protocol extensions. [STANDARDS-TRACK]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 4844.