OSPFv3 as a PE-CE routing protocol
draft-pillay-esnault-moyer-ospfv3-pece-00

Document Type Replaced Internet-Draft (individual)
Last updated 2011-11-09 (latest revision 2008-07-07)
Replaced by draft-ietf-l3vpn-ospfv3-pece
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 Replaced by draft-ietf-l3vpn-ospfv3-pece
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-pillay-esnault-moyer-ospfv3-pece-00.txt

Abstract

Many Service Providers (SPs) offer the Virtual Private Network (VPN) services to their customers, using a technique in which Customer Edge (CE) routers are routing peers of Provider Edge (PE) routers. The Border Gateway Protocol (BGP) is used to distribute the customer's routes across the provider's IP backbone network, and Multiprotocol Label Switching (MPLS) is used to tunnel customer packets across the provider's backbone. This is known as a "BGP/MPLS IP VPN". Originally only IPv4 was supported and it was later extended to support IPv6 VPNs as well. Extensions were later added for the support of the Open Shortest Path First protocol version 2 (OSPFv2) as a PE-CE routing protocol for the IPv4 VPNs. This document extends those specifications to support OSPF version 3 (OSPFv3) as a PE-CE routing protocol. The OSPFv3 PE-CE functionality is identical to that of OSPFv2 except for the differences described in this document.

Authors

Padma Pillay-Esnault (ppe@cisco.com)
Peter Moyer (pete@juniper.net)
Jeff Doyle (jdoyle@doyleassociates.net)
Emre Ertekin (ertekin_emre@bah.com)
Michael Lundberg (lundberg_michael@bah.com)

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