]> ETRI

byyun@etri.re.kr

woori-net

young@woori-net.com

IPPM Working Group performance monitoring interval capabilities capability advertisement YANG This document defines a YANG data model, "ietf-pm-interval-capabilities", that enables a server to advertise which sampling and collection intervals, measurement methods, and collection types it supports for each performance monitoring (PM) parameter. A client reads this capability information before configuring PM collection, so that it selects only values that the server can honour. The capabilities are advertised by augmenting the "ietf-system-capabilities" module defined in , so that a client discovers them at the same well-known location used for subscription and notification capabilities. The model imports the "profile-names" and "collection-type" types and the "performance-parameter" and "measurement-method" identities from the companion PM collection model defined in and mirrors its profile-and-parameter structure, ensuring direct alignment between capability discovery and collection configuration. The model does not define collection data structures or any delivery mechanism; those are defined in the companion document. About This Document The latest revision of this draft can be found at . Status information for this document may be found at . Source for this draft and an issue tracker can be found at . Note to the RFC Editor Please replace "RFC XXXX" with the RFC number assigned to this document, and "RFC YYYY" with the RFC number assigned to , throughout this document and in the YANG module, and remove this note.

Introduction The PM collection data model defined in allows a client to configure sampling and collection intervals for performance parameters within named parameter profiles. The same parameter may require different intervals depending on its type and monitoring objective, and different network elements support different ranges and granularities of intervals. Without a prior discovery step, a client risks configuring interval values that the server cannot honour, leading to configuration errors or suboptimal monitoring. This document defines a YANG data model , "ietf-pm-interval-capabilities", for advertising the interval capabilities a server supports. A client reads this information from the operational datastore before it configures PM collection. The model mirrors the profile-and-parameter structure of the companion PM collection model and reuses its "profile-names" type and "performance-parameter" identity, so that capability discovery aligns directly with collection configuration. In addition to interval ranges, the same discovery step advertises which measurement methods the server can apply to each parameter (active, passive, or hybrid). A parameter may be measurable by more than one method on a given network element -- for example, delay measured either by an active probe or by a hybrid in-band technique -- and a client needs to know the available methods before it configures a measurement or establishes a subscription, so that it obtains data with the intended operational meaning. Advertising the supported methods alongside the supported intervals lets the client make both choices in a single discovery step, using the companion configuration model . The same discovery step also advertises which collection types (counts, snapshot, and tidemarks) the server supports for each parameter, so that a client knows which types it can enable before it configures a parameter; a profile may also restrict a parameter to a subset of the types, for example counts only. Rather than defining a separate top-level container, this module augments the "system-capabilities" container of the "ietf-system-capabilities" module defined in . RFC 9196 provides a placeholder structure that other modules augment to expose YANG-related system capabilities; the companion module "ietf-notification-capabilities" (Section 3 of ) uses the same anchor to advertise subscription and notification capabilities. By augmenting the same anchor, this module lets a NETCONF or RESTCONF client discover the PM interval capabilities and the subscription capabilities through a single, standardised query, without prior knowledge of this module's own layout. This document does not define collection data structures, collection types, threshold events, or any delivery mechanism. All of those are defined in the companion document .

Terminology The terms "client", "server", "datastore", and "operational state" are used as defined in and . The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

Relationship to Companion Documents The functional division between this document and is as follows. defines "ietf-pm-collection", which configures PM collection and exposes the collected data. This document depends only on the types and identities that it imports from that module. This document defines "ietf-pm-interval-capabilities", which covers:

• Read-only advertisement of the sampling and collection interval ranges, units, defaults, and granularity that a server supports
• Read-only advertisement of the measurement methods and collection types that a server supports for each parameter
• Hierarchical alignment with the companion model's profile-and- parameter structure
• Capability discovery prior to collection configuration

The separation of concerns is:

• "What data is collected and how it is structured" is in .
• "Which configurations the server can support" is in this document.

Specific performance parameters are defined as identities derived from "performance-parameter" in other documents. illustrates the relationship between the two YANG modules.

Relationship between ietf-pm-interval-capabilities and ietf-pm-collection

Motivation ITU-T G.7710 does not include a clause that mandates a capability-discovery mechanism for configurable measurement timing parameters. However, because sampling and collection intervals are configurable, a client needs to know in advance which intervals a given server can support, so that requests can be built without violating implementation constraints. This module provides that advertisement.

Monitoring Objectives Require Different Intervals The same PM parameter may need to be collected simultaneously at multiple sampling and collection interval combinations, each serving a distinct operational objective. As illustrated by the use cases in , the number of lost packets counted every second may be aggregated over a 1-minute interval for rapid fault detection in a Network Operations Center (NOC), over a 15-minute interval for routine maintenance monitoring, and over a 24-hour interval for daily QoS reporting -- all three objectives active concurrently on the same parameter. Similarly, latency parameters may be sampled at sub-second granularity with short collection intervals for digital twin synchronization, or at longer intervals for AI/ML model training. A client wishing to configure all of these combinations for all parameters in a profile must first verify that the target server supports every required interval. Without a capability discovery step, the client has no way to know whether a desired combination is valid on the specific server, and may submit configurations that the server silently truncates, rejects, or rounds to the nearest supported value.

Equipment Performance Determines Achievable Intervals Beyond monitoring objective, the processing capacity of the network element itself directly determines which interval configurations are feasible for a given parameter. Network elements vary significantly in their measurement engines and hardware resources. High-performance network elements with dedicated measurement processors can support short minimum sampling intervals and fine-grained collection interval steps, enabling high-resolution monitoring for demanding use cases such as real-time fault detection, network digital twins, and AI-driven analytics. For example, such a device may support a 100-millisecond sampling interval for the lost-packets parameter, with collection intervals as short as 1 minute and a 5-second granularity step. Lower-specification network elements, constrained by processing resources or hardware architecture, may support only longer minimum intervals and coarser granularity steps. The same lost-packets parameter on such a device might have a minimum sampling interval of 1 second and a minimum collection interval of 15 minutes, adequate for traditional operations and maintenance monitoring but insufficient for sub-minute analytics. shows an example comparison for the lost-packets parameter. Example interval capabilities by equipment class (lost-packets parameter)

Equipment class	Min. sampling	Min. collection interval	Granularity
High-performance	100 ms	1 min	5 s
Standard	1 s	1 min	1 min
Low-specification	1 s	15 min	15 min

A client operating across a heterogeneous network cannot assume a uniform interval floor and must discover the capabilities of each network element individually. The interval capability model enables a client to select the highest-resolution intervals a given server supports for each operational objective, rather than applying a conservative lowest-common-denominator configuration across all devices.

Multi-Vendor Interoperability Equipment from different vendors supports different ranges and granularities of intervals, and may impose implementation-specific constraints on the relationship between sampling and collection intervals. In multi-vendor networks, clients must adapt to the capabilities of each element. Without a discovery mechanism, clients risk configuration failures, suboptimal monitoring, or system instability. A standardised capability model addresses these challenges and enables interoperability across diverse network environments.

Structure and the Sampling/Collection Relationship The module follows a hierarchical structure that mirrors the configuration structure of the PM collection model defined in , ensuring consistency between capability discovery and actual configuration. It has three levels: parameter profiles (collections of related parameters such as "example-ip-qos-15min"), PM parameters (individual parameters identified by identities derived from "performance-parameter"), and capabilities (supported sampling and collection intervals, measurement methods, and collection types for each parameter). The relationship between sampling and collection intervals is expressed structurally by nesting collection intervals within their corresponding sampling interval entry. For each interval, the model advertises:

• min-value: minimum supported numeric value
• max-value: maximum supported numeric value
• units: list of supported time units (e.g., second, minute)
• default-value: recommended default numeric value
• default-unit: recommended default time unit
• granularity: step size; valid values must be multiples of this

For a collection interval, the model additionally advertises retained-interval-count: the number of completed intervals the server retains after they end. This value bounds both how many completed intervals a client may read back and, for push delivery, how long a reporting period may be, since a reporting period may span at most retained-interval-count collection intervals. A client uses it to choose a reporting period the server can honour. For each parameter, the model additionally advertises supported-collection-types: the collection types (counts, snapshot, tidemarks) that the server can collect for the parameter. A client enables only the advertised collection types. An absent list means the server does not advertise collection-type information for the parameter. Once a client knows the supported intervals, it can pair a single supported sampling interval with several supported collection intervals to serve different operational purposes for the same parameter. The "Use Cases" section of gives concrete examples of such combinations, which motivate the ranges and granularities a server advertises here.

Capability Discovery and Configuration Workflow A client performs the following three steps to configure PM collection and access the collected data correctly. Steps 2 and 3 use the companion model defined in ; Step 1 uses the model defined in this document.

Combined Capability Discovery and Data Access Workflow | |<--pm-interval-capabilities-------- | | | | Step 2: Configure collection | | [ietf-pm-collection] | |---NETCONF edit-config-----------> | |<--OK------------------------------ | | | | Step 3: Access data | | [ietf-pm-collection] | | | | Option A: Pull (polling) | |---NETCONF get-data--------------> | |<--collected data----------------- | | | | Option B: Push (YANG-Push) | |---establish-subscription--------> | |<--periodic-notifications---------- | | | ]]>

Step 1 -- Discover interval capabilities (this document). On session establishment, the server's YANG Library and capability information indicate whether "ietf-pm-collection" and "ietf-pm-interval-capabilities" are both supported. The client queries the "pm-interval-capabilities" container, which this module augments into the "system-capabilities" container of "ietf-system-capabilities" . Because that container is "config false", the augmented nodes inherit "config false" and reside in the operational datastore per the Network Management Datastore Architecture (NMDA) . Querying the same anchor also returns any subscription and notification capabilities advertised there by "ietf-notification-capabilities" (Section 3 of ). From it, the client retrieves the supported sampling and collection intervals for each parameter and profile, including the minimum and maximum values, allowed units, and granularity, together with the supported measurement methods and collection types. This runtime exposure follows the model described in for advertising capabilities in operational state. The same information MAY also be published as static instance data using the format defined in . The interval ranges advertised here correspond to the Measurement Timing aspect of the Performance Metric Specification described in Section 5.4.2 of ; this document provides the runtime discovery of those timing constraints, which the companion model then applies when collection is configured. Step 2 -- Configure collection (companion document). The client configures PM collection using "ietf-pm-collection" , selecting only sampling and collection interval values, measurement methods, and collection types that Step 1 confirmed the server supports. This avoids configuration errors such as an unsupported interval or collection type being rejected during collection setup or subscription establishment. Step 3 -- Access data (companion document). The client accesses the collected PM data, by pull-based retrieval or push-based subscription, as specified in .

Interval Capabilities Example shows a NETCONF <get-data> request that retrieves, from the operational datastore, the capabilities advertised for the "ex:lost-packets" parameter in the "example-ip-qos-15min" profile. The subtree filter selects the parameter by its list keys only, so the whole entry is returned. The parameter is identified by "ex:lost-packets", an example identity derived from "performance-parameter".

Interval Capabilities Discovery Request Example ds:operational example-ip-qos-15min ex:lost-packets ]]>

shows the "pm-interval-capabilities" data returned within "system-capabilities" in the reply.

Interval Capabilities Discovery Reply Data Example example-ip-qos-15min ex:lost-packets counts 1s 1 1 second 1 second 1 collection-range 5 1440 minute 15 minute 5 1 ]]>

The reply indicates that the server supports 1-second sampling and a collection interval range of 5 to 1440 minutes with 5-minute granularity, with a default of 15 minutes; that it supports the counts collection type for the parameter; and that it retains the most recently completed collection interval. Using this information, the client can configure the "ex:lost-packets" parameter in "ietf-pm-collection" with any collection interval that is a multiple of 5 within the range 5 to 1440 minutes, and with the counts collection type, knowing the server will accept the configuration. When the server also advertises supported measurement methods for the parameter, the reply additionally lists one or more "supported-measurement-method" values (and optionally a "default-measurement-method"), from which the client selects the method to configure in "ietf-pm-collection".

Tree Diagram The following tree diagram, using the notation defined in , shows the structure of the "ietf-pm-interval-capabilities" module.

Tree Diagram of ietf-pm-interval-capabilities

YANG Module Editor: Bin Yeong Yoon "; description "This YANG module defines a data model for advertising performance monitoring (PM) interval capabilities in network equipment. The module enables clients to discover which sampling and collection intervals, measurement methods, and collection types a server supports for each performance parameter within each parameter profile, before configuring PM collection. This module provides hierarchical interval capability discovery, in which collection intervals are nested within their corresponding sampling interval, and each parameter can have different interval capabilities within each parameter profile. This module imports the profile-names type, the performance-parameter and measurement-method identities, and the collection-type typedef from ietf-pm-collection and mirrors its profile-and-parameter structure. It does not define collection data structures, collection types, or any delivery mechanism; those are defined in ietf-pm-collection. The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document are to be interpreted as described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, they appear in all capitals, as shown here. Copyright (c) 2026 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Revised BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX (https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself for full legal notices."; revision 2026-10-29 { description "Initial revision."; reference "RFC XXXX: A YANG Data Model for Performance Monitoring (PM) Interval Capabilities"; } /* * TYPEDEFs */ typedef interval-unit { type enumeration { enum millisecond { description "Time interval in milliseconds."; } enum second { description "Time interval in seconds."; } enum minute { description "Time interval in minutes."; } enum hour { description "Time interval in hours."; } enum day { description "Time interval in days."; } } description "Supported units for expressing time intervals."; } /* * GROUPINGS */ grouping interval-constraints { description "Capability constraints for a single interval type, covering the supported range, units, default, and granularity. Used for both sampling intervals and collection intervals."; leaf min-value { type uint32; description "Minimum supported value for this interval."; } leaf max-value { type uint32; description "Maximum supported value for this interval."; } leaf-list units { type interval-unit; description "List of supported time units for this interval."; } leaf default-value { type uint32; description "Default value recommended for this interval."; } leaf default-unit { type interval-unit; description "Default unit recommended for this interval."; } leaf granularity { type uint32; description "Granularity step for interval values. Only values that are multiples of this granularity are supported. For example, if granularity is 5, valid values are 5, 10, 15, 20, and so on."; } } grouping parameter-interval-capabilities { description "Capabilities for a single PM parameter within a profile. The structure nests collection intervals within their corresponding sampling interval, reflecting the constraints that ietf-pm-collection places on the relationship between the two intervals."; leaf name { type identityref { base pm-co:performance-parameter; } description "Identity of the performance parameter, derived from the performance-parameter base identity of ietf-pm-collection. This value corresponds to the pm-parameter name leaf in ietf-pm-collection."; } leaf-list supported-measurement-method { type identityref { base pm-co:measurement-method; } description "The set of IPPM measurement methods (RFC 7799) that this server can apply to this parameter. A client selects one of the advertised methods when configuring the parameter in ietf-pm-collection. An empty or absent list means the server does not advertise measurement-method information for this parameter."; reference "RFC 7799: Active and Passive Metrics and Methods (with Hybrid Types In-Between)"; } leaf default-measurement-method { type identityref { base pm-co:measurement-method; } description "The measurement method the server uses for this parameter when a client configures the parameter without selecting a method. When present, it MUST be a member of supported-measurement-method."; reference "RFC 7799: Active and Passive Metrics and Methods (with Hybrid Types In-Between)"; } leaf-list supported-collection-types { type pm-co:collection-type; description "The set of collection types (counts, snapshot, tidemarks) that this server supports for this parameter. A client enables only the advertised collection types when configuring the parameter in ietf-pm-collection. An empty or absent list means the server does not advertise collection-type information for this parameter."; } container interval-relationships { description "Hierarchical relationships between sampling and collection intervals for this parameter. Each advertised combination of sampling and collection interval MUST satisfy the constraints of ietf-pm-collection."; list sampling-interval { key "id"; description "List of supported sampling intervals and their compatible collection intervals."; leaf id { type string; description "Unique identifier for this sampling interval capability entry."; } uses interval-constraints; list collection-interval { key "id"; description "List of supported collection intervals for this sampling interval."; leaf id { type string; description "Unique identifier for this collection interval capability entry."; } uses interval-constraints; leaf retained-interval-count { type uint32; description "Number of completed intervals of this collection interval that the server retains after they end. It bounds how many completed intervals a client may read back and, for push delivery, how long a reporting period may be: a reporting period may span at most retained-interval-count collection intervals. A value of 1 means only the most recently completed interval is retained; 0 means completed intervals are not retained (each is delivered only as it ends)."; } } } } } grouping profile-parameter-capabilities { description "Capabilities for all PM parameters within a single parameter profile."; leaf name { type pm-co:profile-names; description "Name of the parameter profile. This value corresponds to the parameter-profile name leaf in ietf-pm-collection (e.g., example-ip-qos-15min)."; } list pm-parameter { key "name"; description "List of PM parameters and their capabilities within this profile."; uses parameter-interval-capabilities; } } /* * AUGMENTATION OF ietf-system-capabilities (RFC 9196) * * The capabilities are advertised by augmenting the * "system-capabilities" container defined in RFC 9196. This * places the PM interval capabilities at the same well-known * location at which a NETCONF/RESTCONF client discovers * subscription and notification capabilities * (ietf-notification-capabilities, RFC 9196 Section 3), so that * both can be retrieved in a single, standardised query. The * "pm-interval-capabilities" wrapper container cleanly separates * this capability group from other capabilities augmented into * the same anchor. All augmented nodes inherit "config false" * from sysc:system-capabilities and therefore reside in the * operational datastore. */ augment "/sysc:system-capabilities" { description "Augments the system capabilities with PM interval capabilities, advertising the sampling and collection intervals, measurement methods, and collection types that this server supports, organised by parameter profile and PM parameter."; container pm-interval-capabilities { description "Read-only advertisement of the PM capabilities of this server, organised by parameter profile and PM parameter. A client reads this container to determine which interval values, measurement methods, and collection types are valid before configuring PM collection in ietf-pm-collection."; list parameter-profile { key "name"; description "List of parameter profiles and their per-parameter capabilities."; uses profile-parameter-capabilities; } } } } ]]>

Manageability Considerations A server SHOULD ensure that the capabilities advertised in "pm-interval-capabilities" remain consistent with its actual ability to honour interval configurations in "ietf-pm-collection". If a server's resources change dynamically (e.g., due to load), it SHOULD update the operational datastore accordingly, and clients that have already configured measurements using previously advertised values SHOULD be notified through standard NETCONF or YANG-Push mechanisms. Operators SHOULD verify that the interval values configured in "ietf-pm-collection" fall within the ranges advertised in this module before deploying measurement configurations in production.

Security Considerations The YANG module defined in this document defines data nodes that are designed to be accessed via network management protocols such as NETCONF or RESTCONF. The module augments the "system-capabilities" container of "ietf-system-capabilities" , which is "config false"; all nodes added by this module therefore inherit "config false" and reside in the operational datastore. Following the guidance in , this section documents the security considerations of the augmented nodes. The lowest NETCONF layer is the secure transport layer, and the mandatory-to-implement secure transport is Secure Shell (SSH). The Network Configuration Access Control Model (NACM) provides the means to restrict access for particular NETCONF or RESTCONF users to a preconfigured subset of all available NETCONF or RESTCONF protocol operations and content. Although all nodes are read-only, the capability information they expose can reveal vendor-specific implementation details about the equipment, such as supported interval ranges and granularities. Operators SHOULD restrict read access to authorised management clients to prevent unintended disclosure of device implementation characteristics.

IANA Considerations This document requests IANA to register the following URI in the "ns" subregistry within the "IETF XML Registry" : URI: urn:ietf:params:xml:ns:yang:ietf-pm-interval-capabilities Registrant Contact: The IESG. XML: N/A; the requested URI is an XML namespace. This document requests IANA to register the following YANG module in the "YANG Module Names" registry : Name: ietf-pm-interval-capabilities Namespace: urn:ietf:params:xml:ns:yang:ietf-pm-interval-capabilities Prefix: pm-ic Reference: RFC XXXX

References Normative References YANG is a data modeling language used to model configuration and state data manipulated by the Network Configuration Protocol (NETCONF), NETCONF remote procedure calls, and NETCONF notifications. [STANDARDS-TRACK] The Network Configuration Protocol (NETCONF) defined in this document provides mechanisms to install, manipulate, and delete the configuration of network devices. It uses an Extensible Markup Language (XML)-based data encoding for the configuration data as well as the protocol messages. The NETCONF protocol operations are realized as remote procedure calls (RPCs). This document obsoletes RFC 4741. [STANDARDS-TRACK] YANG is a data modeling language used to model configuration data, state data, Remote Procedure Calls, and notifications for network management protocols. This document describes the syntax and semantics of version 1.1 of the YANG language. YANG version 1.1 is a maintenance release of the YANG language, addressing ambiguities and defects in the original specification. There are a small number of backward incompatibilities from YANG version 1. This document also specifies the YANG mappings to the Network Configuration Protocol (NETCONF). This document captures the current syntax used in YANG module tree diagrams. The purpose of this document is to provide a single location for this definition. This syntax may be updated from time to time based on the evolution of the YANG language. The standardization of network configuration interfaces for use with the Network Configuration Protocol (NETCONF) or the RESTCONF protocol requires a structured and secure operating environment that promotes human usability and multi-vendor interoperability. There is a need for standard mechanisms to restrict NETCONF or RESTCONF protocol access for particular users to a preconfigured subset of all available NETCONF or RESTCONF protocol operations and content. This document defines such an access control model. This document obsoletes RFC 6536. Datastores are a fundamental concept binding the data models written in the YANG data modeling language to network management protocols such as the Network Configuration Protocol (NETCONF) and RESTCONF. This document defines an architectural framework for datastores based on the experience gained with the initial simpler model, addressing requirements that were not well supported in the initial model. This document updates RFC 7950. This document describes a YANG library that provides information about the YANG modules, datastores, and datastore schemas used by a network management server. Simple caching mechanisms are provided to allow clients to minimize retrieval of this information. This version of the YANG library supports the Network Management Datastore Architecture (NMDA) by listing all datastores supported by a network management server and the schema that is used by each of these datastores. This document defines two YANG modules, "ietf-system-capabilities" and "ietf-notification-capabilities". The module "ietf-system-capabilities" provides a placeholder structure that can be used to discover YANG-related system capabilities for servers. The module can be used to report capability information from the server at runtime or at implementation time by making use of the YANG instance data file format. The module "ietf-notification-capabilities" augments "ietf-system-capabilities" to specify capabilities related to "Subscription to YANG Notifications for Datastore Updates" (RFC 8641). ETRI woori-net This document specifies a YANG data model for Collection Measurement based on the Performance Management (PM) Collection function requirements defined in ITU-T G.7710. The model processes raw performance data sampled at a network node and produces structured data that can be retrieved by clients via pull-based mechanisms or delivered via push-based mechanisms such as YANG-Push. This document does not define new performance metrics; the base metrics are those of the IPPM framework, and the model specifies the collection and exposure of the operationally important subset identified by ITU-T G.7710. In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. Informative References ITU-T This memo provides clear definitions for Active and Passive performance assessment. The construction of Metrics and Methods can be described as either "Active" or "Passive". Some methods may use a subset of both Active and Passive attributes, and we refer to these as "Hybrid Methods". This memo also describes multiple dimensions to help evaluate new methods as they emerge. This document describes a framework and a process for developing Performance Metrics of protocols and applications transported over IETF-specified protocols. These metrics can be used to characterize traffic on live networks and services. This memo documents an Internet Best Current Practice. There is a need to document data defined in YANG models at design time, implementation time, or when a live server is unavailable. This document specifies a standard file format for YANG instance data, which follows the syntax and semantics of existing YANG models and annotates it with metadata. This document extends the Network Configuration Protocol (NETCONF) defined in RFC 6241 in order to support the Network Management Datastore Architecture (NMDA) defined in RFC 8342. This document updates RFCs 6241 and 7950. The update to RFC 6241 adds new and operations and augments existing,, and operations. The update to RFC 7950 requires the usage of the YANG library (described in RFC 8525) by NETCONF servers implementing the NMDA. This document describes an IANA maintained registry for IETF standards which use Extensible Markup Language (XML) related items such as Namespaces, Document Type Declarations (DTDs), Schemas, and Resource Description Framework (RDF) Schemas.

Contributors KT

kwangkoog.lee@kt.com

SK Telecom

jongyoon.shin@sk.com

LGU+

sy.nam@lguplus.co.kr