← Reading listAgendaReviewdatatracker ↗ draft-ietf-bpm-on-path-telemetry-yang-00 · bpm · 29 pp · 2026-10-30 · offline copy



BPM                                                          G. Fioccola
Internet-Draft                                                   T. Zhou
Intended status: Standards Track                                  Huawei
Expires: 3 May 2027                                               Y. Zhu
                                                                W. Zhang
                                                           China Telecom
                                                           A. Huang Feng
                                                        Deutsche Telekom
                                                                  K. Zhu
                                                     Huawei Technologies
                                                         30 October 2026


                   On-Path Telemetry YANG Data Models
                draft-ietf-bpm-on-path-telemetry-yang-00

Abstract

   This document defines two YANG data models for monitoring On-Path
   network performance information to be published in YANG
   notifications.  The Alternate-Marking Method and In-situ Operations,
   Administration, and Maintenance (IOAM) are the On-Path hybrid
   measurement methods considered in this document.

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 3 May 2027.

Copyright Notice

   Copyright (c) 2026 IETF Trust and the persons identified as the
   document authors.  All rights reserved.






Fioccola, et al.           Expires 3 May 2027                   [Page 1]

Internet-Draft           yang-on-path-telemetry             October 2026


   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
     1.2.  Conventions . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Use Case  . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  On-Path Telemetry Tree Diagrams . . . . . . . . . . . . . . .   4
   4.  On-Path Telemetry Augmentation  . . . . . . . . . . . . . . .   6
   5.  On-Path Telemetry Modules . . . . . . . . . . . . . . . . . .   8
     5.1.  AltMark Telemetry YANG Data Model . . . . . . . . . . . .   8
     5.2.  IOAM Telemetry YANG Data Model  . . . . . . . . . . . . .  14
   6.  Operational Considerations  . . . . . . . . . . . . . . . . .  21
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  21
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  22
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  23
   10. Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  23
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  23
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  23
     11.2.  Informative References . . . . . . . . . . . . . . . . .  25
   Appendix A.  Examples . . . . . . . . . . . . . . . . . . . . . .  27
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  28

1.  Introduction

   Alternate-Marking Method [RFC9341] [RFC9342] (AltMark) is a technique
   used to perform packet loss, delay, and jitter measurements on in-
   flight packets.  In-situ Operations, Administration, and Maintenance
   (IOAM) is a method to produce operational and telemetry information
   that may be exported using the in-band or out-of-band method.  The
   data types and data formats for IOAM data records have been defined
   in [RFC9197] [RFC9326].

   This document defines two YANG data models for monitoring On-Path
   telemetry information of Alternate Marking Method and IOAM.  It
   provides YANG data models with performance monitoring parameters that
   can be subscribed to for monitoring and telemetry via YANG-Push
   specified in [RFC8639], [RFC8640] and [RFC8641].





Fioccola, et al.           Expires 3 May 2027                   [Page 2]

Internet-Draft           yang-on-path-telemetry             October 2026


   This document uses the existing mechanisms of [RFC9341], [RFC9342],
   [RFC9197], [RFC9326] to monitor the performance of the network and
   connectivity services.

   Section 3 includes the tree diagrams, while Section 5 includes the
   data models.  Also, an example is reported in Appendix A.

1.1.  Requirements Language

   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.  Conventions

   The following terms are defined in [RFC7950] and are used in this
   specification:

   *  augment

   *  data model

   *  data node

   The terminology for describing YANG data models is found in
   [RFC7950].

2.  Use Case

   Some applications may use the subscription model specified in
   [RFC8641] to subscribe to the On-Path telemetry network performance
   data.  For example, Network Telemetry [RFC9232] updates may be
   subscribed to YANG-Push on-change notifications [RFC8641] for state
   changes.  YANG-Push periodic notifications [RFC8641] can be
   subscribed to obtain real-time performance data.

   There is a need for real-time traffic monitoring of the network to
   optimize the network performance.  The next figure shows an example
   of a high-level workflow for dynamic network control based on traffic
   monitoring that could use the mechanism described in this document.









Fioccola, et al.           Expires 3 May 2027                   [Page 3]

Internet-Draft           yang-on-path-telemetry             October 2026


        +---------------------------------------------------+
        |              Orchestrator/Controller              |
        +---------------------------------------------------+
                |  /|\                     |  /|\
        Monitor |   | Monitor              |   |
        Request |   | Result      Possible |   |
                |   |         Optimization |   | Optimization
               \|/  |                     \|/  | Result
        +---------------------------------------------------+
        |                      Network                      |
        +---------------------------------------------------+

      Figure 1: Workflow for dynamic network control based on traffic
                                 monitoring

   The Controller sends a Monitor Request and receives Monitor Result.
   Because of this Closed-Loop approach, the controller can take
   Optimization actions, that can be related to forwarding path
   modification or performance measurements variation
   ([I-D.ietf-bpm-alt-mark-yang]), as also described in [RFC9342] with
   regard to the flexible and adaptive performance measurements.

3.  On-Path Telemetry Tree Diagrams

   Tree diagrams used in this document follow the notation defined in
   [RFC8340].

   The On-Path Telemetry models are organized as shown in the following
   figure.  These models augments the AltMark model in
   [I-D.ietf-bpm-alt-mark-yang] and the IOAM model in [RFC9617].

   The following tree diagram provides an overview of the AltMark
   Telemetry model.


















Fioccola, et al.           Expires 3 May 2027                   [Page 4]

Internet-Draft           yang-on-path-telemetry             October 2026


      module: altmark-telemetry

        augment /altmark:altmark:
          +--ro altmark-info
             +--ro timestamp-type?             identityref

        augment /altmark:altmark/altmark:available-interfaces
                /altmark:available-interface/altmark:altmark-profiles
                /altmark:altmark-profile:
          +--ro measurement-period-number?     uint32
          +--ro altmark-loss-measurement
          |  +--ro loss-flag?                  boolean
          |  +--ro in-traffic-pkts?            yang:counter64
          |  +--ro out-traffic-pkts?           yang:counter64
          |  +--ro in-traffic-bytes?           uint64
          |  +--ro out-traffic-bytes?          uint64
          +--ro altmark-delay-measurement
          |  +--ro delay-flag?                 boolean
          |  +--ro in-pkts-timestamps?
          |  |  +--ro in-pkt-timestamp?        yang:date-and-time
          |  |  +--ro in-pkt-seq-num?          uint32
          |  +--ro out-pkts-timestamps?
          |     +--ro out-pkt-timestamp?       yang:date-and-time
          |     +--ro out-pkt-seq-num?         uint32
          +--ro path-delay-measurement
             +--ro path-delay-mean?            uint32
             +--ro path-delay-min?             uint32
             +--ro path-delay-max?             uint32
             +--ro path-delay-sum?             uint64


   The following tree diagram provides an overview of the IOAM Telemetry
   model.


















Fioccola, et al.           Expires 3 May 2027                   [Page 5]

Internet-Draft           yang-on-path-telemetry             October 2026


         module: ioam-telemetry

           augment /ioam:ioam/ioam:profiles/ioam:profile:
             +--ro available-interface*           [if-name]
                +--ro if-name                     if:interface-ref
                +--ro ioam-incremental-tracing
                |  +--ro incremental-tracing*     ioam-trace-data
                +--ro ioam-preallocated-tracing
                |  +--ro preallocated-tracing*    ioam-trace-data
                +--ro ioam-direct-export
                |  +--ro direct-export*           ioam-trace-data
                +--ro ioam-proof-of-transit
                |  +--ro proof-of-transit*        ioam-pot-data
                +--ro ioam-edge-to-edge
                |  +--ro edge-to-edge*            ioam-e2e-data
                +--ro path-delay-measurement
                   +--ro path-delay-mean?         uint32
                   +--ro path-delay-min?          uint32
                   +--ro path-delay-max?          uint32
                   +--ro path-delay-sum?          uint64


4.  On-Path Telemetry Augmentation

   The AltMark Telemetry model and IOAM Telemetry model contain detailed
   information for the AltMark telemetry data and IOAM telemetry data.
   The information includes:

   The "altmark-info" is a container for all the read only information
   that assists monitoring systems in the interpretation of the AltMark
   data.

   For AltMark, the module defines the following attributes for on-path
   telemetry:

   *  measurement-period-number: indicates the period number and it is
      defined in [I-D.ietf-ippm-alt-mark-deployment].  Note that it
      corresponds to the altmarkPeriodNumber parameter defined in
      [I-D.ietf-opsawg-ipfix-alt-mark].

   *  altmark-loss-measurement: indicates loss counters.

   *  altmark-delay-measurement: indicates packet timestamps.

   The "altmark-loss-measurement" contains:






Fioccola, et al.           Expires 3 May 2027                   [Page 6]

Internet-Draft           yang-on-path-telemetry             October 2026


   *  loss-flag: indicates the loss flag.  It is defined in [RFC9343]
      for IPv6, in [RFC9947] for SRH and in [RFC9714] for MPLS.  Note
      that it corresponds to the altmarkLossFlag parameter defined in
      [I-D.ietf-opsawg-ipfix-alt-mark].

   *  in-traffic-pkts: indicates the inbound packets of the period.

   *  out-traffic-pkts: indicates the outbound packets of the period.

   *  in-traffic-bytes: indicates the inbound bytes of the period.

   *  out-traffic-bytes: indicates the outbound bytes of the period.

   The "altmark-delay-measurement" contains:

   *  delay-flag: indicates the delay flag.  It is defined in [RFC9343]
      for IPv6, in [RFC9947] for SRH and in [RFC9714] for MPLS.  Note
      that it corresponds to the altmarkDelayFlag parameter defined in
      [I-D.ietf-opsawg-ipfix-alt-mark].

   *  pkts-timestamps: indicates the list of packet timestamps for delay
      measurement in the period (pkt-timestamp) and the corresponding
      sequence numbers (pkt-seq-num).

   The "path-delay-measurement" is introduced in [RFC9951] and contains:

   *  path-delay-mean: indicates the mean path delay between the
      encapsulation/marking node and the local node.

   *  path-delay-min: indicates the lowest path delay between the
      encapsulation/marking node and the local node.

   *  path-delay-max: indicates the highest path delay between the
      encapsulation/marking node and the local node.

   *  path-delay-sum: indicates the sum of the path delay between the
      encapsulation/marking node and the local node.

   For IOAM, the module defines the following attributes for on-path
   telemetry:

   *  available-interface: indicates the list of interface where the On-
      Path Telemetry is applied.

   The "available-interface" contains the detailed information for each
   interface.  The information includes:

   *  if-name: is the interface name



Fioccola, et al.           Expires 3 May 2027                   [Page 7]

Internet-Draft           yang-on-path-telemetry             October 2026


   *  "ioam-incremental-tracing", that contains:

      -  incremental-tracing: indicates the list of incremental tracing
         data.

   *  "ioam-preallocated-tracing", that contains:

      -  preallocated-tracing: indicates the list of preallocated
         tracing data.

   *  "ioam-direct-export", that contains:

      -  direct-export: indicates the list of direct export data.

   *  "ioam-proof-of-transit", that contains:

      -  proof-of-transit: indicates the list of proof of transit data.

   *  "ioam-edge-to-edge", that contains:

      -  edge-to-edge: indicates the list of edge to edge data.

5.  On-Path Telemetry Modules

5.1.  AltMark Telemetry YANG Data Model

   <CODE BEGINS> file "ietf-altmark-telemetry@2026-10-30.yang"
   module ietf-altmark-telemetry {
     yang-version 1.1;
     namespace "urn:ietf:params:xml:ns:yang:ietf-altmark-telemetry";
     prefix "altmark-telemetry";

     import ietf-yang-types {
       prefix yang;
       reference
         "Section 3 of RFC 9911";
     }

     import ietf-altmark {
       prefix altmark;
       reference
         "draft-ietf-bpm-alt-mark-yang";
     }

     import ietf-lime-time-types {
       prefix lime;
       reference
         "RFC 8532: Generic YANG Data Model for the Management of



Fioccola, et al.           Expires 3 May 2027                   [Page 8]

Internet-Draft           yang-on-path-telemetry             October 2026


          Operations, Administration, and Maintenance (OAM) Protocols
          That Use Connectionless Communications";
     }

     organization
       "IETF BPM (Benchmarking & Performance Measurements) Working Group";

     contact
       "WG Web: <https://datatracker.ietf.org/wg/bpm>
        WG List: <bpm@ietf.org>
        Author: giuseppe.fioccola@huawei.com
        Author: zhoutianran@huawei.com
        Author: zhuyq8@chinatelecom.cn
        Author: zhangwq@chinatelecom.cn
        Author: alex.huang-feng@t-systems.com
        Author: zhukeyi@huawei.com";

     description
       "This YANG module specifies vendor-independent data model
        for AltMark Telemetry.

        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-30 {
       description "First revision.";
       reference "RFC XXXX: YANG Data Models for On-path Telemetry";
     }

    /*
     * FEATURES



Fioccola, et al.           Expires 3 May 2027                   [Page 9]

Internet-Draft           yang-on-path-telemetry             October 2026


     */

     feature pathdelay {
       description
         "This feature indicates that the Path Delay is
          supported.";
       reference
         "RFC 9951: Export of Delay Performance Metrics in IPFIX";
     }

    /*
     * GROUP DEFINITIONS
     */

     grouping loss-counters {
       description
         "The set of counters for RFC 9341 and RFC 9342 loss
          calculation.";

       leaf loss-flag {
         type boolean;
         config false;
         description
           "The loss-flag value is defined in RFC 9343 and RFC 9714.
            Note that it corresponds to the altmarkLossFlag parameter
            defined in draft-ietf-opsawg-ipfix-alt-mark.";
       }

       leaf in-traffic-pkts {
         type yang:counter64;
         config false;
         description
           "Total inbound packets of the period according to RFC 9341
            and RFC 9342";
       }

       leaf out-traffic-pkts {
         type yang:counter64;
         config false;
         description
           "Total outbound packets of the period according to RFC 9341
            and RFC 9342";
       }

       leaf in-traffic-bytes {
         type uint64;
         units "bytes";
         config false;



Fioccola, et al.           Expires 3 May 2027                  [Page 10]

Internet-Draft           yang-on-path-telemetry             October 2026


         description
           "Total inbound bytes of the period according to RFC 9341
            and RFC 9342";
       }

       leaf out-traffic-bytes {
         type uint64;
         units "bytes";
         config false;
         description
           "Total outbound bytes of the period according to RFC 9341
            and RFC 9342";
       }
     }

     grouping delay-timestamps {
       description
         "It indicates the set of timestamps for RFC 9341 and RFC 9342
          delay calculation.";

       leaf delay-flag {
         type boolean;
         config false;
         description
           "The delay-flag value is defined in RFC 9343 and RFC 9714.
            Note that it corresponds to the altmarkDelayFlag parameter
            defined in draft-ietf-opsawg-ipfix-alt-mark.";
       }

       container in-pkts-timestamps {
         config false;
         description
           "The list of timestamps of the period according to RFC 9341
            and RFC 9342";

         leaf in-pkt-timestamp {
           type yang:date-and-time;
           description
             "To specify the timestamp of the delay packet for delay
              measurements";
         }

         leaf in-pkt-seq-num {
           type uint32;
           description
             "To specify the sequence number of the delay packet for
              delay measurements";
         }



Fioccola, et al.           Expires 3 May 2027                  [Page 11]

Internet-Draft           yang-on-path-telemetry             October 2026


       }

       container out-pkts-timestamps {
         config false;
         description
           "The list of timestamps of the period according to RFC 9341
            and RFC 9342";

         leaf out-pkt-timestamp {
           type yang:date-and-time;
           description
             "To specify the timestamp of the delay packet for delay
              measurements";
         }

         leaf out-pkt-seq-num {
           type uint32;
           description
             "To specify the sequence number of the delay packet for
              delay measurements";
         }
       }
     }

     grouping path-delay-metrics {
       description
         "It indicates the path delay measurements.";

       leaf path-delay-mean {
         type uint32;
         units "microseconds";
         config false;
         description
           "mean path delay as per RFC 9951";
       }
       leaf path-delay-min {
         type uint32;
         units "microseconds";
         config false;
         description
           "min path delay as per RFC 9951";
       }

       leaf path-delay-max {
         type uint32;
         units "microseconds";
         config false;
         description



Fioccola, et al.           Expires 3 May 2027                  [Page 12]

Internet-Draft           yang-on-path-telemetry             October 2026


           "max path delay as per RFC 9951";
       }

       leaf path-delay-sum {
         type uint64;
         units "microseconds";
         config false;
         description
           "sum of the path delay as per RFC 9951";
       }
     }

    /*
     * DATA NODES
     */

     augment "/altmark:altmark" {
       description "Augments the AltMark with timestamp information";

       container altmark-info {
         config false;
         description
           "Describes information such as units or timestamp format
           that assists monitoring systems in the interpretation of the
           on-path-telemetry data.";

         leaf timestamp-type {
           type identityref {
             base lime:timestamp-type;
           }
           description
             "Type of timestamp, such as Truncated PTP or NTP.";
         }
       }
     }

     augment "/altmark:altmark/altmark:available-interfaces/"
           + "altmark:available-interface/altmark:altmark-profiles/"
           + "altmark:altmark-profile" {
       description "Augments the AltMark with the On-path Telemetry data";

       leaf measurement-period-number {
         type uint32;
         config false;
         description
           "It specifies the On-path Telemetry period number.";
       }




Fioccola, et al.           Expires 3 May 2027                  [Page 13]

Internet-Draft           yang-on-path-telemetry             October 2026


       container altmark-loss-measurement {
         if-feature altmark:altmark;
         presence
           "Present when AltMark loss measurement is enabled.";
         description
           "It reports the loss measurement data.";

         uses loss-counters;
       }

       container altmark-delay-measurement {
         if-feature altmark:altmark;
         presence
           "Present when AltMark delay measurement is enabled.";
         description
           "It reports the delay measurement data.";

         uses delay-timestamps;
       }

       container path-delay-measurement {
         if-feature pathdelay;
         description
           "It reports the path delay measurement data.";

         uses path-delay-metrics;
       }
     }
   }
   <CODE ENDS>


5.2.  IOAM Telemetry YANG Data Model

   <CODE BEGINS> file "ietf-ioam-telemetry@2026-10-30.yang"
   module ietf-ioam-telemetry {
     yang-version 1.1;
     namespace "urn:ietf:params:xml:ns:yang:ietf-ioam-telemetry";
     prefix "ioam-telemetry";

     import ietf-interfaces {
       prefix if;
       reference
         "RFC 8343: A YANG Data Model for Interface Management";
     }

     import ietf-ioam {
       prefix ioam;



Fioccola, et al.           Expires 3 May 2027                  [Page 14]

Internet-Draft           yang-on-path-telemetry             October 2026


       reference
         "RFC 9617";
     }

     organization
       "IETF BPM (Benchmarking & Performance Measurements) Working Group";

     contact
       "WG Web: <https://datatracker.ietf.org/wg/bpm>
        WG List: <bpm@ietf.org>
        Author: giuseppe.fioccola@huawei.com
        Author: zhoutianran@huawei.com
        Author: zhuyq8@chinatelecom.cn
        Author: zhangwq@chinatelecom.cn
        Author: alex.huang-feng@t-systems.com
        Author: zhukeyi@huawei.com";

     description
       "This YANG module specifies vendor-independent data model
        for IOAM Telemetry.

        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-30 {
       description "First revision.";
       reference "RFC XXXX: YANG Data Models for On-path Telemetry";
     }

    /*
     * FEATURES



Fioccola, et al.           Expires 3 May 2027                  [Page 15]

Internet-Draft           yang-on-path-telemetry             October 2026


     */

     feature pathdelay {
       description
         "This feature indicates that the Path Delay is
          supported.";
       reference
         "RFC 9951: Export of Delay Performance Metrics in IPFIX";
     }

    /*
     * IDENTITIES
     */

     identity trace-data {
       description
         "IOAM trace data as defined in RFC 9197.";
     }

     identity pot-data {
       description
         "IOAM pot data as defined in RFC 9197.";
     }

     identity e2e-data {
       description
         "IOAM edge-to-edge data as defined in RFC 9197.";
     }

    /*
     * TYPE DEFINITIONS
     */

     typedef ioam-trace-data {
       type identityref {
         base trace-data;
       }
       description
         "It specifies the trace data.";
     }

     typedef ioam-pot-data {
       type identityref {
         base pot-data;
       }
       description
         "It specifies the pot data.";
     }



Fioccola, et al.           Expires 3 May 2027                  [Page 16]

Internet-Draft           yang-on-path-telemetry             October 2026


     typedef ioam-e2e-data {
       type identityref {
         base e2e-data;
       }
       description
         "It specifies the edge-to-edge data.";
     }

    /*
     * GROUP DEFINITIONS
     */

     grouping path-delay-metrics {
       description
         "It indicates the path delay measurements.";

       leaf path-delay-mean {
         type uint32;
         units "microseconds";
         config false;
         description
           "mean path delay as per RFC 9951";
       }
       leaf path-delay-min {
         type uint32;
         units "microseconds";
         config false;
         description
           "min path delay as per RFC 9951";
       }

       leaf path-delay-max {
         type uint32;
         units "microseconds";
         config false;
         description
           "max path delay as per RFC 9951";
       }

       leaf path-delay-sum {
         type uint64;
         units "microseconds";
         config false;
         description
           "sum of the path delay as per RFC 9951";
       }
     }




Fioccola, et al.           Expires 3 May 2027                  [Page 17]

Internet-Draft           yang-on-path-telemetry             October 2026


     grouping ioam-incremental-tracing-data-list {
       description
         "A grouping for incremental tracing data.";

       leaf-list incremental-tracing {
         type ioam-trace-data;
         config false;
         description
           "This object indicates the incremental tracing data.";
       }
     }

     grouping ioam-preallocated-tracing-data-list {
       description
         "A grouping for the list of pre-allocated tracing data.";

       leaf-list preallocated-tracing {
         type ioam-trace-data;
         config false;
         description
           "This object indicates the preallocated tracing data.";
       }
     }

     grouping ioam-direct-export-tracing-data-list {
       description
         "A grouping for the list of direct export data.";

       leaf-list direct-export {
         type ioam-trace-data;
         config false;
         description
           "This object indicates the direct export data.";
       }
     }

     grouping ioam-proof-of-transit-data-list {
       description
         "A grouping for the list of proof of transit data.";

       leaf-list proof-of-transit {
         type ioam-pot-data;
         config false;
         description
           "This object indicates the proof of transit data.";
       }
     }




Fioccola, et al.           Expires 3 May 2027                  [Page 18]

Internet-Draft           yang-on-path-telemetry             October 2026


     grouping ioam-edge-to-edge-data-list {
       description
         "A grouping for the list of edge-to-edge data.";

       leaf-list edge-to-edge {
         type ioam-e2e-data;
         config false;
         description
           "This object indicates the edge to edge data.";
       }
     }

    /*
     * DATA NODES
     */

     augment "/ioam:ioam/ioam:profiles/ioam:profile" {
       description "Augments the AltMark with the On-path Telemetry data";

       list available-interface {
         key "if-name";
         description
           "It contains the list of the interfaces activated for
            Telemetry";
         leaf if-name {
           type if:interface-ref;
           description "This is a reference to the Interface name.";
         }

         container ioam-incremental-tracing {
           if-feature ioam:incremental-trace;
           presence
             "Present when incremental tracing option is available.";
           description
             "It reports the incremental tracing option data.";

           uses ioam-incremental-tracing-data-list;
         }

         container ioam-preallocated-tracing {
           if-feature ioam:preallocated-trace;
           presence
             "Present when preallocated tracing option is available.";
           description
             "It reports the preallocated tracing option data.";

           uses ioam-preallocated-tracing-data-list;
         }



Fioccola, et al.           Expires 3 May 2027                  [Page 19]

Internet-Draft           yang-on-path-telemetry             October 2026


         container ioam-direct-export {
           if-feature ioam:direct-export;
           presence
             "Present when direct-export option is available.";
           description
             "It reports the direct-export option data";

           uses ioam-direct-export-tracing-data-list;
         }

         container ioam-proof-of-transit {
           if-feature ioam:proof-of-transit;
           presence
             "Present when proof of transit option is available.";
           description
             "It reports the PoT option data.";

           uses ioam-proof-of-transit-data-list;
         }

         container ioam-edge-to-edge {
           if-feature ioam:edge-to-edge;
           presence
             "Present when edge-to-edge option is available.";
           description
             "It reports the edge-to-edge option data.";

           uses ioam-edge-to-edge-data-list;
         }

         container path-delay-measurement {
           if-feature pathdelay;
           description
             "It reports the path delay measurement data.";

           uses path-delay-metrics;
         }
       }
     }
   }
   <CODE ENDS>










Fioccola, et al.           Expires 3 May 2027                  [Page 20]

Internet-Draft           yang-on-path-telemetry             October 2026


6.  Operational Considerations

   The operational and management considerations for the Alternate
   Marking Method are covered in [I-D.ietf-ippm-alt-mark-deployment],
   Alternate Marking [RFC9341] and Multipoint Alternate Marking
   [RFC9342].

   Section 9 of [I-D.ietf-ippm-alt-mark-deployment] explains how to
   operate the measurement domain and also provides the operational
   guidelines for time synchronization, configuration and data export.
   It is also mentioned the applicability of the configuration
   parameters and the exporting values within the measurement domain.

   Further details about the method operation are specified for the
   different extensions: IPv6 [RFC9343], SRH [RFC9947], and MPLS
   [RFC9714].

   Note that, in general, it might be possible to take into account the
   counters handling and choose to reset them regularly regularly, if
   needed.

7.  Security Considerations

   The "ietf-altmark-telemetry" and "ietf-ioam-telemetry" YANG modules
   defines two data models that are designed to be accessed via YANG-
   based management protocols, such as NETCONF [RFC6241] and RESTCONF
   [RFC8040].  These YANG-based management protocols (1) have to use a
   secure transport layer (e.g., Secure Shell (SSH) [RFC4252], TLS
   [RFC8446], and QUIC [RFC9000]) and (2) have to use mutual
   authentication.

   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.

   There are a number of data nodes defined in this YANG module but they
   are only readable.  However, these data nodes may be considered
   sensitive or vulnerable in some network environments.  These are the
   subtrees and data nodes and their sensitivity/vulnerability:

   *  /altmark/available-interfaces/available-interface/altmark-profiles
      /altmark-profile/altmark-loss-measurement

   *  /altmark/available-interfaces/available-interface/altmark-profiles
      /altmark-profile/altmark-delay-measurement





Fioccola, et al.           Expires 3 May 2027                  [Page 21]

Internet-Draft           yang-on-path-telemetry             October 2026


   *  /altmark/available-interfaces/available-interface/altmark-profiles
      /altmark-profile/path-delay-measurement

   *  /ioam/profiles/profile/available-interface/incremental-tracing

   *  /ioam/profiles/profile/available-interface/preallocated-tracing

   *  /ioam/profiles/profile/available-interface/direct-export

   *  /ioam/profiles/profile/available-interface/proof-of-transit

   *  /ioam/profiles/profile/available-interface/edge-to-edge

   *  /ioam/profiles/profile/available-interface/path-delay-measurement

   The entries in the container above include the AltMark, path delay
   and IOAM profile telemetry data which can be considered sensitive or
   vulnerable in some network environments.  It is important to control
   read access (e.g., via get, get-config, or notification) to the
   readable data nodes.

   The top level administrative configurations related to the AltMark
   and IOAM functionalities are already reported in
   [I-D.ietf-bpm-alt-mark-yang] and [RFC9617].  Unexpected changes to
   those items could lead to the AltMark and IOAM function disruption
   and/ or misbehavior of the AltMark.

   IOAM [RFC9197], Alternate Marking [RFC9341] and Multipoint Alternate
   Marking [RFC9342] analyze different security concerns and related
   solutions.  These aspects are valid and applicable also to this
   document.  In particular the fundamental security requirement is that
   Alternate Marking MUST only be applied in a specific limited domain,
   as also mentioned in [RFC8799].

8.  IANA Considerations

   IANA is requested to register the following URI in the "ns" registry
   within the IETF XML Registry [RFC3688]:

           URI: urn:ietf:params:xml:ns:yang:ietf-altmark-telemetry
           Registrant Contact: The IESG
           XML: N/A; the requested URI is an XML namespace.

           URI: urn:ietf:params:xml:ns:yang:ietf-ioam-telemetry
           Registrant Contact: The IESG
           XML: N/A; the requested URI is an XML namespace.





Fioccola, et al.           Expires 3 May 2027                  [Page 22]

Internet-Draft           yang-on-path-telemetry             October 2026


   IANA is requested to register the following YANG module in the "YANG
   Module Names" registry [RFC6020] within the "YANG Parameters"
   registry group:

           Name: ietf-altmark-telemetry
           Maintained by IANA?  N
           Namespace: urn:ietf:params:xml:ns:yang:ietf-altmark-telemetry
           Prefix: altmark-telemetry
           Reference: RFC XXXX

           Name: ietf-ioam-telemetry
           Maintained by IANA?  N
           Namespace: urn:ietf:params:xml:ns:yang:ietf-ioam-telemetry
           Prefix: ioam-telemetry
           Reference: RFC XXXX

9.  Acknowledgements

   The authors would like to thank Martin Bjorklund, Benoit Claise, Paul
   Aitken for the precious comments and suggestions.

10.  Contributors

   Xiaoming He
   China Telecom
   Email: hexm4@chinatelecom.cn


11.  References

11.1.  Normative References

   [I-D.ietf-bpm-alt-mark-yang]
              Graf, T., Wang, M., Fioccola, G., Zhou, T., and X. Min, "A
              YANG Data Model for the Alternate-Marking Method", Work in
              Progress, Internet-Draft, draft-ietf-bpm-alt-mark-yang-00,
              30 October 2026, <https://datatracker.ietf.org/doc/html/
              draft-ietf-bpm-alt-mark-yang-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/info/rfc2119>.

   [RFC3688]  Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
              DOI 10.17487/RFC3688, January 2004,
              <https://www.rfc-editor.org/info/rfc3688>.




Fioccola, et al.           Expires 3 May 2027                  [Page 23]

Internet-Draft           yang-on-path-telemetry             October 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/info/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/info/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/info/rfc7950>.

   [RFC8040]  Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
              Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
              <https://www.rfc-editor.org/info/rfc8040>.

   [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/info/rfc8174>.

   [RFC8343]  Bjorklund, M., "A YANG Data Model for Interface
              Management", RFC 8343, DOI 10.17487/RFC8343, March 2018,
              <https://www.rfc-editor.org/info/rfc8343>.

   [RFC8532]  Kumar, D., Wang, Z., Wu, Q., Ed., Rahman, R., and S.
              Raghavan, "Generic YANG Data Model for the Management of
              Operations, Administration, and Maintenance (OAM)
              Protocols That Use Connectionless Communications",
              RFC 8532, DOI 10.17487/RFC8532, April 2019,
              <https://www.rfc-editor.org/info/rfc8532>.

   [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/info/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/info/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/info/rfc8641>.




Fioccola, et al.           Expires 3 May 2027                  [Page 24]

Internet-Draft           yang-on-path-telemetry             October 2026


   [RFC9197]  Brockners, F., Ed., Bhandari, S., Ed., and T. Mizrahi,
              Ed., "Data Fields for In Situ Operations, Administration,
              and Maintenance (IOAM)", RFC 9197, DOI 10.17487/RFC9197,
              May 2022, <https://www.rfc-editor.org/info/rfc9197>.

   [RFC9326]  Song, H., Gafni, B., Brockners, F., Bhandari, S., and T.
              Mizrahi, "In Situ Operations, Administration, and
              Maintenance (IOAM) Direct Exporting", RFC 9326,
              DOI 10.17487/RFC9326, November 2022,
              <https://www.rfc-editor.org/info/rfc9326>.

   [RFC9341]  Fioccola, G., Ed., Cociglio, M., Mirsky, G., Mizrahi, T.,
              and T. Zhou, "Alternate-Marking Method", RFC 9341,
              DOI 10.17487/RFC9341, December 2022,
              <https://www.rfc-editor.org/info/rfc9341>.

   [RFC9342]  Fioccola, G., Ed., Cociglio, M., Sapio, A., Sisto, R., and
              T. Zhou, "Clustered Alternate-Marking Method", RFC 9342,
              DOI 10.17487/RFC9342, December 2022,
              <https://www.rfc-editor.org/info/rfc9342>.

   [RFC9343]  Fioccola, G., Zhou, T., Cociglio, M., Qin, F., and R.
              Pang, "IPv6 Application of the Alternate-Marking Method",
              RFC 9343, DOI 10.17487/RFC9343, December 2022,
              <https://www.rfc-editor.org/info/rfc9343>.

   [RFC9617]  Zhou, T., Ed., Guichard, J., Brockners, F., and S.
              Raghavan, "A YANG Data Model for In Situ Operations,
              Administration, and Maintenance (IOAM)", RFC 9617,
              DOI 10.17487/RFC9617, August 2024,
              <https://www.rfc-editor.org/info/rfc9617>.

   [RFC9714]  Cheng, W., Ed., Min, X., Ed., Zhou, T., Dai, J., and Y.
              Peleg, "Encapsulation for MPLS Performance Measurement
              with the Alternate-Marking Method", RFC 9714,
              DOI 10.17487/RFC9714, February 2025,
              <https://www.rfc-editor.org/info/rfc9714>.

   [RFC9911]  Schönwälder, J., Ed., "Common YANG Data Types", RFC 9911,
              DOI 10.17487/RFC9911, December 2025,
              <https://www.rfc-editor.org/info/rfc9911>.

   [RFC9951]  Graf, T., Claise, B., and A. Huang-Feng, "Export of Delay
              Performance Metrics in IP Flow Information Export
              (IPFIX)", RFC 9951, DOI 10.17487/RFC9951, April 2026,
              <https://www.rfc-editor.org/info/rfc9951>.

11.2.  Informative References



Fioccola, et al.           Expires 3 May 2027                  [Page 25]

Internet-Draft           yang-on-path-telemetry             October 2026


   [I-D.ietf-ippm-alt-mark-deployment]
              Fioccola, G., Zhu, K., Graf, T., and L. Zhang, "Alternate
              Marking Deployment Framework", Work in Progress, Internet-
              Draft, draft-ietf-ippm-alt-mark-deployment-10, 22 October
              2026, <https://datatracker.ietf.org/doc/html/draft-ietf-
              ippm-alt-mark-deployment-10>.

   [I-D.ietf-opsawg-ipfix-alt-mark]
              Graf, T., Fioccola, G., Zhou, T., and Y. Zhu, "IP Flow
              Information Export (IPFIX) Alternate-Marking Information
              Elements", Work in Progress, Internet-Draft, draft-ietf-
              opsawg-ipfix-alt-mark-08, 26 August 2026,
              <https://datatracker.ietf.org/doc/html/draft-ietf-opsawg-
              ipfix-alt-mark-08>.

   [RFC4252]  Ylonen, T. and C. Lonvick, Ed., "The Secure Shell (SSH)
              Authentication Protocol", RFC 4252, DOI 10.17487/RFC4252,
              January 2006, <https://www.rfc-editor.org/info/rfc4252>.

   [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/info/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/info/rfc8341>.

   [RFC8446]  Rescorla, E., "The Transport Layer Security (TLS) Protocol
              Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
              <https://www.rfc-editor.org/info/rfc8446>.

   [RFC8799]  Carpenter, B. and B. Liu, "Limited Domains and Internet
              Protocols", RFC 8799, DOI 10.17487/RFC8799, July 2020,
              <https://www.rfc-editor.org/info/rfc8799>.

   [RFC9000]  Iyengar, J., Ed. and M. Thomson, Ed., "QUIC: A UDP-Based
              Multiplexed and Secure Transport", RFC 9000,
              DOI 10.17487/RFC9000, May 2021,
              <https://www.rfc-editor.org/info/rfc9000>.

   [RFC9232]  Song, H., Qin, F., Martinez-Julia, P., Ciavaglia, L., and
              A. Wang, "Network Telemetry Framework", RFC 9232,
              DOI 10.17487/RFC9232, May 2022,
              <https://www.rfc-editor.org/info/rfc9232>.






Fioccola, et al.           Expires 3 May 2027                  [Page 26]

Internet-Draft           yang-on-path-telemetry             October 2026


   [RFC9947]  Fioccola, G., Zhou, T., Mishra, G., Wang, X., Zhang, G.,
              and M. Cociglio, "Application of the Alternate-Marking
              Method to the Segment Routing Header", RFC 9947,
              DOI 10.17487/RFC9947, March 2026,
              <https://www.rfc-editor.org/info/rfc9947>.

Appendix A.  Examples

   An example of the way for a client to subscribe to the telemetry
   information is reported in the following figure.  The telemetry
   parameters that the client is interested are Alternate-Marking, path
   delay and IOAM.

<rpc xmlns:netconf="urn:ietf:params:xml:ns:netconf:base:1.0"
    netconf:message-id="101">
    <establish-subscription xmlns="urn:ietf:params:xml:ns:yang:ietf-yang-push:1.0">
      <filter netconf:type="subtree">
        <altmark xmlns="urn:ietf:params:xml:ns:yang:ietf-altmark">
           <available-interfaces>
             <available-interface>
               <if-name/>
               <altmark-profiles>
                 <altmark-profile>
                   <altmark-profile-name/>
                   <filter>
                     <filter-type/>
                     <ace-name/>
                   </filter>
                   <direction/>
                   <protocol-type/>
                   <flow-mon-id/>
                   <measurement-period-number/>
                   <altmark-loss-measurement/>
                   <altmark-delay-measurement/>
                   <path-delay-measurement/>
                 </altmark-profile>
               </altmark-profiles>
             </available-interface>
          </available-interfaces>
        </altmark>
      </filter>
      <period>10</period>
      <encoding>encode-xml</encoding>
    </establish-subscription>
</rpc>






Fioccola, et al.           Expires 3 May 2027                  [Page 27]

Internet-Draft           yang-on-path-telemetry             October 2026


<rpc xmlns:netconf="urn:ietf:params:xml:ns:netconf:base:1.0"
    netconf:message-id="101">
    <establish-subscription xmlns="urn:ietf:params:xml:ns:yang:ietf-yang-push:1.0">
      <filter netconf:type="subtree">
        <ioam xmlns="urn:ietf:params:xml:ns:yang:ietf-ioam">
          <profiles>
            <profile>
              <profile-name/>
              <filter>
                <filter-type/>
                <ace-name/>
              </filter>
              <protocol-type/>
              <available-interface>
                <if-name/>
                <ioam-incremental-tracing/>
                <ioam-preallocated-tracing/>
                <ioam-direct-export/>
                <ioam-proof-of-transit/>
                <ioam-edge-to-edge/>
                <path-delay-measurement/>
              </available-interface>
            </profile>
          </profiles>
        </ioam>
      </filter>
      <period>10</period>
      <encoding>encode-xml</encoding>
    </establish-subscription>
</rpc>

Authors' Addresses

   Giuseppe Fioccola
   Huawei
   Viale Martesana, 12
   20055 Vimodrone (Milan)
   Italy
   Email: giuseppe.fioccola@huawei.com


   Tianran Zhou
   Huawei
   156 Beiqing Rd.
   Beijing
   100095
   China
   Email: zhoutianran@huawei.com



Fioccola, et al.           Expires 3 May 2027                  [Page 28]

Internet-Draft           yang-on-path-telemetry             October 2026


   Yongqing Zhu
   China Telecom
   Guangzhou
   China
   Email: zhuyq8@chinatelecom.cn


   Wenqiang Zhang
   China Telecom
   Beijing
   China
   Email: zhangwq@chinatelecom.cn


   Alex Huang Feng
   Deutsche Telekom
   Barcelona
   Spain
   Email: alex.huang-feng@t-systems.com


   Keyi Zhu
   Huawei Technologies
   Email: zhukeyi@huawei.com



























Fioccola, et al.           Expires 3 May 2027                  [Page 29]