RFC 4271: A Border Gateway Protocol 4 (BGP-4)

This document discusses the Border Gateway Protocol (BGP), which is an inter-Autonomous System routing protocol. The primary function of a BGP speaking system…

Read RFC 4271 on the RFC Editor

Outgoing relationships (22 related RFCs)

Obsoletes, Informative reference — RFC 1771: A Border Gateway Protocol 4 (BGP-4)
Informative reference — RFC 2474: Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers
Informative reference — RFC 1519: Classless Inter-Domain Routing (CIDR): an Address Assignment and Aggregation Strategy
Informative reference — RFC 4272: BGP Security Vulnerabilities Analysis
Informative reference — RFC 1997: BGP Communities Attribute
Informative reference — RFC 904: Exterior Gateway Protocol formal specification
Informative reference — RFC 1930: Guidelines for creation, selection, and registration of an Autonomous System (AS)
Informative reference — RFC 1267: Border Gateway Protocol 3 (BGP-3)
Informative reference — RFC 2439: BGP Route Flap Damping
Informative reference — RFC 1518: An Architecture for IP Address Allocation with CIDR
Informative reference — RFC 2858: Multiprotocol Extensions for BGP-4
Informative reference — RFC 4020: Early IANA Allocation of Standards Track Code Points
Informative reference — RFC 1092: EGP and policy based routing in the new NSFNET backbone
Informative reference — RFC 1772: Application of the Border Gateway Protocol in the Internet
Informative reference — RFC 1093: NSFNET routing architecture
Informative reference — RFC 3065: Autonomous System Confederations for BGP
Informative reference — RFC 3562: Key Management Considerations for the TCP MD5 Signature Option
Informative reference — RFC 2918: Route Refresh Capability for BGP-4
Informative reference — RFC 1163: Border Gateway Protocol (BGP)
Informative reference — RFC 2796: BGP Route Reflection - An Alternative to Full Mesh IBGP
Informative reference — RFC 1105: Border Gateway Protocol (BGP)
Informative reference — RFC 3392: Capabilities Advertisement with BGP-4

Incoming relationships (160 related RFCs)

Showing 50 of 160 related RFCs.

Updated by, Normatively referenced by — RFC 7606: Revised Error Handling for BGP UPDATE Messages
Updated by, Normatively referenced by — RFC 6793: BGP Support for Four-Octet Autonomous System (AS) Number Space
Updated by, Normatively referenced by — RFC 4724: Graceful Restart Mechanism for BGP
Updated by, Normatively referenced by — RFC 6286: Autonomous-System-Wide Unique BGP Identifier for BGP-4
Updated by, Normatively referenced by — RFC 7705: Autonomous System Migration Mechanisms and Their Effects on the BGP AS_PATH Attribute
Updated by — RFC 7607: Codification of AS 0 Processing
Updated by, Normatively referenced by — RFC 8212: Default External BGP (EBGP) Route Propagation Behavior without Policies
Updated by — RFC 8654: Extended Message Support for BGP
Updated by, Normatively referenced by — RFC 6608: Subcodes for BGP Finite State Machine Error
Updated by — RFC 9072: Extended Optional Parameters Length for BGP OPEN Message
Updated by, Normatively referenced by — RFC 9687: Border Gateway Protocol 4 (BGP-4) Send Hold Timer
Updated by, Normatively referenced by — RFC 9774: Deprecation of AS_SET and AS_CONFED_SET in BGP
Normatively referenced by — RFC 5925: The TCP Authentication Option
Normatively referenced by — RFC 4379: Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures
Normatively referenced by — RFC 7432: BGP MPLS-Based Ethernet VPN
Normatively referenced by — RFC 4732: Internet Denial-of-Service Considerations
Normatively referenced by — RFC 6514: BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs
Normatively referenced by — RFC 4272: BGP Security Vulnerabilities Analysis
Normatively referenced by — RFC 4360: BGP Extended Communities Attribute
Normatively referenced by — RFC 7752: North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP
Normatively referenced by — RFC 8029: Detecting Multiprotocol Label Switched (MPLS) Data-Plane Failures
Normatively referenced by — RFC 4456: BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP)
Normatively referenced by — RFC 6811: BGP Prefix Origin Validation
Normatively referenced by — RFC 9012: The BGP Tunnel Encapsulation Attribute
Normatively referenced by — RFC 4684: Constrained Route Distribution for Border Gateway Protocol/MultiProtocol Label Switching (BGP/MPLS) Internet Protocol (IP) Virtual Private Networks (VPNs)
Normatively referenced by — RFC 5065: Autonomous System Confederations for BGP
Normatively referenced by — RFC 6836: Locator/ID Separation Protocol Alternative Logical Topology (LISP+ALT)
Normatively referenced by — RFC 8205: BGPsec Protocol Specification
Normatively referenced by — RFC 6039: Issues with Existing Cryptographic Protection Methods for Routing Protocols
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 9552: Distribution of Link-State and Traffic Engineering Information Using BGP
Normatively referenced by — RFC 5512: The BGP Encapsulation Subsequent Address Family Identifier (SAFI) and the BGP Tunnel Encapsulation Attribute
Normatively referenced by — RFC 8669: Segment Routing Prefix Segment Identifier Extensions for BGP
Normatively referenced by — RFC 5492: Capabilities Advertisement with BGP-4
Normatively referenced by — RFC 7454: BGP Operations and Security
Normatively referenced by — RFC 5575: Dissemination of Flow Specification Rules
Normatively referenced by — RFC 5701: IPv6 Address Specific BGP Extended Community Attribute
Normatively referenced by — RFC 9252: BGP Overlay Services Based on Segment Routing over IPv6 (SRv6)
Normatively referenced by — RFC 7947: Internet Exchange BGP Route Server
Normatively referenced by — RFC 9830: Advertising Segment Routing Policies in BGP
Normatively referenced by — RFC 5291: Outbound Route Filtering Capability for BGP-4
Normatively referenced by — RFC 5566: BGP IPsec Tunnel Encapsulation Attribute
Normatively referenced by — RFC 6483: Validation of Route Origination Using the Resource Certificate Public Key Infrastructure (PKI) and Route Origin Authorizations (ROAs)
Normatively referenced by — RFC 6996: Autonomous System (AS) Reservation for Private Use
Normatively referenced by — RFC 8209: A Profile for BGPsec Router Certificates, Certificate Revocation Lists, and Certification Requests
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 4273: Definitions of Managed Objects for BGP-4
Normatively referenced by — RFC 4781: Graceful Restart Mechanism for BGP with MPLS