datatracker.ietf.org
Sign In
Version 4.50, 2013-05-15
Report a bug

OSPF as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs)
draft-ietf-l3vpn-ospf-2547-06

RFC
Document Stream: IETF
Last updated: 2006-02-17
Intended RFC status: Proposed Standard
Other versions: (expired, archived): plain text, pdf, html

Document shepherd:(None)
Shepherd writeup
Consensus:Unknown

IESG State: RFC 4577
Responsible AD: Mark Townsley
Send notices to: rick@rhwilder.net, rcallon@juniper.net, rbonica@juniper.net, erosen@cisco.com, ppsenak@cisco.com, padma@juniper.net

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-ietf-l3vpn-ospf-2547.

Abstract:
Many Service Providers offer Virtual Private Network (VPN) services to their customers, using a technique in which customer edge routers (CE routers) are routing peers of provider edge routers (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". The base specification for BGP/MPLS IP VPNs presumes that the routing protocol on the interface between a PE router and a CE router is BGP. This document extends that specification by allowing the routing protocol on the PE/CE interface to be the Open Shortest Path First (OSPF) protocol.

Authors:
Padma Pillay-Esnault <ppe@cisco.com>
Eric Rosen <erosen@cisco.com>
Peter Psenak <ppsenak@cisco.com>

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