wiki:RtgYangArchDT

The Routing Area Yang Architecture design team

Version 2: Aug 19, 2016 ->

Charter

Announcement

Going forward, the Design Team will focus on:

*Conventions as specified in the original charter* : Common conventions and use of YANG functionality in similar ways can help make the interactions of models easier to understand. RFC 6087 provides some guidance; an update; is underway now in draft-ietf-netmod-rfc6087bis. If the design team has recommendations for how the models should be written, those which are not routing-specific can be written down and discussed in netmod.

*Ideas for how to handle extensions and features as specified in the original charter*:

It is also important to consider how future extensibility and features in Routing Area work will need to be captured inYANG models. While the IETF is busy developing YANG models, we are still working on new routing area features and technology. The design team should publish and maintain best current practices for how new features can easily augment existing YANG models so that authors of those new features and technologies can understand how to consider YANG modeling.

*Classification*: The ability to specify metadata for classification and manipulation of models is being defined in draft-ietf-netmod-yang-mode l-classification-02 <https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-model-classification/>. The DT will suggest classifications for Routing Area YANG models and encourage consistency.

*Support work based on requirements*: The DT will continue to support work based on requirements from its previous work. Examples of such work include draft-ietf-netmod-schema-mount-02 <https://datatracker.ietf.org/doc/draft-ietf-netmod-schema-mount/> and opstate/revised datastores.

*Progress WG Drafts authored*: The DT and the specific draft authors will push to publication of the existing drafts: draft-ietf-rtgwg-device-model-00 <https://datatracker.ietf.org/doc/draft-ietf-rtgwg-device-model/>, draft-ietf-rtgwg-lne-model-00 <https://datatracker.ietf.org/doc/draft-ietf-rtgwg-lne-model/>, and draft-ietf-rtgwg-ni-model-00 <https://datatracker.ietf.org/doc/draft-ietf-rtgwg-ni-model/> .

*Consistency of Models across the Routing Area*: The DT will look at YANG models in the Routing Area and encourage that common parts be factored out into reusable models. The DT will look at how well the set of models will work together and raise any related issues. There will be a particular focus on models expected to progress to RFC in the next 12 months.

*Device Profiles of Needed Models:* Different devices will need different sets of YANG models for common operations. There have been some initial drafts (e.g. draft-faq-netmod-cpe-yang-profile-00.txt <https://www.ietf.org/archive/id/draft-faq-netmod-cpe-yang-profile-00.txt>) in this space. The DTwill provide guidance for what is needed in a device profile, as far as the Routing Area aspects, are concerned and facilitate the creation of appropriate device profiles. This should aid in determining what groups of models are needed for practical use for particular device roles.

Design team members

Acee Lindem <​acee@…>
Anees Shaikh <​aashaikh@…>
Christian Hopps <​chopps@…>
Dean Bogdanovic <​deanb@…>
Ebben Aries <exa@…>
Lou Berger <​lberger@…> (lead)
Qin Wu <​bill.wu@…>
Rob Shakir <​rjs@…>
Xufeng Liu <xliu@…>
Yingzhen Qu <yiqu@…>

Version 1: Mar 26, 2015 -> Aug 19, 2016

Charter

Announcement

With the increase of YANG models, it is desirable to have an architecture that can suggest and articulate common functionality to be used by multiple models and how the models interconnect. Some individual work has been done in this space and the design team is encouraged to consider such input. Although this is a concern across the entire scope of YANG models, this design team is focused on the question of providing an architecture for the protocols and functionality contained inside the Routing Area. This may identify additional desirable models and common functionality; those suggestions can be raised in Netmod.

Common conventions and use of YANG functionality in similar ways can help make the interactions of models easier to understand. RFC 6087 provides some guidance; an update is underway now in draft-ietf-netmod-rfc6087bis. If the design team has recommendations for how the models should be written, those which are not routing-specific can be written down and discussed in netmod as part of a planned update of RFC 6087.

It is also important to consider how future extensibility and features in Routing Area work will need to be captured in YANG models. While the IETF is busy developing YANG models, we are still working on new routing area features and technology. The design team should publish and maintain best current practices for how new features can easily augment existing YANG models so that authors of those new features and technologies can understand how to consider YANG modeling in their manageability considerations.

This design team will write one or more internet-drafts describing the proposed architecture of the models, the recommended common conventions, and considerations for how to model new features. The architecture is the highest priority. The design team will address all the aspects of the routing area modeling: from configuration, to operational state, notifications, and RPCs. This design team will regularly coordinate with the YANG doctors for review and advice. These drafts will be discussed in RTGWG. It is possible that some of the content, such as the details of the architecture, will go to a wiki to be updated while other content, such as advice for extensions and common conventions, would be published by IETF consensus.

Design team members

Acee Lindem <acee@…>
Anees Shaikh <aashaikh@…>
Christian Hopps <chopps@…>
Dean Bogdanovic <deanb@…>
Lou Berger <lberger@…>
Qin Wu <bill.wu@…>
Rob Shakir <rjs@…>
Stephane Litkowski <stephane.litkowski@…>
Yan Gang <yangang@…>

Last modified 14 months ago Last modified on Aug 19, 2016, 10:37:31 AM