Signaling Tunnel Identifiers and Capabilities in BGP
draft-raggarwa-l3vpn-tunnel-attribute-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Rahul Aggarwal | ||
| Last updated | 2005-10-19 | ||
| 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 document proposes a mechanism that allows a router to signal the identifiers of IP/MPLS Tunnels, for which it is the headend, using Border Gateway Protocol (BGP). One application of this mechanism is multicast in BGP - Multi-Protocol-Label Switching (MPLS) Virtual Private Networks (VPNs). This document also proposes a mechanism that allows a router to signal its tunnel enapsulation/decapsulation capabilities using BGP. One application of this is signaling MPLS upstream label assignment capability when BGP is used to advertise MPLS upstream assigned labels.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)