Using BGP as an Auto-Discovery Mechanism for VR-based Layer-3 VPNs
draft-ietf-l3vpn-bgpvpn-auto-09

 
Document
Type Withdrawn by IETF Internet-Draft (l3vpn WG)
Last updated 2007-05-07 (latest revision 2007-04-25)
Stream IETF
Intended RFC status Informational
Formats
Expired & archived
plain text pdf html
Stream
WG state WG Document
Document shepherd No shepherd assigned
IESG
IESG state Withdrawn by IETF (IESG: Dead)
Telechat date
Responsible AD Mark Townsley
Send notices to rick@rhwilder.net, rcallon@juniper.net, rbonica@juniper.net, ananth@juniper.net, suzuki.muneyoshi@lab.ntt.co.jp, j.sumimoto@ntt.com, bensons@savvis.net

Email authors IPR References Referenced by Nits Search lists

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
//www.ietf.org/archive/id/draft-ietf-l3vpn-bgpvpn-auto-09.txt

Abstract

In any provider-based VPN scheme, the Provider Edge (PE) devices attached to a common VPN must exchange certain information as a prerequisite to establish VPN-specific connectivity. The main purpose of an auto-discovery mechanism is to enable a PE to dynamically discover the set of remote PEs having VPN members in common. The auto-discovery mechanism proceeds by having a PE advertises to other PEs, at a minimum, its own IP address and the list of VPN members configured on that PE. Once that information is received the remote PEs will then identify the list of VPN sites members of the same VPN, and use the information carried within the discovery mechanism to establish VPN connectivity. This draft defines a BGP based auto-discovery mechanism for Virtual Router-based layer-3 VPNs. This mechanism is based on the approach used by BGP/MPLS-IP-VPN for distributing VPN routing information within the service provider(s).

Authors

Hamid Ould-Brahim (hbrahim@nortel.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)