RFC 4272: BGP Security Vulnerabilities Analysis

Border Gateway Protocol 4 (BGP-4), along with a host of other infrastructure protocols designed before the Internet environment became perilous, was…

Read RFC 4272 on the RFC Editor

Outgoing relationships (5 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 4271: A Border Gateway Protocol 4 (BGP-4)
Normative reference — RFC 2385: Protection of BGP Sessions via the TCP MD5 Signature Option
Informative reference — RFC 2401: Security Architecture for the Internet Protocol
Informative reference — RFC 2725: Routing Policy System Security

Incoming relationships (31 related RFCs)

Normatively referenced by — RFC 7313: Enhanced Route Refresh Capability for BGP-4
Normatively referenced by — RFC 8821: PCE-Based Traffic Engineering (TE) in Native IP Networks
Normatively referenced by — RFC 9723: BGP Colored Prefix Routing (CPR) for Services Based on Segment Routing over IPv6 (SRv6)
Normatively referenced by — RFC 9832: BGP Classful Transport Planes
Informatively referenced by — RFC 4271: A Border Gateway Protocol 4 (BGP-4)
Informatively referenced by — RFC 7432: BGP MPLS-Based Ethernet VPN
Informatively referenced by — RFC 6514: BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs
Informatively referenced by — RFC 7752: North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP
Informatively referenced by — RFC 9012: The BGP Tunnel Encapsulation Attribute
Informatively referenced by — RFC 8365: A Network Virtualization Overlay Solution Using Ethernet VPN (EVPN)
Informatively referenced by — RFC 5065: Autonomous System Confederations for BGP
Informatively referenced by — RFC 9552: Distribution of Link-State and Traffic Engineering Information Using BGP
Informatively referenced by — RFC 5492: Capabilities Advertisement with BGP-4
Informatively referenced by — RFC 9252: BGP Overlay Services Based on Segment Routing over IPv6 (SRv6)
Informatively referenced by — RFC 9830: Advertising Segment Routing Policies in BGP
Informatively referenced by — RFC 5566: BGP IPsec Tunnel Encapsulation Attribute
Informatively referenced by — RFC 6996: Autonomous System (AS) Reservation for Private Use
Informatively referenced by — RFC 7132: Threat Model for BGP Path Security
Informatively referenced by — RFC 8209: A Profile for BGPsec Router Certificates, Certificate Revocation Lists, and Certification Requests
Informatively referenced by — RFC 8814: Signaling Maximum SID Depth (MSD) Using the Border Gateway Protocol - Link State
Informatively referenced by — RFC 8950: Advertising IPv4 Network Layer Reachability Information (NLRI) with an IPv6 Next Hop
Informatively referenced by — RFC 6396: Multi-Threaded Routing Toolkit (MRT) Routing Information Export Format
Informatively referenced by — RFC 6774: Distribution of Diverse BGP Paths
Informatively referenced by — RFC 8097: BGP Prefix Origin Validation State Extended Community
Informatively referenced by — RFC 8212: Default External BGP (EBGP) Route Propagation Behavior without Policies
Informatively referenced by — RFC 9104: Distribution of Traffic Engineering Extended Administrative Groups Using the Border Gateway Protocol - Link State (BGP-LS)
Informatively referenced by — RFC 9469: Applicability of Ethernet Virtual Private Network (EVPN) to Network Virtualization over Layer 3 (NVO3) Networks
Informatively referenced by — RFC 7447: Deprecation of BGP Entropy Label Capability Attribute
Informatively referenced by — RFC 9003: Extended BGP Administrative Shutdown Communication
Informatively referenced by — RFC 9125: Gateway Auto-Discovery and Route Advertisement for Site Interconnection Using Segment Routing
Informatively referenced by — RFC 9871: BGP Color-Aware Routing (CAR)