Node behavior upon originating and receiving Resource ReserVation Protocol (RSVP) Path Error message
draft-vasseur-mpls-3209-patherr-01
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Author | Vasseur Jp | ||
| Last updated | 2010-01-05 (latest revision 2006-10-22) | ||
| Replaced by | RFC 5711 | ||
| Stream | (None) | ||
| Intended RFC status | (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 | Replaced by draft-ietf-mpls-3209-patherr | |
| 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-vasseur-mpls-3209-patherr-01.txt
https://www.ietf.org/archive/id/draft-vasseur-mpls-3209-patherr-01.txt
Abstract
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).
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)