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 (all versions)
- BIRD (version 2.0.1 and higher)
- OpenBGPD (OpenBSD 6.4 and higher)
- Nokia SR OS (19.5.R1 or higher)
- FRRouting (7.4 or higher)
Non-compliant BGP implementations
- Arista EOS 1
- Cisco IOS (classic)
- Cisco IOS-XE
- Cisco NX-OS
- Juniper Junos 2
- Quagga
- FRRouting (7.0 to 7.3) 3
- Extreme IronWare (6.3.0a and earlier)
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: Adam Chappell wrote a RFC 8212 SLAX script to side-load a RFC 8212 shim on Junos devices.
3: FRRouting (7.0+) allows you to emulate RFC 8212 behaviour by configuring the below, however this is not the default as of yet:
router bgp XXX
bgp ebgp-require-policy
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent