RFC 6565: OSPFv3 as a Provider Edge to Customer Edge (PE-CE) Routing Protocol

Many Service Providers (SPs) offer Virtual Private Network (VPN) services to their customers using a technique in which Customer Edge (CE) routers are routing…

Read RFC 6565 on the RFC Editor

Outgoing relationships (11 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 2328: OSPF Version 2
Normative reference — RFC 4364: BGP/MPLS IP Virtual Private Networks (VPNs)
Normative reference — RFC 5340: OSPF for IPv6
Normative reference — RFC 4760: Multiprotocol Extensions for BGP-4
Normative reference — RFC 4360: BGP Extended Communities Attribute
Normative reference — RFC 4659: BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPN
Normative reference — RFC 4577: OSPF as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs)
Normative reference — RFC 5838: Support of Address Families in OSPFv3
Normative reference — RFC 4576: Using a Link State Advertisement (LSA) Options Bit to Prevent Looping in BGP/MPLS IP Virtual Private Networks (VPNs)
Informative reference — RFC 2547: BGP/MPLS VPNs

Incoming relationships (7 related RFCs)

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 9129: YANG Data Model for the OSPF Protocol
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
Informatively referenced by — RFC 9181: A Common YANG Data Model for Layer 2 and Layer 3 VPNs