wiki:YangModelCoordGroup

Our current phase approach is:

  • Phase 1: List of the YANG models (inventory)
  • Phase 2: Tooling
  • Phase 3: Help with compilation
  • Phase 4: Training & Education
  • Phase 5: Coordination across SDOs/Opensource
  • Phase 6: Model Coordination within the IETF
  • Phase 7: Standardization Priorities

Actions Items

  • Benoit, Qin: organize the next hackathon
  • Benoit, Mahesh, Glen Parsons: RFC for IEEE URN. In progress.
  • Benoit: Coordination with the different SDOs (liaisons)
  • Benoit: speak with the RFC-editor on the YANG modules, including the ones from the IANA page. DONE, but need to document it.
  • Benoit: YANG Modeling Efforts in The Industry (to be updated)
  • Benoit: advice pyang --lint to other SDOs
  • Benoit: RFC extracted YANG models in stable location in IANA or RFC editor web site
  • Benoit: extract URI and revision number from RFC (to be done during the hackathon)
  • Benoit, Carl: IETF L2VPN YANG model and MEF: what is the right place for the IETF L2VPN YANG model?
  • Benoit: hachathon: flag the duplicate names for YANG data models
  • Benoit: hackathon: create a mailing for all draft dependencies (ex: when the routing draft is updated)
  • Carl, Dean: draft-bogdanovic-netmod-yang-model-classification
  • Carl: RFC 6087bis: write a section wrt advice for other SDOs? Namespace, naming convention
  • Carl: tools (advice) in one place. Client library, IDE. DONE, need to advertise it. Send the tools link to yang-central.org
  • Carl, Mahesh: universal data model catalog service (URN -> URL)
  • Carl: yangvalidator.com: include in pyang PATH all the YANG models coming from existing RFC and IETF drafts
  • Carl: work with Henrik to include in pyang PATH all the YANG models coming from existing RFC and IETF drafts
  • Carl: work on draft for YANG to JSON schema translation
  • Carl: review the L3SM draft-ietf-l3sm-l3vpn-service-model draft
  • Qin: start to populate the data model catalog with the YANG models coming from the RFC, with Carl's help. Create a tool during the hackathon
  • Qin: coordination with the RTG YANG COORD WIKI
  • Qin: help the draft authors with compilation errors at http://www.claise.be/IETFYANGPageCompilation.html
  • Qin: xim.py and pyang now integrated with idnits. Check that everything works fine.

YANG Modeling Efforts in The Industry

http://trac.tools.ietf.org/area/ops/trac/wiki/YANGModelingEffortsinTheIndustry

YANG Modules and extraction tool

http://www.claise.be/IETFYANGPageCompilation.html

YANG Tools

http://www.yang-central.org/twiki/bin/view/Main/YangTools

Some numbers (July 3rd 2015)

IETF YANG MODELS Number of correctly extracted YANG models from IETF drafts: 126 Number of YANG models in IETF drafts that passed compilation without warnings: 44/126 Number of YANG models in IETF drafts that passed compilation with warnings: 27/126 Number of all YANG models in IETF drafts (example, badly formatted, etc. ): 203 OPENDAYLIGHT YANG MODELS Number of YANG models in Hydrogen release: 117 Number of YANG models in Helium release: 220 Number of YANG models in Lithium release: 473

NETCONF

The Network Configuration Protocol (NETCONF) provides operators and application developers with a standard framework and a set of standard Remote Procedure Call (RPC) methods to manipulate the configuration of a network device. As CLI is designed as human interface, using Perl/Tcl? + Expect with CLI, is not the best way to create programmatic interface to networking devices. Hence, NETCONF was designed to be a replacement for old programmatic interface, that would enable creation of better abstractions.

More information about NETCONF http://netconfcentral.org/netconf_docs

YANG YANG is a data modeling language used to model configuration and state data manipulated by the NETCONF protocol (RFC 6241), NETCONF remote procedure calls, and NETCONF notifications.

List of current NETCONF RFCs

NETCONF Protocol (RFC 6241)
NETCONF Protocol Over SSH (RFC 6242)
NETCONF Protocol Over TLS (RFC 5539)
Partial Lock RPC for NETCONF (RFC 5717)
NETCONF Access Control Model (RFC 6536)
NETCONF Notifications (RFC 5277)
NETCONF Base Notifications (RFC 6470)
NETCONF Monitoring Schema (RFC 6022)
With-defaults Capability for NETCONF (RFC 6243)

List of current YANG RFCs

YANG Data Modeling Language (RFC 6020)
YANG Guidelines (RFC 6087)
NETCONF/YANG Architecture (RFC 6244)
YANG to DSDL Translation (RFC 6110)
Extending YANG with Language Abstractions (RFC 6095)
SMIv2 to YANG Translation (RFC 6643)
Common YANG Data Types (RFC 6991)
A YANG Data Model for Interface Management (RFC 7223)
IANA Interface Type YANG Module (RFC 7224)
A YANG Data Model for IP Management (RFC 7277)
A YANG Data Model for System Management (RFC 7317)
A YANG Data Model for SNMP Configuration (RFC 7407)

YANG model classification At very high level YANG models can be classified as Configuration model is published by vendors and it describes what the device capabilities are and how to enable them. Within IETF, we are trying to standardize configuration models.

Service models are deployed configurations as services in the network. Service models use a subset of configuration model to set desired state in the device and network. More info at http://datatracker.ietf.org/doc/draft-bogdanovic-netmod-yang-model-classification/?include_text=1

GitHub? YANG repository A combination of IETF and Open Daylight, some vendor YANG model repos and a tool section https://github.com/YangModels/yang

All IETF drafts and RFCs that reference the YANG RFC 6020 http://datatracker.ietf.org/doc/rfc6020/referencedby/

External sources for NETCONF and YANG

http://netconfcentral.org/

http://yang-central.org/

Routing Area YANG Coordination Forum

https://trac.tools.ietf.org/area/rtg/trac/wiki/RtgYangCoord

IETF drafts: help with the YANG data model extraction and compilation

YangCoordModelExtractionandCompilation


Back to the YANG Model Coordination Group Page.

Last modified 6 years ago Last modified on 24/03/16 13:51:12