Supported Standards for BGP

Junos OS substantially supports the following RFCs and Internet drafts, which define standards for IP version 4 (IPv4) BGP.

For a list of supported IP version 6 (IPv6) BGP standards, see Supported IPv6 Standards.

Junos OS BGP supports authentication for protocol exchanges (MD5 authentication).

• RFC 1745, BGP4/IDRP for IP—OSPF Interaction

• RFC 1772, Application of the Border Gateway Protocol in the Internet

• RFC 1997, BGP Communities Attribute

• RFC 2283, Multiprotocol Extensions for BGP-4

• RFC 2385, Protection of BGP Sessions via the TCP MD5 Signature Option

• RFC 2439, BGP Route Flap Damping

• RFC 2545, Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain Routing

• RFC 2796, BGP Route Reflection – An Alternative to Full Mesh IBGP

• RFC 2858, Multiprotocol Extensions for BGP-4

• RFC 2918, Route Refresh Capability for BGP-4

• RFC 3065, Autonomous System Confederations for BGP

• RFC 3107, Carrying Label Information in BGP-4

• RFC 3345, Border Gateway Protocol (BGP) Persistent Route Oscillation Condition

• RFC 3392, Capabilities Advertisement with BGP-4

• RFC 4271, A Border Gateway Protocol 4 (BGP-4)

• RFC 4273, Definitions of Managed Objects for BGP-4

• RFC 4360, BGP Extended Communities Attribute

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

• RFC 4456, BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP)

• RFC 4486, Subcodes for BGP Cease Notification Message

• RFC 4576, Using a Link State Advertisement (LSA) Options Bit to Prevent Looping in BGP/MPLS IP Virtual Private Networks (VPNs)

• RFC 4659, BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPN

• RFC 4632, Classless Inter-domain Routing (CIDR): The Internet Address Assignment and Aggregation Plan

• RFC 4684, Constrained Route Distribution for Border Gateway Protocol/MultiProtocol Label Switching (BGP/MPLS) Internet Protocol (IP) Virtual Private Networks (VPNs)

• RFC 4724, Graceful Restart Mechanism for BGP

• RFC 4760, Multiprotocol Extensions for BGP-4

• RFC 4781, Graceful Restart Mechanism for BGP with MPLS

• RFC 4798, Connecting IPv6 Islands over IPv4 MPLS Using IPv6 Provider Edge Routers (6PE)

  Option 4b (eBGP redistribution of labeled IPv6 routes from AS to neighboring AS) is not supported.

• RFC 4893, BGP Support for Four-octet AS Number Space

• RFC 5004, Avoid BGP Best Path Transitions from One External to Another

• RFC 5065, Autonomous System Confederations for BGP

• RFC 5082, The Generalized TTL Security Mechanism (GTSM)

• RFC 5291, Outbound Route Filtering Capability for BGP-4 (partial support)

• RFC 5292, Address-Prefix-Based Outbound Route Filter for BGP-4 (partial support)

  Devices running Junos OS can receive prefix-based ORF messages.

• RFC 5396, Textual Representation of Autonomous System (AS) Numbers

• RFC 5492, Capabilities Advertisement with BGP-4

• RFC 5512, The BGP Encapsulation Subsequent Address Family Identifier (SAFI) and the BGP Tunnel Encapsulation Attribute

• RFC 5549, Advertising IPv4 Network Layer Reachability Information with an IPv6 Next Hop

• RFC 5575, Dissemination of flow specification rules. Covers RFC 8955 and RFC 8956.

  RFC-8955 - Provides a Border Gateway Protocol Network Layer Reachability Information (BGP NLRI) encoding format that can be used to distribute (intra-domain and inter-domain) traffic flow specifications for IPv4 unicast and IPv4 BGP/MPLS VPN services.

  RFC8956 - Provides a Border Gateway Protocol (BGP) extension for the propagation of traffic flow specifications for the purpose of rate limiting or filtering IPv6 protocol data packets.

• RFC 5668, 4-Octet AS Specific BGP Extended Community

• RFC 5701, IPv6 Address Specific BGP Extended Community Attribute

• RFC 5925, The TCP Authentication Option

• RFC 6286, Autonomous-System-Wide Unique BGP Identifier for BGP-4- fully compliant

• RFC 6368, Internal BGP as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs)

• RFC 6774, Distribution of Diverse BGP Paths

• RFC 6793, BGP Support for Four-Octet Autonomous System (AS) Number Space

• RFC 6810, The Resource Public Key Infrastructure (RPKI) to Router Protocol

• RFC 6811, BGP Prefix Origin Validation

• RFC 6996, Autonomous System (AS) Reservation for Private Use

• RFC 7300, Reservation of Last Autonomous System (AS) Numbers

• RFC 7311, The Accumulated IGP Metric Attribute for BGP

• RFC 7404, Using Only Link-Local Addressing inside an IPv6 Network

• RFC 7432, BGP MPLS-Based Ethernet VPN (eVPN)

• RFC 7606, Revised Error Handling for BGP UPDATE Messages

• RFC 7611, BGP ACCEPT_OWN Community Attribute

  We support the RFC by enabling Juniper routers to accept routes received from a route reflector with the accept-own community value.

• RFC 7752, North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP

• RFC 7854, BGP Monitoring Protocol (BMP)

• RFC 7911, Advertisement of Multiple Paths in BGP

• RFC 8097, BGP Prefix Origin Validation State Extended Community

• RFC 8210, The Resource Public Key Infrastructure (RPKI) to Router Protocol, Version 1

• RFC 8212, Default External BGP (EBGP) Route Propagation Behavior without Policies- fully compliant

  Exceptions:

  The behaviors in RFC 8212 are not implemented by default in order to avoid disruption of existing customer configuration. The default behavior is still kept to accept and advertise all routes with regard to EBGP peers.

• RFC 8277, Using BGP to Bind MPLS Labels to Address Prefixes

• RFC 8326, Graceful BGP session Shutdown

• RFC 8481, Clarifications to BGP Origin Validation Based on Resource Public Key Infrastructure (RPKI)

• RFC 8538, Notification Message Support for BGP Graceful Restart

• RFC 8571, BGP - Link State (BGP-LS) Advertisement of IGP Traffic Engineering Performance Metric Extensions

• RFC 8584, Framework for Ethernet VPN Designated Forwarder Election Extensibility

• RFC 8642, Policy Behavior for Well-Known BGP Communities

• RFC 8669, Segment Routing Prefix Segment Identifier Extensions for BGP

• RFC 8810, Revision to Capability Codes Registration Procedures

• RFC 8814 Signaling Maximum SID Depth (MSD) Using the Border Gateway Protocol - Link State (partial support)

• RFC 8950, Advertising IPv4 Network Layer Reachability Information (NLRI) with an IPv6 Next Hop

• RFC 8955

• RFC 8956

• RFC 9003, Extended BGP Administrative Shutdown Communication

• RFC 9012, The BGP Tunnel Encapsulation Attribute

• RFC 9029, Updates to the Allocation Policy for the Border Gateway Protocol - Link State (BGP-LS) Parameters Registries

• RFC 9069, Support for Local RIB in the BGP Monitoring Protocol (BMP)

• RFC 9085, Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing

• RFC 9117, Revised Validation procedure for Dissemination of BGP Flow Specifications. This enables the Flow Specifications to be originated within the same autonomous system as the BGP peer performing the validation.

• RFC 9384, A BGP Cease NOTIFICATION Subcode for Bidirectional Forwarding Detection (BFD)

• Internet draft draft-idr-rfc8203bis-00, BGP Administrative Shutdown Communication (expires October 2018)

• Internet draft draft-ietf-grow-bmp-adj-rib-out-01, Support for Adj-RIB-Out in BGP Monitoring Protocol (BMP) (expires September 3, 2018)

• Internet draft draft-ietf-idr-aigp-06, The Accumulated IGP Metric Attribute for BGP (expires December 2011)

• Internet draft draft-ietf-idr-as0-06, Codification of AS 0 processing (expires February 2013)

• Internet draft draft-ietf-idr-link-bandwidth-06.txt, BGP Link Bandwidth Extended Community (expires July 2013)

• Internet draft draft-ietf-sidr-origin-validation-signaling-00, BGP Prefix Origin Validation State Extended Community (partial support) (expires May 2011)

  The extended community (origin validation state) is supported in Junos OS routing policy. The specified change in the route selection procedure is not supported.

• Internet draft draft-kato-bgp-ipv6-link-local-00.txt, BGP4+ Peering Using IPv6 Link-local Address

The following RFCs and Internet draft do not define standards, but provide information about BGP and related technologies. The IETF classifies them variously as “Experimental” or “Informational.”

• RFC 1965, Autonomous System Confederations for BGP

• RFC 1966, BGP Route Reflection—An alternative to full mesh IBGP

• RFC 2270, Using a Dedicated AS for Sites Homed to a Single Provider

• RFC 3345, Border Gateway Protocol (BGP) Persistent Route Oscillation Condition

• RFC 3562, Key Management Considerations for the TCP MD5 Signature Option

• Internet draft draft-ietf-ngtrans-bgp-tunnel-04.txt, Connecting IPv6 Islands across IPv4 Clouds with BGP (expires July 2002)