Skip to main content
  • IETF email infrastructure transition completed on 11 September

    A transition to a new modern, modular, and containerized infrastructure for email services provided for ietf.org, iab.org, irtf.org, rfc-editor.org (including email lists) was completed on 11 September 2026.

    11 Sep 2026
  • Survey to gather input on ISE selection criteria

    The survey to gather input for Independent Series Editor (ISE) selection criteria survey is live and we welcome your input on the capabilities and expectations the Internet Architecture Board (IAB) should consider when selecting a future ISE.

    10 Sep 2026
  • IETF 126 Highlights

    The IETF 126 meeting was held 18–24 July 2026 at the Hilton Vienna Park in Vienna, Austria, and online, hosted by Cisco. The week included the IETF Hackathon and Code Sprint, the New Participants' Program, five Birds-of-a-Feather (BoF) sessions, and more than 100 working group and research group sessions. The Applied Network Research Workshop also took place during the IETF 126 meeting week.

    1 Sep 2026
  • Post-Quantum Authentication: Up Next

    Post-quantum key establishment has moved from standards into deployment. Post-quantum authentication has not moved nearly as far, and specification work is no longer the only constraint. The IAB is holding a workshop in Prague on 11 and 12 October 2026 to bring deployment experience together with the people working on the relevant protocols and standards.

    27 Aug 2026
  • IETF 126 post-meeting survey: what we heard

    The IETF 126 Vienna meeting was held 18-24 July 2026 and the results of the post-meeting survey are now available.

    27 Aug 2026

Filter by topic and date

Filter by topic and date

YANG Really Takes Off in the Industry

27 Nov 2014

Just after the IETF 90 meeting last July, I posted this “YANG Takes Off in the Industry” blog.

One IETF meeting 91 later (just 2 weeks ago), the trend is confirmed: a big wave of YANG models is coming!

This big wave was confirmed by Dave Ward, in his “Open Standards, Open Source, Open Loop” talk to the IETF community.

New YANG models are not only seen in the OPS area, but also in the RTG, INT, TSV, and SEC areas. In total, about 20 working groups, 65 YANG model Internet-Drafts currently active, and 43 of these are at version 00. Granted, there are some redundant drafts, while the community organizes itself, but this shows a willingness to build data models with the YANG language [RFC 6020]. There are two types of models. First, the protocol-specific YANG models: For example QoS, ISIS, OSPF, MPLS, Traffic Engineering, 6Tisch, Multicast … to name a few. However, the end goal is for the operators to create services out of these building blocks, and some services YANG models start to appear at IETF, such as L2VPN or L3VPN. Some (services) YANG models were discussed in the different BoFs: In Abstraction and Control of Transport Networks (ACTN), in I2NSF (Interface to Network Security Functions, and also in the SUPA (Shared Unified Policy Automation) bar BoF

The second YANG Advice and Editing Session, was again a success with 15 YANG models reviewed by the YANG doctors. I was extremely pleased to see one operator, with a “newcomer” badge, present at this session to get feedback on his YANG model. Note that, in preparation for the review of all these YANG models, the YANG doctors team recently expanded.

Finally, a new working group, LIME, has been created just before the IETF meeting, focusing on YANG data model(s) for generic layer-independent and technology-independent configuration, reporting and presentation for Operations, Administration, and Maintenance (OAM) mechanisms.

It’s great to see some YANG traction within the IETF, and in the industry. My prediction is that more YANG models will follow. Many more, and not only from the IETF but from different Standard Development Organizations and consortia. Now it’s time to organize the coordination of all these YANG model so that the big wave doesn’t turn into a tsunami.


Share this page