Extensions to RSVP-TE for LSP Instant Install
draft-saad-mpls-lsp-instant-install-rsvpte-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Tarek Saad , George Swallow | ||
| Last updated | 2016-04-21 (Latest revision 2015-10-19) | ||
| Replaces | draft-saad-lsp-instant-install-rsvpte | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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 establishing new RSVP-TE LSPs, it is permissible that LSRs along the LSP path to forward the RSVP Resv message upstream before installing the forwarding state. In practise, this is done to parallelize the forwarding state installation. While the ingress can start to use the LSP as soon as the RSVP Resv message arrives, doing so may lead to traffic drops at intermediate LSRs that may not have completed the installation of forwarding state for the new LSP. This document describes procedures and provides extensions to RSVP-TE protocol to allow an ingress LSR to immediately install and forward traffic on a newly signalled LSP as soon as the RSVP reservation state is received.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)