Your browser failed to load CSS style sheets. Your browser or web proxy might not support elliptic-curve TLS

Building network automation solutions

9 module online course

Start now!
back to overview

RFC 8212: Bringing Sane Defaults to EBGP

It’s amazing how long it can take to get some sanity into networking technologies. RFC 8212 specifies that a BGP router should not announce prefixes over EBGP until its routing policy has been explicitly configured. It took us only 22 years to get there…

For more technical details, read this email by Job Snijders.

Please read our Blog Commenting Policy before writing a comment.


  1. And now for all the purchasing departments: require support of this RFC in your next router to prevent operational accidents. Vendors need customer input/demands to justify implementation.

  2. Let's make a list of all the protocols with their ridiculous defaults now. So many!

  3. Vladimir Troitskiy09 August, 2017 07:28

    BGP route leaks are quite popular nowadays...

    1. This seems to be another awesome step in the right direction (yet again, at least a decade too late).

  4. The problem is not having sane defaults or not. Your definition of sane might not be the same as mine. The problem is lack of consistency, which leads to operational mistakes.

    1. I guess our definition of "sane" is very similar (although reading various IETF mailing lists one starts to wonder...). The definition of "defaults I want to fit my needs" obviously varies.

      How about rephrasing "sane" as "something that will do the least damage in the hands of clueless people randomly playing google-and-paste game on their edge routers" ;)


Constructive courteous comments are most welcome. Anonymous trolling will be removed with prejudice.