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.

Net neutrality is one of those topics that should never have existed, but of course it inevitably erupts every so often, so here we go…

Not so long ago Robert Graham published his anti-net-neutrality arguments which are (no surprise) not much different from what I wrote when I still cared about this argument (here, here, here and here). While I agree with his overall perspective, I completely disagree with his view of Comcast’s initial response to network congestion.

You wouldn’t believe it – after almost 22 years (yeah, it’s been that long since RFC 1883 was published), IPv6 became an Internet standard (RFC8200/STD86). No wonder some people claim IETF moves at glacial speed ;)

Speaking of IPv6, IETF and glacial speeds – there’s been a hilarious thread before Prague IETF meeting heatedly arguing whether the default WLAN SSID should be IPv6-only (+NAT64). Definitely worth reading (for the entertainment value) over a beer or two.

I’ve added two new case studies to Ansible for Networking Engineers online course:

Create network diagrams from LLDP information playbook focuses on creating a single summary report based on information from numerous devices (and the report just happens to be network diagram in DOT format).

One of the more interesting presentations we had during Tech Field Day Extra @ Cisco Live Berlin was coming from Paessler, a company developing PRTG, a little-known network monitoring software.

More about PRTG in TFD videos and here, here, here and here.

Finally a group of engineers figured out it’s a good idea to make things less complex instead of heaping layers of complexity on top of already-complex kludges.

RFC 8196 specifies default values and extensions to IS-IS that make it a true plug-and-play routing protocol. I wonder when we’ll see it implemented now that everyone is obsessed with intent-based hype.

I got several interesting replies to my automation and orchestration blog post. Some of them were so far in the land of alternate definitions that they were literally off the charts. Here’s one of the best I got in that category:

If you’re not old enough to know otherwise, you’d think (based on recent hype) that we discovered network automation a few years ago. Not true. One of my readers sent me a link to excellent Managing IP Networks with Free Software presentation from NANOG26 (October 2002).

I found the presentation awesome, nothing new, and extremely sad… all at the same time.

One of my readers sent me an email that’s easiest paraphrased into: “Why can’t I have a different IPv6 link-local address (LLA) on every access port connected to a VLAN interface?”

There’s probably nothing stopping someone from implementing such an approach, but it would go against the usual understanding of how bridging and routing interact in L2+L3 switches.

I got tons of questions about the upcoming Building Network Automation Solutions online course. It always starts with the same one:

Is access to the self-study material granted upon enrollment?

Absolutely. You also get access to everything we did in January, and the new self-paced Ansible for Networking Engineers online course.

Have you ever wondered what the difference between automation and orchestration is?

Wikipedia defines automation as use of various control systems for operating equipment. The definition I prefer (because it’s easier to understand in network automation environment) is elimination of well-defined repeatable manual tasks – the emphasis being on well-defined and repeatable.

Another question from someone watching my Designing Active-Active and Disaster Recovery Data Centers webinar (you know, the one where I tell people how to avoid the world-spanning-layer-2 madness):

In the video about parallel application stacks (swimlanes) you mentioned that one of the options for using the R/W database in Datacenter A if the user traffic landed in Datacenter B in which the replica of the database is read-only was to redirect the user browser with the purpose that the follow up HTTP POST land in Datacenter A.

Here’s the diagram he’s referring to:

Here’s the list of materials (and other changes) I added to the Ansible for Networking Engineers webinar and online course in June 2017.

The first thing you’ll notice is the brand-new user interface with collapsible sections, making it easier to grasp the big picture (the change was badly needed – the webinar is already almost 12 hours long).

Got this remark from one of my SDN mailing list subscribers:

There are NMSs that are based on SNMP, their manufacturers that say they can replace an SDN architecture, because they allow to automate the management of the network.

O’RLY?

I get a “how do I get started with network automation” question every other week, and when I wrote a lengthy reply to one about configuration templating of existing snowflake network on networktocode Slack channel I decided it’s time to turn my replies into a blog post.