<?xml version="1.0" encoding="US-ASCII"?>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc2629 version 1.2.6 -->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc="yes"?>
<?rfc sortrefs="yes"?>
<?rfc symrefs="yes"?>
<?rfc comments="yes"?>
<rfc category="std" docName="draft-chen-idr-bgp-ls-algo-related-adjacency-sid-05"
     ipr="trust200902">
  <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">Algorithm Related Adjacency SID Advertisement</title>
<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 fullname="Yao Liu" initials="Y." surname="Liu">
       <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>liu.yao71@zte.com.cn</email>
        <!-- uri and facsimile elements may also be added -->
     </address>
    </author>	
    <date year="2026"/>
    <!-- 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>Inter-Domain Routing</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.ietf-idr-sr-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><xref target="RFC9857"/> describes a mechanism to distribute SR policy information to external components using BGP-LS. SR policy information can be used by external components for path computation, re-optimization, service placement, network visualization, etc.</t>
	<t>This draft describes a mechanism to distribute SR-MPLS algorithm Related Adjacency SID to external components using BGP-LS.</t>
      	 <section numbered="true" toc="default">
        <name>Requirements Language</name>
        <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" format="default"/> <xref target="RFC8174" format="default"/> when, and only when, they appear in all capitals, as shown here.</t>
      </section>
    </section>
		<section numbered="true" toc="default">
        <name>BGP-LS Extensions for SR-MPLS Adjacency SID with optional SR Algorithm </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 introduces extensions to BGP-LS to convey algorithm information associated with SR-MPLS adjacency SIDs.</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 with Algorithm</td>
            </tr>
            <tr>
             <td align="center">TBD2</td>
              <td align="center">LAN Adjacency SID with Algorithm</td>
            </tr>
          </tbody>
		</table> 
		<section numbered="true" toc="default">
        <name>Adjacency SID with Algorithm TLV</name>
	   <t>The Adjacency SID with 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) with 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 with Algorithm TLV has the following format:</t>
  <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            |              Length           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | Flags         |     Weight    |   Algorithm   |   Reserved    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                   SID/Label/Index (variable)                 //
   +---------------------------------------------------------------+
   ]]></artwork>
 <t>where:</t>
 <t>Type: TBD1 (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>Refer to the flags defined in the IS-IS Adj-SID with Algorithm Sub-TLV, as described in Section 4.1.1 of <xref target="I-D.ietf-lsr-algorithm-related-adjacency-sid"/>.</li>
        <li>Refer to the flags defined in the OSPFv2 Adj-SID with Algorithm Sub-TLV, as described in Section 4.2.1 of <xref target="I-D.ietf-lsr-algorithm-related-adjacency-sid"/>)</li>
		<li>Refer to the flags defined in the OSPFv3 Adj-SID with Algorithm Sub-TLV, as described 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 4 of <xref target="I-D.ietf-lsr-algorithm-related-adjacency-sid"/>.</t>
 <t>Algorithm: 1-octet value identifies the algorithm. The semantics of the algorithm are described in ISIS/OSPFv2/OSPFv3 Adj-SID with 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: Label or index value as defined in Section 4 of <xref target="I-D.ietf-lsr-algorithm-related-adjacency-sid"/>.</t>
 </section>	
    <section numbered="true" toc="default">
    <name>LAN Adjacency SID with Algorithm TLV</name>
    <t>This information is derived from LAN-Adj-SID with 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 with Algorithm TLV has the following format:</t>
<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             |            Length             |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Flags     |     Weight    |  Algorithm    |  Reserved     |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

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

   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                    SID/Label/Index (variable)                //
   +---------------------------------------------------------------+	
 ]]></artwork>
 <t>where:</t>
 <t>Type: TBD2 (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>Refer to the flags defined in the IS-IS LAN-Adj-SID with Algorithm Sub-TLV, as described in Section 4.1.2 of <xref target="I-D.ietf-lsr-algorithm-related-adjacency-sid"/>.</li>
        <li>Refer to the flags defined in the OSPFv2 LAN-Adj-SID with Algorithm Sub-TLV, as described in Section 4.2.2 of <xref target="I-D.ietf-lsr-algorithm-related-adjacency-sid"/>.</li>
		<li>Refer to the flags defined in the OSPFv3 LAN-Adj-SID with Algorithm Sub-TLV, as described 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 4 of <xref target="I-D.ietf-lsr-algorithm-related-adjacency-sid"/>.</t>
 <t>Algorithm: 1-octet value identifies the algorithm. The semantics of the algorithm are described in ISIS/OSPFv2/OSPFv3 LAN-Adj-SID with 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: 6 octets for IS-IS for the System ID, and 4 octets for OSPF for the OSPF Router-ID of the neighbor. </t>
 <t>SID/Label/Index: Label or index value as defined in ISIS/OSPFv2/OSPFv3 LAN-Adj-SID with Algorithm(<xref target="I-D.ietf-lsr-algorithm-related-adjacency-sid"/>).</t>
 </section>
  </section>
  
 <section numbered="true" toc="default">
   <name>BGP-LS Extensions for new Segment Descriptors</name>
   <t><xref target="I-D.ietf-idr-sr-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="RFC9857"/>.</t>
    <t>The following Segment Descriptors are defined and their mapping to the respective segment types defined in <xref target="I-D.ietf-idr-sr-te-policy-attr"/>:</t>
         <artwork><![CDATA[		
   +======+============================================================+
   | Type |                    Segment Description                     |
   +======+============================================================+
   | TBD3 |        (Type L)IPv4 Address and Local Interface ID         |
   |      |                  with optional Algorithm                   |
   +------+------------------------------------------------------------+
   | TBD4 |        (Type M)IPv4 Addresses for link endpoints as        |
   |      |         Local, Remote pair with optional Algorithm         |
   +------+------------------------------------------------------------+
   | TBD5 |          (Type N)IPv6 Prefix and Interface ID for          |
   |      |         link endpoints as Local, Remote pair, with         |
   |      |               optional Algorithm for SR-MPLS               |
   +------+------------------------------------------------------------+
   | TBD6 |        (Type O)IPv6 Addresses for link endpoints as        |
   |      |        Local, Remote pair, with optional Algorithm         |
   |      |                        for SR-MPLS                         |
   +------+------------------------------------------------------------+
 ]]></artwork>
	<section numbered="true" toc="default">
    <name>Type TBD3: IPv4 Node Address and Local Interface ID with optional SR Algorithm for SR-MPLS</name>
	<t> The Segment is SR-MPLS Adjacency SID with optional Algorithm 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><![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. The algorithm values are from IGP Algorithm Types registry under the IANA Interior Gateway Protocol (IGP) Parameters.</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 SR Algorithm for SR-MPLS</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><![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="RFC9857"/>.  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 6 Segment Descriptor in Section 5.7.1.1.6 of <xref target="RFC9857"/>, 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 Node Addresses and Interface ID for link endpoints as Local, Remote pair, with optional SR 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><![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="RFC9857"/>.  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 7 Segment Descriptor in Section 5.7.1.1.7 of <xref target="RFC9857"/>, 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 SR 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><![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="RFC9857"/>.  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 8 Segment Descriptor in Section 5.7.1.1.8 of <xref target="RFC9857"/>, 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 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><![CDATA[		
Value  Description                          Reference
--------------------------------------------------------------
TBD1  Adjacency SID with Algorithm           This document
TBD2  LAN Adjacency SID with 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><![CDATA[		
Value   Segment Description                                         Reference
---------------------------------------------------------------------------------
TBD3   IPv4 Node Address and Local Interface ID with optional       This document
       SR Algorithm for SR-MPLS       
TBD4   IPv4 Addresses for link endpoints as Local, Remote           This document
       pair with SR optional Algorithm for SR-MPLS                              
TBD5   IPv6 Node Addresses and Interface ID for link endpoints as   This document
       Local, Remote pair, with optional SR Algorithm for SR-MPLS                               
TBD6   IPv6 Addresses for link endpoints as Local, Remote pair,     This document
       with optional SR Algorithm for SR-MPLS                                 
           ]]></artwork>
		</section>  
		</section>  
    <section anchor="Security" numbered="true" toc="default">
      <name>Security Considerations</name>
     <t> Procedures and protocol extensions defined in this document do not affect the BGP security model. See the "Security Considerations"section of <xref target="RFC4271" format="default"></xref> for a discussion of BGP security. Security considerations for acquiring and distributing BGP-LS SR information are discussed in <xref target="RFC9085" format="default"></xref>.  Security considerations for acquiring and distributing BGP-LS SR Policy information are discussed in <xref target="RFC9857" format="default"></xref>.
</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 title="Normative References">
        <!--?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml"?-->
      <?rfc include='reference.RFC.2119'?>
	  <?rfc include='reference.RFC.4271'?>
	  <?rfc include='reference.RFC.8174'?>
	  <?rfc include='reference.RFC.9085'?>
	  <?rfc include='reference.RFC.9857'?>
	  <?rfc include='reference.I-D.ietf-idr-sr-te-policy-attr'?>
	 <?rfc include='reference.I-D.ietf-lsr-algorithm-related-adjacency-sid'?>
      </references>
 </back>
</rfc>
