BGP/IP VPNs: BGP and CE-Based Virtual Private Networks
draft-berger-l3vpn-ip-tunnels-01

Document Type Expired Internet-Draft (individual)
Last updated 2007-10-24
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-berger-l3vpn-ip-tunnels-01.txt

Abstract

This memo describes a routing architecture that is most applicable to Customer Edge (CE)-based Virtual Private Networks (VPNs). In this architecture, customer devices use BGP to exchange VPN routes with one another. The BGP UPDATES include a new attribute that identifies the endpoint of a tunnel that can be used to reach a particular VPN prefix. The encapsulation strategy described in this memo is more flexible than that described in RFC 4364. In this architecture, the edge router can encapsulate the original datagram twice, as in RFC 4364. In this case, the inner header provides VPN context and the outer header identifies the tunnel between edge routers. Alternatively, the edge router can encapsulate the original datagram only once, with the tunnel providing both VPN context and identifying a tunnel to the remote edge router.Contents

Authors

Lou Berger (lberger@labn.net)
Ron Bonica (rbonica@juniper.net)
Russ White (riw@cisco.com)

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