RFC 7950: The YANG 1.1 Data Modeling Language

YANG is a data modeling language used to model configuration data, state data, Remote Procedure Calls, and notifications for network management protocols.…

Read RFC 7950 on the RFC Editor

Outgoing relationships (17 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 5234: Augmented BNF for Syntax Specifications: ABNF
Normative reference — RFC 3986: Uniform Resource Identifier (URI): Generic Syntax
Normative reference — RFC 3629: UTF-8, a transformation format of ISO 10646
Normative reference — RFC 6241: Network Configuration Protocol (NETCONF)
Normative reference — RFC 4648: The Base16, Base32, and Base64 Data Encodings
Normative reference — RFC 7405: Case-Sensitive String Support in ABNF
Normative reference — RFC 5277: NETCONF Event Notifications
Normative reference — RFC 7895: YANG Module Library
Informative reference — RFC 2578: Structure of Management Information Version 2 (SMIv2)
Informative reference — RFC 2579: Textual Conventions for SMIv2
Informative reference — RFC 6020: YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)
Informative reference — RFC 6991: Common YANG Data Types
Informative reference — RFC 7951: JSON Encoding of Data Modeled with YANG
Informative reference — RFC 4844: The RFC Series and RFC Editor
Informative reference — RFC 3780: SMIng - Next Generation Structure of Management Information
Informative reference — RFC 6643: Translation of Structure of Management Information Version 2 (SMIv2) MIB Modules to YANG Modules

Incoming relationships (100 related RFCs)

Showing 50 of 100 related RFCs.

Updated by, Normatively referenced by — RFC 8342: Network Management Datastore Architecture (NMDA)
Updated by — RFC 8526: NETCONF Extensions to Support the Network Management Datastore Architecture
Normatively referenced by — RFC 8341: Network Configuration Access Control Model
Normatively referenced by — RFC 8343: A YANG Data Model for Interface Management
Normatively referenced by — RFC 8349: A YANG Data Model for Routing Management (NMDA Version)
Normatively referenced by — RFC 7951: JSON Encoding of Data Modeled with YANG
Normatively referenced by — RFC 8294: Common YANG Data Types for the Routing Area
Normatively referenced by — RFC 8177: YANG Data Model for Key Chains
Normatively referenced by — RFC 8345: A YANG Data Model for Network Topologies
Normatively referenced by — RFC 8299: YANG Data Model for L3VPN Service Delivery
Normatively referenced by — RFC 8791: YANG Data Structure Extensions
Normatively referenced by — RFC 9132: Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Specification
Normatively referenced by — RFC 9182: A YANG Network Data Model for Layer 3 VPNs
Normatively referenced by — RFC 9640: YANG Data Types and Groupings for Cryptography
Normatively referenced by — RFC 9645: YANG Groupings for TLS Clients and TLS Servers
Normatively referenced by — RFC 8969: A Framework for Automating Service and Network Management with YANG
Normatively referenced by — RFC 9291: A YANG Network Data Model for Layer 2 VPNs
Normatively referenced by — RFC 9408: A YANG Network Data Model for Service Attachment Points (SAPs)
Normatively referenced by — RFC 9641: A YANG Data Model for a Truststore
Normatively referenced by — RFC 9642: A YANG Data Model for a Keystore
Normatively referenced by — RFC 7952: Defining and Using Metadata with YANG
Normatively referenced by — RFC 8344: A YANG Data Model for IP Management
Normatively referenced by — RFC 9643: YANG Groupings for TCP Clients and TCP Servers
Normatively referenced by — RFC 9911: Common YANG Data Types
Normatively referenced by — RFC 8795: YANG Data Model for Traffic Engineering (TE) Topologies
Normatively referenced by — RFC 8960: A YANG Data Model for MPLS Base
Normatively referenced by — RFC 8995: Bootstrapping Remote Secure Key Infrastructure (BRSKI)
Normatively referenced by — RFC 9181: A Common YANG Data Model for Layer 2 and Layer 3 VPNs
Normatively referenced by — RFC 9644: YANG Groupings for SSH Clients and SSH Servers
Normatively referenced by — RFC 8366: A Voucher Artifact for Bootstrapping Protocols
Normatively referenced by — RFC 8695: A YANG Data Model for the Routing Information Protocol (RIP)
Normatively referenced by — RFC 8776: Common YANG Data Types for Traffic Engineering
Normatively referenced by — RFC 9129: YANG Data Model for the OSPF Protocol
Normatively referenced by — RFC 9835: A Network YANG Data Model for Attachment Circuits
Normatively referenced by — RFC 8242: Interface to the Routing System (I2RS) Ephemeral State Requirements
Normatively referenced by — RFC 9130: YANG Data Model for the IS-IS Protocol
Normatively referenced by — RFC 9195: A File Format for YANG Instance Data
Normatively referenced by — RFC 9244: Distributed Denial-of-Service Open Threat Signaling (DOTS) Telemetry
Normatively referenced by — RFC 9254: Encoding of Data Modeled with YANG in the Concise Binary Object Representation (CBOR)
Normatively referenced by — RFC 9633: Deterministic Networking (DetNet) YANG Data Model
Normatively referenced by — RFC 9907: Guidelines for Authors and Reviewers of Documents Containing YANG Data Models
Normatively referenced by — RFC 8049: YANG Data Model for L3VPN Service Delivery
Normatively referenced by — RFC 8346: A YANG Data Model for Layer 3 Topologies
Normatively referenced by — RFC 8808: A YANG Data Model for Factory Default Settings
Normatively referenced by — RFC 9020: YANG Data Model for Segment Routing
Normatively referenced by — RFC 9067: A YANG Data Model for Routing Policy
Normatively referenced by — RFC 9313: Pros and Cons of IPv6 Transition Technologies for IPv4-as-a-Service (IPv4aaS)
Normatively referenced by — RFC 9595: YANG Schema Item iDentifier (YANG SID)
Normatively referenced by — RFC 8348: A YANG Data Model for Hardware Management
Normatively referenced by — RFC 8819: YANG Module Tags