Routing Working Groups YANG Models Status, Drafts, and Design Teams

Last Updated 2015-02-24 by Dhruv Dhody


Last Updated 2015-10-02 by jhaas

Overview of BFD YANG Issues

The BFD Working Group had a design team produce the initial Yang module for BFD. This work covers not only providing configuration for the BFD protocol and useful groupings for protocol components, but also in modeling the operational state of the protocol.

One of the interesting modeling challenges for BFD is the fact that it is a component that is used by other protocols, typically for faster detection of connectivity failures than the native protocol timers. Such use of BFD from within an implementation minimally involves enabling BFD for the feature. Many implementations also permit the configuration of BFD timers as part of enabling BFD for the protocol.

In most implementations, when two endpoints (e.g. src:dst IP address pairs) are configured from multiple places (e.g. static routes, BGP, OSPF, etc.) but have differing timer requirements, a single BFD session is created between those endpoints with the most granular timer requirements and that session services all consumers regardless of having previously requested a less granular timer.

The implication is that configuration:

  • May request the same endpoints be covered from multiple protocol components.
  • Configured timers may differ for such multiple configuration.
  • Fewer sessions may be instantiated to cover the configured sessions.
  • Configuration may be desired to be present not only in the core BFD module but also in protocol modules.
  • There needs to be a way to map instantiated BFD sessions to configured (explicitly or implicitly) sessions.

Design Team

The BFD Yang Design team has concluded their closed work on August 2015 with the publication and adoption of draft-ietf-bfd-yang. They will continue working on the draft with Working Group input on the rtg-bfd@… mailing list.


  • Vero Zheng (vero.zheng@…)
  • Reshad Rahman (rrahman@…)


  • Mahesh Jethanandani (mjethanandani@…)
  • Santosh P K (santoshpk@…)


  • Sam Aldrin (aldrin.ietf@…)
  • Tissa Senevirathne (tsenevir@…)

Drafts and RFCs

The core BFD yang module has been published as draft-ietf-bfd-yang and work will continue on the mailing list.

Open Issues:

  • Support for VCCV
  • Support for Multipoint BFD
  • Coordination with other protocol yang modules that want to use BFD.


Last Updated 2014-11-13 by Matt Hartley

Drafts and RFCs


Last Updated 2014-10-22 by jhaas

Overview of I2RS Modeling efforts

In the first IETF meeting of 2014, YANG and NetConf? were chosen as the basis for I2RS use cases. Currently, there are two classes of modeling work expected:

  1. Fully disjoint models that do not have any interaction with non-I2RS configuration state. Examples of these include the RIB model and the Topology Model.
  2. Models that interact with non-I2RS configuration state. Such interaction may be due to dependencies (must to another object in another model, e.g.) or augmenting an existing configuration model with I2RS-related configuration or operational state.

Design Teams

Formal design teams have not been been spun up as of IETF 91 in Honolulu, but work is progressing to formalize informal design efforts for standalone drafts. A significant portion of this effort is currently being driven by Susan Hares.


No specific design team resources have been allocated at this time.

Drafts and RFCs

TODO - list Sue's drafts here. TODO - point to relevant use case documents or info model docs.


Drafts and RFCs


IPPM is not a Routing working group, but the work is related to routing.


The IPPM WG is looking at the following to develop the YANG module for TWAMP.

  • Ruth Civil (gcivil@…)
  • Mahesh Jethanandani (mjethanandani@…)
  • Alfred Morton (acmorton@…)
  • Kostas Pentikousis (k.pentikousis@…) (Lead)
  • Reshad Rahman (rrahman@…)
  • Vero Zheng (vero.zheng@…)


LIME is not a Routing working group, but the work is extremely relevant to routing.

Last Updated 2014-11-10 by Carlos Pignataro

Layer Independent OAM Management in the Multi-Layer Environment (lime)

The working group will work on the following deliverables:

  • YANG data model(s) for generic layer-independent and technology-independent configuration, reporting and presentation for OAM mechanisms.
  • An architecture for OAM that can be used as guidance by other IETF working groups developing new OAM protocols or modifying existing OAM protocols, at any layer and for any technology. This guidance will cover both the management and data planes. Existing OAM architectures will be reviewed.
  • Applicability document: The YANG model(s) specified in this working group must be usable and extensible by the existing OAM technologies. This usability and extensibility must be demonstrated, for example with IP Ping, traceroute, BFD, and LSP Ping. Note the technology-specific data model extensions should ideally be worked on in the respective working groups.


Last Updated 2015-10-15 by Luigi Iannone

Drafts and RFCs

  • This document describes a YANG data model to use with the Locator/ID Separation Protocol (LISP).
  • Slides: IETF-92



Last Updated 2014-11-13 by Matt Hartley

Authors are currently discussing a common approach and high-level structure for MPLS YANG models; the current mpls-te-yang drafts will be merged or otherwise reorganized.

Drafts and RFCs


Last Updated 2014-11-12 by Mingui Zhang

Overview of NVO3 YANG Issues

Network Virtualization Overlays (NVO3) enable network virtualization for data center networks environment that assumes an IP-based underlay. Operators running the data center need manage their NVO3 overlays. The Netconf+Yang method greatly facilitates the management of networks. NVO3 WG will work on the YANG data model that can be used to configure and manage NVO3 protocols and gather operational states. The WG is currently working on the architecture document. The work on the architecture and the work on the YANG data model should benefit from each other.

The base YANG data model covers the preliminary configuration of NVO3 instances as well as their operation states. This would be taken as the start point to move forward.

NVO3 has opened the door to solutions. The NVO3 YANG module needs to cover the upcoming solutions. As new solutions for NVO3 are developed, corresponding YANG data modules may be specified (e.g., the YANG data model for active-active multi-homing). The base YANG data model may be augmented to accommodate these new solutions.

Now, the developing of the YANG data modules for NVO3 is calling for more participants.

Drafts and RFCs


  • Mingui Zhang (zhangmingui@…)
  • Vero Zheng (vero.zheng@…)


  • Jinwei Xia (xiajinwei@…)
  • Muhammad Durrani (mdurrani@…)
  • Sujay Gupta (sujay.gupta@…)
  • Feng Zheng (habby.zheng@…)
  • Qiao Fu (fuqiao@…)


  • Tao Han, Weilian Jiang


The git url for nvo3 YANG modules: nvo3-yang


Drafts and RFCs


Last Updated 2015-02-24 by Dhruv Dhody

Basic YANG Module based on the RFC5440 and PCEP-MIB is published.

The latest update takes care of notifications, capability,scope, domain of PCEs etc.

A means, procedure and order to handle to following PCE features needs to be decided:

  • Stateful PCE
  • Path-Key
  • OF
  • GCO
  • P2MP
  • Inter-Layer

Drafts and RFCs


  • Rohit Pobbathi (rohit.pobbathi@…)
  • Vinod KumarS (vinods.kumar@…)
  • Dhruv Dhody, Ed. (dhruv.ietf@…; dhruv.dhody@…)
  • Jonathan Hardwick (jonathan.hardwick@…)


  • Young Lee, Udayasree Palle, Vishnu Pavan Beeram, Xian Zhang

Working Copy


Last Updated 2015-10-05 by Bruno Decraene

Drafts and RFCs


  • Configuration and operation of the SPRING IGP parts (IS-IS, OSPF). (not BGP, BGP EPE)
  • Does not define the IGP extensions to support segment routing but defines generic groupings that SHOULD be reused by IGP extension modules.
  • Slides: IETF92 IETF93 .


Last Updated 2015-03-23 by Matt Hartley

Design team has been working on TE yang models since IETF 91 and meeting on a weekly basis.


Drafts in TEAS:

Other relevant drafts:


Last Updated 2015-07-03 by Qin Wu

Design team has been working on multicast yang models since IETF 92 and meeting on a biweekly basis.

Design Team members

Huawei - Feng Guo, Yisong Liu
Ericsson - Mike McBride?, Xufeng Liu, Steve Baillargeon
ZTE - Ran Chen, Fangwei Hu
Juniper - Robert Kebler, Anish Peter
Brocade - Mike Davison
ALU - Andrew Dolganow, Greg Hankins, Tanmoy Kundu
Cisco - Mahesh Sivakumar, Nataraj Bacthu, Nagendra Kumar Nainar, Stig Venaas
DIRECTV - Jethwani Sunil
Telefonica - Luis Miguel C. Murillo
Universidad Carlos III de Madrid - Carlos J. Bernardos
Concordia University - William Atwood
Ignas Bagdonas
Metaswitch - Pete McAllister?


Drafts in PIM:

Currently there are no published Internet-Drafts for Multicast YANG models.

Mailing list info

List address: yang-multicast@…
To subscribe:


20150422 slides recording
20150506 slides recording
20150520 slides recording
20150603 slides recording
20150617 slides recording

Return to Routing YANG Coordination page?

Last modified 4 years ago Last modified on Oct 15, 2015, 2:30:22 AM