YANG Data Modeling Language
YANG is to NETCONF what JSON Schema is to REST APIs — it describes the data model. Any network automation work with modern devices (Juniper, Cisco IOS-XR, Nokia SR-OS) requires reading and writing YANG models.
What It Defines
YANG is the data modeling language for NETCONF, RESTCONF, and gNMI. Defines the structure of network configuration and state data: modules, containers, lists, leaf-lists, leaf, typedef, grouping, augment, and deviation statements. YANG models describe everything from BGP policy to interface configuration. OpenConfig and IETF maintain vendor-neutral YANG modules.
Canonical (Normative)
Convenient (Practical)
Related References
The canonical publication point for finalized RFCs. If a protocol is standardized as an RFC, the RFC Editor text is the normative final reference. Published by the IETF, IRTF, IAB, and independent stream.
Related Specs
NETCONF replaced manual CLI for network device configuration in most modern SD-WAN, carrier, and enterprise deployments. Understanding datastores, capabilities, and YANG-driven RPC is essential for network automation.
RESTCONF brings network device management to the HTTP/JSON world. Most modern network OSes (Cisco IOS-XE 16.6+, Junos 17.3+, Nokia SR-OS) support it. If you prefer REST over SSH/XML for network automation, this is your interface.
gNMI is replacing SNMP for modern network monitoring: lower latency, higher efficiency, native streaming telemetry. Arista, Cisco (IOS-XR, IOS-XE), Juniper, and Nokia all support gNMI. Key for network observability pipelines (Telegraf, gnmic).