A collection of post-mortems

Probably because networking protocols are slow to update since everybody has to get on board.

A lot of changes in networking have been happening recently; in particular, software defined networking is (slowly) replacing dedicated routers and hardware devices.

The downside of this is that it's much easier to change configuration than it was before, and so the pace of such changes is increasing. Given that most errors can be traced back to a human error at the start of the chain, he problem isn't really in the networking stack but the meat at the end of the buttons.

Realistically you need to address that end of the problem, not the networking protocols themselves.

Most of those config errors are router configurations, it's hard to disrupt that because it is tied to the hardware. As a networking guy, I'm not surprised either. Cisco's interface is really awful and they have no interest in making it better. They make tons of money selling expensive courses and certifications. There is very little sanity checking in the interface which makes it easy to shoot yourself in the foot.