BPM Working Group B. Y. Yoon
Internet-Draft ETRI
Intended status: Standards Track Y. You
Expires: 7 May 2027 woori-net
3 November 2026
A YANG Data Model for Performance Monitoring (PM) Capabilities
draft-yoon-bpm-pm-capabilities-00
Abstract
This document defines a YANG data model, "ietf-pm-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 [RFC9196], 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
[I-D.yoon-bpm-pm-collection] 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
This note is to be removed before publishing as an RFC.
The latest revision of this draft can be found at
https://binyeongyoon-ietf.github.io/ietf-pm-streaming/draft-yoon-bpm-
pm-capabilities.html. Status information for this document may be
found at https://datatracker.ietf.org/doc/draft-yoon-bpm-pm-
capabilities/.
Source for this draft and an issue tracker can be found at
https://github.com/binyeongyoon-ietf/ietf-pm-streaming.
Note to the RFC Editor
Yoon & You Expires 7 May 2027 [Page 1]
Internet-Draft PM Capabilities YANG November 2026
Please replace "RFC XXXX" with the RFC number assigned to this
document, and "RFC YYYY" with the RFC number assigned to
[I-D.yoon-bpm-pm-collection], throughout this document and in the
YANG module, and remove this note.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on 7 May 2027.
Copyright Notice
Copyright (c) 2026 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. Code Components
extracted from this document must include Revised BSD License text as
described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Revised BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
1.2. Relationship to Companion Documents . . . . . . . . . . . 4
2. Motivation . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.1. Monitoring Objectives Require Different Intervals . . . . 6
2.2. Equipment Performance Determines Achievable Intervals . . 6
2.3. Multi-Vendor Interoperability . . . . . . . . . . . . . . 7
3. Structure and the Sampling/Collection Relationship . . . . . 8
4. Capability Discovery and Configuration Workflow . . . . . . . 9
5. PM Capabilities Example . . . . . . . . . . . . . . . . . . . 10
Yoon & You Expires 7 May 2027 [Page 2]
Internet-Draft PM Capabilities YANG November 2026
6. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . . . 13
7. YANG Module . . . . . . . . . . . . . . . . . . . . . . . . . 13
8. Manageability Considerations . . . . . . . . . . . . . . . . 20
9. Security Considerations . . . . . . . . . . . . . . . . . . . 20
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 21
11.1. Normative References . . . . . . . . . . . . . . . . . . 21
11.2. Informative References . . . . . . . . . . . . . . . . . 22
Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23
1. Introduction
The PM collection data model defined in [I-D.yoon-bpm-pm-collection]
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 [RFC7950], "ietf-pm-
capabilities", for advertising the PM 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 [RFC7799] 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 [I-D.yoon-bpm-pm-collection].
Yoon & You Expires 7 May 2027 [Page 3]
Internet-Draft PM Capabilities YANG November 2026
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 [RFC9196]. 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 [RFC9196]) 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 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 [I-D.yoon-bpm-pm-collection].
1.1. Terminology
The terms "client", "server", "datastore", and "operational state"
are used as defined in [RFC6241] and [RFC8342].
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 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
1.2. Relationship to Companion Documents
The functional division between this document and
[I-D.yoon-bpm-pm-collection] is as follows.
[I-D.yoon-bpm-pm-collection] 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-capabilities", which covers:
* Read-only advertisement of the sampling and collection interval
ranges, units, defaults, and granularity that a server supports
Yoon & You Expires 7 May 2027 [Page 4]
Internet-Draft PM Capabilities YANG November 2026
* 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
[I-D.yoon-bpm-pm-collection].
* "Which configurations the server can support" is in this document.
Specific performance parameters are defined as identities derived
from "performance-parameter" in other documents.
Figure 1 illustrates the relationship between the two YANG modules.
+------------------------------------------+
| ietf-pm-capabilities |
| (this document) |
| |
| pm-capabilities |
| parameter-profile [profile-names] -+ |
| pm-parameter [identityref] | |
| supported-collection-types | |
| interval-relationships | |
| sampling-interval | |
| collection-interval | |
+------------------------------|-----------+
| imports profile-names,
| performance-parameter,
| measurement-method,
| collection-type
v
+------------------------------------------+
| ietf-pm-collection |
| (companion document) |
| PM collection model |
+------------------------------------------+
Figure 1: Relationship between ietf-pm-capabilities and ietf-pm-
collection
Yoon & You Expires 7 May 2027 [Page 5]
Internet-Draft PM Capabilities YANG November 2026
2. Motivation
ITU-T G.7710 [G7710] 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.
2.1. 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
[I-D.yoon-bpm-pm-collection], 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.
2.2. 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.
Yoon & You Expires 7 May 2027 [Page 6]
Internet-Draft PM Capabilities YANG November 2026
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.
Table 1 shows an example comparison for the lost-packets parameter.
+===================+===============+=================+=============+
| Equipment class | Min. | Min. collection | Granularity |
| | sampling | interval | |
+===================+===============+=================+=============+
| High-performance | 100 ms | 1 min | 5 s |
+-------------------+---------------+-----------------+-------------+
| Standard | 1 s | 1 min | 1 min |
+-------------------+---------------+-----------------+-------------+
| Low-specification | 1 s | 15 min | 15 min |
+-------------------+---------------+-----------------+-------------+
Table 1: Example interval capabilities by equipment class (lost-
packets parameter)
A client operating across a heterogeneous network cannot assume a
uniform interval floor and must discover the capabilities of each
network element individually. The PM capabilities 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.
2.3. 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.
Yoon & You Expires 7 May 2027 [Page 7]
Internet-Draft PM Capabilities YANG November 2026
3. Structure and the Sampling/Collection Relationship
The module follows a hierarchical structure that mirrors the
configuration structure of the PM collection model defined in
[I-D.yoon-bpm-pm-collection], 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.
Yoon & You Expires 7 May 2027 [Page 8]
Internet-Draft PM Capabilities YANG November 2026
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 [I-D.yoon-bpm-pm-collection]
gives concrete examples of such combinations, which motivate the
ranges and granularities a server advertises here.
4. 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 [I-D.yoon-bpm-pm-collection]; Step
1 uses the model defined in this document.
+-----------+ +-----------+
| Client | | Server |
| (NMS/Ctrl)| | (NE) |
+-----+-----+ +-----+-----+
| |
| Step 1: Discover capabilities |
| [ietf-pm-capabilities] |
|---NETCONF get-data--------------> |
|<--pm-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---------- |
| |
Figure 2: Combined Capability Discovery and Data Access Workflow
*Step 1 -- Discover PM capabilities (this document).* On session
establishment, the server's YANG Library [RFC8525] and capability
information indicate whether "ietf-pm-collection" and "ietf-pm-
capabilities" are both supported. The client queries the "pm-
capabilities" container, which this module augments into the "system-
Yoon & You Expires 7 May 2027 [Page 9]
Internet-Draft PM Capabilities YANG November 2026
capabilities" container of "ietf-system-capabilities" [RFC9196].
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) [RFC8342]. Querying
the same anchor also returns any subscription and notification
capabilities advertised there by "ietf-notification-capabilities"
(Section 3 of [RFC9196]). 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 [RFC9196] for advertising capabilities in operational state. The
same information MAY also be published as static instance data using
the format defined in [RFC9195]. The interval ranges advertised here
correspond to the Measurement Timing aspect of the Performance Metric
Specification described in Section 5.4.2 of [RFC6390]; this document
provides the runtime discovery of those timing constraints, which the
companion model [I-D.yoon-bpm-pm-collection] then applies when
collection is configured.
*Step 2 -- Configure collection (companion document).* The client
configures PM collection using "ietf-pm-collection"
[I-D.yoon-bpm-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 [I-D.yoon-bpm-pm-collection].
5. PM Capabilities Example
Figure 3 shows a NETCONF <get-data> request [RFC8526] 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".
Yoon & You Expires 7 May 2027 [Page 10]
Internet-Draft PM Capabilities YANG November 2026
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"
message-id="301">
<get-data
xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-nmda"
xmlns:ds="urn:ietf:params:xml:ns:yang:ietf-datastores">
<datastore>ds:operational</datastore>
<subtree-filter>
<system-capabilities
xmlns=
"urn:ietf:params:xml:ns:yang:ietf-system-capabilities">
<pm-capabilities
xmlns=
"urn:ietf:params:xml:ns:yang:ietf-pm-capabilities"
xmlns:ex="urn:example:pm-parameters">
<parameter-profile>
<name>example-ip-qos-15min</name>
<pm-parameter>
<name>ex:lost-packets</name>
</pm-parameter>
</parameter-profile>
</pm-capabilities>
</system-capabilities>
</subtree-filter>
</get-data>
</rpc>
Figure 3: PM Capabilities Discovery Request Example
Figure 4 shows the "pm-capabilities" data returned within "system-
capabilities" in the reply.
Yoon & You Expires 7 May 2027 [Page 11]
Internet-Draft PM Capabilities YANG November 2026
<pm-capabilities
xmlns=
"urn:ietf:params:xml:ns:yang:ietf-pm-capabilities"
xmlns:ex="urn:example:pm-parameters">
<parameter-profile>
<name>example-ip-qos-15min</name>
<pm-parameter>
<name>ex:lost-packets</name>
<supported-collection-types>counts</supported-collection-types>
<interval-relationships>
<sampling-interval>
<id>1s</id>
<min-value>1</min-value>
<max-value>1</max-value>
<units>second</units>
<default-value>1</default-value>
<default-unit>second</default-unit>
<granularity>1</granularity>
<collection-interval>
<id>collection-range</id>
<min-value>5</min-value>
<max-value>1440</max-value>
<units>minute</units>
<default-value>15</default-value>
<default-unit>minute</default-unit>
<granularity>5</granularity>
<retained-interval-count>1</retained-interval-count>
</collection-interval>
</sampling-interval>
</interval-relationships>
</pm-parameter>
</parameter-profile>
</pm-capabilities>
Figure 4: PM Capabilities Discovery Reply Data Example
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.
Yoon & You Expires 7 May 2027 [Page 12]
Internet-Draft PM Capabilities YANG November 2026
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".
6. Tree Diagram
The following tree diagram, using the notation defined in [RFC8340],
shows the structure of the "ietf-pm-capabilities" module.
module: ietf-pm-capabilities
augment /sysc:system-capabilities:
+--ro pm-capabilities
+--ro parameter-profile* [name]
+--ro name pm-co:profile-names
+--ro pm-parameter* [name]
+--ro name identityref
+--ro supported-measurement-method* identityref
+--ro default-measurement-method? identityref
+--ro supported-collection-types*
| pm-co:collection-type
+--ro interval-relationships
+--ro sampling-interval* [id]
+--ro id string
+--ro min-value? uint32
+--ro max-value? uint32
+--ro units* interval-unit
+--ro default-value? uint32
+--ro default-unit? interval-unit
+--ro granularity? uint32
+--ro collection-interval* [id]
+--ro id string
+--ro min-value? uint32
+--ro max-value? uint32
+--ro units* interval-unit
+--ro default-value? uint32
+--ro default-unit? interval-unit
+--ro granularity? uint32
+--ro retained-interval-count? uint32
Figure 5: Tree Diagram of ietf-pm-capabilities
7. YANG Module
Yoon & You Expires 7 May 2027 [Page 13]
Internet-Draft PM Capabilities YANG November 2026
<CODE BEGINS> file "ietf-pm-capabilities@2026-11-03.yang"
module ietf-pm-capabilities {
yang-version 1.1;
namespace
"urn:ietf:params:xml:ns:yang:ietf-pm-capabilities";
prefix pm-cap;
import ietf-pm-collection {
prefix pm-co;
reference
"RFC YYYY: A YANG Data Model for Performance Monitoring (PM)
Collection";
}
import ietf-system-capabilities {
prefix sysc;
reference
"RFC 9196: YANG Modules Describing Capabilities for
Systems and Datastore Update Notifications";
}
organization
"IETF Benchmarking & Performance Measurements (bpm)
Working Group";
contact
"WG Web: <https://datatracker.ietf.org/wg/bpm/>
Editor: Bin Yeong Yoon <mailto:byyun@etri.re.kr>";
description
"This YANG module defines a data model for advertising
performance monitoring (PM) 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.
Yoon & You Expires 7 May 2027 [Page 14]
Internet-Draft PM Capabilities YANG November 2026
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-11-03 {
description
"Initial revision.";
reference
"RFC XXXX: A YANG Data Model for Performance Monitoring (PM)
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.";
Yoon & You Expires 7 May 2027 [Page 15]
Internet-Draft PM Capabilities YANG November 2026
}
}
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.";
}
}
Yoon & You Expires 7 May 2027 [Page 16]
Internet-Draft PM Capabilities YANG November 2026
grouping parameter-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
Yoon & You Expires 7 May 2027 [Page 17]
Internet-Draft PM Capabilities YANG November 2026
"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
Yoon & You Expires 7 May 2027 [Page 18]
Internet-Draft PM Capabilities YANG November 2026
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-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 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-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" {
Yoon & You Expires 7 May 2027 [Page 19]
Internet-Draft PM Capabilities YANG November 2026
description
"Augments the system capabilities with PM 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-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;
}
}
}
}
<CODE ENDS>
8. Manageability Considerations
A server SHOULD ensure that the capabilities advertised in "pm-
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.
9. 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 [RFC6241] or RESTCONF. The module augments the "system-
capabilities" container of "ietf-system-capabilities" [RFC9196],
which is "config false"; all nodes added by this module therefore
inherit "config false" and reside in the operational datastore.
Yoon & You Expires 7 May 2027 [Page 20]
Internet-Draft PM Capabilities YANG November 2026
Following the guidance in [RFC9196], 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) [RFC8341] 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.
10. IANA Considerations
This document requests IANA to register the following URI in the "ns"
subregistry within the "IETF XML Registry" [RFC3688]:
URI: urn:ietf:params:xml:ns:yang:ietf-pm-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 [RFC6020]:
Name: ietf-pm-capabilities Namespace:
urn:ietf:params:xml:ns:yang:ietf-pm-capabilities Prefix: pm-cap
Reference: RFC XXXX
11. References
11.1. Normative References
[I-D.yoon-bpm-pm-collection]
Yoon, B. Y. and Y. You, "A YANG Data Model for Performance
Monitoring (PM) Collection", Work in Progress, Internet-
Draft, draft-yoon-bpm-pm-collection-00, November 2026,
<https://datatracker.ietf.org/doc/html/draft-yoon-bpm-pm-
collection-00>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/rfc/rfc2119>.
Yoon & You Expires 7 May 2027 [Page 21]
Internet-Draft PM Capabilities YANG November 2026
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010,
<https://www.rfc-editor.org/rfc/rfc6020>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<https://www.rfc-editor.org/rfc/rfc6241>.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, DOI 10.17487/RFC7950, August 2016,
<https://www.rfc-editor.org/rfc/rfc7950>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/rfc/rfc8174>.
[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
<https://www.rfc-editor.org/rfc/rfc8340>.
[RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration
Access Control Model", STD 91, RFC 8341,
DOI 10.17487/RFC8341, March 2018,
<https://www.rfc-editor.org/rfc/rfc8341>.
[RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "Network Management Datastore Architecture
(NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,
<https://www.rfc-editor.org/rfc/rfc8342>.
[RFC8525] Bierman, A., Bjorklund, M., Schoenwaelder, J., Watsen, K.,
and R. Wilton, "YANG Library", RFC 8525,
DOI 10.17487/RFC8525, March 2019,
<https://www.rfc-editor.org/rfc/rfc8525>.
[RFC9196] Lengyel, B., Clemm, A., and B. Claise, "YANG Modules
Describing Capabilities for Systems and Datastore Update
Notifications", RFC 9196, DOI 10.17487/RFC9196, February
2022, <https://www.rfc-editor.org/rfc/rfc9196>.
11.2. Informative References
[G7710] ITU-T, "Common Equipment Management Function
Requirements", ITU-T Recommendation G.7710, November 2025,
<https://www.itu.int/rec/T-REC-G.7710>.
Yoon & You Expires 7 May 2027 [Page 22]
Internet-Draft PM Capabilities YANG November 2026
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/rfc/rfc3688>.
[RFC6390] Clark, A. and B. Claise, "Guidelines for Considering New
Performance Metric Development", BCP 170, RFC 6390,
DOI 10.17487/RFC6390, October 2011,
<https://www.rfc-editor.org/rfc/rfc6390>.
[RFC7799] Morton, A., "Active and Passive Metrics and Methods (with
Hybrid Types In-Between)", RFC 7799, DOI 10.17487/RFC7799,
May 2016, <https://www.rfc-editor.org/rfc/rfc7799>.
[RFC8526] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "NETCONF Extensions to Support the Network
Management Datastore Architecture", RFC 8526,
DOI 10.17487/RFC8526, March 2019,
<https://www.rfc-editor.org/rfc/rfc8526>.
[RFC9195] Lengyel, B. and B. Claise, "A File Format for YANG
Instance Data", RFC 9195, DOI 10.17487/RFC9195, February
2022, <https://www.rfc-editor.org/rfc/rfc9195>.
Contributors
Kwangkoog Lee
KT
Email: kwangkoog.lee@kt.com
Jongyoon Shin
SK Telecom
Email: jongyoon.shin@sk.com
Sungyong Nam
LGU+
Email: sy.nam@lguplus.co.kr
Authors' Addresses
Bin Yeong Yoon
ETRI
Email: byyun@etri.re.kr
Yoon & You Expires 7 May 2027 [Page 23]
Internet-Draft PM Capabilities YANG November 2026
Youngkil You
woori-net
Email: young@woori-net.com
Yoon & You Expires 7 May 2027 [Page 24]