Skip to main content

Node behavior upon originating and receiving Resource ReserVation Protocol (RSVP) Path Error message

Document Type Replaced Internet-Draft (individual)
Expired & archived
Author JP Vasseur
Last updated 2010-01-05 (Latest revision 2006-10-22)
Replaced by draft-ietf-mpls-3209-patherr
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-mpls-3209-patherr
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


The aim of this document is to describe a common practice with regard to the behavior of a node sending a Resource ReserVation Protocol (RSVP) Path Error message and to the behavior of a node receiving an RSVP Path Error message for a particular Multi-Protocol Label Switching - Traffic Engineering (MPLS-TE) Label Switched Path (LSP).


JP Vasseur

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