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

This document describes a method by which a Service Provider may use an IP backbone to provide IP Virtual Private Networks (VPNs) for its customers. This…

Read RFC 4364 on the RFC Editor

Outgoing relationships (1 related RFC)

Obsoletes — RFC 2547: BGP/MPLS VPNs

Incoming relationships (95 related RFCs)

Showing 50 of 95 related RFCs.

Updated by, Normatively referenced by — RFC 5462: Multiprotocol Label Switching (MPLS) Label Stack Entry: "EXP" Field Renamed to "Traffic Class" Field
Updated by, Normatively referenced by — RFC 4684: Constrained Route Distribution for Border Gateway Protocol/MultiProtocol Label Switching (BGP/MPLS) Internet Protocol (IP) Virtual Private Networks (VPNs)
Updated by — RFC 4577: OSPF as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs)
Normatively referenced by — RFC 5920: Security Framework for MPLS and GMPLS Networks
Normatively referenced by — RFC 7432: BGP MPLS-Based Ethernet VPN
Normatively referenced by — RFC 6513: Multicast in MPLS/BGP IP VPNs
Normatively referenced by — RFC 6514: BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs
Normatively referenced by — RFC 4761: Virtual Private LAN Service (VPLS) Using BGP for Auto-Discovery and Signaling
Normatively referenced by — RFC 6073: Segmented Pseudowire
Normatively referenced by — RFC 6074: Provisioning, Auto-Discovery, and Signaling in Layer 2 Virtual Private Networks (L2VPNs)
Normatively referenced by — RFC 7855: Source Packet Routing in Networking (SPRING) Problem Statement and Requirements
Normatively referenced by — RFC 8299: YANG Data Model for L3VPN Service Delivery
Normatively referenced by — RFC 8955: Dissemination of Flow Specification Rules
Normatively referenced by — RFC 9182: A YANG Network Data Model for Layer 3 VPNs
Normatively referenced by — RFC 8669: Segment Routing Prefix Segment Identifier Extensions for BGP
Normatively referenced by — RFC 6625: Wildcards in Multicast VPN Auto-Discovery Routes
Normatively referenced by — RFC 6565: OSPFv3 as a Provider Edge to Customer Edge (PE-CE) Routing Protocol
Normatively referenced by — RFC 9251: Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Proxies for Ethernet VPN (EVPN)
Normatively referenced by — RFC 5575: Dissemination of Flow Specification Rules
Normatively referenced by — RFC 6624: Layer 2 Virtual Private Networks Using BGP for Auto-Discovery and Signaling
Normatively referenced by — RFC 9135: Integrated Routing and Bridging in Ethernet VPN (EVPN)
Normatively referenced by — RFC 9252: BGP Overlay Services Based on Segment Routing over IPv6 (SRv6)
Normatively referenced by — RFC 5549: Advertising IPv4 Network Layer Reachability Information with an IPv6 Next Hop
Normatively referenced by — RFC 9181: A Common YANG Data Model for Layer 2 and Layer 3 VPNs
Normatively referenced by — RFC 4381: Analysis of the Security of BGP/MPLS IP Virtual Private Networks (VPNs)
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 6037: Cisco Systems' Solution for Multicast in BGP/MPLS IP VPNs
Normatively referenced by — RFC 7716: Global Table Multicast with BGP Multicast VPN (BGP-MVPN) Procedures
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 8950: Advertising IPv4 Network Layer Reachability Information (NLRI) with an IPv6 Next Hop
Normatively referenced by — RFC 9168: Path Computation Element Communication Protocol (PCEP) Extension for Flow Specification
Normatively referenced by — RFC 6512: Using Multipoint LDP When the Backbone Has No Route to the Root
Normatively referenced by — RFC 7582: Multicast Virtual Private Network (MVPN): Using Bidirectional P-Tunnels
Normatively referenced by — RFC 8049: YANG Data Model for L3VPN Service Delivery
Normatively referenced by — RFC 5824: Requirements for Supporting Customer Resource ReSerVation Protocol (RSVP) and RSVP Traffic Engineering (RSVP-TE) over a BGP/MPLS IP-VPN
Normatively referenced by — RFC 6674: Gateway-Initiated Dual-Stack Lite Deployment
Normatively referenced by — RFC 7814: Virtual Subnet: A BGP/MPLS IP VPN-Based Subnet Extension Solution
Normatively referenced by — RFC 6198: Requirements for the Graceful Shutdown of BGP Sessions
Normatively referenced by — RFC 7257: Virtual Private LAN Service (VPLS) Management Information Base
Normatively referenced by — RFC 7611: BGP ACCEPT_OWN Community Attribute
Normatively referenced by — RFC 7789: Impact of BGP Filtering on Inter-Domain Routing Policies
Normatively referenced by — RFC 9832: BGP Classful Transport Planes
Normatively referenced by — RFC 9889: A Realization of Network Slices for 5G Networks Using Current IP/MPLS Technologies
Informatively referenced by — RFC 4762: Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling
Informatively referenced by — RFC 4360: BGP Extended Communities Attribute
Informatively referenced by — RFC 7752: North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP
Informatively referenced by — RFC 5921: A Framework for MPLS in Transport Networks
Informatively referenced by — RFC 5884: Bidirectional Forwarding Detection (BFD) for MPLS Label Switched Paths (LSPs)
Informatively referenced by — RFC 5102: Information Model for IP Flow Information Export