bgp / rfc8212

RFC 8212 - Default EBGP Route Propagation Behavior Without Policies

RFC 8212 compliance tracking

RFC 8212 updates the core BGP specification (RFC 4271) by defining the default behavior of a BGP speaker when there is no Import or Export Policy associated with an External BGP session.

Contributions

If you observe a mistake on this page or if you can contribute an update, please file a pull-request or email [email protected]. If you can include version numbers or point to public documentation that would be ideal.

Compliant BGP implementations

• Cisco IOS XR
• BIRD (version 2.0.1 and higher)
• OpenBGPD (OpenBSD 6.4 and higher)
• Nokia SR Linux (19.11.R1 and higher)
• Nokia SR OS (19.5.R1 and higher)
• FRRouting (7.4 and higher)
• Bio routing / bio-rd
• freeRouter (22.4.1 and higher)

Non-compliant BGP implementations

• Arista EOS ¹
• Cisco IOS (classic) / NX-OS
• Cisco IOS XE ²
• Juniper Junos ³
• Quagga
• Extreme IronWare
• Huawei VRP

Footnotes

1: Arista EOS 4.18.0f allow you to emulate RFC 8212 behaviour by configuring the below, however this is not the default as of yet:

bgp missing-policy direction in action deny
bgp missing-policy direction out action deny

2: IOS XE 17.2.1 allow you to emulate RFC 8212 behaviour by configuring the below, however this is not the default as of yet:

bgp safe-ebgp-policy

3: Junos 20.3R1 allows to set `defaults ebgp no-policy` at the `[edit protocols bgp]` hierarchy level, more information here.
Adam Chappell wrote a RFC 8212 SLAX script to side-load a RFC 8212 shim on Junos devices.

rfc8212's Issues

FRR is no longer RFC8212-compliant out of the box

Recent FRR release (I tested 8.4.0) support traditional and datacenter profiles. The traditional profile is RFC8212-compliant, the datacenter one is not (it would make EBGP-only data center fabrics way less attractive). Unfortunately, the default profile seems to be datacenter, which makes FRR no longer RFC8212-compliant in its default setup (at least as shipped in a Docker container)