RFC 8342: Network Management Datastore Architecture (NMDA)

Datastores are a fundamental concept binding the data models written in the YANG data modeling language to network management protocols such as the Network…

Read RFC 8342 on the RFC Editor

Outgoing relationships (9 related RFCs)

Updates, Normative reference — RFC 7950: The YANG 1.1 Data Modeling Language
Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 8174: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
Normative reference — RFC 6241: Network Configuration Protocol (NETCONF)
Normative reference — RFC 8040: RESTCONF Protocol
Normative reference — RFC 7952: Defining and Using Metadata with YANG
Informative reference — RFC 3688: The IETF XML Registry
Informative reference — RFC 6020: YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)
Informative reference — RFC 6244: An Architecture for Network Management Using NETCONF and YANG

Incoming relationships (56 related RFCs)

Showing 50 of 56 related RFCs.

Updated by, Normatively referenced by — RFC 8808: A YANG Data Model for Factory Default Settings
Normatively referenced by — RFC 8791: YANG Data Structure Extensions
Normatively referenced by — RFC 9291: A YANG Network Data Model for Layer 2 VPNs
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 8695: A YANG Data Model for the Routing Information Protocol (RIP)
Normatively referenced by — RFC 9834: YANG Data Models for Bearers and Attachment Circuits as a Service (ACaaS)
Normatively referenced by — RFC 9835: A Network YANG Data Model for Attachment Circuits
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 9833: A Common YANG Data Model for Attachment Circuits
Normatively referenced by — RFC 9836: A YANG Data Model for Augmenting VPN Service and Network Models with Attachment Circuits
Normatively referenced by — RFC 9907: Guidelines for Authors and Reviewers of Documents Containing YANG Data Models
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 8819: YANG Module Tags
Normatively referenced by — RFC 9105: A YANG Data Model for Terminal Access Controller Access-Control System Plus (TACACS+)
Normatively referenced by — RFC 9128: YANG Data Model for Protocol Independent Multicast (PIM)
Normatively referenced by — RFC 9348: A YANG Data Model for IP Traffic Flow Security
Normatively referenced by — RFC 9363: A YANG Data Model for Static Context Header Compression (SCHC)
Normatively referenced by — RFC 9648: YANG Data Model for TCP
Normatively referenced by — RFC 8916: A YANG Data Model for the Multicast Source Discovery Protocol (MSDP)
Normatively referenced by — RFC 9093: A YANG Data Model for Layer 0 Types
Normatively referenced by — RFC 9094: A YANG Data Model for Wavelength Switched Optical Networks (WSONs)
Normatively referenced by — RFC 9166: A YANG Data Model for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Snooping
Normatively referenced by — RFC 9179: A YANG Grouping for Geographic Locations
Normatively referenced by — RFC 9194: A YANG Module for IS-IS Reverse Metric
Normatively referenced by — RFC 9243: A YANG Data Model for DHCPv6 Configuration
Normatively referenced by — RFC 9398: A YANG Data Model for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Proxy Devices
Normatively referenced by — RFC 9403: A YANG Data Model for RIB Extensions
Normatively referenced by — RFC 9617: A YANG Data Model for In Situ Operations, Administration, and Maintenance (IOAM)
Normatively referenced by — RFC 9702: YANG Data Model for Maximum Segment Identifier (SID) Depth (MSD) Types and MPLS MSD
Normatively referenced by — RFC 9719: YANG Data Model for Routing in Fat Trees (RIFT)
Normatively referenced by — RFC 9899: Extensions to the YANG Data Model for Access Control Lists (ACLs)
Normatively referenced by — RFC 9950: A YANG Data Model for Terminal Access Controller Access-Control System Plus (TACACS+)
Informatively referenced by — RFC 9182: A YANG Network Data Model for Layer 3 VPNs
Informatively referenced by — RFC 9640: YANG Data Types and Groupings for Cryptography
Informatively referenced by — RFC 9645: YANG Groupings for TLS Clients and TLS Servers
Informatively referenced by — RFC 8969: A Framework for Automating Service and Network Management with YANG
Informatively referenced by — RFC 9408: A YANG Network Data Model for Service Attachment Points (SAPs)
Informatively referenced by — RFC 9641: A YANG Data Model for a Truststore
Informatively referenced by — RFC 9642: A YANG Data Model for a Keystore
Informatively referenced by — RFC 9314: YANG Data Model for Bidirectional Forwarding Detection (BFD)
Informatively referenced by — RFC 9643: YANG Groupings for TCP Clients and TCP Servers
Informatively referenced by — RFC 9644: YANG Groupings for SSH Clients and SSH Servers
Informatively referenced by — RFC 8531: Generic YANG Data Model for Connection-Oriented Operations, Administration, and Maintenance (OAM) Protocols
Informatively referenced by — RFC 9127: YANG Data Model for Bidirectional Forwarding Detection (BFD)
Informatively referenced by — RFC 8944: A YANG Data Model for Layer 2 Network Topologies
Informatively referenced by — RFC 9826: A YANG Data Model for the Path Computation Element Communication Protocol (PCEP)
Informatively referenced by — RFC 8913: Two-Way Active Measurement Protocol (TWAMP) YANG Data Model