<?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-chen-lsr-adv-lkno-04"
     ipr="trust200902">
  <front>
    <title abbrev="Advertise Link No">IGP Extensions for Advertising Link Numbers</title>

     <author initials="H" surname="Chen" fullname="Huaimo Chen">
      <organization>Futurewei</organization>
      <address>
        <postal>
          <street></street>
          <city>Boston, MA</city>
          <region></region>
          <code></code>
          <country>USA</country>
        </postal>
        <email>hchen.ietf@gmail.com</email>
      </address>
    </author>

    <author fullname="Donald E. Eastlake 3rd" initials="D" surname="Eastlake">
      <organization>Futurewei</organization>
      <address>
        <postal>
          <street>2386 Panoramic Circle</street>
          <city>Apopka, FL</city>
          <region></region>
          <code>32703</code>
          <country>USA</country>
        </postal>
        <phone>+1-508-333-2270</phone>
        <email>d3e3e3@gmail.com</email>
      </address>
    </author>

     <author initials="A" fullname="Aijun Wang" 
            surname="Wang">
      <organization>China Telecom</organization>
      <address>
        <postal>
          <street>Beiqijia Town, Changping District</street>
          <city>Beijing</city>
          <region> </region>
          <code>102209</code>
          <country>China</country>
        </postal>
        <email>wangaj3@chinatelecom.cn</email>
      </address>
    </author>

    <author fullname="Gyan S. Mishra" initials="G" surname="Mishra">
      <organization>Verizon Inc.</organization>
      <address>
        <postal>
          <street>13101 Columbia Pike</street>
          <city>Silver Spring</city>
          <code>MD 20904</code>
          <country>USA</country>
        </postal>
        <phone> 301 502-1347</phone>
        <email>gyan.s.mishra@verizon.com</email>
      </address>
    </author>

  <author fullname="Yisong Liu" initials="Y" surname="Liu">
   <organization>China Mobile</organization>
   <address>
        <postal>
          <street></street>
          <city></city>
          <region></region>
          <code></code>
          <country></country>
        </postal>
    <email>liuyisong@chinamobile.com</email>
   </address>
  </author>

   <author initials="Y" fullname="Yanhe Fan" 
            surname="Fan">
      <organization>Casa Systems</organization>
      <address>
        <postal>
          <street></street>
          <city></city>
          <region></region>
          <code></code>
          <country>USA</country>
        </postal>
        <email>yfan@casa-systems.com</email>
      </address>
    </author>

   <author initials="L" fullname="Lei Liu" 
            surname="Liu">
      <organization>Fujitsu</organization>
      <address>
        <postal>
          <street> </street>
          <city> </city>
          <region></region>
          <code></code>
          <country>USA</country>
        </postal>
        <email>liulei.kddi@gmail.com</email>
      </address>
    </author>

   <author initials="X" fullname="Xufeng Liu" 
            surname="Liu">
      <organization>Alef Edge </organization>
      <address>
        <postal>
          <street> </street>
          <city> </city>
          <region> </region>
          <code></code>
          <country>USA</country>
        </postal>
        <email>xufeng.liu.ietf@gmail.com</email>
      </address>
    </author>

    <date year="2024"/>

    <abstract>
      <t>This document describes OSPF and IS-IS extensions for distributing 
         the link numbers assigned to the links originating at a node. 
      </t>
    </abstract>

    <note title="Requirements Language">
      <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
      "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
      document are to be interpreted as described in 
      <xref target="RFC2119"/> <xref target="RFC8174"/> 
      when, and only when, they appear in all capitals, as shown here.</t>
    </note>
  </front>

  <middle>
    <section title="Introduction">
     <t>When the links originating at each node in a network are numbered 
   from 1 to the
   number of the such links for that node, an efficient stateless multicast along 
   an explicit P2MP path can be achieved through using
   the link numbers of the links on the path to represent the path.</t>

     <t>This document proposes OSPF and IS-IS extensions for distributing
        the link numbers assigned to the links originating at a node 
        which will support such multicast.

        After a controller such as PCE as a controller has the
        link numbers of the links originating at every node, 
        for an explicit P2MP path, the controller 
        can send the ingress the path represented by the link numbers 
        of the links on the path.</t>

    <section title="Terminology">
      <t>
      <list style="hanging" hangIndent="6">
       <t hangText="LSA:">Link State Advertisement.</t>
       <t hangText="OSPF:">Open Shortest Path First.</t>
       <t hangText="LSP:">Link State Protocol data unit.</t>
       <t hangText="IS-IS:">Intermediate System to Intermediate System.</t>
       <t hangText="MT:">Multi-Topology.</t>
       <t hangText="TE:">Traffic Engineering.</t>
      </list></t>
    </section> <!-- Terminology -->
    </section> <!-- Introduction -->


   <section title="Extensions to OSPFv2">
     <t>This section describes extensions to OSPFv2 for distributing
        the link numbers assigned to the links of a node.</t>

     <t><xref target="RFC7684"/> defines the OSPFv2 Extended Link TLV
        to advertise the information about a link.
        Multiple Link TLVs for the links of a router are included
        in the OSPFv2 Extended Link Opaque LSA of the router.
 
        The OSPFv2 Extended Link TLV has the following format: 

           <figure anchor="ospfv2-link-tlv" 
           title="OSPFv2 Extended Link TLV">
  <artwork> <![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
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |            Type (1)           |      Length (Variable)        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |   Link Type   |                    Reserved                   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                             Link ID                           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                            Link Data                          |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                       Sub-TLVs (variable)                     |
   ~                                                               ~
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]></artwork>
</figure>
 
      <list style="hanging" hangIndent="6">
         <t hangText="Type:">1.</t>
         <t hangText="Length:">Variable, dependent on Sub-TLVs.</t>
         <t hangText="Link Type, Link ID and Link Data:">
            They are defined in Section A.4.2 of 
            <xref target="RFC2328"/>.</t>
<!--
         <t hangText="Link Type:"> 
            1 - Point-to-Point connection to another router,
            2 - Transit Network (or say LAN or broadcast link),
            3 - Stub Network,
            4 - Virtual Link.</t>
         <t hangText="Link ID:"> 
            Identifies the object that this router 
            link connects to. Value depends on the link's Type.
            For Link Type 1, it is Neighboring router's Router ID, 
            2, IP address of Designated Router
            3, IP network/subnet number
            4, Neighboring router's Router ID.</t>
         <t hangText="Link Data:">Value again depends on Link Type. 
            For Link Type 3, it is network's IP address mask. 
            For unnumbered point-to-point connections, it is
                the interface's MIB-II ifIndex. 
            For the other link types (1, 2, 4), 
                it is the router interface's IP address.</t>
-->
         <t hangText="Reserved:">MUST be set to 0 on transmission and MUST 
            be ignored on reception.</t>
      </list> 
     </t>

      <t>
         Under the OSPFv2 Extended Link TLV for a link,
         a Link Number Sub-TLV is
         defined for distributing the link number assigned to the link
         by the router originating the LSA. 
         A Link Number Sub-TLV is included in the Link TLV for a link of 
         Link Type Point-to-Point, Broadcast 
         (i.e., link to LAN or Transit Network), or stub (i.e., link to stub network).

         The Link Number Sub-TLV has the following format:

           <figure anchor="lk-no-sub-tlv" 
           title="Link Number Sub-TLV">
  <artwork> <![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
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |          Type (TBD1)          |             Length            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |         Link Number           | 
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]></artwork>
</figure>
</t>
     <t>
      <list style="hanging" hangIndent="6">
         <t hangText="Type:">TBD1. (Note this is the Sub-TLV Type, not the Link Type.) </t>
         <t hangText="Length:">2.</t>

         <t hangText="Link Number:">A 2-octet field carrying the link number
            assigned to the link when the Link Type of 
            the link in the OSPFv2 Extended Link TLV containing this Sub-TLV
            is 1 (i.e., Point-to-Point connection to another router), 
            2 (i.e., connection to a Transit Network or LAN), or 
            3 (i.e., connection to a stub network).
            </t>
      </list>
     </t>

<!--
     <t>For a link connected to a Transit Network or say LAN from a node,
        a Reverse Link Number Sub-TLV is defined for distributing
        the link number assigned to the reverse link, i.e., the link from
        the designated router (DR) of the LAN to the node.

         A Reverse Link Number Sub-TLV is included in the Link TLV for 
         a link of Link Type Broadcast (or say LAN or Transit Network).
         The Reverse Link Number Sub-TLV has the following format:

           <figure anchor="re-lk-no-sub-tlv" 
           title="Reverse Link Number Sub-TLV">
  <artwork> <![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
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |          Type (TBD2)          |             Length            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      Reverse Link Number      | 
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]></artwork>
</figure>
</t>
     <t>
      <list style="hanging" hangIndent="6">
         <t hangText="Type:">TBD2 is to be assigned by IANA.</t>
         <t hangText="Length:">2.</t>
         <t hangText="Reverse Link Number:">A 2-octet field carrying 
            the link number
            assigned to the link from the DR to the node when the Link Type of 
            the link in the OSPFv2 Extended Link TLV containing this Sub-TLV
            is 2 (i.e., connection to Transit Network or say LAN).
            </t>
      </list>
     </t>
-->
   </section> <!--  Extensions to OSPFv2 -->

   <section title="Extensions to OSPFv3">
     <t>This section describes extensions to OSPFv3
        for distributing 
        the link numbers assigned to the links of a node.</t>

      <t><xref target="RFC8362"/> defines the OSPFv3 Extended Router LSA,
         which may include multiple Router-Link TLVs.

           <figure anchor="e-router-lsa" 
           title="Extended Router-LSA">
  <artwork> <![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
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |              LS Age         |1|0|1|             0x21          |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |                        Link State ID                          |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |                      Advertising Router                       |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |                      LS Sequence Number                       |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |        LS Checksum          |             Length              |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |  0  |N|x|V|E|B|                  Options                      |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |                              TLVs                             |
  :                                                               :
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]></artwork>
</figure>

         A Router-Link TLV defines a single router link.
           <figure anchor="router-link-tlv" 
           title="Router-Link TV">
  <artwork> <![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
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |   Type (1 - Router-Link)    |         Length (Variable)       |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |  Link Type  |       0       |              Metric             |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |                        Interface ID                           |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |                    Neighbor Interface ID                      |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |                      Neighbor Router ID                       |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |                          Sub-TLVs                             |
  :                                                               :
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]></artwork>
</figure>
</t>

<t>Under the Router-Link TLV for a link,  
a Link Number Sub-TLV is defined.
This Sub-TLV has the same format as the Link Number Sub-TLV
defined above for the OSPFv2 Extended Link TLV.
<!--
a Link Number Sub-TLV and a Reverse Number Sub-TLV are defined.
These two Sub-TLVs have the same formats as those two Sub-TLVs
defined under the OSPFv2 Extended Link TLV for a link.
-->
</t>

<t>The Router-Link TLV for a link
         may include a Link Number Sub-TLV   
         for distributing the link number assigned to the link
         by the router originating the LSA.  
<!--
         The Router-Link TLV for a link from a node to a LAN may 
         also include
         a Reverse Link Number Sub-TLV to
         distribute the link number
         assigned to the link from the DR to the node.
-->
</t>
    </section>  <!--  Extensions to OSPFv3 -->



   <section title="Extensions to IS-IS">
     <t>This section describes extensions to IS-IS
        for distributing 
        the link numbers assigned to the links of a node.</t>

    <t>The Extended IS Reachability TLV (Type 22) 
       defined in <xref target="RFC5305"/> 
       may contain Sub-TLVs (such as those for TE (Traffic Engineering)) 
       that apply to a link/interface to a neighbor. 
<!--
       The format of the TLV is as follows:

           <figure anchor="ex-is-reach-tlv" 
           title="Extended IS reachability TLV (22)">
  <artwork> <![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
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |   Type (22)   |    Length     |                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+                               |
   |  Neighbor System ID (6 bytes) and Pseudonode Number (1 byte)  |
   |               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |               |               Metric (3 bytes)                |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                        Sub-TLVs (variable)                    ~
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]></artwork>
</figure>
      <list style="hanging" hangIndent="6">
         <t hangText="Type:">22.</t>
         <t hangText="Length:">Variable, dependent on the number of 
            neighbors.</t>
         <t hangText="Neighbor System ID and Pseudonode Number (7 bytes):">
            Identifies a neighbor over a link/interface.</t>
         <t hangText="Metric (3 bytes):">Indicates the metric to
            the neighbor.</t>

         <t hangText="Sub-TLVs:">Encode the information about the 
            link/interface to the neighbor.</t>
      </list>
-->
   To encode multiple links or interfaces to neighbors, 
   the structure inside TLV is repeated.
</t>

    <t>The Multi-Topology (MT) Intermediate Systems TLV (Type 222) defined in 
       <xref target="RFC5120"/>
       may contain Sub-TLVs (such as those for TE) 
       that apply to a link/interface. 
       It is aligned with the Extended IS
       Reachability TLV (Type 22) but has an additional two bytes in front at
       the beginning of the TLV for MT-ID.</t>

<!--
<t>
           <figure anchor="mt-is-tlv" 
           title="MT Intermediate Systems TLV (222)">
  <artwork> <![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
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |   Type (222)  |    Length     |R R R R|          MT-ID        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Neighbor system ID (6 bytes) and pseudonode number (1 byte)  |
   |                                               +-+-+-+-+-+-+-+-+
   |                                               |Metric(3 bytes)|
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Metric (3 bytes)          | Sub-TLVs-Len  |               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+               |
   |                        Sub-TLVs (variable)                    ~
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]></artwork>
</figure>
   To encode multiple adjacencies, 
   the structure inside TLV is repeated.
   If no Sub-TLVs are used, 11 bytes is needed for a neighbor.
   The TLV can contain up to 23 neighbors.
</t>
-->

    <t>
A Link Number Sub-TLV is defined and 
        used in the Extended IS Reachability TLV (Type 22) and/or 
        MT Intermediate Systems TLV (Type 222) to
        advertise the link numbers assigned to the links of a node.
<!--
Two Sub-TLVs are defined and 
        used in the Extended IS Reachability TLV (Type 22) and/or 
        MT Intermediate Systems TLV (Type 222) to
        advertise the link numbers assigned to the links of a node.
        One is Link Number Sub-TLV and 
        the other is Reverse Link Number Sub-TLV.
-->
</t> 

      <t>
         The Link Number Sub-TLV has the following format:

           <figure anchor="isis-lk-no-sub-tlv" 
           title="IS-IS Link Number Sub-TLV">
  <artwork> <![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
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Type (TBD3)  |    Length     |         Link Number           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>
</t>
     <t>
      <list style="hanging" hangIndent="6">
         <t hangText="Type:">TBD3.</t>
         <t hangText="Length:">2.</t>

         <t hangText="Link Number:">A 2-octet field carrying the link number
            assigned to the link.
            </t>
      </list>
     </t>

<!--
     <t>For a link connected to a Transit Network or say LAN from a node,
        a Reverse Link Number Sub-TLV is defined for distributing
        the link number assigned to the reverse link, i.e., the link from
        the designated router (DR) of the LAN to the node.

         The Reverse Link Number Sub-TLV has the following format:

           <figure anchor="isis-re-lk-no-sub-tlv" 
           title="IS-IS Reverse Link Number Sub-TLV">
  <artwork> <![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
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |  Type (TBD4)  |    Length     |     Reverse Link Number       |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>
</t>
     <t>
      <list style="hanging" hangIndent="6">
         <t hangText="Type:">TBD4 is to be assigned by IANA.</t>
         <t hangText="Length:">2.</t>
         <t hangText="Reverse Link Number:">A 2-octet field carrying 
            the link number
            assigned to the link from the DR to the node when  
            the link is a connection to a Transit Network or say LAN.
            </t>
      </list>
     </t>
-->
    </section>  <!--  Extensions to IS-IS -->



    <section anchor="Security" title="Security Considerations">
      <t>TBD.</t>
    </section>

    <section anchor="IANA" title="IANA Considerations">
      <t>Under "OSPFv2 Extended Link TLV Sub-TLVs registry" as defined
         in <xref target="RFC7684"/>, IANA is
         requested to assign a registry value for 
         Link Number Sub-TLV as follows:

<figure>
  <artwork> 
  +==============+======================+=====================+
  |  Value       |  Description         |    reference        |
  +==============+======================+=====================+
  |  TBD1        |  Link Number         |    This document    |
  +--------------+----------------------+---------------------+
  </artwork>
</figure>
</t>

      <t>Under "OSPFv3 Extended-LSA Sub-TLVs registry" as defined
         in <xref target="RFC8362"/>, IANA is
         requested to assign a registry value for 
         Link Number Sub-TLV as follows:

<figure>
  <artwork> 
  +==============+======================+=====================+
  |  Value       |  Description         |    reference        |
  +==============+======================+=====================+
  |  TBD2        |  Link Number         |    This document    |
  +--------------+----------------------+---------------------+
  </artwork>
</figure>
</t>

      <t>Under "Sub-TLVs for TLVs 22, 23, 25, 141, 222, and 223" 
         for IS-IS TLV Codepoints, IANA is
         requested to assign a codepoint for 
         Link Number Sub-TLV as follows:

<figure>
  <artwork> 
+============+===================+==+==+==+===+===+===+=============+
|Sub-TLV Type|Sub-TLV Name       |22|23|25|141|222|223|reference    |
+============+===================+==+==+==+===+===+===+=============+
| TBD3       |Link Number        |y |n |n | n | y | n |This document|
+------------+-------------------+--+--+--+---+---+---+-------------+
  </artwork>
</figure>
</t>

    </section>


    <section anchor="Acknowledgements" title="Acknowledgements">
      <t>TBD.</t>
    </section>
  </middle>

  <back>
    <references title="Normative References">
      <?rfc include="reference.RFC.2119"?>
      <?rfc include="reference.RFC.8174"?>
      <?rfc include="reference.RFC.5226"?>
      <?rfc include="reference.RFC.7684"?>
      <?rfc include="reference.RFC.8362"?>
      <?rfc include="reference.RFC.2328"?>

      <?rfc include="reference.RFC.5305"?>
      <?rfc include="reference.RFC.5120"?>
    </references>

    <references title="Informative References">
      <?rfc include="reference.RFC.5250"?>
    </references>

  </back>

</rfc>
