Last time we talked about a few things that go wrong in the IETF — this time we’ll talk about a few more things that can go wrong. Boiling the Ocean. Engineers, as a rule, like to solve problems. The problem is we often seem to think the bigger the problem, the better the solution. […]
The post HTIRW: Reality at the Mic (2) appeared first on Packet Pushers Podcast and was written by Russ White.
All About That YANG at the 92nd IETF Meeting
I was at the 92nd IETF meeting in Dallas a few weeks ago. I attended 16 sessions, mostly in the routing area, and every single one had a discussion about the YANG data model (indeed most had several such discussions).
YANG is the data modeling language for the NETCONF protocol. NETCONF/YANG was picked by the Interface to Routing System (I2RS) Working Group for an SDN controller to interact with IP/MPLS routers. It makes an IP/MPLS network programmable. There are other IETF protocols in play as well, such as Path Computation Element Protocol (PCEP). To make SDN management and orchestration (MANO) service aware, we need to bind these paths to the services they are intended for. This is where NETCONF/YANG data models come to the rescue. I was very pleased to see the attention NETCONF/YANG data models got at the IETF.
One thing that can hinder quick adoption and implementation for some data models is competing proposals. Indeed, some camps have formed around competing proposals. This is not unusual in the IETF. Different Internet-drafts (documents intended to be adopted by Continue reading
Let's take a look at EIGRP and the state a route can get into where EIGRP tells you “FD is Infinity”.