Graceful Restart Mechanism for BGP with MPLS
draft-rekhter-bgp-mpls-restart-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Yakov Rekhter , Rahul Aggarwal | ||
| Last updated | 2001-10-22 | ||
| 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
[1] describes a mechanism for BGP that would help minimize the negative effects on routing caused by BGP restart. This document extends this mechanism to also minimize the negative effects on MPLS forwarding when BGP is used to carry MPLS labels [2]. The mechanism described in this document is agnostic with respect to the types of the addresses carried in the BGP NLRI. As such it works in conjunction with any of the address famililies that could be carried in BGP (e.g., IPv4, IPv6, etc...)
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)