RFC 4577: OSPF as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs)
In plain English — editorial summary, not part of the RFC
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. This document updates RFC 4364. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4577
- Published
- June 2006
- Authors
- E. Rosen; P. Psenak; P. Pillay-Esnault
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 25
- Also known as
- —
- Updates:
- RFC 4364
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5038The Label Distribution Protocol (LDP) Implementation Survey ResultsCurrent
October 2007
- RFC 3815Definitions of Managed Objects for the Multiprotocol Label Switching (MPLS), Label Distribution Protocol (LDP)Current
June 2004
- RFC 3814Multiprotocol Label Switching (MPLS) Forwarding Equivalence Class To Next Hop Label Forwarding Entry (FEC-To-NHLFE) Management Information Base (MIB)Current
June 2004
- RFC 3812Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB)Current
June 2004
- RFC 3811Definitions of Textual Conventions (TCs) for Multiprotocol Label Switching (MPLS) ManagementUpdated
June 2004
- RFC 5392OSPF Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic EngineeringCurrent
January 2009
- RFC 3612Applicability Statement for Restart Mechanisms for the Label Distribution Protocol (LDP)Current
September 2003
- RFC 3480Signalling Unnumbered Links in CR-LDP (Constraint-Routing Label Distribution Protocol)Current
February 2003
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?