BGP/VPN: VPN Information Discovery for Network-based VPNs
draft-ouldbrahim-bgp-vpn-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Hamid H. Ould-Brahim , Gregory Wright , Bryan Gleeson | ||
| Last updated | 2000-07-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
VPN information can be piggybacked into BGP to allow a network-based VPN to auto-discover its membership and adequate information needed before any data exchange between private sites takes place across the backbone. Other drafts (e.g.[VPN-RFC2547]) also piggyback VPN information onto the backbone instance of BGP. However, [VPN- RFC2547] implicitly allows only for a single reachability mechanism (also BGP piggybacking) and a single tunneling mechanism (MPLS). This draft allows for the explicit indication of the reachability modes supported (e.g. piggybacking or virtual router) and the tunneling mechanisms supported, by a VPN device. The purpose of this draft is to define a common VPN information protocol that can be used for both piggybacking and virtual router schemes. It allows for the auto-discovery of the nodes in a particular VPN, the selection of the reachability mechanism to use, and the selection of the tunneling protocol to use.
Authors
Hamid H. Ould-Brahim
Gregory Wright
Bryan Gleeson
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)