LSP Self-Ping
draft-bonica-mpls-self-ping-06
| Document | Type |
Replaced Internet-Draft
(mpls WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Raveendra Torvi , Ron Bonica , Ina Minei , Michael Conn , Dante Pacella , Luis Tomotaki , Mark Wygant | ||
| Last updated | 2015-10-14 (Latest revision 2015-05-18) | ||
| Replaced by | RFC 7746 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | Loa Andersson | ||
| IESG | IESG state | Replaced by draft-ietf-mpls-self-ping | |
| Consensus boilerplate | Unknown | ||
| 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:
Abstract
When certain RSVP-TE optimizations are implemented, ingress LSRs can receive RSVP RESV messages before forwarding state has been installed on all downstream nodes. According to the RSVP-TE specification, the ingress LSR can forward traffic through an LSP as soon as it receives a RESV message. However, if the ingress LSR forwards traffic through the LSP before forwarding state has been installed on all downstream nodes, traffic can be lost. This memo describes LSP Self-ping. When an ingress LSR receives an RESV message, it can invoke LSP Self-ping procedures to ensure that forwarding state has been installed on all downstream nodes. LSP Self-ping is an extremely light-weight mechanism. It does not consume control plane resources on transit or egress LSRs.
Authors
Raveendra Torvi
Ron Bonica
Ina Minei
Michael Conn
Dante Pacella
Luis Tomotaki
Mark Wygant
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)