<?xml version='1.0' encoding='utf-8'?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" category="std" docName="draft-ietf-ippm-ioam-yang-13" number="9617" ipr="trust200902" obsoletes="" updates="" submissionType="IETF" consensus="true" xml:lang="en" tocInclude="true" tocDepth="3" symRefs="true" sortRefs="true" prepTime="2024-08-27T08:55:24" indexInclude="true" scripts="Common,Latin">
  <link href="https://datatracker.ietf.org/doc/draft-ietf-ippm-ioam-yang-13" rel="prev"/>
  <link href="https://dx.doi.org/10.17487/rfc9617" rel="alternate"/>
  <link href="urn:issn:2070-1721" rel="alternate"/>
  <front>
    <title abbrev="YANG Data Model for IOAM">A YANG Data Model for In Situ Operations, Administration, and Maintenance (IOAM)</title>
    <seriesInfo name="RFC" value="9617" stream="IETF"/>
    <author fullname="Tianran Zhou" initials="T." surname="Zhou" role="editor">
      <organization showOnFrontPage="true">Huawei</organization>
      <address>
        <postal>
          <street>156 Beiqing Rd.</street>
          <city>Beijing</city>
          <code>100095</code>
          <country>China</country>
        </postal>
        <email>zhoutianran@huawei.com</email>
      </address>
    </author>
    <author fullname="Jim Guichard" initials="J." surname="Guichard">
      <organization showOnFrontPage="true">Futurewei</organization>
      <address>
        <postal>
          <country>United States of America</country>
        </postal>
        <email>james.n.guichard@futurewei.com</email>
      </address>
    </author>
    <author fullname="Frank Brockners" initials="F." surname="Brockners">
      <organization showOnFrontPage="true">Cisco Systems</organization>
      <address>
        <postal>
          <street>Hansaallee 249, 3rd Floor</street>
          <city>Düsseldorf, Nordrhein-Westfalen</city>
          <code>40549</code>
          <country>Germany</country>
        </postal>
        <email>fbrockne@cisco.com</email>
      </address>
    </author>
    <author fullname="Srihari Raghavan" initials="S." surname="Raghavan">
      <organization showOnFrontPage="true">Cisco Systems</organization>
      <address>
        <postal>
          <street>Tril Infopark Sez, Ramanujan IT City</street>
          <street>Neville Block, 2nd floor, Old Mahabalipuram Road</street>
          <city>Chennai</city>
          <region>Tamil Nadu</region>
          <code>600113</code>
          <country>India</country>
        </postal>
        <email>srihari@cisco.com</email>
      </address>
    </author>
    <date month="08" year="2024"/>
    <area>OPS</area>
    <workgroup>ippm</workgroup>
    <keyword>OAM</keyword>
    <keyword>Configuration</keyword>
    <abstract pn="section-abstract">
      <t indent="0" pn="section-abstract-1">In situ Operations, Administration, and Maintenance (IOAM) is an
      example of an on-path hybrid measurement method. IOAM defines a method
      for producing operational and telemetry information that may be exported
      using the in-band or out-of-band method. RFCs 9197 and 9326 discuss the
      data fields and associated data types for IOAM. This document defines a
      YANG module for the configuration of IOAM functions.</t>
    </abstract>
    <boilerplate>
      <section anchor="status-of-memo" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.1">
        <name slugifiedName="name-status-of-this-memo">Status of This Memo</name>
        <t indent="0" pn="section-boilerplate.1-1">
            This is an Internet Standards Track document.
        </t>
        <t indent="0" pn="section-boilerplate.1-2">
            This document is a product of the Internet Engineering Task Force
            (IETF).  It represents the consensus of the IETF community.  It has
            received public review and has been approved for publication by
            the Internet Engineering Steering Group (IESG).  Further
            information on Internet Standards is available in Section 2 of 
            RFC 7841.
        </t>
        <t indent="0" pn="section-boilerplate.1-3">
            Information about the current status of this document, any
            errata, and how to provide feedback on it may be obtained at
            <eref target="https://www.rfc-editor.org/info/rfc9617" brackets="none"/>.
        </t>
      </section>
      <section anchor="copyright" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.2">
        <name slugifiedName="name-copyright-notice">Copyright Notice</name>
        <t indent="0" pn="section-boilerplate.2-1">
            Copyright (c) 2024 IETF Trust and the persons identified as the
            document authors. All rights reserved.
        </t>
        <t indent="0" pn="section-boilerplate.2-2">
            This document is subject to BCP 78 and the IETF Trust's Legal
            Provisions Relating to IETF Documents
            (<eref target="https://trustee.ietf.org/license-info" brackets="none"/>) 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.
        </t>
      </section>
    </boilerplate>
    <toc>
      <section anchor="toc" numbered="false" removeInRFC="false" toc="exclude" pn="section-toc.1">
        <name slugifiedName="name-table-of-contents">Table of Contents</name>
        <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1">
          <li pn="section-toc.1-1.1">
            <t indent="0" keepWithNext="true" pn="section-toc.1-1.1.1"><xref derivedContent="1" format="counter" sectionFormat="of" target="section-1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-introduction">Introduction</xref></t>
          </li>
          <li pn="section-toc.1-1.2">
            <t indent="0" keepWithNext="true" pn="section-toc.1-1.2.1"><xref derivedContent="2" format="counter" sectionFormat="of" target="section-2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-conventions-used-in-this-do">Conventions Used in This Document</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.2.2">
              <li pn="section-toc.1-1.2.2.1">
                <t indent="0" keepWithNext="true" pn="section-toc.1-1.2.2.1.1"><xref derivedContent="2.1" format="counter" sectionFormat="of" target="section-2.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-tree-diagrams">Tree Diagrams</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.3">
            <t indent="0" pn="section-toc.1-1.3.1"><xref derivedContent="3" format="counter" sectionFormat="of" target="section-3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-design-of-the-ioam-yang-dat">Design of the IOAM YANG Data Model</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.3.2">
              <li pn="section-toc.1-1.3.2.1">
                <t indent="0" pn="section-toc.1-1.3.2.1.1"><xref derivedContent="3.1" format="counter" sectionFormat="of" target="section-3.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-overview">Overview</xref></t>
              </li>
              <li pn="section-toc.1-1.3.2.2">
                <t indent="0" pn="section-toc.1-1.3.2.2.1"><xref derivedContent="3.2" format="counter" sectionFormat="of" target="section-3.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-pre-allocated-tracing-profi">Pre-allocated Tracing Profile</xref></t>
              </li>
              <li pn="section-toc.1-1.3.2.3">
                <t indent="0" pn="section-toc.1-1.3.2.3.1"><xref derivedContent="3.3" format="counter" sectionFormat="of" target="section-3.3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-incremental-tracing-profile">Incremental Tracing Profile</xref></t>
              </li>
              <li pn="section-toc.1-1.3.2.4">
                <t indent="0" pn="section-toc.1-1.3.2.4.1"><xref derivedContent="3.4" format="counter" sectionFormat="of" target="section-3.4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-direct-export-profile">Direct Export Profile</xref></t>
              </li>
              <li pn="section-toc.1-1.3.2.5">
                <t indent="0" pn="section-toc.1-1.3.2.5.1"><xref derivedContent="3.5" format="counter" sectionFormat="of" target="section-3.5"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-proof-of-transit-profile">Proof of Transit Profile</xref></t>
              </li>
              <li pn="section-toc.1-1.3.2.6">
                <t indent="0" pn="section-toc.1-1.3.2.6.1"><xref derivedContent="3.6" format="counter" sectionFormat="of" target="section-3.6"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-edge-to-edge-profile">Edge-to-Edge Profile</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.4">
            <t indent="0" pn="section-toc.1-1.4.1"><xref derivedContent="4" format="counter" sectionFormat="of" target="section-4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-ioam-yang-module">IOAM YANG Module</xref></t>
          </li>
          <li pn="section-toc.1-1.5">
            <t indent="0" pn="section-toc.1-1.5.1"><xref derivedContent="5" format="counter" sectionFormat="of" target="section-5"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-security-considerations">Security Considerations</xref></t>
          </li>
          <li pn="section-toc.1-1.6">
            <t indent="0" pn="section-toc.1-1.6.1"><xref derivedContent="6" format="counter" sectionFormat="of" target="section-6"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-iana-considerations">IANA Considerations</xref></t>
          </li>
          <li pn="section-toc.1-1.7">
            <t indent="0" pn="section-toc.1-1.7.1"><xref derivedContent="7" format="counter" sectionFormat="of" target="section-7"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-normative-references">Normative References</xref></t>
          </li>
          <li pn="section-toc.1-1.8">
            <t indent="0" pn="section-toc.1-1.8.1"><xref derivedContent="Appendix A" format="default" sectionFormat="of" target="section-appendix.a"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-an-example-of-the-increment">An Example of the Incremental Tracing Profile</xref></t>
          </li>
          <li pn="section-toc.1-1.9">
            <t indent="0" pn="section-toc.1-1.9.1"><xref derivedContent="Appendix B" format="default" sectionFormat="of" target="section-appendix.b"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-an-example-of-the-pre-alloc">An Example of the Pre-allocated Tracing Profile</xref></t>
          </li>
          <li pn="section-toc.1-1.10">
            <t indent="0" pn="section-toc.1-1.10.1"><xref derivedContent="Appendix C" format="default" sectionFormat="of" target="section-appendix.c"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-an-example-of-the-direct-ex">An Example of the Direct Export Profile</xref></t>
          </li>
          <li pn="section-toc.1-1.11">
            <t indent="0" pn="section-toc.1-1.11.1"><xref derivedContent="Appendix D" format="default" sectionFormat="of" target="section-appendix.d"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-an-example-of-the-proof-of-">An Example of the Proof of Transit Profile</xref></t>
          </li>
          <li pn="section-toc.1-1.12">
            <t indent="0" pn="section-toc.1-1.12.1"><xref derivedContent="Appendix E" format="default" sectionFormat="of" target="section-appendix.e"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-an-example-of-the-edge-to-e">An Example of the Edge-to-Edge Profile</xref></t>
          </li>
          <li pn="section-toc.1-1.13">
            <t indent="0" pn="section-toc.1-1.13.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.f"/><xref derivedContent="" format="title" sectionFormat="of" target="name-acknowledgements">Acknowledgements</xref></t>
          </li>
          <li pn="section-toc.1-1.14">
            <t indent="0" pn="section-toc.1-1.14.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.g"/><xref derivedContent="" format="title" sectionFormat="of" target="name-authors-addresses">Authors' Addresses</xref></t>
          </li>
        </ul>
      </section>
    </toc>
  </front>
  <middle>
    <section numbered="true" toc="include" removeInRFC="false" pn="section-1">
      <name slugifiedName="name-introduction">Introduction</name>
      <t indent="0" pn="section-1-1">In situ Operations, Administration, and Maintenance (IOAM) is an
      example of an on-path hybrid measurement method. IOAM defines a method
      for producing 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 <xref target="RFC9197" format="default" sectionFormat="of" derivedContent="RFC9197"/> and
      <xref target="RFC9326" format="default" sectionFormat="of" derivedContent="RFC9326"/>. The IOAM data can be embedded in many protocol
      encapsulations, such as the Network Service Header (NSH) <xref target="RFC9452" format="default" sectionFormat="of" derivedContent="RFC9452"/> and IPv6.</t>
      <t indent="0" pn="section-1-2">This document defines a data model for the configuration of IOAM
      capabilities using the <xref target="RFC7950" format="default" sectionFormat="of" derivedContent="RFC7950">YANG data modeling
      language</xref>. This YANG data model supports five IOAM options, which
      are as follows:</t>
      <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-1-3">
        <li pn="section-1-3.1">
          <t indent="0" pn="section-1-3.1.1"><xref target="RFC9197" format="default" sectionFormat="of" derivedContent="RFC9197">Incremental Trace-Option </xref></t>
        </li>
        <li pn="section-1-3.2">
          <t indent="0" pn="section-1-3.2.1"><xref target="RFC9197" format="default" sectionFormat="of" derivedContent="RFC9197">Pre-allocated Trace-Option</xref></t>
        </li>
        <li pn="section-1-3.3">
          <t indent="0" pn="section-1-3.3.1"><xref target="RFC9326" format="default" sectionFormat="of" derivedContent="RFC9326">Direct Export Option</xref></t>
        </li>
        <li pn="section-1-3.4">
          <t indent="0" pn="section-1-3.4.1"><xref target="RFC9197" format="default" sectionFormat="of" derivedContent="RFC9197">Proof of Transit (POT) Option</xref></t>
        </li>
        <li pn="section-1-3.5">
          <t indent="0" pn="section-1-3.5.1"><xref target="RFC9197" format="default" sectionFormat="of" derivedContent="RFC9197">Edge-to-Edge Option</xref></t>
        </li>
      </ul>
    </section>
    <section numbered="true" toc="include" removeInRFC="false" pn="section-2">
      <name slugifiedName="name-conventions-used-in-this-do">Conventions Used in This Document</name>
      <t indent="0" pn="section-2-1">The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>",
       "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>",
       "<bcp14>SHALL NOT</bcp14>", "<bcp14>SHOULD</bcp14>",
       "<bcp14>SHOULD NOT</bcp14>",
       "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
       "<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document
       are to be interpreted as described in BCP 14
       <xref target="RFC2119" format="default" sectionFormat="of" derivedContent="RFC2119"/> <xref target="RFC8174" format="default" sectionFormat="of" derivedContent="RFC8174"/> when, and only
       when, they appear in all capitals, as shown here.</t>
      <t indent="0" pn="section-2-2">The following terms are defined in <xref target="RFC7950" format="default" sectionFormat="of" derivedContent="RFC7950"/> and are
      used in this specification: </t>
      <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-2-3">
        <li pn="section-2-3.1">
          <t indent="0" pn="section-2-3.1.1">augment</t>
        </li>
        <li pn="section-2-3.2">
          <t indent="0" pn="section-2-3.2.1">data model</t>
        </li>
        <li pn="section-2-3.3">
          <t indent="0" pn="section-2-3.3.1">data node</t>
        </li>
      </ul>
      <t indent="0" pn="section-2-4">The terminology for describing YANG data models is found in
      <xref target="RFC7950" format="default" sectionFormat="of" derivedContent="RFC7950"/>.</t>
      <section anchor="tree-diagrams" numbered="true" toc="include" removeInRFC="false" pn="section-2.1">
        <name slugifiedName="name-tree-diagrams">Tree Diagrams</name>
        <t indent="0" pn="section-2.1-1">Tree diagrams used in this document follow the notation defined in
        <xref target="RFC8340" format="default" sectionFormat="of" derivedContent="RFC8340"/>.</t>
      </section>
    </section>
    <section numbered="true" toc="include" removeInRFC="false" pn="section-3">
      <name slugifiedName="name-design-of-the-ioam-yang-dat">Design of the IOAM YANG Data Model</name>
      <section numbered="true" toc="include" removeInRFC="false" pn="section-3.1">
        <name slugifiedName="name-overview">Overview</name>
        <t indent="0" pn="section-3.1-1">The IOAM model is organized as a list of profiles, as shown in the
        following figure. Each profile associates with one flow and the
        corresponding IOAM information.</t>
        <sourcecode type="yangtree" markers="false" pn="section-3.1-2">module: ietf-ioam
  +--rw ioam
     +--ro info
     |  +--ro timestamp-type?        identityref
     |  +--ro available-interface* [if-name]
     |     +--ro if-name    if:interface-ref
     +--rw admin-config
     |  +--rw enabled?   boolean
     +--rw profiles
        +--rw profile* [profile-name]
           +--rw profile-name                    string
           +--rw filter
           |  +--rw filter-type?   ioam-filter-type
           |  +--rw ace-name?      -&gt; /acl:acls/acl/aces/ace/name
           +--rw protocol-type?                  ioam-protocol-type
           +--rw incremental-tracing-profile {incremental-trace}?
           |  ...
           +--rw preallocated-tracing-profile {preallocated-trace}?
           |  ...
           +--rw direct-export-profile {direct-export}?
           |  ...
           +--rw pot-profile {proof-of-transit}?
           |  ...
           +--rw e2e-profile {edge-to-edge}?
</sourcecode>
        <t indent="0" pn="section-3.1-3">The "info" parameter is a container for all the read-only information that
        assists monitoring systems in the interpretation of the IOAM data.</t>
        <t indent="0" pn="section-3.1-4">The "enabled" parameter is an administrative configuration. When it is set to
        "true", IOAM configuration is enabled for the system. Meanwhile, the
        IOAM data plane functionality is enabled.</t>
        <t indent="0" pn="section-3.1-5">The "filter" parameter is used to identify a flow, where the IOAM profile can
        apply. There may be multiple filter types. <xref target="RFC8519" format="default" sectionFormat="of" derivedContent="RFC8519">Access Control Lists (ACLs)</xref> provide a common way to specify a flow. Each
        IOAM profile can associate with an ACE (Access Control Entry). When the
matched ACE "forwarding" action is "accept", IOAM actions <bcp14>MUST</bcp14> be driven by the accepted packets.</t>
        <t indent="0" pn="section-3.1-6">The IOAM data can be encapsulated into multiple protocols, e.g.,
        <xref target="RFC9486" format="default" sectionFormat="of" derivedContent="RFC9486">IPv6</xref> and <xref target="RFC9452" format="default" sectionFormat="of" derivedContent="RFC9452">the NSH</xref>. The "protocol-type" parameter is used to indicate
        where IOAM is applied. For example, if "protocol-type" is set to
        "ipv6", the IOAM ingress node will encapsulate the associated flow
        according to <xref target="RFC9486" format="default" sectionFormat="of" derivedContent="RFC9486"/>.</t>
        <t indent="0" pn="section-3.1-7">In this document, IOAM data includes five encapsulation types,
        i.e., incremental tracing data, pre-allocated tracing data, direct
        export data, proof of transit data, and end-to-end data. In practice,
        multiple IOAM data types can be encapsulated into the same IOAM
        header. The "profile" parameter contains a set of sub-profiles, each of which
        relates to one encapsulation type. The configured object may not
        support all the sub-profiles. The supported sub-profiles are indicated
        by five defined features, i.e., "incremental-trace",
        "preallocated-trace", "direct-export", "proof-of-transit", and
        "edge-to-edge".</t>
        <t indent="0" pn="section-3.1-8">This document uses the <xref target="RFC8519" format="default" sectionFormat="of" derivedContent="RFC8519">"ietf-access-control-list" YANG module</xref>, the <xref target="RFC8343" format="default" sectionFormat="of" derivedContent="RFC8343">"ietf-interfaces" YANG
        module</xref>, and the <xref target="RFC8532" format="default" sectionFormat="of" derivedContent="RFC8532">"ietf-lime-time-types" YANG module</xref>.</t>
        <t indent="0" pn="section-3.1-9">The YANG data model in this document conforms to the Network
        Management Datastore Architecture (NMDA) defined in <xref target="RFC8342" format="default" sectionFormat="of" derivedContent="RFC8342"/>.</t>
      </section>
      <section numbered="true" toc="include" anchor="prealloc-tracing" removeInRFC="false" pn="section-3.2">
        <name slugifiedName="name-pre-allocated-tracing-profi">Pre-allocated Tracing Profile</name>
        <t indent="0" pn="section-3.2-1">To ensure visibility into the entire path that a packet takes within an IOAM domain, the IOAM tracing data is expected to be collected at every node
        that a packet traverses. The Pre-allocated Trace-Option
        will create pre-allocated space for each node to populate its
        information. The "preallocated-tracing-profile" parameter contains the detailed
        information for the pre-allocated tracing data. This information
        includes:</t>
        <dl spacing="normal" indent="3" newline="false" pn="section-3.2-2">
          <dt pn="section-3.2-2.1">node-action:</dt>
          <dd pn="section-3.2-2.2">indicates the operation (e.g., encapsulate the IOAM
            header, transit the IOAM data, or decapsulate the IOAM header) applied
            to the dedicated flow.</dd>
          <dt pn="section-3.2-2.3">use-namespace:</dt>
          <dd pn="section-3.2-2.4">indicates the namespace used for the trace
            types.</dd>
          <dt pn="section-3.2-2.5">trace-type:</dt>
          <dd pn="section-3.2-2.6">indicates the per-hop data to be captured by
            IOAM-enabled nodes and included in the node data list.</dd>
          <dt pn="section-3.2-2.7">max-length:</dt>
          <dd pn="section-3.2-2.8">specifies the maximum length of the node data list
            in octets.  "max-length" is only defined at the encapsulation
            node.</dd>
        </dl>
        <sourcecode type="yangtree" markers="false" pn="section-3.2-3">+--rw preallocated-tracing-profile {preallocated-trace}?
   +--rw node-action?            ioam-node-action
   +--rw trace-types
   |  +--rw use-namespace?   ioam-namespace
   |  +--rw trace-type*   ioam-trace-type
   +--rw max-length?             uint32
</sourcecode>
      </section>
      <section numbered="true" toc="include" removeInRFC="false" pn="section-3.3">
        <name slugifiedName="name-incremental-tracing-profile">Incremental Tracing Profile</name>
        <t indent="0" pn="section-3.3-1">The Incremental Trace-Option contains a variable-length list of node data fields,
        where each node allocates and pushes its node data immediately
        following the option header. The "incremental-tracing-profile" parameter
        contains the detailed information for the incremental tracing data.
        This information is the same as that for the Pre-allocated Tracing
        Profile; see <xref target="prealloc-tracing" format="default" sectionFormat="of" derivedContent="Section 3.2"/>.</t>
        <sourcecode type="yangtree" markers="false" pn="section-3.3-2">+--rw incremental-tracing-profile {incremental-trace}?
   +--rw node-action?            ioam-node-action
   +--rw trace-types
   |  +--rw use-namespace?   ioam-namespace
   |  +--rw trace-type*   ioam-trace-type
   +--rw max-length?             uint32
</sourcecode>
      </section>
      <section numbered="true" toc="include" removeInRFC="false" pn="section-3.4">
        <name slugifiedName="name-direct-export-profile">Direct Export Profile</name>
        <t indent="0" pn="section-3.4-1">The Direct Export Option is used as a trigger for IOAM data to be
        directly exported or locally aggregated without being pushed into
        in-flight data packets. The "direct-export-profile" parameter contains the
        detailed information for the direct export data. This
        information is the same as that for the Pre-allocated Tracing Profile (<xref target="prealloc-tracing" format="default" sectionFormat="of" derivedContent="Section 3.2"/>), but with
        two more optional variables:</t>
        <dl spacing="normal" indent="3" newline="false" pn="section-3.4-2">
          <dt pn="section-3.4-2.1">flow-id:</dt>
          <dd pn="section-3.4-2.2">used to correlate the exported data of the same
            flow from multiple nodes and from multiple packets.</dd>
          <dt pn="section-3.4-2.3">enable-sequence-number:</dt>
          <dd pn="section-3.4-2.4">indicates whether the sequence number
            is used in the Direct Export Option.</dd>
        </dl>
        <sourcecode type="yangtree" markers="false" pn="section-3.4-3">+--rw direct-export-profile {direct-export}?
   +--rw node-action?            ioam-node-action
   +--rw trace-types
   |  +--rw use-namespace?   ioam-namespace
   |  +--rw trace-type*      ioam-trace-type
   +--rw flow-id?             uint32
   +--rw enable-sequence-number? boolean
</sourcecode>
      </section>
      <section numbered="true" toc="include" removeInRFC="false" pn="section-3.5">
        <name slugifiedName="name-proof-of-transit-profile">Proof of Transit Profile</name>
        <t indent="0" pn="section-3.5-1">The IOAM proof of transit data is used to support the path or service
        function chain verification use cases. The "pot-profile" parameter is intended
        to contain the detailed information for the proof of transit data. The
        "use-namespace" parameter indicates the namespace used for the POT types.
        The "pot-type" parameter indicates a particular POT variant that specifies the POT
        data that is included. There may be several POT types, each having
        different configuration data. To align with <xref target="RFC9197" format="default" sectionFormat="of" derivedContent="RFC9197"/>,
        this document only defines IOAM POT type 0. Users need to augment this
        module for the configuration of a specific POT type.</t>
        <sourcecode type="yangtree" markers="false" pn="section-3.5-2">+--rw pot-profile {proof-of-transit}?
   +--rw use-namespace?   ioam-namespace
   +--rw pot-type?   ioam-pot-type
</sourcecode>
      </section>
      <section numbered="true" toc="include" removeInRFC="false" pn="section-3.6">
        <name slugifiedName="name-edge-to-edge-profile">Edge-to-Edge Profile</name>
        <t indent="0" pn="section-3.6-1">The IOAM Edge-to-Edge Option is used to carry data that is added by the
        IOAM encapsulating node and interpreted by the IOAM decapsulating node.
        The "e2e-profile" parameter contains the detailed information for the
        edge-to-edge data. This information includes:</t>
        <dl spacing="normal" indent="3" newline="false" pn="section-3.6-2">
          <dt pn="section-3.6-2.1">node-action:</dt>
          <dd pn="section-3.6-2.2">the same semantic as that provided in <xref target="prealloc-tracing" format="default" sectionFormat="of" derivedContent="Section 3.2"/>.</dd>
          <dt pn="section-3.6-2.3">use-namespace:</dt>
          <dd pn="section-3.6-2.4">indicates the namespace used for the edge-to-edge
            types.</dd>
          <dt pn="section-3.6-2.5">e2e-type:</dt>
          <dd pn="section-3.6-2.6">indicates data to be carried from the ingress IOAM
            node to the egress IOAM node.</dd>
        </dl>
        <sourcecode type="yangtree" markers="false" pn="section-3.6-3">+--rw e2e-profile {edge-to-edge}?
   +--rw node-action?   ioam-node-action
   +--rw e2e-types
      +--rw use-namespace?   ioam-namespace
      +--rw e2e-type*        ioam-e2e-type
</sourcecode>
      </section>
    </section>
    <section numbered="true" toc="include" removeInRFC="false" pn="section-4">
      <name slugifiedName="name-ioam-yang-module">IOAM YANG Module</name>
      <t indent="0" pn="section-4-1">The "ietf-ioam" module defined in this document imports typedefs from <xref target="RFC8519" format="default" sectionFormat="of" derivedContent="RFC8519"/>, <xref target="RFC8343" format="default" sectionFormat="of" derivedContent="RFC8343"/>, and <xref target="RFC8532" format="default" sectionFormat="of" derivedContent="RFC8532"/>. This document also references <xref target="RFC9197" format="default" sectionFormat="of" derivedContent="RFC9197"/>, <xref target="RFC9326" format="default" sectionFormat="of" derivedContent="RFC9326"/>, <xref target="RFC9486" format="default" sectionFormat="of" derivedContent="RFC9486"/>, and <xref target="RFC9452" format="default" sectionFormat="of" derivedContent="RFC9452"/>.</t>
      <sourcecode name="ietf-ioam@2024-08-27.yang" type="yang" markers="true" pn="section-4-2">
module ietf-ioam {
  yang-version 1.1;
  namespace "urn:ietf:params:xml:ns:yang:ietf-ioam";
  prefix ioam;

  import ietf-access-control-list {
    prefix acl;
    reference
      "RFC 8519: YANG Data Model for Network Access Control
       Lists (ACLs)";
  }
  import ietf-interfaces {
    prefix if;
    reference
      "RFC 8343: A YANG Data Model for Interface Management";
  }
  import ietf-lime-time-types {
    prefix lime;
    reference
      "RFC 8532: Generic YANG Data Model for the Management of
       Operations, Administration, and Maintenance (OAM) Protocols
       That Use Connectionless Communications";
  }

  organization
    "IETF IPPM (IP Performance Measurement) Working Group";
  contact
    "WG Web:   &lt;https://datatracker.ietf.org/wg/ippm&gt;
     WG List:  &lt;mailto:ippm@ietf.org&gt;
     Editor:   Tianran Zhou
               &lt;mailto:zhoutianran@huawei.com&gt;
     Author:   Jim Guichard
               &lt;mailto:james.n.guichard@futurewei.com&gt;
     Author:   Frank Brockners
               &lt;mailto:fbrockne@cisco.com&gt;
     Author:   Srihari Raghavan
               &lt;mailto:srihari@cisco.com&gt;";
  description
    "This YANG module specifies a vendor-independent data model
     for In Situ Operations, Administration, and Maintenance
     (IOAM).

     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) 2024 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 9617; see the
     RFC itself for full legal notices.";

  revision 2024-08-27 {
    description
      "Initial revision.";
    reference
      "RFC 9617: A YANG Data Model for In Situ Operations,
       Administration, and Maintenance (IOAM)";
  }

  /*
   * FEATURES
   */

  feature incremental-trace {
    description
      "This feature indicates that the Incremental Trace-Option is
       supported.";
    reference
      "RFC 9197: Data Fields for In Situ Operations,
       Administration, and Maintenance (IOAM)";
  }

  feature preallocated-trace {
    description
      "This feature indicates that the Pre-allocated Trace-Option
       is supported.";
    reference
      "RFC 9197: Data Fields for In Situ Operations,
       Administration, and Maintenance (IOAM)";
  }

  feature direct-export {
    description
      "This feature indicates that the Direct Export Option is
       supported.";
    reference
      "RFC 9326: In Situ Operations, Administration, and
       Maintenance (IOAM) Direct Exporting";
  }

  feature proof-of-transit {
    description
      "This feature indicates that the Proof of Transit Option is
       supported.";
    reference
      "RFC 9197: Data Fields for In Situ Operations,
       Administration, and Maintenance (IOAM)";
  }

  feature edge-to-edge {
    description
      "This feature indicates that the Edge-to-Edge Option is
       supported.";
    reference
      "RFC 9197: Data Fields for In Situ Operations,
       Administration, and Maintenance (IOAM)";
  }

  /*
   * IDENTITIES
   */

  identity filter {
    description
      "Base identity to represent a filter.  A filter is used to
       specify the flow to apply the IOAM profile.";
  }

  identity acl-filter {
    base filter;
    description
      "Apply Access Control List (ACL) rules to specify the
       flow.";
  }

  identity protocol {
    description
      "Base identity to represent the carrier protocol.  It is
       used to indicate in what layer and protocol the IOAM data
       is embedded.";
  }

  identity ipv6 {
    base protocol;
    description
      "The described IOAM data is embedded in IPv6.";
    reference
      "RFC 9486: IPv6 Options for In Situ Operations,
       Administration, and Maintenance (IOAM)";
  }

  identity nsh {
    base protocol;
    description
      "The described IOAM data is embedded in the Network Service
       Header (NSH).";
    reference
      "RFC 9452: Network Service Header (NSH) Encapsulation for
       In Situ OAM (IOAM) Data";
  }

  identity node-action {
    description
      "Base identity to represent the node actions.  It is used to
       indicate what action the node will take.";
  }

  identity action-encapsulate {
    base node-action;
    description
      "This identity indicates that the node is used to
       encapsulate the IOAM packet.";
  }

  identity action-decapsulate {
    base node-action;
    description
      "This identity indicates that the node is used to
       decapsulate the IOAM packet.";
  }

  identity action-transit {
    base node-action;
    description
      "This identity indicates that the node is used to transit
       the IOAM packet.";
  }

  identity trace-type {
    description
      "Base identity to represent trace types.";
  }

  identity trace-hop-lim-node-id {
    base trace-type;
    description
      "This identity indicates the presence of 'Hop_Lim' and
       'node_id' in the node data.";
    reference
      "RFC 9197: Data Fields for In Situ Operations,
       Administration, and Maintenance (IOAM)";
  }

  identity trace-if-id {
    base trace-type;
    description
      "This identity indicates the presence of 'ingress_if_id' and
       'egress_if_id' (short format) in the node data.";
    reference
      "RFC 9197: Data Fields for In Situ Operations,
       Administration, and Maintenance (IOAM)";
  }

  identity trace-timestamp-seconds {
    base trace-type;
    description
      "This identity indicates the presence of timestamp seconds
       in the node data.";
  }

  identity trace-timestamp-fraction {
    base trace-type;
    description
      "This identity indicates the presence of a timestamp
       fraction in the node data.";
  }

  identity trace-transit-delay {
    base trace-type;
    description
      "This identity indicates the presence of transit delay in
       the node data.";
  }

  identity trace-namespace-data {
    base trace-type;
    description
      "This identity indicates the presence of namespace-specific
       data (short format) in the node data.";
  }

  identity trace-queue-depth {
    base trace-type;
    description
      "This identity indicates the presence of queue depth in the
       node data.";
  }

  identity trace-checksum-complement {
    base trace-type;
    description
      "This identity indicates the presence of the Checksum
       Complement in the node data.";
    reference
      "RFC 9197: Data Fields for In Situ Operations,
       Administration, and Maintenance (IOAM)";
  }

  identity trace-hop-lim-node-id-wide {
    base trace-type;
    description
      "This identity indicates the presence of 'Hop_Lim' and
       'node_id' (wide format) in the node data.";
  }

  identity trace-if-id-wide {
    base trace-type;
    description
      "This identity indicates the presence of 'ingress_if_id' and
       'egress_if_id' (wide format) in the node data.";
  }

  identity trace-namespace-data-wide {
    base trace-type;
    description
      "This identity indicates the presence of
       IOAM-namespace-specific data (wide format) in the
       node data.";
  }

  identity trace-buffer-occupancy {
    base trace-type;
    description
      "This identity indicates the presence of buffer occupancy
       in the node data.";
  }

  identity trace-opaque-state-snapshot {
    base trace-type;
    description
      "This identity indicates the presence of the variable-length
       Opaque State Snapshot field.";
  }

  identity pot-type {
    description
      "Base identity to represent Proof of Transit (POT) types.";
  }

  identity pot-type-0 {
    base pot-type;
    description
      "The IOAM field value for the POT type is 0, and POT data is
       a 16-octet field to carry data associated with POT
       procedures.";
  }

  identity e2e-type {
    description
      "Base identity to represent edge-to-edge types.";
  }

  identity e2e-seq-num-64 {
    base e2e-type;
    description
      "This identity indicates the presence of a 64-bit
       sequence number.";
  }

  identity e2e-seq-num-32 {
    base e2e-type;
    description
      "This identity indicates the presence of a 32-bit
       sequence number.";
  }

  identity e2e-timestamp-seconds {
    base e2e-type;
    description
      "This identity indicates the presence of timestamp seconds
       representing the time at which the packet entered the
       IOAM domain.";
  }

  identity e2e-timestamp-fraction {
    base e2e-type;
    description
      "This identity indicates the presence of a timestamp
       fraction representing the time at which the packet entered
       the IOAM domain.";
  }

  identity namespace {
    description
      "Base identity to represent the Namespace-ID.";
  }

  identity default-namespace {
    base namespace;
    description
      "The Namespace-ID value of 0x0000 is defined as the
       Default-Namespace-ID and MUST be known to all the nodes
       implementing IOAM.";
  }

  /*
   * TYPE DEFINITIONS
   */

  typedef ioam-filter-type {
    type identityref {
      base filter;
    }
    description
      "This type specifies a known type of filter.";
  }

  typedef ioam-protocol-type {
    type identityref {
      base protocol;
    }
    description
      "This type specifies a known type of carrier protocol for
       the IOAM data.";
  }

  typedef ioam-node-action {
    type identityref {
      base node-action;
    }
    description
      "This type specifies a known type of node action.";
  }

  typedef ioam-trace-type {
    type identityref {
      base trace-type;
    }
    description
      "This type specifies a known trace type.";
  }

  typedef ioam-pot-type {
    type identityref {
      base pot-type;
    }
    description
      "This type specifies a known POT type.";
  }

  typedef ioam-e2e-type {
    type identityref {
      base e2e-type;
    }
    description
      "This type specifies a known edge-to-edge type.";
  }

  typedef ioam-namespace {
    type identityref {
      base namespace;
    }
    description
      "This type specifies the supported namespace.";
  }

  /*
   * GROUP DEFINITIONS
   */

  grouping ioam-filter {
    description
      "A grouping for IOAM filter definitions.";
    leaf filter-type {
      type ioam-filter-type;
      description
        "Filter type.";
    }
    leaf ace-name {
      when "derived-from-or-self(../filter-type, 'ioam:acl-filter')";
      type leafref {
        path "/acl:acls/acl:acl/acl:aces/acl:ace/acl:name";
      }
      description
        "The Access Control Entry name is used to refer to an ACL
         specification.";
    }
  }

  grouping encap-tracing {
    description
      "A grouping for the generic configuration for the
       tracing profile.";
    container trace-types {
      description
        "This container provides the list of trace types for
         encapsulation.";
      leaf use-namespace {
        type ioam-namespace;
        default "default-namespace";
        description
          "This object indicates the namespace used for
           encapsulation.";
      }
      leaf-list trace-type {
        type ioam-trace-type;
        description
          "The trace type is only defined at the encapsulation
           node.";
      }
    }
    leaf max-length {
      when "derived-from-or-self(../node-action,
            'ioam:action-encapsulate')";
      type uint32;
      units "bytes";
      description
        "This field specifies the maximum length of the node data
         list in octets.  'max-length' is only defined at the
         encapsulation node.";
    }
  }

  grouping ioam-incremental-tracing-profile {
    description
      "A grouping for the Incremental Tracing Profile.";
    leaf node-action {
      type ioam-node-action;
      default "action-transit";
      description
        "This object indicates the action the node needs to
         take, e.g., encapsulation.";
    }
    uses encap-tracing {
      when "derived-from-or-self(node-action,
            'ioam:action-encapsulate')";
    }
  }

  grouping ioam-preallocated-tracing-profile {
    description
      "A grouping for the Pre-allocated Tracing Profile.";
    leaf node-action {
      type ioam-node-action;
      default "action-transit";
      description
        "This object indicates the action the node needs to
         take, e.g., encapsulation.";
    }
    uses encap-tracing {
      when "derived-from-or-self(node-action,
            'ioam:action-encapsulate')";
    }
  }

  grouping ioam-direct-export-profile {
    description
      "A grouping for the Direct Export Profile.";
    leaf node-action {
      type ioam-node-action;
      default "action-transit";
      description
        "This object indicates the action the node needs to
         take, e.g., encapsulation.";
    }
    uses encap-tracing {
      when "derived-from-or-self(node-action,
            'ioam:action-encapsulate')";
    }
    leaf flow-id {
      when "derived-from-or-self(../node-action,
            'ioam:action-encapsulate')";
      type uint32;
      description
        "A 32-bit flow identifier.  The field is set at the
         encapsulating node.  The Flow ID can be uniformly
         assigned by a central controller or algorithmically
         generated by the encapsulating node.  The latter approach
         cannot guarantee the uniqueness of the Flow ID, yet the
         probability of conflict is small due to the large Flow ID
         space.  'flow-id' is used to correlate the exported data
         of the same flow from multiple nodes and from multiple
         packets.";
    }
    leaf enable-sequence-number {
      when "derived-from-or-self(../node-action,
            'ioam:action-encapsulate')";
      type boolean;
      default "false";
      description
        "This boolean value indicates whether the sequence number
         is used in the Direct Export Option's 32-bit flow
         identifier.  If this value is set to 'true', the sequence
         number is used.  It is turned off by default.";
    }
  }

  grouping ioam-e2e-profile {
    description
      "A grouping for the Edge-to-Edge Profile.";
    leaf node-action {
      type ioam-node-action;
      default "action-transit";
      description
        "This object indicates the action the node needs to
         take, e.g., encapsulation.";
    }
    container e2e-types {
      when "derived-from-or-self(../node-action,
            'ioam:action-encapsulate')";
      description
        "This container provides the list of edge-to-edge types
         for encapsulation.";
      leaf use-namespace {
        type ioam-namespace;
        default "default-namespace";
        description
          "This object indicates the namespace used for
           encapsulation.";
      }
      leaf-list e2e-type {
        type ioam-e2e-type;
        description
          "The edge-to-edge type is only defined at the
           encapsulation node.";
      }
    }
  }

  grouping ioam-admin-config {
    description
      "IOAM top-level administrative configuration.";
    leaf enabled {
      type boolean;
      default "false";
      description
        "This object is used to control the availability of
         configuration.  It MUST be set to 'true' before anything
         in the /ioam/profiles/profile subtree can be edited.
         If 'false', any configuration in place is not used.";
    }
  }

  /*
   * DATA NODES
   */

  container ioam {
    description
      "IOAM top-level container.";
    container info {
      config false;
      description
        "Describes information, such as units or timestamp format,
         that assists monitoring systems in the interpretation of
         the IOAM data.";
      leaf timestamp-type {
        type identityref {
          base lime:timestamp-type;
        }
        description
          "Type of timestamp, such as Truncated PTP (Precision
           Time Protocol) or NTP.";
      }
      list available-interface {
        key "if-name";
        description
          "A list of available interfaces that support IOAM.";
        leaf if-name {
          type if:interface-ref;
          description
            "This is a reference to the interface name.";
        }
      }
    }
    container admin-config {
      description
        "Contains all the administrative configurations related to
         the IOAM functionalities and all the IOAM profiles.";
      uses ioam-admin-config;
    }
    container profiles {
      description
        "Contains a list of IOAM profiles.";
      list profile {
        key "profile-name";
        description
          "A list of IOAM profiles that are configured on the
           node.  There is no mandatory type of profile (e.g.,
           'incremental-trace', 'preallocated-trace') in the list.
           But at least one profile should be added.";
        leaf profile-name {
          type string {
            length "1..300";
          }
          description
            "Unique identifier for each IOAM profile.";
        }
        container filter {
          uses ioam-filter;
          description
            "The filter that is used to indicate the flow to apply
             IOAM.";
        }
        leaf protocol-type {
          type ioam-protocol-type;
          description
            "This object is used to indicate the carrier protocol
             where IOAM is applied.";
        }
        container incremental-tracing-profile {
          if-feature "incremental-trace";
          presence "Enables the Incremental Trace-Option.";
          description
            "This container describes the profile for the
             Incremental Trace-Option.";
          uses ioam-incremental-tracing-profile;
        }
        container preallocated-tracing-profile {
          if-feature "preallocated-trace";
          presence "Enables the Pre-allocated Trace-Option.";
          description
            "This container describes the profile for the
             Pre-allocated Trace-Option.";
          uses ioam-preallocated-tracing-profile;
        }
        container direct-export-profile {
          if-feature "direct-export";
          presence "Enables the Direct Export Option.";
          description
            "This container describes the profile for the
             Direct Export Option.";
          uses ioam-direct-export-profile;
        }
        container pot-profile {
          if-feature "proof-of-transit";
          presence "Enables the Proof of Transit Option.";
          description
            "This container describes the profile for the
             Proof of Transit Option.";
          leaf use-namespace {
            type ioam-namespace;
            default "default-namespace";
            description
              "This object indicates the namespace used for the
               POT types.";
          }
          leaf pot-type {
            type ioam-pot-type;
            description
              "The type of a particular POT variant that specifies
               the POT data that is included.";
          }
        }
        container e2e-profile {
          if-feature "edge-to-edge";
          presence "Enables the Edge-to-Edge Option.";
          description
            "This container describes the profile for the
             Edge-to-Edge Option.";
          uses ioam-e2e-profile;
        }
      }
    }
  }
}
</sourcecode>
    </section>
    <section anchor="Security" numbered="true" toc="include" removeInRFC="false" pn="section-5">
      <name slugifiedName="name-security-considerations">Security Considerations</name>
      <t indent="0" pn="section-5-1">The YANG module specified in this document defines a schema for data
     that is designed to be accessed via network management protocols such
     as NETCONF <xref target="RFC6241" format="default" sectionFormat="of" derivedContent="RFC6241"/> or RESTCONF <xref target="RFC8040" format="default" sectionFormat="of" derivedContent="RFC8040"/>.
     The lowest NETCONF layer is the secure transport layer, and the
     mandatory-to-implement secure transport is Secure Shell (SSH)
     <xref target="RFC6242" format="default" sectionFormat="of" derivedContent="RFC6242"/>. The lowest RESTCONF layer is HTTPS, and the
     mandatory-to-implement secure transport is TLS <xref target="RFC8446" format="default" sectionFormat="of" derivedContent="RFC8446"/>.</t>
      <t indent="0" pn="section-5-2">The Network Configuration Access Control Model (NACM) <xref target="RFC8341" format="default" sectionFormat="of" derivedContent="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.</t>
      <t indent="0" pn="section-5-3">There are a number of data nodes defined in this YANG module that are
     writable/creatable/deletable (i.e., config true, which is the default). These
     data nodes may be considered sensitive or vulnerable in some network
     environments. Write operations (e.g., edit-config) to these data nodes without
     proper protection can have a negative effect on network operations. These are
     the subtrees and data nodes and their sensitivity/vulnerability:</t>
      <dl spacing="normal" indent="3" newline="false" pn="section-5-4">
        <dt pn="section-5-4.1">/ioam/admin-config:</dt>
        <dd pn="section-5-4.2">The items in the "admin-config" container above include the
          top-level administrative configurations related to the IOAM
          functionalities and all the IOAM profiles. Unexpected changes to
          these items could lead to disruption of IOAM functions and/or
          misbehaving IOAM profiles.</dd>
        <dt pn="section-5-4.3">/ioam/profiles/profile:</dt>
        <dd pn="section-5-4.4">The entries in the "profile" list above include the
          whole IOAM profile configurations. Unexpected changes to these
          entries could lead to incorrect IOAM behavior for the
          corresponding flows. Consequently, such changes would impact performance
          monitoring, data analytics, and associated interactions with network
          services.</dd>
      </dl>
      <t indent="0" pn="section-5-5">Some of the readable data nodes in this YANG module may be considered
     sensitive or vulnerable in some network environments. It is thus important to
     control read access (e.g., via get, get-config, or notification) to these data
     nodes. These are the subtrees and data nodes and their
     sensitivity/vulnerability:</t>
      <dl spacing="normal" indent="3" newline="false" pn="section-5-6">
        <dt pn="section-5-6.1">/ioam/profiles/profile:</dt>
        <dd pn="section-5-6.2">The information contained in this subtree
          might reveal information about the services deployed for
          customers. For instance, a customer might be given access to monitor
          the status of their services. In this scenario, the customer's access should
          be restricted to nodes representing their services so as not to
          divulge information about the underlying network structure or
          services.</dd>
      </dl>
    </section>
    <section anchor="IANA" numbered="true" toc="include" removeInRFC="false" pn="section-6">
      <name slugifiedName="name-iana-considerations">IANA Considerations</name>
      <t indent="0" pn="section-6-1">IANA has registered the following URI in the <xref target="RFC3688" format="default" sectionFormat="of" derivedContent="RFC3688">"IETF XML Registry"</xref>:</t>
      <dl spacing="compact" indent="3" newline="false" pn="section-6-2">
        <dt pn="section-6-2.1">URI:</dt>
        <dd pn="section-6-2.2">urn:ietf:params:xml:ns:yang:ietf-ioam</dd>
        <dt pn="section-6-2.3">Registrant Contact:</dt>
        <dd pn="section-6-2.4">The IESG.</dd>
        <dt pn="section-6-2.5">XML:</dt>
        <dd pn="section-6-2.6">N/A; the requested URI is an XML namespace.</dd>
      </dl>
      <t indent="0" pn="section-6-3">IANA has registered the following YANG module in the <xref target="RFC6020" format="default" sectionFormat="of" derivedContent="RFC6020">"YANG Module Names" registry</xref>:</t>
      <dl spacing="compact" indent="3" newline="false" pn="section-6-4">
        <dt pn="section-6-4.1">Name:</dt>
        <dd pn="section-6-4.2">ietf-ioam</dd>
        <dt pn="section-6-4.3">Namespace:</dt>
        <dd pn="section-6-4.4">urn:ietf:params:xml:ns:yang:ietf-ioam</dd>
        <dt pn="section-6-4.5">Prefix:</dt>
        <dd pn="section-6-4.6">ioam</dd>
        <dt pn="section-6-4.7">Reference:</dt>
        <dd pn="section-6-4.8">RFC 9617</dd>
      </dl>
    </section>
  </middle>
  <back>
    <references pn="section-7">
      <name slugifiedName="name-normative-references">Normative References</name>
      <reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2119" quoteTitle="true" derivedAnchor="RFC2119">
        <front>
          <title>Key words for use in RFCs to Indicate Requirement Levels</title>
          <author fullname="S. Bradner" initials="S." surname="Bradner"/>
          <date month="March" year="1997"/>
          <abstract>
            <t indent="0">In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
          </abstract>
        </front>
        <seriesInfo name="BCP" value="14"/>
        <seriesInfo name="RFC" value="2119"/>
        <seriesInfo name="DOI" value="10.17487/RFC2119"/>
      </reference>
      <reference anchor="RFC3688" target="https://www.rfc-editor.org/info/rfc3688" quoteTitle="true" derivedAnchor="RFC3688">
        <front>
          <title>The IETF XML Registry</title>
          <author fullname="M. Mealling" initials="M." surname="Mealling"/>
          <date month="January" year="2004"/>
          <abstract>
            <t indent="0">This document describes an IANA maintained registry for IETF standards which use Extensible Markup Language (XML) related items such as Namespaces, Document Type Declarations (DTDs), Schemas, and Resource Description Framework (RDF) Schemas.</t>
          </abstract>
        </front>
        <seriesInfo name="BCP" value="81"/>
        <seriesInfo name="RFC" value="3688"/>
        <seriesInfo name="DOI" value="10.17487/RFC3688"/>
      </reference>
      <reference anchor="RFC6020" target="https://www.rfc-editor.org/info/rfc6020" quoteTitle="true" derivedAnchor="RFC6020">
        <front>
          <title>YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)</title>
          <author fullname="M. Bjorklund" initials="M." role="editor" surname="Bjorklund"/>
          <date month="October" year="2010"/>
          <abstract>
            <t indent="0">YANG is a data modeling language used to model configuration and state data manipulated by the Network Configuration Protocol (NETCONF), NETCONF remote procedure calls, and NETCONF notifications. [STANDARDS-TRACK]</t>
          </abstract>
        </front>
        <seriesInfo name="RFC" value="6020"/>
        <seriesInfo name="DOI" value="10.17487/RFC6020"/>
      </reference>
      <reference anchor="RFC6241" target="https://www.rfc-editor.org/info/rfc6241" quoteTitle="true" derivedAnchor="RFC6241">
        <front>
          <title>Network Configuration Protocol (NETCONF)</title>
          <author fullname="R. Enns" initials="R." role="editor" surname="Enns"/>
          <author fullname="M. Bjorklund" initials="M." role="editor" surname="Bjorklund"/>
          <author fullname="J. Schoenwaelder" initials="J." role="editor" surname="Schoenwaelder"/>
          <author fullname="A. Bierman" initials="A." role="editor" surname="Bierman"/>
          <date month="June" year="2011"/>
          <abstract>
            <t indent="0">The Network Configuration Protocol (NETCONF) defined in this document provides mechanisms to install, manipulate, and delete the configuration of network devices. It uses an Extensible Markup Language (XML)-based data encoding for the configuration data as well as the protocol messages. The NETCONF protocol operations are realized as remote procedure calls (RPCs). This document obsoletes RFC 4741. [STANDARDS-TRACK]</t>
          </abstract>
        </front>
        <seriesInfo name="RFC" value="6241"/>
        <seriesInfo name="DOI" value="10.17487/RFC6241"/>
      </reference>
      <reference anchor="RFC6242" target="https://www.rfc-editor.org/info/rfc6242" quoteTitle="true" derivedAnchor="RFC6242">
        <front>
          <title>Using the NETCONF Protocol over Secure Shell (SSH)</title>
          <author fullname="M. Wasserman" initials="M." surname="Wasserman"/>
          <date month="June" year="2011"/>
          <abstract>
            <t indent="0">This document describes a method for invoking and running the Network Configuration Protocol (NETCONF) within a Secure Shell (SSH) session as an SSH subsystem. This document obsoletes RFC 4742. [STANDARDS-TRACK]</t>
          </abstract>
        </front>
        <seriesInfo name="RFC" value="6242"/>
        <seriesInfo name="DOI" value="10.17487/RFC6242"/>
      </reference>
      <reference anchor="RFC7950" target="https://www.rfc-editor.org/info/rfc7950" quoteTitle="true" derivedAnchor="RFC7950">
        <front>
          <title>The YANG 1.1 Data Modeling Language</title>
          <author fullname="M. Bjorklund" initials="M." role="editor" surname="Bjorklund"/>
          <date month="August" year="2016"/>
          <abstract>
            <t indent="0">YANG is a data modeling language used to model configuration data, state data, Remote Procedure Calls, and notifications for network management protocols. This document describes the syntax and semantics of version 1.1 of the YANG language. YANG version 1.1 is a maintenance release of the YANG language, addressing ambiguities and defects in the original specification. There are a small number of backward incompatibilities from YANG version 1. This document also specifies the YANG mappings to the Network Configuration Protocol (NETCONF).</t>
          </abstract>
        </front>
        <seriesInfo name="RFC" value="7950"/>
        <seriesInfo name="DOI" value="10.17487/RFC7950"/>
      </reference>
      <reference anchor="RFC8040" target="https://www.rfc-editor.org/info/rfc8040" quoteTitle="true" derivedAnchor="RFC8040">
        <front>
          <title>RESTCONF Protocol</title>
          <author fullname="A. Bierman" initials="A." surname="Bierman"/>
          <author fullname="M. Bjorklund" initials="M." surname="Bjorklund"/>
          <author fullname="K. Watsen" initials="K." surname="Watsen"/>
          <date month="January" year="2017"/>
          <abstract>
            <t indent="0">This document describes an HTTP-based protocol that provides a programmatic interface for accessing data defined in YANG, using the datastore concepts defined in the Network Configuration Protocol (NETCONF).</t>
          </abstract>
        </front>
        <seriesInfo name="RFC" value="8040"/>
        <seriesInfo name="DOI" value="10.17487/RFC8040"/>
      </reference>
      <reference anchor="RFC8174" target="https://www.rfc-editor.org/info/rfc8174" quoteTitle="true" derivedAnchor="RFC8174">
        <front>
          <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
          <author fullname="B. Leiba" initials="B." surname="Leiba"/>
          <date month="May" year="2017"/>
          <abstract>
            <t indent="0">RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t>
          </abstract>
        </front>
        <seriesInfo name="BCP" value="14"/>
        <seriesInfo name="RFC" value="8174"/>
        <seriesInfo name="DOI" value="10.17487/RFC8174"/>
      </reference>
      <reference anchor="RFC8340" target="https://www.rfc-editor.org/info/rfc8340" quoteTitle="true" derivedAnchor="RFC8340">
        <front>
          <title>YANG Tree Diagrams</title>
          <author fullname="M. Bjorklund" initials="M." surname="Bjorklund"/>
          <author fullname="L. Berger" initials="L." role="editor" surname="Berger"/>
          <date month="March" year="2018"/>
          <abstract>
            <t indent="0">This document captures the current syntax used in YANG module tree diagrams. The purpose of this document is to provide a single location for this definition. This syntax may be updated from time to time based on the evolution of the YANG language.</t>
          </abstract>
        </front>
        <seriesInfo name="BCP" value="215"/>
        <seriesInfo name="RFC" value="8340"/>
        <seriesInfo name="DOI" value="10.17487/RFC8340"/>
      </reference>
      <reference anchor="RFC8341" target="https://www.rfc-editor.org/info/rfc8341" quoteTitle="true" derivedAnchor="RFC8341">
        <front>
          <title>Network Configuration Access Control Model</title>
          <author fullname="A. Bierman" initials="A." surname="Bierman"/>
          <author fullname="M. Bjorklund" initials="M." surname="Bjorklund"/>
          <date month="March" year="2018"/>
          <abstract>
            <t indent="0">The standardization of network configuration interfaces for use with the Network Configuration Protocol (NETCONF) or the RESTCONF protocol requires a structured and secure operating environment that promotes human usability and multi-vendor interoperability. There is a need for standard mechanisms to restrict NETCONF or RESTCONF protocol access for particular users to a preconfigured subset of all available NETCONF or RESTCONF protocol operations and content. This document defines such an access control model.</t>
            <t indent="0">This document obsoletes RFC 6536.</t>
          </abstract>
        </front>
        <seriesInfo name="STD" value="91"/>
        <seriesInfo name="RFC" value="8341"/>
        <seriesInfo name="DOI" value="10.17487/RFC8341"/>
      </reference>
      <reference anchor="RFC8342" target="https://www.rfc-editor.org/info/rfc8342" quoteTitle="true" derivedAnchor="RFC8342">
        <front>
          <title>Network Management Datastore Architecture (NMDA)</title>
          <author fullname="M. Bjorklund" initials="M." surname="Bjorklund"/>
          <author fullname="J. Schoenwaelder" initials="J." surname="Schoenwaelder"/>
          <author fullname="P. Shafer" initials="P." surname="Shafer"/>
          <author fullname="K. Watsen" initials="K." surname="Watsen"/>
          <author fullname="R. Wilton" initials="R." surname="Wilton"/>
          <date month="March" year="2018"/>
          <abstract>
            <t indent="0">Datastores are a fundamental concept binding the data models written in the YANG data modeling language to network management protocols such as the Network Configuration Protocol (NETCONF) and RESTCONF. This document defines an architectural framework for datastores based on the experience gained with the initial simpler model, addressing requirements that were not well supported in the initial model. This document updates RFC 7950.</t>
          </abstract>
        </front>
        <seriesInfo name="RFC" value="8342"/>
        <seriesInfo name="DOI" value="10.17487/RFC8342"/>
      </reference>
      <reference anchor="RFC8343" target="https://www.rfc-editor.org/info/rfc8343" quoteTitle="true" derivedAnchor="RFC8343">
        <front>
          <title>A YANG Data Model for Interface Management</title>
          <author fullname="M. Bjorklund" initials="M." surname="Bjorklund"/>
          <date month="March" year="2018"/>
          <abstract>
            <t indent="0">This document defines a YANG data model for the management of network interfaces. It is expected that interface-type-specific data models augment the generic interfaces data model defined in this document. The data model includes definitions for configuration and system state (status information and counters for the collection of statistics).</t>
            <t indent="0">The YANG data model in this document conforms to the Network Management Datastore Architecture (NMDA) defined in RFC 8342.</t>
            <t indent="0">This document obsoletes RFC 7223.</t>
          </abstract>
        </front>
        <seriesInfo name="RFC" value="8343"/>
        <seriesInfo name="DOI" value="10.17487/RFC8343"/>
      </reference>
      <reference anchor="RFC8446" target="https://www.rfc-editor.org/info/rfc8446" quoteTitle="true" derivedAnchor="RFC8446">
        <front>
          <title>The Transport Layer Security (TLS) Protocol Version 1.3</title>
          <author fullname="E. Rescorla" initials="E." surname="Rescorla"/>
          <date month="August" year="2018"/>
          <abstract>
            <t indent="0">This document specifies version 1.3 of the Transport Layer Security (TLS) protocol. TLS allows client/server applications to communicate over the Internet in a way that is designed to prevent eavesdropping, tampering, and message forgery.</t>
            <t indent="0">This document updates RFCs 5705 and 6066, and obsoletes RFCs 5077, 5246, and 6961. This document also specifies new requirements for TLS 1.2 implementations.</t>
          </abstract>
        </front>
        <seriesInfo name="RFC" value="8446"/>
        <seriesInfo name="DOI" value="10.17487/RFC8446"/>
      </reference>
      <reference anchor="RFC8519" target="https://www.rfc-editor.org/info/rfc8519" quoteTitle="true" derivedAnchor="RFC8519">
        <front>
          <title>YANG Data Model for Network Access Control Lists (ACLs)</title>
          <author fullname="M. Jethanandani" initials="M." surname="Jethanandani"/>
          <author fullname="S. Agarwal" initials="S." surname="Agarwal"/>
          <author fullname="L. Huang" initials="L." surname="Huang"/>
          <author fullname="D. Blair" initials="D." surname="Blair"/>
          <date month="March" year="2019"/>
          <abstract>
            <t indent="0">This document defines a data model for Access Control Lists (ACLs). An ACL is a user-ordered set of rules used to configure the forwarding behavior in a device. Each rule is used to find a match on a packet and define actions that will be performed on the packet.</t>
          </abstract>
        </front>
        <seriesInfo name="RFC" value="8519"/>
        <seriesInfo name="DOI" value="10.17487/RFC8519"/>
      </reference>
      <reference anchor="RFC8532" target="https://www.rfc-editor.org/info/rfc8532" quoteTitle="true" derivedAnchor="RFC8532">
        <front>
          <title>Generic YANG Data Model for the Management of Operations, Administration, and Maintenance (OAM) Protocols That Use Connectionless Communications</title>
          <author fullname="D. Kumar" initials="D." surname="Kumar"/>
          <author fullname="Z. Wang" initials="Z." surname="Wang"/>
          <author fullname="Q. Wu" initials="Q." role="editor" surname="Wu"/>
          <author fullname="R. Rahman" initials="R." surname="Rahman"/>
          <author fullname="S. Raghavan" initials="S." surname="Raghavan"/>
          <date month="April" year="2019"/>
          <abstract>
            <t indent="0">This document presents a base YANG Data model for the management of Operations, Administration, and Maintenance (OAM) protocols that use connectionless communications. The data model is defined using the YANG data modeling language, as specified in RFC 7950. It provides a technology-independent abstraction of key OAM constructs for OAM protocols that use connectionless communication. The base model presented here can be extended to include technology-specific details.</t>
            <t indent="0">There are two key benefits of this approach: First, it leads to uniformity between OAM protocols. Second, it supports both nested OAM workflows (i.e., performing OAM functions at the same level or different levels through a unified interface) as well as interactive OAM workflows (i.e., performing OAM functions at the same level through a unified interface).</t>
          </abstract>
        </front>
        <seriesInfo name="RFC" value="8532"/>
        <seriesInfo name="DOI" value="10.17487/RFC8532"/>
      </reference>
      <reference anchor="RFC9197" target="https://www.rfc-editor.org/info/rfc9197" quoteTitle="true" derivedAnchor="RFC9197">
        <front>
          <title>Data Fields for In Situ Operations, Administration, and Maintenance (IOAM)</title>
          <author fullname="F. Brockners" initials="F." role="editor" surname="Brockners"/>
          <author fullname="S. Bhandari" initials="S." role="editor" surname="Bhandari"/>
          <author fullname="T. Mizrahi" initials="T." role="editor" surname="Mizrahi"/>
          <date month="May" year="2022"/>
          <abstract>
            <t indent="0">In situ Operations, Administration, and Maintenance (IOAM) collects operational and telemetry information in the packet while the packet traverses a path between two points in the network. This document discusses the data fields and associated data types for IOAM. IOAM-Data-Fields can be encapsulated into a variety of protocols, such as Network Service Header (NSH), Segment Routing, Generic Network Virtualization Encapsulation (Geneve), or IPv6. IOAM can be used to complement OAM mechanisms based on, e.g., ICMP or other types of probe packets.</t>
          </abstract>
        </front>
        <seriesInfo name="RFC" value="9197"/>
        <seriesInfo name="DOI" value="10.17487/RFC9197"/>
      </reference>
      <reference anchor="RFC9326" target="https://www.rfc-editor.org/info/rfc9326" quoteTitle="true" derivedAnchor="RFC9326">
        <front>
          <title>In Situ Operations, Administration, and Maintenance (IOAM) Direct Exporting</title>
          <author fullname="H. Song" initials="H." surname="Song"/>
          <author fullname="B. Gafni" initials="B." surname="Gafni"/>
          <author fullname="F. Brockners" initials="F." surname="Brockners"/>
          <author fullname="S. Bhandari" initials="S." surname="Bhandari"/>
          <author fullname="T. Mizrahi" initials="T." surname="Mizrahi"/>
          <date month="November" year="2022"/>
          <abstract>
            <t indent="0">In situ Operations, Administration, and Maintenance (IOAM) is used for recording and collecting operational and telemetry information. Specifically, IOAM allows telemetry data to be pushed into data packets while they traverse the network. This document introduces a new IOAM option type (denoted IOAM-Option-Type) called the "IOAM Direct Export (DEX) Option-Type". This Option-Type is used as a trigger for IOAM data to be directly exported or locally aggregated without being pushed into in-flight data packets. The exporting method and format are outside the scope of this document.</t>
          </abstract>
        </front>
        <seriesInfo name="RFC" value="9326"/>
        <seriesInfo name="DOI" value="10.17487/RFC9326"/>
      </reference>
      <reference anchor="RFC9452" target="https://www.rfc-editor.org/info/rfc9452" quoteTitle="true" derivedAnchor="RFC9452">
        <front>
          <title>Network Service Header (NSH) Encapsulation for In Situ OAM (IOAM) Data</title>
          <author fullname="F. Brockners" initials="F." role="editor" surname="Brockners"/>
          <author fullname="S. Bhandari" initials="S." role="editor" surname="Bhandari"/>
          <date month="August" year="2023"/>
          <abstract>
            <t indent="0">In situ Operations, Administration, and Maintenance (IOAM) is used for recording and collecting operational and telemetry information while the packet traverses a path between two points in the network. This document outlines how IOAM-Data-Fields are encapsulated with the Network Service Header (NSH).</t>
          </abstract>
        </front>
        <seriesInfo name="RFC" value="9452"/>
        <seriesInfo name="DOI" value="10.17487/RFC9452"/>
      </reference>
      <reference anchor="RFC9486" target="https://www.rfc-editor.org/info/rfc9486" quoteTitle="true" derivedAnchor="RFC9486">
        <front>
          <title>IPv6 Options for In Situ Operations, Administration, and Maintenance (IOAM)</title>
          <author fullname="S. Bhandari" initials="S." role="editor" surname="Bhandari"/>
          <author fullname="F. Brockners" initials="F." role="editor" surname="Brockners"/>
          <date month="September" year="2023"/>
          <abstract>
            <t indent="0">In situ Operations, Administration, and Maintenance (IOAM) records operational and telemetry information in the packet while the packet traverses a path between two points in the network. This document outlines how IOAM Data-Fields are encapsulated in IPv6.</t>
          </abstract>
        </front>
        <seriesInfo name="RFC" value="9486"/>
        <seriesInfo name="DOI" value="10.17487/RFC9486"/>
      </reference>
      <reference anchor="W3C.REC-xml11-20060816" target="https://www.w3.org/TR/2006/REC-xml11-20060816" quoteTitle="true" derivedAnchor="W3C.REC-xml11-20060816">
        <front>
          <title>Extensible Markup Language (XML) 1.1 (Second Edition)</title>
          <author initials="T." surname="Bray" fullname="Tim Bray">
            <organization showOnFrontPage="true"/>
          </author>
          <author initials="J." surname="Paoli" fullname="Jean Paoli">
            <organization showOnFrontPage="true"/>
          </author>
          <author initials="C. M." surname="Sperberg-McQueen" fullname="Michael Sperberg-McQueen">
            <organization showOnFrontPage="true"/>
          </author>
          <author initials="E." surname="Maler" fullname="Eve Maler">
            <organization showOnFrontPage="true"/>
          </author>
          <author initials="F." surname="Yergeau" fullname="François Yergeau">
            <organization showOnFrontPage="true"/>
          </author>
          <author initials="J." surname="Cowan" fullname="John Cowan">
            <organization showOnFrontPage="true"/>
          </author>
          <date month="August" year="2006"/>
        </front>
        <refcontent>W3C Consortium Recommendation REC-xml11-20060816</refcontent>
      </reference>
    </references>
    <section numbered="true" toc="include" removeInRFC="false" pn="section-appendix.a">
      <name slugifiedName="name-an-example-of-the-increment">An Example of the Incremental Tracing Profile</name>
      <t indent="0" pn="section-appendix.a-1">An XML example (per <xref target="W3C.REC-xml11-20060816" format="default" sectionFormat="of" derivedContent="W3C.REC-xml11-20060816"/>) of the Incremental Tracing Profile is depicted in the
      following figure. This configuration is received by an IOAM ingress
      node. This node encapsulates the IOAM data in the IPv6 Hop-by-Hop option
      header. The trace type indicates that each on-path node needs to capture
      the transit delay and add the data to the IOAM node data list. The incremental
      tracing data space is variable; however, the node data list must not
      exceed 512 bytes.</t>
      <sourcecode name="" type="xml" markers="false" pn="section-appendix.a-2">&lt;rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"
     message-id="101"&gt;
  &lt;edit-config&gt;
    &lt;target&gt;
      &lt;candidate/&gt;
    &lt;/target&gt;
    &lt;config&gt;
      &lt;ioam xmlns="urn:ietf:params:xml:ns:yang:ietf-ioam"&gt;
        &lt;admin-config&gt;
          &lt;enabled&gt;true&lt;/enabled&gt;
        &lt;/admin-config&gt;
        &lt;profiles&gt;
          &lt;profile&gt;
            &lt;profile-name&gt;ietf-test-profile&lt;/profile-name&gt;
            &lt;protocol-type&gt;ipv6&lt;/protocol-type&gt;
            &lt;incremental-tracing-profile&gt;
              &lt;node-action&gt;action-encapsulate&lt;/node-action&gt;
              &lt;trace-types&gt;
                &lt;use-namespace&gt;default-namespace&lt;/use-namespace&gt;
                &lt;trace-type&gt;trace-transit-delay&lt;/trace-type&gt;
              &lt;/trace-types&gt;
              &lt;max-length&gt;512&lt;/max-length&gt;
            &lt;/incremental-tracing-profile&gt;
          &lt;/profile&gt;
        &lt;/profiles&gt;
      &lt;/ioam&gt;
    &lt;/config&gt;
  &lt;/edit-config&gt;
&lt;/rpc&gt;
</sourcecode>
    </section>
    <section numbered="true" toc="include" removeInRFC="false" pn="section-appendix.b">
      <name slugifiedName="name-an-example-of-the-pre-alloc">An Example of the Pre-allocated Tracing Profile</name>
      <t indent="0" pn="section-appendix.b-1">An example of the Pre-allocated Tracing Profile is depicted in the
      following figure. This configuration is received by an IOAM ingress
      node. This node first identifies the target flow by using the ACL
      parameter "test-acl" and then encapsulates the IOAM data in the NSH. The
      trace type indicates that each on-path node needs to capture the
      namespace-specific data in short format and add the data to the IOAM node data
      list. This node pre-allocates the node data list in the packet with 512
      bytes.</t>
      <sourcecode name="" type="xml" markers="false" pn="section-appendix.b-2">&lt;rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"
     message-id="101"&gt;
  &lt;edit-config&gt;
    &lt;target&gt;
      &lt;candidate/&gt;
    &lt;/target&gt;
    &lt;config&gt;
      &lt;ioam xmlns="urn:ietf:params:xml:ns:yang:ietf-ioam"&gt;
        &lt;admin-config&gt;
          &lt;enabled&gt;true&lt;/enabled&gt;
        &lt;/admin-config&gt;
        &lt;profiles&gt;
          &lt;profile&gt;
            &lt;profile-name&gt;ietf-test-profile&lt;/profile-name&gt;
            &lt;filter&gt;
              &lt;filter-type&gt;acl-filter&lt;/filter-type&gt;
              &lt;ace-name&gt;test-acl&lt;/ace-name&gt;
            &lt;/filter&gt;
            &lt;protocol-type&gt;nsh&lt;/protocol-type&gt;
            &lt;preallocated-tracing-profile&gt;
              &lt;node-action&gt;action-encapsulate&lt;/node-action&gt;
              &lt;trace-types&gt;
                &lt;use-namespace&gt;default-namespace&lt;/use-namespace&gt;
                &lt;trace-type&gt;trace-namespace-data&lt;/trace-type&gt;
              &lt;/trace-types&gt;
              &lt;max-length&gt;512&lt;/max-length&gt;
            &lt;/preallocated-tracing-profile&gt;
          &lt;/profile&gt;
        &lt;/profiles&gt;
      &lt;/ioam&gt;
    &lt;/config&gt;
  &lt;/edit-config&gt;
&lt;/rpc&gt;
</sourcecode>
    </section>
    <section numbered="true" toc="include" removeInRFC="false" pn="section-appendix.c">
      <name slugifiedName="name-an-example-of-the-direct-ex">An Example of the Direct Export Profile</name>
      <t indent="0" pn="section-appendix.c-1">An example of the Direct Export Profile is depicted in the following
      figure. This configuration is received by an IOAM egress node. This node
      detects the IOAM Direct Export Option in the IPv6 extension header and
      removes the option to clean all the IOAM data.</t>
      <sourcecode name="" type="xml" markers="false" pn="section-appendix.c-2">&lt;rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"
     message-id="101"&gt;
  &lt;edit-config&gt;
    &lt;target&gt;
      &lt;candidate/&gt;
    &lt;/target&gt;
    &lt;config&gt;
      &lt;ioam xmlns="urn:ietf:params:xml:ns:yang:ietf-ioam"&gt;
        &lt;admin-config&gt;
          &lt;enabled&gt;true&lt;/enabled&gt;
        &lt;/admin-config&gt;
        &lt;profiles&gt;
          &lt;profile&gt;
            &lt;profile-name&gt;ietf-test-profile&lt;/profile-name&gt;
            &lt;protocol-type&gt;ipv6&lt;/protocol-type&gt;
            &lt;direct-export-profile&gt;
              &lt;node-action&gt;action-decapsulate&lt;/node-action&gt;
            &lt;/direct-export-profile&gt;
          &lt;/profile&gt;
        &lt;/profiles&gt;
      &lt;/ioam&gt;
    &lt;/config&gt;
  &lt;/edit-config&gt;
&lt;/rpc&gt;
</sourcecode>
    </section>
    <section numbered="true" toc="include" removeInRFC="false" pn="section-appendix.d">
      <name slugifiedName="name-an-example-of-the-proof-of-">An Example of the Proof of Transit Profile</name>
      <t indent="0" pn="section-appendix.d-1">A simple example of the Proof of Transit Profile is depicted in
the following figure. This
      configuration indicates the node to apply POT type 0 with IPv6
      encapsulation.</t>
      <sourcecode name="" type="xml" markers="false" pn="section-appendix.d-2">&lt;rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"
     message-id="101"&gt;
  &lt;edit-config&gt;
    &lt;target&gt;
      &lt;candidate/&gt;
    &lt;/target&gt;
    &lt;config&gt;
      &lt;ioam xmlns="urn:ietf:params:xml:ns:yang:ietf-ioam"&gt;
        &lt;admin-config&gt;
          &lt;enabled&gt;true&lt;/enabled&gt;
        &lt;/admin-config&gt;
        &lt;profiles&gt;
          &lt;profile&gt;
            &lt;profile-name&gt;ietf-test-profile&lt;/profile-name&gt;
            &lt;protocol-type&gt;ipv6&lt;/protocol-type&gt;
            &lt;pot-profile&gt;
              &lt;pot-type&gt;pot-type-0&lt;/pot-type&gt;
            &lt;/pot-profile&gt;
          &lt;/profile&gt;
        &lt;/profiles&gt;
      &lt;/ioam&gt;
    &lt;/config&gt;
  &lt;/edit-config&gt;
&lt;/rpc&gt;
</sourcecode>
    </section>
    <section numbered="true" toc="include" removeInRFC="false" pn="section-appendix.e">
      <name slugifiedName="name-an-example-of-the-edge-to-e">An Example of the Edge-to-Edge Profile</name>
      <t indent="0" pn="section-appendix.e-1">An example of the Edge-to-Edge Profile is depicted in the following figure.
      This
      configuration is received by an IOAM egress node. This node detects the
      IOAM Edge-to-Edge Option in the IPv6 extension header and removes the
      option to clean all the IOAM data. As the IOAM egress node, it may
      collect the edge-to-edge data and deliver it to the data-exporting
      process.</t>
      <sourcecode name="" type="xml" markers="false" pn="section-appendix.e-2">&lt;rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"
     message-id="101"&gt;
  &lt;edit-config&gt;
    &lt;target&gt;
      &lt;candidate/&gt;
    &lt;/target&gt;
    &lt;config&gt;
      &lt;ioam xmlns="urn:ietf:params:xml:ns:yang:ietf-ioam"&gt;
        &lt;admin-config&gt;
          &lt;enabled&gt;true&lt;/enabled&gt;
        &lt;/admin-config&gt;
        &lt;profiles&gt;
          &lt;profile&gt;
            &lt;profile-name&gt;ietf-test-profile&lt;/profile-name&gt;
            &lt;protocol-type&gt;ipv6&lt;/protocol-type&gt;
            &lt;e2e-profile&gt;
              &lt;node-action&gt;action-decapsulate&lt;/node-action&gt;
            &lt;/e2e-profile&gt;
          &lt;/profile&gt;
        &lt;/profiles&gt;
      &lt;/ioam&gt;
    &lt;/config&gt;
  &lt;/edit-config&gt;
&lt;/rpc&gt;
</sourcecode>
    </section>
    <section anchor="Acknowledgements" numbered="false" toc="include" removeInRFC="false" pn="section-appendix.f">
      <name slugifiedName="name-acknowledgements">Acknowledgements</name>
      <t indent="0" pn="section-appendix.f-1">For their valuable comments, discussions, and feedback, we wish to
      acknowledge <contact fullname="Greg Mirsky"/>, <contact fullname="Reshad Rahman"/>, <contact fullname="Tom Petch"/>, <contact fullname="Mickey Spiegel"/>,
      <contact fullname="Thomas Graf"/>, <contact fullname="Alex Huang Feng"/>, and <contact fullname="Justin Iurman"/>.</t>
    </section>
    <section anchor="authors-addresses" numbered="false" removeInRFC="false" toc="include" pn="section-appendix.g">
      <name slugifiedName="name-authors-addresses">Authors' Addresses</name>
      <author fullname="Tianran Zhou" initials="T." surname="Zhou" role="editor">
        <organization showOnFrontPage="true">Huawei</organization>
        <address>
          <postal>
            <street>156 Beiqing Rd.</street>
            <city>Beijing</city>
            <code>100095</code>
            <country>China</country>
          </postal>
          <email>zhoutianran@huawei.com</email>
        </address>
      </author>
      <author fullname="Jim Guichard" initials="J." surname="Guichard">
        <organization showOnFrontPage="true">Futurewei</organization>
        <address>
          <postal>
            <country>United States of America</country>
          </postal>
          <email>james.n.guichard@futurewei.com</email>
        </address>
      </author>
      <author fullname="Frank Brockners" initials="F." surname="Brockners">
        <organization showOnFrontPage="true">Cisco Systems</organization>
        <address>
          <postal>
            <street>Hansaallee 249, 3rd Floor</street>
            <city>Düsseldorf, Nordrhein-Westfalen</city>
            <code>40549</code>
            <country>Germany</country>
          </postal>
          <email>fbrockne@cisco.com</email>
        </address>
      </author>
      <author fullname="Srihari Raghavan" initials="S." surname="Raghavan">
        <organization showOnFrontPage="true">Cisco Systems</organization>
        <address>
          <postal>
            <street>Tril Infopark Sez, Ramanujan IT City</street>
            <street>Neville Block, 2nd floor, Old Mahabalipuram Road</street>
            <city>Chennai</city>
            <region>Tamil Nadu</region>
            <code>600113</code>
            <country>India</country>
          </postal>
          <email>srihari@cisco.com</email>
        </address>
      </author>
    </section>
  </back>
</rfc>
