RFC 4577: OSPF as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs)

Many Service Providers offer Virtual Private Network (VPN) services to their customers, using a technique in which customer edge routers (CE routers) are…

Read RFC 4577 on the RFC Editor

Outgoing relationships (1 related RFC)

Updates — RFC 4364: BGP/MPLS IP Virtual Private Networks (VPNs)

Incoming relationships (11 related RFCs)

Normatively referenced by — RFC 8299: YANG Data Model for L3VPN Service Delivery
Normatively referenced by — RFC 9182: A YANG Network Data Model for Layer 3 VPNs
Normatively referenced by — RFC 9552: Distribution of Link-State and Traffic Engineering Information Using BGP
Normatively referenced by — RFC 6565: OSPFv3 as a Provider Edge to Customer Edge (PE-CE) Routing Protocol
Normatively referenced by — RFC 4576: Using a Link State Advertisement (LSA) Options Bit to Prevent Looping in BGP/MPLS IP Virtual Private Networks (VPNs)
Normatively referenced by — RFC 9834: YANG Data Models for Bearers and Attachment Circuits as a Service (ACaaS)
Normatively referenced by — RFC 9835: A Network YANG Data Model for Attachment Circuits
Normatively referenced by — RFC 9833: A Common YANG Data Model for Attachment Circuits
Normatively referenced by — RFC 8049: YANG Data Model for L3VPN Service Delivery
Informatively referenced by — RFC 9181: A Common YANG Data Model for Layer 2 and Layer 3 VPNs
Informatively referenced by — RFC 8379: OSPF Graceful Link Shutdown