A YANG Data Model for Performance Monitoring Streaming on Common Transport Equipment
draft-yoon-ccamp-pm-streaming-07
This document is an Internet-Draft (I-D).
Anyone may submit an I-D to the IETF.
This I-D is not endorsed by the IETF and has no formal standing in the
IETF standards process.
| Document | Type | Active Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Bin Yeong Yoon , Youngkil You | ||
| Last updated | 2026-07-05 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Yang Validation | 0 errors, 0 warnings | ||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | I-D Exists | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
draft-yoon-ccamp-pm-streaming-07
CCAMP Working Group B. Y. Yoon
Internet-Draft ETRI
Intended status: Informational Y. You
Expires: 7 January 2027 woori-net
6 July 2026
A YANG Data Model for Performance Monitoring Streaming on Common
Transport Equipment
draft-yoon-ccamp-pm-streaming-07
Abstract
This document describes how the generic collection measurement YANG
data model and its interval-capability companion model are applied to
common transport equipment. It is informational. It defines a small
YANG module of transport performance parameters, organizes those
parameters into maintenance and QoS profiles, and gives end-to-end
examples that show capability discovery followed by YANG-Push
subscription, notification, and threshold reporting for a transport
profile.
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-
ccamp-pm-streaming.html. Status information for this document may be
found at https://datatracker.ietf.org/doc/draft-yoon-ccamp-pm-
streaming/.
Discussion of this document takes place on the Common Control and
Measurement Plane Working Group mailing list (mailto:ccamp@ietf.org),
which is archived at https://mailarchive.ietf.org/arch/browse/ccamp/.
Subscribe at https://www.ietf.org/mailman/listinfo/ccamp/.
Source for this draft and an issue tracker can be found at
https://github.com/binyeongyoon-ietf/ietf-pm-streaming.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Yoon & You Expires 7 January 2027 [Page 1]
Internet-Draft PM Streaming Transport YANG July 2026
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 January 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 . . . . . . . . . . . . . . . . . . . . . . . 3
2. Relationship to the Collection Measurement Documents . . . . 4
3. Placement in the Transport Network Element . . . . . . . . . 5
4. Transport Common PM Parameters and Profiles . . . . . . . . . 6
4.1. itu-transport-maintenance-15min Profile . . . . . . . . . 7
4.2. itu-transport-maintenance-24hr Profile . . . . . . . . . 7
4.3. itu-transport-qos-24hr Profile . . . . . . . . . . . . . 8
4.4. Profile Relationships and Operational Integration . . . . 8
4.5. Transport Parameter Module . . . . . . . . . . . . . . . 9
5. Use Cases: Streaming a Transport Profile . . . . . . . . . . 13
5.1. Step 1: Discover Supported Intervals . . . . . . . . . . 13
5.2. Step 2: Subscribe to Periodic Measurement . . . . . . . . 15
5.3. Step 3: Receive Periodic Notification . . . . . . . . . . 15
5.4. Step 4: Threshold Reporting . . . . . . . . . . . . . . . 16
6. Streaming Considerations for Transport Equipment . . . . . . 18
7. Security Considerations . . . . . . . . . . . . . . . . . . . 18
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 18
9.1. Normative References . . . . . . . . . . . . . . . . . . 19
Yoon & You Expires 7 January 2027 [Page 2]
Internet-Draft PM Streaming Transport YANG July 2026
9.2. Informative References . . . . . . . . . . . . . . . . . 20
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20
1. Introduction
Performance Management (PM) data generated by a transport Network
Element (NE) is processed into summarized statistics and delivered to
external clients. The continuous, push-based delivery of that data
is referred to in this document as PM streaming.
Two companion documents define the generic models used here. The
collection measurement data model [I-D.yoon-ippm-collection-measure]
defines the performance parameters structure, the sampling and
collection interval hierarchy, the three ITU-T G.7710 [G7710]
collection types (counts, snapshot, and tidemarks), and the
threshold-event notification. The interval-capability model
[I-D.yoon-ippm-collection-interval-capabilities] lets a server
advertise which intervals it supports. Both models are generic and
neutral to the transport technology.
This document is informational. It describes how those generic
models are applied to common transport equipment, defines a small
YANG module listing the transport performance parameters, organizes
the parameters into transport profiles, and gives end-to-end examples
of capability discovery, subscription, notification, and threshold
reporting. This document does not define any new subscription or
notification mechanism; the collected data and events are carried
using the YANG-Push framework [RFC8639] [RFC8640] [RFC8641].
1.1. Terminology
The term "client" refers to any consumer of the PM streaming
interface of a transport NE, such as an operations system (OS), a
Physical Network Controller (PNC), a network digital twin (NDT), or
an AI-driven application. The term "transport" is used in the sense
of [G7710] and covers technologies such as OTN, MPLS-TP, and
transport Ethernet.
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.
Yoon & You Expires 7 January 2027 [Page 3]
Internet-Draft PM Streaming Transport YANG July 2026
2. Relationship to the Collection Measurement Documents
This document is the transport-equipment member of a three-document
set. It continues the work formerly published as draft-yoon-ccamp-
pm-streaming-05: the generic, transport-neutral YANG modules that
earlier versions defined have been extracted into two companion
documents so that they can be reused independently, and this document
(continued as draft-yoon-ccamp-pm-streaming-06) now imports them
instead of defining them. The resulting structure is shown in
Figure 1.
+-------------------------------------------------+
| RFC 9196: ietf-system-capabilities |
| (system capability discovery anchor) |
+-------------------------------------------------+
^
(2) augments | to advertise the
| supported intervals
|
+---------------------------------+ imports +-----------------------------+
| (2) ietf-pm-interval- | profile-names| (1) ietf-pm-collection |
| capabilities | type from | draft-yoon-ippm- |
| draft-yoon-ippm-collection- | (1) -------> | collection-measure |
| interval-capabilities | +-----------------------------+
+---------------------------------+ ^
^ |
| imports (1) and (2) |
+----------------------+----------------------+
|
+---------------------------------------------+
| (3) ietf-pm-parameters (THIS DOCUMENT) |
| draft-yoon-ccamp-pm-streaming-06 |
| (CCAMP, Informational; formerly -05) |
+---------------------------------------------+
Figure 1: Relationship between this document and the collection
measurement model documents
The three documents play distinct, layered roles:
* (1) The collection measurement model
[I-D.yoon-ippm-collection-measure] (module ietf-pm-collection) is
the generic, transport-neutral core: the performance parameter
structure, the sampling and collection interval hierarchy, the
three ITU-T G.7710 [G7710] collection types (counts, snapshot, and
tidemarks), and the threshold-event notification.
Yoon & You Expires 7 January 2027 [Page 4]
Internet-Draft PM Streaming Transport YANG July 2026
* (2) The interval-capability model
[I-D.yoon-ippm-collection-interval-capabilities] (module ietf-pm-
interval-capabilities) imports the profile-names type from (1) and
augments the "ietf-system-capabilities" module of [RFC9196], so
that a server can advertise which sampling and collection
intervals it supports at the standard capability discovery anchor.
* (3) This document (module ietf-pm-parameters) imports both (1) and
(2), defines the transport-specific PM parameters and profiles
(see Section 4), and shows how the imported models are streamed on
common transport equipment.
This document imports the YANG modules of (1) and (2) and does not
modify them; module (2) imports the profile-names type from module
(1) and augments the "ietf-system-capabilities" module of [RFC9196].
The normative measurement and capability semantics remain in
[I-D.yoon-ippm-collection-measure] and
[I-D.yoon-ippm-collection-interval-capabilities]; this document adds
only the transport-specific parameter module (see Section 4.5) and
the applicability guidance.
3. Placement in the Transport Network Element
The generic models are implemented within the Equipment Management
Function (EMF) of a transport NE, as defined in ITU-T G.7710
Section 6.2. The collection measurement model
[I-D.yoon-ippm-collection-measure] provides the data structures, the
interval-capability model
[I-D.yoon-ippm-collection-interval-capabilities] advertises the
supported intervals, and the transport parameter module defined in
this document (see Section 4.5) lists the transport parameters that
the profiles refer to. The data is exposed at the NE management
interface and consumed by remote clients, as illustrated in Figure 2.
Yoon & You Expires 7 January 2027 [Page 5]
Internet-Draft PM Streaming Transport YANG July 2026
+------+ +-----+ +--------+
| OS | | NDT | ... | AI APP |
+---+--+ +--+--+ +----+---+
| | |
| PM data and notifications
| via YANG-Push (RFC 8639/8640/8641)
| | |
+---+--------+-------------+---+
| Transport NE |
| +-----------------------+ |
| | EMF / Collection | |
| | ietf-pm-collection(1)| |
| | + interval-caps (2) | |
| | + pm-parameters | |
| +-----------------------+ |
+------------------------------+
OS: Operations System
NDT: Network Digital Twins
APP: Application
Figure 2: PM streaming from a transport NE
4. Transport Common PM Parameters and Profiles
Metric values of PM parameters are measured for maintenance and QoS
monitoring over transport networks. Quality of Service (QoS)
parameters assess the network's long-term ability to deliver agreed-
upon service quality. They verify performance against contractual
obligations defined in service-level agreements (SLAs) over longer
intervals (24 hours, monthly periods). By simultaneously measuring
both directions of a bidirectional connection, QoS parameters provide
a holistic view of the sustained quality experienced by users.
Maintenance parameters focus on short-term monitoring and detailed
analysis for operational reliability. Over intervals such as 15
minutes or 24 hours, they enable swift responses to intermittent
faults, bursts of errors, and subtle performance changes.
Maintenance parameters typically involve unidirectional analysis,
where each direction of transmission is monitored independently.
This approach helps operators precisely pinpoint faults, troubleshoot
intermittent issues, and perform preventive maintenance effectively.
Key PM parameters for circuit-oriented transport networks such as OTN
are listed below. Additional parameters may be needed for packet
networks.
* ES -- Errored Seconds
Yoon & You Expires 7 January 2027 [Page 6]
Internet-Draft PM Streaming Transport YANG July 2026
* SES -- Severely Errored Seconds
* BBE -- Background Block Errors
* BBC -- Background Block Count
* UAS -- Unavailable Seconds
* SEP -- Severely Errored Period
* PJE -- Pointer Justification Events
According to collection types, purposes, and time intervals,
different parameters are used. The following three transport
profiles, named using the profile-naming format of the collection
measurement model [I-D.yoon-ippm-collection-measure], provide
comprehensive coverage for maintenance and QoS monitoring across
different temporal resolutions. The "transport" network token
indicates that a profile applies across multiple transport
technologies (for example OTN, MPLS-TP, and transport Ethernet).
4.1. itu-transport-maintenance-15min Profile
The "itu-transport-maintenance-15min" profile is designed for short-
term operational monitoring and rapid fault detection. It uses all
three collection types (counts, snapshot, and tidemarks) over
15-minute intervals. The profile includes core maintenance
parameters: ES, SES, BBE, BBC, and UAS.
The 15-minute interval enables operators to quickly detect and
respond to performance degradation, making it ideal for proactive
maintenance and immediate troubleshooting. The combination of counts
(for cumulative event tracking), snapshot (for instantaneous state
capture), and tidemarks (for extreme value monitoring) provides a
comprehensive view of network behaviour within each measurement
period. This profile is particularly valuable for network operations
centres (NOCs) requiring real-time visibility into transport network
health and for automated systems that need to trigger immediate
responses to performance anomalies.
4.2. itu-transport-maintenance-24hr Profile
The "itu-transport-maintenance-24hr" profile extends maintenance
monitoring to longer-term analysis and trend identification. Like
the 15-minute profile, it employs all three collection types (counts,
snapshot, and tidemarks) but over 24-hour intervals. The parameter
set includes ES, SES, BBE, BBC, UAS, and additionally PJE.
Yoon & You Expires 7 January 2027 [Page 7]
Internet-Draft PM Streaming Transport YANG July 2026
The 24-hour interval allows for comprehensive daily performance
analysis, enabling operators to identify patterns, trends, and
recurring issues not apparent in shorter intervals. The inclusion of
PJE provides additional insight into synchronisation-related
performance issues that are more relevant over longer observation
periods. This profile supports strategic maintenance planning,
capacity management, and historical performance analysis. It
complements the 15-minute profile by providing the broader context
needed for long-term network optimisation and preventive maintenance
strategies.
4.3. itu-transport-qos-24hr Profile
The "itu-transport-qos-24hr" profile is designed for QoS monitoring
and SLA compliance verification. Unlike the maintenance profiles, it
focuses exclusively on the counts collection type over 24-hour
intervals, emphasising sustained performance assessment rather than
detailed operational monitoring. The parameter set includes ES, SES,
BBE, BBC, SEP, and UAS.
The exclusive use of counts reflects its focus on cumulative
performance over extended periods, which is essential for SLA
compliance and service quality reporting. The 24-hour interval
aligns with typical SLA measurement periods and provides the
statistical basis for service quality assessments. The inclusion of
SEP is particularly relevant for QoS monitoring as it represents
sustained periods of degraded performance that directly impact
service quality commitments.
4.4. Profile Relationships and Operational Integration
These three profiles work together to provide a comprehensive
performance monitoring framework. The "itu-transport-maintenance-
15min" profile serves as the primary operational tool for immediate
network management, while the "itu-transport-maintenance-24hr"
profile provides the analytical foundation for strategic planning and
trend analysis. The "itu-transport-qos-24hr" profile ensures that
service quality commitments are met and provides the data necessary
for SLA reporting and customer assurance.
Yoon & You Expires 7 January 2027 [Page 8]
Internet-Draft PM Streaming Transport YANG July 2026
The hierarchical relationship between these profiles enables
operators to correlate short-term operational events with long-term
performance trends and service quality metrics. For example, a spike
in ES detected by the 15-minute maintenance profile can be correlated
with daily trends from the 24-hour maintenance profile and assessed
against SLA thresholds defined in the QoS profile. This integrated
approach supports both reactive troubleshooting and proactive network
optimisation while ensuring compliance with service quality
commitments.
4.5. Transport Parameter Module
The following module lists the transport performance parameters as
identities and provides the maintenance and QoS parameter containers
used by the profiles above. The tree diagram uses the notation
defined in [RFC8340].
module: ietf-pm-parameters
+--ro maintenance-parameters-15min
| +--ro es? uint32
| +--ro ses? uint32
| +--ro bbe? uint32
| +--ro bbc? uint32
| +--ro uas? uint32
+--ro maintenance-parameters-24hr
| +--ro es? uint32
| +--ro ses? uint32
| +--ro bbe? uint32
| +--ro bbc? uint32
| +--ro uas? uint32
| +--ro pje? uint32
+--ro qos-parameters-24hr
+--ro es? uint32
+--ro ses? uint32
+--ro bbe? uint32
+--ro bbc? uint32
+--ro uas? uint32
+--ro sep? uint32
<CODE BEGINS> file "ietf-pm-parameters@2026-06-03.yang"
module ietf-pm-parameters {
yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-pm-parameters";
prefix pm-param;
organization
"IETF Common Control and Measurement Plane (ccamp)
Working Group";
Yoon & You Expires 7 January 2027 [Page 9]
Internet-Draft PM Streaming Transport YANG July 2026
contact
"WG Web: <https://datatracker.ietf.org/wg/ccamp/>
Editor: Bin Yeong Yoon
<mailto:byyun@etri.re.kr>";
description
"This YANG module defines performance management parameters
for common transport equipment, based on ITU-T G.7710.
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-06-03 {
description
"Initial revision.";
reference
"RFC XXXX: A YANG Data Model for Performance Monitoring
Streaming on Common Transport Equipment";
}
identity performance-parameter {
description
"Base identity for performance monitoring parameters.";
}
identity es {
base performance-parameter;
description "Errored Second.";
}
identity ses {
base performance-parameter;
description "Severely Errored Second.";
}
identity bbe {
base performance-parameter;
description "Background Block Error.";
}
identity bbc {
base performance-parameter;
Yoon & You Expires 7 January 2027 [Page 10]
Internet-Draft PM Streaming Transport YANG July 2026
description "Background Block Count.";
}
identity uas {
base performance-parameter;
description "Unavailable Second.";
}
identity pje {
base performance-parameter;
description "Pointer Justification Event.";
}
identity sep {
base performance-parameter;
description "Severely Errored Period.";
}
container maintenance-parameters-15min {
config false;
description
"Transport maintenance parameters for the 15-minute
monitoring interval.";
leaf es {
type uint32;
units "seconds";
description "Errored Second.";
}
leaf ses {
type uint32;
units "seconds";
description "Severely Errored Second.";
}
leaf bbe {
type uint32;
units "errors";
description "Background Block Error.";
}
leaf bbc {
type uint32;
units "blocks";
description "Background Block Count.";
}
leaf uas {
type uint32;
units "seconds";
description "Unavailable Second.";
}
}
container maintenance-parameters-24hr {
Yoon & You Expires 7 January 2027 [Page 11]
Internet-Draft PM Streaming Transport YANG July 2026
config false;
description
"Transport maintenance parameters for the 24-hour
monitoring interval.";
leaf es {
type uint32;
units "seconds";
description "Errored Second.";
}
leaf ses {
type uint32;
units "seconds";
description "Severely Errored Second.";
}
leaf bbe {
type uint32;
units "errors";
description "Background Block Error.";
}
leaf bbc {
type uint32;
units "blocks";
description "Background Block Count.";
}
leaf uas {
type uint32;
units "seconds";
description "Unavailable Second.";
}
leaf pje {
type uint32;
units "events";
description "Pointer Justification Event.";
}
}
container qos-parameters-24hr {
config false;
description
"Transport QoS parameters for the 24-hour monitoring
interval.";
leaf es {
type uint32;
units "seconds";
description "Errored Second.";
}
leaf ses {
type uint32;
Yoon & You Expires 7 January 2027 [Page 12]
Internet-Draft PM Streaming Transport YANG July 2026
units "seconds";
description "Severely Errored Second.";
}
leaf bbe {
type uint32;
units "errors";
description "Background Block Error.";
}
leaf bbc {
type uint32;
units "blocks";
description "Background Block Count.";
}
leaf uas {
type uint32;
units "seconds";
description "Unavailable Second.";
}
leaf sep {
type uint32;
units "periods";
description "Severely Errored Period.";
}
}
}
<CODE ENDS>
5. Use Cases: Streaming a Transport Profile
This section shows the end-to-end flow for a transport profile, from
capability discovery to subscription, notification, and threshold
reporting. The examples use the SES parameter of the "itu-transport-
maintenance-15min" profile.
5.1. Step 1: Discover Supported Intervals
The client first reads the interval capabilities
[I-D.yoon-ippm-collection-interval-capabilities] for the parameter,
to learn which sampling and collection intervals the transport NE
supports. These capabilities are advertised by augmenting the "ietf-
system-capabilities" container of [RFC9196], so the client retrieves
them under "system-capabilities", the same anchor used for
subscription and notification capabilities.
Yoon & You Expires 7 January 2027 [Page 13]
Internet-Draft PM Streaming Transport YANG July 2026
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"
xmlns:sysc=
"urn:ietf:params:xml:ns:yang:ietf-system-capabilities"
xmlns:ipc=
"urn:ietf:params:xml:ns:yang:ietf-pm-interval-capabilities"
message-id="301">
<get>
<filter>
<sysc:system-capabilities>
<ipc:pm-interval-capabilities>
<parameter-profile>
<name>itu-transport-maintenance-15min</name>
<pm-parameter>
<name>ses</name>
<interval-relationships>
<sampling-interval>
<id>1s</id>
<min-value>1</min-value>
<max-value>1</max-value>
<units>second</units>
<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>
<granularity>5</granularity>
</collection-interval>
</sampling-interval>
</interval-relationships>
</pm-parameter>
</parameter-profile>
</ipc:pm-interval-capabilities>
</sysc:system-capabilities>
</filter>
</get>
</rpc>
Figure 3: Capability discovery for a transport parameter
The response shows that the NE supports 1-second sampling and a
collection interval range of 5 to 1440 minutes with 5-minute
granularity, defaulting to 15 minutes. The client therefore selects
a 1-second sampling interval and a 15-minute collection interval,
which the NE supports.
Yoon & You Expires 7 January 2027 [Page 14]
Internet-Draft PM Streaming Transport YANG July 2026
5.2. Step 2: Subscribe to Periodic Measurement
Using the supported intervals, the client establishes a YANG-Push
[RFC8641] subscription to the counts measurement value, with the
period set to 900 seconds so that a notification is sent at the end
of each 15-minute interval.
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"
xmlns:sn=
"urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications"
xmlns:pm-coll=
"urn:ietf:params:xml:ns:yang:ietf-pm-collection"
message-id="101">
<sn:establish-subscription>
<sn:stream>YANG-PUSH</sn:stream>
<sn:encoding>encode-xml</sn:encoding>
<sn:filter>
<sn:datastore>operational</sn:datastore>
<sn:xpath-filter>
/pm-coll:pm-periodic-collection/
parameter-profile[name='itu-transport-maintenance-15min']/
pm-parameter[name='ses']/
sampling-interval[id='1s']/
collection-interval[id='15min']/
collection-types/counts/collection-value
</sn:xpath-filter>
</sn:filter>
<sn:period>900</sn:period>
<sn:anchor-time>2026-07-01T00:00:00Z</sn:anchor-time>
</sn:establish-subscription>
</rpc>
Figure 4: Subscription to a transport profile parameter
5.3. Step 3: Receive Periodic Notification
At the end of each interval the NE sends a notification. The
measured value of 5 is the total severely errored seconds in the
period.
Yoon & You Expires 7 January 2027 [Page 15]
Internet-Draft PM Streaming Transport YANG July 2026
<notification
xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0"
xmlns:pm-coll=
"urn:ietf:params:xml:ns:yang:ietf-pm-collection">
<eventTime>2026-07-01T00:15:00Z</eventTime>
<pm-coll:pm-periodic-collection>
<parameter-profile>
<name>itu-transport-maintenance-15min</name>
<pm-parameter>
<name>ses</name>
<sampling-interval>
<id>1s</id>
<interval-value>1</interval-value>
<unit>second</unit>
<collection-interval>
<id>15min</id>
<interval-value>15</interval-value>
<unit>minute</unit>
<collection-types>
<counts>
<collection-value>5</collection-value>
</counts>
</collection-types>
</collection-interval>
</sampling-interval>
</pm-parameter>
</parameter-profile>
</pm-coll:pm-periodic-collection>
</notification>
Figure 5: Periodic notification for the transport profile
5.4. Step 4: Threshold Reporting
The client can also subscribe to threshold events. When the counts
value crosses the configured transient threshold during the interval,
a Threshold Report is delivered using the "pm-threshold-events"
notification of the collection measurement model. No transport-
specific event mechanism is required.
Yoon & You Expires 7 January 2027 [Page 16]
Internet-Draft PM Streaming Transport YANG July 2026
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"
xmlns:sn=
"urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications"
message-id="102">
<sn:establish-subscription>
<sn:stream>YANG-PUSH</sn:stream>
<sn:encoding>encode-xml</sn:encoding>
<sn:filter>
<sn:datastore>operational</sn:datastore>
<sn:subtree-filter>
<pm-threshold-events
xmlns="urn:ietf:params:xml:ns:yang:ietf-pm-collection"/>
</sn:subtree-filter>
</sn:filter>
</sn:establish-subscription>
</rpc>
Figure 6: Subscription to threshold events
<notification
xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0"
xmlns:pm-coll=
"urn:ietf:params:xml:ns:yang:ietf-pm-collection">
<eventTime>2026-07-01T00:09:00Z</eventTime>
<pm-coll:pm-threshold-events>
<periodic-events>
<parameter-profile>
<name>itu-transport-maintenance-15min</name>
<pm-parameter>
<name>ses</name>
<sampling-interval>
<id>1s</id>
<collection-interval>
<id>15min</id>
<event-types>
<counts-transient>
<event-type>transient</event-type>
<event-occurred>true</event-occurred>
<event-time>2026-07-01T00:09:00Z</event-time>
</counts-transient>
</event-types>
</collection-interval>
</sampling-interval>
</pm-parameter>
</parameter-profile>
</periodic-events>
</pm-coll:pm-threshold-events>
</notification>
Yoon & You Expires 7 January 2027 [Page 17]
Internet-Draft PM Streaming Transport YANG July 2026
Figure 7: Transient threshold notification
6. Streaming Considerations for Transport Equipment
On transport equipment the following points apply. Collection
intervals should align with the NE clock source so that interval
boundaries are consistent across the network and snapshots taken at a
uniform time can be correlated across NEs. A transport NE may serve
many parameters across many monitored objects (links, tunnels,
equipment sensors), so operators should consider the load of large
numbers of concurrent subscriptions and choose profiles and intervals
accordingly. Threshold events, both periodic and the non-periodic
BUT, EUT, and CSES events, are carried in the notification defined by
the collection measurement model.
7. Security Considerations
This document is informational. It defines one YANG module of
transport parameters; all of its nodes are read-only ("config false")
and are designed to be accessed via NETCONF [RFC6241] or RESTCONF
over a secure transport such as SSH, with access restricted using the
Network Configuration Access Control Model (NACM) [RFC8341]. The
security considerations of the underlying models
[I-D.yoon-ippm-collection-measure]
[I-D.yoon-ippm-collection-interval-capabilities] and of the YANG-Push
framework [RFC8639] [RFC8641] apply. The exposed performance and
capability data can reveal information about the transport network;
operators may wish to restrict access accordingly.
8. 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-parameters
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-parameters
Namespace: urn:ietf:params:xml:ns:yang:ietf-pm-parameters
Prefix: pm-param
Reference: RFC XXXX
9. References
Yoon & You Expires 7 January 2027 [Page 18]
Internet-Draft PM Streaming Transport YANG July 2026
9.1. Normative 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>.
[I-D.yoon-ippm-collection-interval-capabilities]
Yoon, B. Y., "A YANG Data Model for PM Collection Interval
Capabilities", Work in Progress, Internet-Draft, draft-
yoon-ippm-collection-interval-capabilities-00, 2026,
<https://datatracker.ietf.org/doc/html/draft-yoon-ippm-
collection-interval-capabilities-00>.
[I-D.yoon-ippm-collection-measure]
Yoon, B. Y., "A YANG Data Model of Collection
Measurement", Work in Progress, Internet-Draft, draft-
yoon-ippm-collection-measure-00, 2026,
<https://datatracker.ietf.org/doc/html/draft-yoon-ippm-
collection-measure-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>.
[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>.
[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>.
Yoon & You Expires 7 January 2027 [Page 19]
Internet-Draft PM Streaming Transport YANG July 2026
[RFC8639] Voit, E., Clemm, A., Gonzalez Prieto, A., Nilsen-Nygaard,
E., and A. Tripathy, "Subscription to YANG Notifications",
RFC 8639, DOI 10.17487/RFC8639, September 2019,
<https://www.rfc-editor.org/rfc/rfc8639>.
[RFC8640] Voit, E., Clemm, A., Gonzalez Prieto, A., Nilsen-Nygaard,
E., and A. Tripathy, "Dynamic Subscription to YANG Events
and Datastores over NETCONF", RFC 8640,
DOI 10.17487/RFC8640, September 2019,
<https://www.rfc-editor.org/rfc/rfc8640>.
[RFC8641] Clemm, A. and E. Voit, "Subscription to YANG Notifications
for Datastore Updates", RFC 8641, DOI 10.17487/RFC8641,
September 2019, <https://www.rfc-editor.org/rfc/rfc8641>.
9.2. Informative References
[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>.
Acknowledgments
This document is derived from draft-yoon-ccamp-pm-streaming, whose
content it carries forward as the transport-equipment instantiation
of the generic collection measurement models.
Authors' Addresses
Bin Yeong Yoon
ETRI
Email: byyun@etri.re.kr
Youngkil You
woori-net
Email: young@woori-net.com
Yoon & You Expires 7 January 2027 [Page 20]