<?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-ni-05"
     ipr="trust200902"
     xmlns:xi="http://www.w3.org/2001/XInclude"
>
  <front>
    <title abbrev="Advertise Node Ix">IGP Extensions for Advertising Node Index</title>

     <author initials="H" surname="Chen" fullname="Huaimo Chen">
      <organization>Independent</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>Independent</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 fullname="Mike McBride" initials="M" surname="McBride">
      <organization>Futurewei</organization>
      <address>
        <email>michael.mcbride@futurewei.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" month="september" day="24"/>

    <abstract>
      <t>This document describes OSPF and IS-IS extensions for 
         distributing the node index 
         configured on 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 nodes in a network 
        are numbered or indexed 
        from 1 to the number of the nodes, 
     an efficient stateless multicast along the shortest paths to the egresses
     of a P2MP tree can be achieved using the node indices of the egresses.</t>

     <t>This document proposes OSPF and IS-IS extensions for distributing the 
        node index configured on a node 
        to support the best effort stateless multicast.

        When a controller such as PCE as a controller 
        has the node indexes,
        it can send the P2MP tree encoded in the node indexes to
        the ingress of the tree.</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>

      </list></t>
    </section> <!-- Terminology -->

    </section> <!-- Introduction -->


   <section title="Extensions to OSPF">
     <t>This section describes extensions to OSPF
        for distributing the node index configured on a node.
        The node index of a node MUST be unique in a network. 
        This is like the identifier (ID) of the node.</t>

     <t><xref target="RFC7770"/> defines the  
Router Information (RI) Link state Advertisement (LSA). 
The RI LSA is used to advertise Optional Router Information 
using Router Information LSA TLVs. 

        A new Router Information LSA TLV, called Node Index TLV,
is defined to carry the Node Index configured on the node originating
the RI LSA. 
 
        The Node Index TLV has the following format: 

           <figure anchor="node-index-tlv" 
           title="Node Index 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 (2)          |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |            Node Index         |  
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]></artwork>
</figure>
 
      <list style="hanging" hangIndent="6">
         <t hangText="Type:">TBD1.</t>
         <t hangText="Length:">2.</t>
         <t hangText="Node Index:">The node index configured on a node.</t>
      </list> 
     </t>

   <t>This TLV is optional. It is applicable to both OSPFv2 and OSPFv3.
   For advertising a node index, the area-scoped RI LSA including 
a Node Index TLV is used.</t> 

   </section> <!--  Extension to OSPF -->


   <section title="Extension to IS-IS">
     <t>This section describes an extension to IS-IS
        for distributing the Node Index configured on a node.</t>

     <t><xref target="RFC7981"/> defines the IS-IS Router   
CAPABILITY TLV to advertise Router Information.  
The TLV includes multiple sub-TLVs. 

        A new Node Index sub-TLV to be included in the TLV, 
is defined to carry the Node Index configured on the node originating
the TLV in its LSP. 
 
        This sub-TLV has the following format: 

           <figure anchor="node-index-sub-tlv" 
           title="Node Index 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 (2)  |           Node Index          |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
</figure>
 
      <list style="hanging" hangIndent="6">
         <t hangText="Type:">TBD2.</t>
         <t hangText="Length:">2.</t>
         <t hangText="Node Index:">The Node Index configured on a node.</t>
      </list> 
     </t>

   <t>This sub-TLV is optional.
   For advertising a node index, the area-scoped LSP including 
a Node Index sub-TLV in an IS-IS Router CAPABILITY TLV is used.</t> 

   </section> <!--  Extensions to IS-IS -->


    <section anchor="Security" title="Security Considerations">
      <t>TBD.</t>
    </section>

    <section anchor="IANA" title="IANA Considerations">
    <section anchor="IANA-OSPF" title="OSPF RI TLVs Registry">
      <t>Under "OSPF Router Information (RI) TLVs registry" as defined
         in <xref target="RFC7770"/>, IANA is
         requested to assign a new type as follows:

<figure>
  <artwork> 
  +==============+===================+=====================+
  |  Value       |  Description      |    reference        |
  +==============+===================+=====================+
  |  TBD1        |  Node Index       |    This document    |
  +--------------+-------------------+---------------------+
  </artwork>
</figure>
</t>
    </section>
    <section anchor="IANA-ISIS" title="IS-IS Sub-TLVs for TLV 242 Registry">
      <t>Under "Sub-TLVs for TLV 242 (IS-IS
   Router CAPABILITY TLV) registry" as defined
         in <xref target="RFC7981"/>, IANA is
         requested to assign a new sub-TLV as follows:

<figure>
  <artwork> 
  +==============+===================+=====================+
  |  Value       |  Description      |    reference        |
  +==============+===================+=====================+
  |  TBD2        |  Node Index       |    This document    |
  +--------------+-------------------+---------------------+
  </artwork>
</figure>
</t>
    </section>
    </section>


    <section anchor="Acknowledgements" title="Acknowledgements">
      <t>The authors would like to thank people
      for their comments on this work.</t>
    </section>
  </middle>

  <back>
    <references title="Normative References">
<xi:include
    href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.2119.xml"/>
<xi:include
    href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.7770.xml"/>
<xi:include
    href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.7981.xml"/>
<xi:include
    href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.8174.xml"/>
<!--      <?rfc include="reference.RFC.2119"?>
      <?rfc include="reference.RFC.8174"?>
      <?rfc include="reference.RFC.5226"?>
      <?rfc include="reference.RFC.7770"?>
      <?rfc include="reference.RFC.7981"?>-->
    </references>

<!--    <references title="Informative References">
     <?rfc include="reference.RFC.5250"?>
    </references>-->

  </back>

</rfc>
