<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc="yes"?>
<?rfc tocompact="yes"?>
<?rfc tocdepth="3"?>
<?rfc tocindent="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<rfc category="std" docName="draft-ietf-6man-enhanced-vpn-vtn-id-17"
     ipr="trust200902">
  <front>
    <title abbrev="IPv6 NR Option">Carrying Network Resource Context
    Information in IPv6 Extension Headers and its Applicability to Network
    Resource Partitions</title>

    <author fullname="Jie Dong" initials="J." surname="Dong">
      <organization>Huawei Technologies</organization>

      <address>
        <postal>
          <street>Huawei Campus, No. 156 Beiqing Road</street>

          <city>Beijing</city>

          <code>100095</code>

          <country>China</country>
        </postal>

        <email>jie.dong@huawei.com</email>
      </address>
    </author>

    <author fullname="Zhenbin Li" initials="Z." surname="Li">
      <organization>Huawei Technologies</organization>

      <address>
        <postal>
          <street/>

          <city>Beijing</city>

          <code>100095</code>

          <country>China</country>
        </postal>

        <email>robinli314@163.com</email>
      </address>
    </author>

    <author fullname="Chongfeng Xie" initials="C." surname="Xie">
      <organization>China Telecom</organization>

      <address>
        <postal>
          <street>China Telecom Beijing Information Science &amp; Technology,
          Beiqijia</street>

          <city>Beijing</city>

          <code>102209</code>

          <country>China</country>
        </postal>

        <email>xiechf@chinatelecom.cn</email>
      </address>
    </author>

    <author fullname="Chenhao Ma" initials="C." surname="Ma">
      <organization>China Telecom</organization>

      <address>
        <postal>
          <street>China Telecom Beijing Information Science &amp; Technology,
          Beiqijia</street>

          <city>Beijing</city>

          <code>102209</code>

          <country>China</country>
        </postal>

        <email>machh@chinatelecom.cn</email>
      </address>
    </author>

    <author fullname="Gyan Mishra" initials="G." surname="Mishra">
      <organization>Verizon Inc.</organization>

      <address>
        <postal>
          <street/>

          <city/>

          <region/>

          <code/>

          <country/>
        </postal>

        <email>gyan.s.mishra@verizon.com</email>
      </address>
    </author>

    <date day="17" month="November" year="2026"/>

    <abstract>
      <t>This document specifies a new IPv6 Hop-by-Hop option to carry Network
      Resource related information in data packets. The new option is called
      the Network Resource (NR) Option. It can be used to carry general
      information about network resource semantics and functions.</t>

      <t>A Network Resource Partition (NRP) is a subset of the network
      resources and associated policies on each of a connected set of links in
      an underlay network. When forwarding packets within a specific NRP, some
      fields in the data packet (these fields are called the NRP Selector ID)
      are used to identify the NRP to which the packet belongs so that
      NRP-specific processing can be performed on each node along the
      forwarding path. The Network Resource Option can be used to carry the
      NRP Selector ID in IPv6 packets.</t>
    </abstract>
  </front>

  <middle>
    <section title="Introduction">
      <t>This document specifies a mechanism to carry network resource related
      information in a new IPv6 Hop-by-Hop option (Section 4.3 of <xref
      target="RFC8200"/>) called the "Network Resource (NR) option". This is a
      generic mechanism designed to carry resource identifiers and related
      information that has network-wide meaning and is applicable to different
      semantics and functions.</t>

      <t>Virtual Private Networks (VPNs) <xref target="RFC4026"/> provide
      different customers with logically isolated connectivity over a common
      network infrastructure. Some customers require network connectivity
      services with features that are more advanced compared to conventional
      VPNs. This kind of network service is called an enhanced VPN <xref
      target="RFC9732"/>. Enhanced VPNs can be used, for example, to deliver
      Network Slice Services as described in Section 7.4 of <xref
      target="RFC9543"/>.</t>

      <t>Section 7.1 of <xref target="RFC9543"/> introduces the concept of the
      Network Resource Partition (NRP), which is "a subset of the
      buffer/queuing/scheduling resources and associated policies on each of a
      connected set of links in the underlay network". An NRP may be
      associated with a logical network topology to select or specify the set
      of links and nodes involved.</t>

      <t><xref target="RFC9732"/> specifies the framework of NRP-based
      enhanced VPNs and describes the candidate component technologies in
      different network planes and network layers. An NRP could be used as the
      underlay to meet the requirement of one or a group of enhanced VPN
      services.</t>

      <t>One approach to deploying NRPs is to introduce a dedicated NRP
      Selector ID carried in data packets and used to identify the set of
      network resources allocated to an NRP. This way, packets mapped to an
      NRP can be processed and forwarded using the NRP-specific network
      resources. The NRP Selector ID can identify a subset of the network
      resources (e.g., bandwidth, buffer, and queuing resources) allocated on
      the set of links and nodes involved in the NRP. The logical topology
      associated with an NRP could be defined and identified using mechanisms
      such as Multi-Topology <xref target="RFC4915"/>, <xref
      target="RFC5120"/>, or Flex-Algo <xref target="RFC9350"/>.</t>

      <t>In networks built with NRPs, the NRP Selector ID can be carried in
      the NR option. Each intermediate node along the forwarding path examines
      every hop-by-hop option, so it will look at the NR option and can
      extract the NRP Selector ID, map it to the corresponding NRP, and invoke
      NRP-specific packet processing and forwarding using the set of
      NRP-specific resources.</t>

      <t>The Network Resource option can support a large number of NRPs in an
      IPv6 network, but operators deploying NRPs are advised to consider the
      trade-offs between scalability, manageability, and flexibility discussed
      in <xref target="I-D.ietf-teas-nrp-scalability"/>.</t>

      <section title="Requirements Language">
        <t>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 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only
        when, they appear in all capitals, as shown here.</t>
      </section>
    </section>

    <section title="IPv6 Extension Header Option for Network Resource Information">
      <t>A new Hop-by-Hop option (Section 4.3 of <xref target="RFC8200"/>)
      type "Network Resource" is defined to carry the network resource related
      information. Its format is shown in Figure 1.</t>

      <t><figure>
          <artwork align="center"><![CDATA[      0                   1                   2                   3
      0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1

                                     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                     |   Option Type |  Opt Data Len |
                                     |B B C T T T T T|               |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |     Flags     | Context Type  |            Reserved           |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     ~                     Network Resource ID                       ~
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

           Figure 1. The format of Network Resource (NR) Option]]></artwork>
        </figure></t>

      <t>Option Type: 8-bit identifier of the type of option. The type of NR
      option is TBA. The encoding of the Option Type identifier follows the
      rules as specified in <xref target="RFC8200"/>. The bits of the type
      field are defined as shown below:</t>

      <t><list style="symbols">
          <t>BB 00 The highest-order 2 bits are set to 00 to indicate that a
          node which does not recognize this type will skip over it and
          continue processing the header.</t>

          <t>C 0 The third highest-order bit is set to 0 to indicate this
          option does not change en route.</t>

          <t>TTTTT Option Type to be assigned from IANA.</t>
        </list></t>

      <t>Opt Data Len: 8-bit unsigned integer indicates the length of the
      option Data field of this option, in octets.</t>

      <t>Flags: 8-bit flags field. The most significant bit is defined in this
      document.</t>

      <t><figure>
          <artwork align="center"><![CDATA[           0 1 2 3 4 5 6 7
          +-+-+-+-+-+-+-+-+
          |S|R R R R R R R|
          +-+-+-+-+-+-+-+-+]]></artwork>
        </figure><list style="symbols">
          <t>S (Strict Match): The S flag is used to indicate whether the NR
          ID MUST be strictly matched for the processing of the packet. When
          the S flag in the NR option of a received packet is set to 1, if the
          NR ID in the packet does not match with any of the network resources
          provisioned on the network node, the packet MUST be dropped. When
          the S flag in the NR option of a received packet is set to 0, if the
          NR ID in the packet does not match with any of the network resources
          provisioned on the network node, the packet MUST be forwarded using
          the default set of resource and behavior as if the NR option does
          not exist.</t>

          <t>R (Reserved): These bits are reserved for future use. They MUST
          be set to 0 on transmission and MUST be ignored on receipt.</t>
        </list></t>

      <t>The setting of the S flag depends on the operator's policy. Such
      policy can be NRP-specific, and may be at a fine granularity to apply to
      a subset of packets within an NRP. Such policy needs to be provided to
      the ingress nodes to apply to packets which are mapped to corresponding
      NRPs. For a given NRP, the suggested default policy is to make the S
      flag set.</t>

      <t>As an example, for OAM packets which are used to detect the
      availability of a forwarding path associated with NRP-specific
      resources, the S flag should be set to 1. This way, only when the set of
      network resources and policies are correctly instantiated for the NRP on
      all network links along a path, the OAM packets can be received by an
      egress endpoint and the availability check can be passed.</t>

      <t>The S flag in the NR option provides an approach for fine-granular
      control of the forwarding policy of packets whose NR IDs do not match
      with the network resources provisioned on the transit network nodes. One
      alternate approach is to specify the forwarding policy of packets in
      different NRPs via configuration, while additional configuration would
      be needed when non-default fine-granular policy is required for a given
      NRP.</t>

      <t>Context Type (CT): One-octet field used to indicate the semantics and
      length of the NR ID carried in the option. The context value defined in
      this document is as follows:</t>

      <t><list style="symbols">
          <t>CT=0: The NR ID is a 4-octet network-wide unique NRP Selector ID,
          which is used to identify the subset of network resources allocated
          to the NRP on the involved network links.</t>
        </list>Reserved: 2-octet field reserved for future use. They MUST be
      set to 0 on transmission and MUST be ignored on receipt.</t>

      <t>NR ID: The identifier of a set of network resources, the semantics of
      the ID is determined by the Context Type. The length of the NR ID is the
      Opt Data Length minus 4.</t>

      <t>Note that, in the context of 5G network slicing, if a deployment
      found it useful, a four-octet NRP Selector ID field (CT=0) may be
      derived from the four-octet Single Network Slice Selection Assistance
      Information (S-NSSAI) defined in 3GPP <xref target="TS23501"/>.</t>
    </section>

    <section title="Procedures">
      <t>This section describes the procedures for NR option processing when
      the value of the Context Type (CT) is set to 0. In this case the NRP
      Selector ID is carried in the NR option. The processing procedures for
      NR option with other CT values are out of the scope of this document,
      and will be specified in separate documents which introduce those CT
      values.</t>

      <section anchor="adding" title="Adding NR Option to Packets">
        <t>When an ingress node of an IPv6 domain receives a packet, according
        to the traffic classification and mapping policy, if the packet needs
        to be steered into an NRP, then the packet MUST be encapsulated in an
        outer IPv6 header with the source and destination addresses set
        according to the local policy. The NRP Selector ID which the packet is
        mapped to according to the policy MUST be carried in the NR option of
        the Hop-by-Hop Options header, which is associated with the outer IPv6
        header. It is RECOMMENDED the NR option is carried as the first option
        in the Hop-by-Hop Options header because the behaviors triggered by
        the other hop-by-hop options may need to be applied in the context of
        the NRP.</t>

        <t>Note that adding an extension header to a packet changes the header
        overheader and so reduces the part of the MTU that is available to
        carry data. If a packet already fills the MTU, then adding an
        extension header will cause it to be too large and so cause
        fragmentation. Thus, when it is known that the NR option will be added
        to the packets, the path MTU should be reported to take this into
        account. See <xref target="RFC8200"/> for more discussion of this
        issue.</t>
      </section>

      <section title="NRP-specific Packet Forwarding">
        <t>On receipt of a packet with an NR option, each transit network
        nodes that can process the Hop-by-Hop Options header and the NR option
        at full forwarding rate <xref target="RFC9673"/> MUST use the NRP
        Selector ID to determine the set of local network resources which are
        allocated to the NRP. The packet forwarding behavior is based on both
        the destination IP address and the NRP Selector ID. More specifically,
        the destination IP address is used to determine the next-hop and the
        outgoing interface, and the NRP Selector ID is used to determine the
        subset of network resources on the outgoing interface which are
        allocated to the NRP for processing and sending the packet. If the NRP
        Selector ID in the packet does not match with any of the NRP
        provisioned on the outgoing interface, the S flag in the NR option
        SHOULD be used to determine whether the packet should be dropped or
        forwarded using the default set of network resources of the outgoing
        interface. The Traffic Class field of the outer IPv6 header MAY be
        used to provide differentiated treatment for packets which belong to
        the same NRP. On the egress nodes of the IPv6 domain, if the
        destination address in the outer IPv6 header of a received packet
        matches with a local address, it MUST decapsulate the outer IPv6
        header and the Hop-by-Hop Options header which includes the NR
        option.</t>

        <t>There can be different approaches of partitioning the network
        resources and allocating them to different NRPs in the forwarding
        plane. For example, on one physical interface, a subset of the
        forwarding plane resources (e.g., bandwidth and the associated buffer
        and queuing resources) can be allocated to a particular NRP and
        represented as a virtual sub-interface or a data channel with reserved
        bandwidth resource. The IPv6 destination address of the received
        packet is used to identify the next-hop and the outgoing Layer 3
        interface, and the NRP Selector ID is used to further identify the
        virtual sub-interface or the data channel on the outgoing interface
        which is associated with the NRP.</t>

        <t>According to <xref target="RFC9673"/>, network nodes which do not
        support the processing of Hop-by-Hop Options header would ignore the
        Hop-by-Hop options header and forward the packet only based on the
        destination IP address. Network nodes which support Hop-by-Hop Options
        header, but do not support the NR option would ignore the NR option
        and forward the packet only based on the destination IP address. The
        network node may process the rest of the Hop-by-Hop options in the
        Hop-by-Hop Options header.</t>
      </section>
    </section>

    <section anchor="opscons" title="Operational Considerations">
      <t>The NRP Selecor ID is a network-wide unique identifier which needs to
      be managed by the network operator. To avoid possible conflicts in the
      assignment and use of NRP Selector IDs, operators are RECOMMENDED to
      start the allocation of NRP Selector ID from 1, and continue the
      allocation incrementally in the NRP Selector ID space.</t>

      <t>As described in section 4.8 of <xref target="RFC8200"/>, network
      nodes may be configured to ignore the Hop-by-Hop Options header, drop
      packets containing a Hop-by-Hop Options header, or assign packets
      containing a Hop-by-Hop Options header to a slow processing path. In
      networks with such network nodes, packets mapped to an NRP may be
      dropped due to the existence of the Hop-by-Hop Options header. Thus
      operators need to make sure that all the network nodes involved in an
      NRP can either process the Hop-by-Hop Options header in full forwarding
      rate, or ignore the Hop-by-Hop Options header. Since an NRP is
      associated with a logical network topology, one practical approach is to
      ensure that all the network nodes involved in that logical topology
      support the processing of the Hop-by-Hop Options header and the NR
      option in the fast path, and constrain the packet forwarding path to the
      logical topology of the NRP.</t>

      <t><xref target="adding"/> and <xref target="RFC8200"/> provide
      discussion of the MTU implications of adding an NR option to
      packets.</t>

      <t><xref target="RFC9673"/> specifies the modified procedures for the
      processing of IPv6 Hop-by-Hop Options header, with the purpose of making
      the Hop-by-Hop Options header useful. Network nodes complying with <xref
      target="RFC9673"/> will not drop packets with Hop-by-Hop Options header
      and the NR option.</t>
    </section>

    <section title="Considerations about Generalization">
      <t>This section gives some analysis about to what extent the semantics
      of NR Option could be generalized, and how the generalization could be
      achieved with the encoding specified in section 2.</t>

      <t>Based on the NRP definition in <xref target="RFC9543"/>, the concept
      of NRP could be extended as: an underlay network construct which is
      associated with a set of network-wide attributes and states maintained
      on each participating network node. The attributes associated with an
      NRP may include but not limited to, forwarding plane resources, network
      topologies, and network functions etc.</t>

      <t><list style="symbols">
          <t>The network resource can refer to various type of forwarding
          plane resources, including link bandwidth, buffering and queueing
          resources.</t>

          <t>The network resource can refer to topologies with
          multipoint-to-multipoint, point-to-point, point-to-multipoint, or
          multipoint-to-point connectivity.</t>

          <t>The network resources may include both packet forwarding actions
          and other types network functions which can be executed on data
          packets.</t>
        </list>Thus the semantics of network resource can be quite generic.
      Although generalization is something good to have, it would be important
      to understand and identify the boundary of generalization. In this
      document, it is anticipated that for one network attribute to be
      considered as network resource, it needs to be network-wide attribute
      rather than a single node-specific attribute. Thus whether a
      network-wide view can be provided or not could be considered as one
      prerequisite of making one attribute part of the NR option.</t>

      <t>The format of the NR option contains the Flags field, the Context
      Type field, and the Reserved field, which provide the capability for
      future extensions. That said, since the NR option needs to be processed
      by network nodes with full forwarding rate, the capability of network
      devices need to be considered when new semantics and encoding are
      introduced.</t>
    </section>

    <section anchor="IANA" title="IANA Considerations">
      <t>This document requests IANA to assign a new option type from
      "Destination Options and Hop-by-Hop Options" registry <xref
      target="IANA-HBH"/>.</t>

      <t><figure>
          <artwork><![CDATA[   Hex Value      Binary Value      Description      Reference
                  act chg rest
   -----------------------------------------------------------
      TBA         00   0  tba        NR Option      [this document] ]]></artwork>
        </figure></t>

      <t>This document requests IANA to create a new registry for the "Network
      Resource Option Context Type" under the "Internet Protocol Version 6
      (IPv6) Parameters" registry. The allocation policy of this registry is
      "Standards Action". The initial code points are assigned by this
      document as follows:</t>

      <t><figure>
          <artwork><![CDATA[   Value          Description            Reference
   -----------------------------------------------------
     0            NRP Selector ID      [this document]
   1-251          Unassigned
  252-254         Experimental Use
    255           Reserved             [this document]
]]></artwork>
        </figure></t>

      <t>This document requests IANA to create a new registry for the "NR
      Option Flags" under the "Internet Protocol Version 6 (IPv6) Parameters"
      registry. The allocation policy of this registry is "Standards Action".
      The initial code points are assigned by this document as follows:</t>

      <t><figure>
          <artwork><![CDATA[    Bit           Description            Reference
   -----------------------------------------------------
     0            Strict Match         [this document]
    1-7           Reserved
]]></artwork>
        </figure></t>
    </section>

    <section anchor="Security" title="Security Considerations">
      <t>The security considerations with IPv6 Hop-by-Hop Options header are
      described in <xref target="RFC8200"/>, <xref target="RFC7045"/>, <xref
      target="RFC9098"/> <xref target="RFC9099"/> and <xref
      target="RFC9673"/>. This document introduces a new IPv6 Hop-by-Hop
      option which is either processed in the fast path or ignored by network
      nodes, thus it does not introduce additional security issues to the
      network nodes.</t>

      <t>When the NR option is used to carry the NRP Selector ID, the exposure
      of this identifier introduces two primary security risks. First, an
      attacker may observe the NRP Selector ID to infer the service type or
      performance requirements (e.g., low latency, high throughput) of the
      associated flow. Such inference could facilitate targeted
      attacks&mdash;e.g., selectively disrupting high-priority or
      delay-sensitive services. Second, an attacker capable of modifying the
      NRP Selector ID in transit can alter the network treatment applied to a
      packet (e.g., sending the packet to a different queue). This
      manipulation may degrade performance guarantees, potentially violating
      service level agreements (SLAs) or compromising isolation between
      different services. The NR option SHOULD be used in trusted domains
      which are under the administration of the network operator, and
      filtering SHOULD be performed at the ingress to a domain to eliminate
      packets entering the domain that already carry an NR option.</t>

      <t>Operators should be aware that the sequential nature of assignment of
      NRP Selector IDs as described in <xref target="opscons"/> may make the
      values more predictable for an attacker.</t>

      <t>The privacy of users and their data flows should not be impacted by
      the procedures described in this document. The NR option does not carry
      identifiers of users or of applications. However, specific types of
      packet flows may be mapped to specific NRPs based on their source and
      destination addresses and their other flow identifiers. Thus, knowing
      the Network Resource ID might allow an attacker to identify packets
      belonging to a flow. This is, however, only a short-cut as all of this
      information is available in the packets.</t>
    </section>

    <section title="Contributors">
      <t><figure>
          <artwork><![CDATA[   Zhibo Hu
   Email: huzhibo@huawei.com

   Lei Bao
   Email: baolei7@huawei.com
]]></artwork>
        </figure></t>
    </section>

    <section anchor="Acknowledgements" title="Acknowledgements">
      <t>The authors would like to thank Juhua Xu, James Guichard, Joel
      Halpern, Tom Petch, Aijun Wang, Zhenqiang Li, Tom Herbert, Adrian
      Farrel, Eric Vyncke, Erik Kline, Mohamed Boucadair, Ketan Talaulikar,
      Vishnu Pavan Beeram, and Eric Vyncke for their review and valuable
      comments.</t>
    </section>
  </middle>

  <back>
    <references title="Normative References">
      <reference anchor="IANA-HBH"
                 target="https://www.iana.org/assignments/ipv6-parameters/">
        <front>
          <title>IANA, "Destination Options and Hop-by-Hop Options"</title>

          <author>
            <organization/>
          </author>

          <date year="2016"/>
        </front>
      </reference>

      <?rfc include="reference.RFC.2119"?>

      <?rfc include='reference.RFC.8174'?>

      <?rfc include='reference.RFC.8200'?>

      <?rfc include='reference.RFC.9543'?>

      <?rfc include='reference.RFC.9673'?>

      <?rfc include='reference.RFC.9732'?>
    </references>

    <references title="Informative References">
      <reference anchor="TS23501"
                 target="https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3144">
        <front>
          <title>3GPP TS23.501</title>

          <author>
            <organization/>
          </author>

          <date year="2016"/>
        </front>
      </reference>

      <?rfc include='reference.RFC.4026'?>

      <?rfc include='reference.RFC.4915'?>

      <?rfc include='reference.RFC.5120'?>

      <?rfc include='reference.RFC.7045'?>

      <?rfc include='reference.RFC.9098'?>

      <?rfc include='reference.RFC.9099'?>

      <?rfc include='reference.RFC.9350'?>

      <?rfc include='reference.I-D.ietf-teas-nrp-scalability'?>
    </references>
  </back>
</rfc>
