LDP/CR-LDP Session Reestablishment -- I'll Be Back
draft-matthews-mpls-ldp-ibb-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Philip Matthews | ||
| Last updated | 2000-02-23 | ||
| 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
This contribution proposes modifications to the LDP and CR-LDP protocols that allow an LDP or CR-LDP session to be reestablished using a new TCP connection if the old TCP connection goes down unexpectedly. It also proposes that, in certain situations, an LSR continue to use the label bindings associated with a session for a short time after the session goes down, to allow forwarding to continue uninterrupted while the two peer LSRs attempt to reestablish the session. These modifications allow an LSR to easily implement hitless software upgrades and hitless activity switches.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)