IETF YANG

IETF YANG
Name	IETF YANG
Developer	Internet Engineering Task Force
Introduced	2010
Latest release	RFC 7950
Genre	Data modeling language

IETF YANG IETF YANG is a data modeling language standardized by the Internet Engineering Task Force used for modeling configuration and state data manipulated by network configuration protocols. It complements network management protocols and interacts with standards from multiple organizations including Internet Engineering Task Force, IETF NETCONF Working Group, IETF RESTCONF Working Group, IETF NETMOD Working Group, and standards produced by bodies such as International Telecommunication Union, European Telecommunications Standards Institute, and Institute of Electrical and Electronics Engineers. The language is referenced by protocol specifications, implementation projects, and operator guidance produced by organizations like IETF RFC Series, OpenConfig, Linux Foundation, and Open Network Automation Platform.

Overview

YANG is engineered to express hierarchical data models for network elements, supporting configuration datastore modeling, operational state, remote procedure calls, and notifications. It is used alongside protocols that provide transport and access semantics, engaging with protocol specifications from NETCONF, RESTCONF, gNMI, and related work in SNMP and BGP automation efforts. The model expresses schemas consumed by management systems, orchestration platforms, and intent-based networking frameworks developed by communities at IETF, ONF, MEF Forum, OpenDaylight, and vendor programs at Cisco Systems, Juniper Networks, Arista Networks, Huawei Technologies, and Nokia.

History and Development

YANG development traces through IETF standardization activity during the 2000s and 2010s, reflecting contributions from authors and contributors affiliated with organizations such as Cisco Systems, Juniper Networks, Bell Labs, Ericsson, Nokia, and academic groups from University of California, Berkeley, Carnegie Mellon University, and Massachusetts Institute of Technology. Key milestones include publication in the RFC series and successive updates influenced by working groups like IETF NETMOD Working Group and coordination with protocol work in IETF NETCONF Working Group and IETF RESTCONF Working Group. Broader community input came via industry consortia including OpenConfig, Linux Foundation Networking, Telefónica, AT&T, and cloud providers such as Google, Amazon Web Services, and Microsoft.

Language Design and Features

YANG uses a modular, tree-structured schema language with constructs for containers, lists, leafs, choices, augments, and groupings; these map to network data modeled in implementations by projects such as OpenDaylight and NETCONF clients. The language design emphasizes type system extensibility, typedefs, identityrefs, unions, and built-in types influenced by data modeling practices from XML Schema, JSON Schema, and protocol specifications like SOAP and RESTful API guidance. YANG models include annotations, revision tracking, and import/include mechanisms that support reuse across modules maintained by vendors, operators, and standard bodies such as IETF RFC Series, ETSI, and MEF Forum. Validation, derivation, and semantic constraints are expressed via statements similar in purpose to constructs used in ASN.1 and SMI.

Data Modeling and Module Structure

A YANG module encapsulates namespace, prefix, imports, typedefs, groupings, augmentations, and top-level nodes; common patterns are seen in modules published by IETF RFC Series authors and community repositories like OpenConfig and vendor SDKs from Cisco Systems and Juniper Networks. Submodules enable collaborative decomposition used by multi-vendor projects such as ONF and Open Networking Foundation initiatives. The module structure supports semantic versioning and tooling workflows practiced in projects at Linux Foundation, OpenDaylight, FD.io, and cloud provider open projects. Integration adapters translate YANG models to programming-language bindings used in Python, Go (programming language), Java, and C++ ecosystems.

Standardization and IETF Working Groups

Standardization is driven through IETF processes involving working groups like IETF NETMOD Working Group, IETF NETCONF Working Group, and IETF RESTCONF Working Group, with outputs published as RFCs in the IETF RFC Series. Contributions and reviews commonly involve vendor engineering teams from Cisco Systems, Juniper Networks, Arista Networks, research labs at Bell Labs, Microsoft Research, and operator contributors from AT&T, Verizon, Deutsche Telekom, and Telefonica. Liaison and harmonization occur with standards organizations such as IEEE Standards Association, ETSI, ITU-T, and open-source communities like OpenConfig and Linux Foundation projects.

Implementations and Tooling

Multiple implementations and toolchains support authoring, validation, and runtime usage of YANG models, including open-source projects such as pyang, yang-explorer, OpenDaylight, NETCONF, ConfD, sysrepo, and vendor SDKs from Cisco Systems and Juniper Networks. Tooling includes model validators, code generators, and translators that emit bindings for languages used in projects at Google, Facebook, Amazon Web Services, Microsoft Azure, and orchestration platforms like Kubernetes and OpenStack. Testing and continuous integration practices incorporate model linting, unit tests, and conformance suites contributed by communities around IETF and the Linux Foundation.

Use Cases and Adoption

YANG is widely adopted for device configuration, telemetry, service orchestration, intent-based networking, and network automation in environments operated by AT&T, Verizon, NTT, BT Group, Deutsche Telekom, hyperscalers such as Google, Amazon Web Services, and Microsoft, and enterprise deployments from Cisco Systems and Juniper Networks. It underpins management interfaces for protocols like NETCONF, RESTCONF, and gNMI, and is referenced in interoperability programs run by OpenConfig, MEF Forum, ONF, and operator forums. Adoption patterns follow integration into SDN controllers, cloud-native network functions in OpenStack, and telemetry pipelines used in observability platforms developed by Grafana Labs, Prometheus, and vendor monitoring stacks.

Category:Network management