<?xml version='1.0' encoding='utf-8'?>
<!-- This template is for creating an Internet Draft using xml2rfc,
    which is available here: http://xml.resource.org. -->
<!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<!-- used by XSLT processors -->
<!-- For a complete list and description of processing instructions (PIs), 
    please see http://xml.resource.org/authoring/README.html. -->
<rfc
      xmlns:xi="http://www.w3.org/2001/XInclude"
      category="std"
      docName="draft-chen-idr-bgp-ls-algo-related-adjacency-sid-04"
      ipr="trust200902"
      obsoletes=""
      updates=""
      submissionType="IETF"
      xml:lang="en"
      tocInclude="true"
      tocDepth="4"
      symRefs="true"
      sortRefs="true"
      version="3">
  <!-- xml2rfc v2v3 conversion 2.38.1 -->
  <!-- category values: std, bcp, info, exp, and historic
    ipr values: trust200902, noModificationTrust200902, noDerivativesTrust200902,
       or pre5378Trust200902
    you can add the attributes updates="NNNN" and obsoletes="NNNN" 
    they will automatically be output with "(if approved)" -->

 <!-- ***** FRONT MATTER ***** -->

 <front>
    <!-- The abbreviated title is used in the page header - it is only necessary if the 
        full title is longer than 39 characters -->

   <title abbrev="BGP-LS Extensions for Algorithm Related Adjacency SID">Algorithm Related Adjacency SID Advertisement</title>
    <seriesInfo name="Internet-Draft" value="draft-chen-idr-bgp-ls-algo-related-adjacency-sid-04"/>
    <!-- add 'role="editor"' below for the editors if appropriate -->

   <!-- Another author who claims to be an editor -->

	
	   <author fullname="Ran Chen" initials="R." surname="Chen">
      <organization>ZTE Corporation</organization>
      <address>
        <postal>
          <street/>
          <!-- Reorder these if your country does things differently -->

         <city>Nanjing</city>
          <region/>
          <code/>
          <country>China</country>
        </postal>
        <email>chen.ran@zte.com.cn</email>
        <!-- uri and facsimile elements may also be added -->
     </address>
    </author>
	
	<author fullname="Shaofu Peng" initials="Sh." surname="Peng">
      <organization>ZTE Corporation</organization>
      <address>
        <postal>
          <street/>
          <!-- Reorder these if your country does things differently -->

         <city>Nanjing</city>
          <region/>
          <code/>
          <country>China</country>
        </postal>
        <email>peng.shaofu@zte.com.cn</email>
        <!-- uri and facsimile elements may also be added -->
     </address>
    </author>
	
<author fullname="Peter Psenak" initials="P." surname="Psenak">
      <organization>Cisco Systems</organization>
      <address>
        <postal>
          <street/>
          <!-- Reorder these if your country does things differently -->

         <city/>
          <region/>
          <code/>
          <country>Slovakia</country>
        </postal>
        <email>ppsenak@cisco.com</email>
        <!-- uri and facsimile elements may also be added -->
     </address>
    </author>
	
<author initials="L" surname="Yao" fullname="Liu Yao">
    <organization>ZTE Corporation</organization>
    <address>
        <postal>
		<street/>
            <country>China</country>
        </postal>
        <email>liu.yao71@zte.com.cn</email>
    </address>
    </author>	
    <date year="2024"/>
    <!-- If the month and year are both specified and are the current ones, xml2rfc will fill 
        in the current day for you. If only the current year is specified, xml2rfc will fill 
	 in the current day and month for you. If the year is not the current one, it is 
	 necessary to specify at least a month (xml2rfc assumes day="1" if not specified for the 
	 purpose of calculating the expiry date).  With drafts it is normally sufficient to 
	 specify just the year. -->

   <!-- Meta-data Declarations -->

   <area>Routing</area>
    <workgroup>IDR</workgroup>
    <!-- WG name at the upperleft corner of the doc,
        IETF is fine for individual submissions.  
	 If this element is not present, the default is "Network Working Group",
        which is used by the RFC Editor as a nod to the history of the IETF. -->

   <keyword>Internet Draft</keyword>
    <!-- Keywords will be incorporated into HTML output
        files in a meta tag but they have no effect on text or nroff
        output. If you submit your draft to the RFC Editor, the
        keywords will be used for the search engine. -->

  
   <abstract>
      <t>This draft describes a mechanism to distribute SR-MPLS algorithm Related Adjacency SID from controllers to the headend routers using BGP-LS.</t>
    </abstract>
  </front>
  <middle>
  
    <section numbered="true" toc="default">
      <name>Introduction</name>
	<t><xref target="I-D.ietf-lsr-algorithm-related-adjacency-sid"/> defines the algorithm identifier can be included as part of an Adjacency-SID advertisement for SR-MPLS.</t>
    <t><xref target="I-D.peng-idr-segment-routing-te-policy-attr"/> proposes extensions of BGP and defines new Segment
   Types to provide algorithm information for SR-MPLS Adjacency-SIDs when delivering SR Policy via BGP.</t>
	<t><xref target="RFC9085"/>defines extensions to the Border Gateway Protocol-Link State (BGP-LS) address family in order to carry SR information via BGP, and an algorithm identifier is included as part of the Prefix-SID TLV advertisement.</t>
	<t>This draft describes a mechanism to distribute SR-MPLS algorithm Related Adjacency SID from controllers to the headend routers using BGP-LS.</t>
	</section>
      <section numbered="true" toc="default">
        <name>Requirements Language</name>
        <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" format="default">RFC 2119</xref>.</t>
      </section>
	  
	  <section numbered="true" toc="default">
        <name>BGP-LS Extensions for SR-MPLS Adjacency with optional</name>
		<section numbered="true" toc="default">
        <name>BGP-LS Extensions for link Attribute</name>
		<t><xref target="I-D.ietf-lsr-algorithm-related-adjacency-sid"/> defines the algorithm identifier can be included as part of an Adjacency-SID advertisement for SR-MPLS. This section defines the encoding of SR-MPLS algorithm Related Adjacency SID describes in <xref target="I-D.ietf-lsr-algorithm-related-adjacency-sid"/>.</t>
        <t>The following link attribute TLVs are defined:</t>
         <table anchor="table_example" align="center">
          <name>New link attribute TLVs</name>
          <thead>
            <tr>
              <th align="center">Type</th>
              <th align="center">Description</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="center">TBD1</td>
              <td align="center">Adjacency SID per Algorithm</td>
            </tr>
            <tr>
             <td align="center">TBD2</td>
              <td align="center">LAN Adjacency SID per Algorithm</td>
            </tr>
          </tbody>
		</table> 
		<section numbered="true" toc="default">
        <name>Adjacency SID per Algorithm TLV</name>
	   <t>The Adjacency SID per Algorithm TLV is used in order to advertise information related to an algorithm Related Adjacency SID. This information is derived from the Adjacency Segment Identifier (Adj-SID) per Algorithm Sub-TLV of ISIS/OSPFv2/OSPFv3(Section 4 of <xref target="I-D.ietf-lsr-algorithm-related-adjacency-sid"/>).</t>
	   <t>The Adjacency SID per Algorithm TLV has the following format:</t>
  <artwork align="center" name="">
			<![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            |              Length           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | Flags         |     Weight    |   Algorithm   |   Reserved    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                   SID/Label/Index (variable)                 //
   +---------------------------------------------------------------+
   ]]></artwork>
 <t>where:</t>
 <t>Type: TBD1 (Suggested value to be assigned by IANA)</t>
 <t>Length: variable.</t>
 <t>Flags: 1-octet value that should be set as:</t>
  <ul spacing="normal">
        <li>IS-IS Adj-SID per Algorithm flags as defined in Section 4.1.1 of <xref target="I-D.ietf-lsr-algorithm-related-adjacency-sid"/></li>
        <li>OSPFv2 Adj-SID per Algorithm Sub-TLV as defined in Section 4.2.1 of <xref target="I-D.ietf-lsr-algorithm-related-adjacency-sid"/>)</li>
		<li>OSPFv3 Adj-SID per Algorithm Sub-TLV as defined in Section 4.3.1 of <xref target="I-D.ietf-lsr-algorithm-related-adjacency-sid"/>)</li>
		 </ul>
 <t>Weight: 1 octet carrying the weight used for load-balancing purposes. The use of weight is described in Section 3.4 of <xref target="RFC8402"/>.</t>
 <t>Algorithm: Refer to ISIS/OSPFv2/OSPFv3 Adj-SID per Algorithm(<xref target="I-D.ietf-lsr-algorithm-related-adjacency-sid"/>). </t>
 <t>Reserved: 1-octet that MUST be set to 0 and ignored on receipt.</t>
 <t>SID/Label/Index:Refer to ISIS/OSPFv2/OSPFv3 Adj-SID per Algorithm(<xref target="I-D.ietf-lsr-algorithm-related-adjacency-sid"/>).</t>
 </section>	
    <section numbered="true" toc="default">
    <name>LAN Adjacency SID per Algorithm TLV</name>
    <t>This information is derived from LAN-Adj-SID per Algorithm Sub-TLV of ISIS/OSPFv2/OSPFv3(Section 4 of <xref target="I-D.ietf-lsr-algorithm-related-adjacency-sid"/>).</t>
    <t>The LAN Adjacency SID per Algorithm TLV has the following format:</t>
 <artwork align="center" name="">
  <![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             |            Length             |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Flags     |     Weight    |  Algorithm    |  Reserved     |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |             OSPF Neighbor ID / IS-IS System ID                |
   +                               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                    SID/Label/Index (variable)                //
   +---------------------------------------------------------------+	
 ]]></artwork>
 <t>where:</t>
 <t>Type: TBD2 (Suggested value to be assigned by IANA)</t>
  <t>Length: variable.</t>
  <t>Flags: 1-octet value that should be set as:</t>
  <ul spacing="normal">
        <li>IS-IS LAN-Adj-SID per Algorithm flags as defined in Section 4.1.2 of <xref target="I-D.ietf-lsr-algorithm-related-adjacency-sid"/></li>
        <li>OSPFv2 LAN-Adj-SID per Algorithm Sub-TLV as defined in Section 4.2.2 of <xref target="I-D.ietf-lsr-algorithm-related-adjacency-sid"/>)</li>
		<li>OSPFv3 LAN-Adj-SID per Algorithm Sub-TLV as defined in Section 4.3.2 of <xref target="I-D.ietf-lsr-algorithm-related-adjacency-sid"/>)</li>
		 </ul>
 <t>Weight: 1 octet carrying the weight used for load-balancing purposes. The use of weight is described in Section 3.4 of <xref target="RFC8402"/>.</t>
 <t>Algorithm: Refer to ISIS/OSPFv2/OSPFv3 LAN-Adj-SID per Algorithm(<xref target="I-D.ietf-lsr-algorithm-related-adjacency-sid"/>).</t>
 <t>Reserved: 1-octet that MUST be set to 0 and ignored on receipt.</t>
 <t>Neighbor ID/IS-IS System ID: Refer to ISIS/OSPFv2/OSPFv3 LAN-Adj-SID per Algorithm(<xref target="I-D.ietf-lsr-algorithm-related-adjacency-sid"/>). </t>
 <t>SID/Label/Index:Refer to ISIS/OSPFv2/OSPFv3 LAN-Adj-SID per Algorithm(<xref target="I-D.ietf-lsr-algorithm-related-adjacency-sid"/>).</t>
 </section>
  </section>
  
 <section numbered="true" toc="default">
   <name>BGP-LS Extensions for Segment Descriptors</name>
   <t><xref target="I-D.peng-idr-segment-routing-te-policy-attr"/> defines four new Segment types of Segment Sub-TLV to provide algorithm information for SR-MPLS Adjacency-SIDs. This section defines the encoding of the Segment Descriptors for each of those Segment types to be used in the Segment sub-TLV describes in <xref target="I-D.ietf-idr-bgp-ls-sr-policy"/>.</t>
    <t>The following Segment Descriptors are defined and their mapping to the respective segment types defined in <xref target="I-D.peng-idr-segment-routing-te-policy-attr"/>:</t>
         <table anchor="table_example1" align="center">
          <name>New Segment Descriptors</name>
          <thead>
            <tr>
              <th align="center">Type</th>
              <th align="center">Segment Description</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="center">TBD3</td>
              <td align="center">(Type L)IPv4 Address and Local Interface ID with optional Algorithm</td>
            </tr>
            <tr>
             <td align="center">TBD4</td>
              <td align="center">(Type M)IPv4 Addresses for link endpoints as Local, Remote pair with optional Algorithm</td>
            </tr>
			 <tr>
             <td align="center">TBD5</td>
              <td align="center">(Type N)IPv6 Prefix and Interface ID for link endpoints as Local, Remote pair, with optional Algorithm for SR-MPLS</td>
            </tr>
			 <tr>
             <td align="center">TBD6</td>
              <td align="center">(Type O)IPv6 Addresses for link endpoints as Local, Remote pair, with optional Algorithm for SR-MPLS</td>
            </tr>
          </tbody>
		</table> 
	<section numbered="true" toc="default">
    <name>Type TBD3: IPv4 Address and Local Interface ID with optional Algorithm</name>
	<t> The Segment is SR-MPLS Adjacency SID with optional Algorithm type and is specified as an IPv4 node address along with the local interface ID on that node. The format of its Segment Descriptor is as follows:</t>
  <artwork align="center" name="">
  <![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
   +-+-+-+-+-+-+-+-+
   |   Algorithm   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                 IPv4 Node Address (4 octets)                  |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                Local Interface ID (4 octets)                  |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 ]]></artwork>
 <t>where:</t>
    <t>Algorithm:  1-octet value that indicates the algorithm used for picking the SID. This is valid only when the A-flag has been set in the Segment TLV as defined in <xref target="I-D.ietf-idr-bgp-ls-sr-policy"/>.  When A-Flag is not encoded, this field SHOULD be set to zero on transmission and MUST be ignored on receipt.</t>
	<t> Other fields have the same meaning as the Type G Segment Sub-TLV Section 5.8.1.5 of <xref target="I-D.ietf-idr-bgp-ls-sr-policy"/>, where:</t>
	<t>IPv4 Node Address: 4-octet value which carries the IPv4 address associated with the node</t>
	<t>Local Interface ID: 4-octet value which carries the local interface ID of the node identified by the Node Address.</t>
	</section>	
		
   <section numbered="true" toc="default">
    <name>Type TBD4: IPv4 Addresses for link endpoints as Local, Remote pair with optional Algorithm</name>
	<t>The Segment is SR-MPLS Adjacency SID with optional Algorithm type and is specified as a pair of IPv4 local and remote addresses. The format of its Segment Descriptor is as follows:</t>
  <artwork align="center" name="">
  <![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
   +-+-+-+-+-+-+-+-+
   |   Algorithm   |	
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                IPv4 Local Address (4 octets)                  |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |               IPv4 Remote Address (4 octets)                  |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 ]]></artwork>
 <t>where:</t>
	<t>Algorithm:  1-octet value that indicates the algorithm used for picking the SID. This is valid only when the A-flag has been set in the Segment TLV as defined in <xref target="I-D.ietf-idr-bgp-ls-sr-policy"/>.  When A-Flag is not encoded, this field SHOULD be set to zero on transmission and MUST be ignored on receipt.</t>
	<t> Other fields have the same meaning as the Type G Segment Sub-TLV Section 5.8.1.6 of <xref target="I-D.ietf-idr-bgp-ls-sr-policy"/>, where:</t>
	<t>IPv4 Local Address: 4-octet value which carries the local IPv4 address associated with the node.</t>
	<t>IPv4 Remote Address: 4-octet value which carries the remote IPv4 address associated with the node's neighbor.  This is optional and MAY be set to 0 when not used (e.g. when identifying point-to-point links).</t>
	</section>	
		
	<section numbered="true" toc="default">
    <name>Type TBD5: IPv6 Prefix and Interface ID for link endpoints as Local, Remote pair, with optional Algorithm for SR-MPLS</name>
	<t> The Segment is SR-MPLS Adjacency SID optional Algorithm type and is specified as a pair of IPv6 global address and interface ID for local and remote nodes. The format of its Segment Descriptor is as follows:</t>
  <artwork align="center" name="">
  <![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
   +-+-+-+-+-+-+-+-+
   |   Algorithm   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |          IPv6 Local Node Global Address (16 octets)           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |          Local Node Interface ID (4 octets)                   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |          IPv6 Remote Node Global Address (16 octets)          |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |          Remote Node Interface ID (4 octets)                  |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 ]]></artwork>
   <t>where:</t>
   <t>Algorithm:  1-octet value that indicates the algorithm used for picking the SID. This is valid only when the A-flag has been set in the Segment TLV as defined in <xref target="I-D.ietf-idr-bgp-ls-sr-policy"/>.  When A-Flag is not encoded, this field SHOULD be set to zero on transmission and MUST be ignored on receipt.</t>
   <t> Other fields have the same meaning as the Type G Segment Sub-TLV Section 5.8.1.7 of <xref target="I-D.ietf-idr-bgp-ls-sr-policy"/>, where:</t>
	<t>IPv6 Local Node Global Address: 16-octet value which carries the IPv6 global address associated with the local node.</t>
	<t>Local Node Interface ID : 4-octet value which carries the interface ID of the local node identified by the Local Node Address.</t>
	<t>IPv6 Remote Node Global Address: 16-octet value which carries the IPv6 global address associated with the remote node. This is optional and MAY be set to 0 when not used (e.g.  when identifying point-to-point links).</t>
	<t> Remote Node Interface ID: 4-octet value which carries the interface ID of the remote node identified by the Remote Node Address. This is optional and MAY be set to 0 when not used (e.g. when identifying point-to-point links).</t>
	</section>	
		
	<section numbered="true" toc="default">
    <name>Type TBD6: IPv6 Addresses for link endpoints as Local, Remote pair, with optional Algorithm for SR-MPLS</name>
    <t>The Segment is SR-MPLS Adjacency SID optional Algorithm type and is specified as a pair of IPv6 Global addresses for local and remote interface addresses. The format of its Segment Descriptor is as follows:</t>
  <artwork align="center" name="">
  <![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
   +-+-+-+-+-+-+-+-+
   |   Algorithm   |	
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                  IPv6 Local Address (16 octets)               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                  IPv6 Remote Address (16 octets)              |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 ]]></artwork>
    <t>where:</t>
	<t>Algorithm:  1-octet value that indicates the algorithm used for picking the SID. This is valid only when the A-flag has been set in the Segment TLV as defined in <xref target="I-D.ietf-idr-bgp-ls-sr-policy"/>.  When A-Flag is not encoded, this field SHOULD be set to zero on transmission and MUST be ignored on receipt.</t>
	<t> Other fields have the same meaning as the Type G Segment Sub-TLV Section 5.8.1.8 of <xref target="I-D.ietf-idr-bgp-ls-sr-policy"/>, where:</t>
	<t>IPv6 Local Address: 16-octet value which carries the local IPv6 address associated with the node.</t>
	<t>IPv6 Remote Address: 16-octet value which carries the remote IPv6 address associated with the node's neighbor</t>	
    </section>	
	</section>	
	</section>	
    <section anchor="Acknowledgements" numbered="true" toc="default">
      <name>Acknowledgements</name>
      <t>TBD.</t>
    </section>
    <!-- Possibly a 'Contributors' section ... -->

   <section anchor="IANA" numbered="true" toc="default">
      <name>IANA Considerations</name>
	<section numbered="true" toc="default">
    <name>BGP-LS Link Attribute TLVs registry</name>
	 <t>This document makes the following Link Attribute TLVs registry under the "Border Gateway Protocol-Link State (BGP-LS) Parameter".</t>
	  <artwork align="center" name=""><![CDATA[
Value  Description                          Reference
--------------------------------------------------------------
TBD1  Adjacency SID per Algorithm           This document
TBD2  LAN Adjacency SID per Algorithm       This document                          	  
           ]]></artwork>
	</section>  
	 <section numbered="true" toc="default">
    <name>BGP-LS SR Segment Descriptors</name>
	<t>This document makes the following SR Segment Descriptor Types registry under the "SR Segment Descriptor Types". The registry contains the following codepoints to be assigned by IANA with the reference set to this document:</t>
	 <artwork align="center" name=""><![CDATA[
Value   Segment Description                                              Reference
--------------------------------------------------------------------------------------
TBD3   IPv4 Address and Local Interface ID with optional Algorithm      This document
TBD4   IPv4 Addresses for link endpoints as Local, Remote pair with     This document
       optional Algorithm                               
TBD5   IPv6 Prefix and Interface ID for link endpoints as Local,        This document
       Remote pair, with optional Algorithm for SR-MPLS                               
TBD6   IPv6 Addresses for link endpoints as Local, Remote pair,         This document
       with optional Algorithm for SR-MPLS                                 
           ]]></artwork>
		</section>  
		</section>  
    <section anchor="Security" numbered="true" toc="default">
      <name>Security Considerations</name>
     <t>TBD.</t>
    </section>
  </middle>
  <!--  *****BACK MATTER ***** -->

 <back>
    <!-- References split into informative and normative -->

   <!-- There are 2 ways to insert reference entries from the citation libraries:
    1. define an ENTITY at the top, and use "ampersand character"RFC2629; here (as shown)
    2. simply use a PI "less than character"?rfc include="reference.RFC.2119.xml"?> here
       (for I-Ds: include="reference.I-D.narten-iana-considerations-rfc2434bis.xml")

    Both are cited textually in the same manner: by using xref elements.
    If you use the PI option, xml2rfc will, by default, try to find included files in the same
    directory as the including file. You can also define the XML_LIBRARY environment variable
    with a value containing a set of directories to search.  These can be either in the local
    filing system or remote ones accessed by http (http://domain/dir/... ).-->

   <references>
        <name>Normative References</name>
        <!--?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml"?-->
      <?rfc include="reference.RFC.2119.xml"?>
	  <?rfc include="reference.RFC.8174.xml"?>
	  <?rfc include="reference.RFC.9085.xml"?>
	  <?rfc include="reference.RFC.8402.xml"?>
	  <?rfc include='reference.I-D.ietf-lsr-algorithm-related-adjacency-sid.xml'?>
	   <?rfc include='reference.I-D.ietf-idr-bgp-ls-sr-policy.xml'?>
	  <?rfc include='reference.I-D.peng-idr-segment-routing-te-policy-attr.xml'?>
      </references>
       
    <!-- Change Log

v00 2006-03-15  EBD   Initial version

v01 2006-04-03  EBD   Moved PI location back to position 1 -
                     v3.1 of XMLmind is better with them at this location.
v02 2007-03-07  AH    removed extraneous nested_list attribute,
                     other minor corrections
v03 2007-03-09  EBD   Added comments on null IANA sections and fixed heading capitalization.
                     Modified comments around figure to reflect non-implementation of
                     figure indent control.  Put in reference using anchor="DOMINATION".
                     Fixed up the date specification comments to reflect current truth.
v04 2007-03-09 AH     Major changes: shortened discussion of PIs,
                     added discussion of rfc include.
v05 2007-03-10 EBD    Added preamble to C program example to tell about ABNF and alternative 
                     images. Removed meta-characters from comments (causes problems).

v06 2010-04-01 TT     Changed ipr attribute values to latest ones. Changed date to
                     year only, to be consistent with the comments. Updated the 
                     IANA guidelines reference from the I-D to the finished RFC.
v07 2020-01-21 HL    Converted the template to use XML schema version 3.
    -->
 </back>
</rfc>
