<?xml version='1.0' encoding='utf-8'?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" ipr="trust200902" docName="draft-ietf-6man-sidlist-clarification-03" number="10094" category="std" consensus="true" obsoletes="" updates="8754" submissionType="IETF" xml:lang="en" tocInclude="true" tocDepth="3" symRefs="true" sortRefs="true" prepTime="2026-11-18T02:17:05" indexInclude="true" scripts="Common,Latin">
  <link href="https://datatracker.ietf.org/doc/draft-ietf-6man-sidlist-clarification-03" rel="prev"/>
  <link href="https://dx.doi.org/10.17487/rfc10094" rel="alternate"/>
  <link href="urn:issn:2070-1721" rel="alternate"/>
  <front>
    <title abbrev="SID List Clarification">Clarifying Segment Routing over IPv6 (SRv6) Segment Identifier (SID) List Processing</title>
    <seriesInfo name="RFC" value="10094" stream="IETF"/>
    <author initials="A." surname="Farrel" fullname="Adrian Farrel">
      <organization showOnFrontPage="true">Old Dog Consulting</organization>
      <address>
        <postal>
          <country>United Kingdom</country>
        </postal>
        <email>adrian@olddog.co.uk</email>
      </address>
    </author>
    <author fullname="Suresh Krishnan" initials="S." surname="Krishnan">
      <organization showOnFrontPage="true">Cisco Systems, Inc.</organization>
      <address>
        <postal>
          <country>United States of America</country>
        </postal>
        <email>suresh.krishnan@gmail.com</email>
      </address>
    </author>
    <date month="11" year="2026"/>
    <area>INT</area>
    <workgroup>6man</workgroup>
    <keyword>Segment Routing</keyword>
    <keyword>SR</keyword>
    <keyword>Segment Identifier</keyword>
    <keyword>SID</keyword>
    <keyword>IPv6</keyword>
    <keyword>Segment Routing Header</keyword>
    <keyword>SRH</keyword>
    <abstract pn="section-abstract">
      <t indent="0" pn="section-abstract-1">Segment Routing over IPv6 (SRv6) is the instantiation of Segment Routing (SR) on the IPv6 data
         plane. Segments are indicated by Segment Identifiers (SIDs). SRv6 utilizes the Segment Routing
         Header (SRH), an IPv6 extension header that includes a SID list indicating the sequence of
         segments and any additional processing to be performed.</t>
      <t indent="0" pn="section-abstract-2">This document updates RFC 8754 by clarifying the processing of SID list entries. It does not change
         any elements of the SRv6 architecture.</t>
    </abstract>
    <boilerplate>
      <section anchor="status-of-memo" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.1">
        <name slugifiedName="name-status-of-this-memo">Status of This Memo</name>
        <t indent="0" pn="section-boilerplate.1-1">
            This is an Internet Standards Track document.
        </t>
        <t indent="0" pn="section-boilerplate.1-2">
            This document is a product of the Internet Engineering Task Force
            (IETF).  It represents the consensus of the IETF community.  It has
            received public review and has been approved for publication by
            the Internet Engineering Steering Group (IESG).  Further
            information on Internet Standards is available in Section 2 of 
            RFC 7841.
        </t>
        <t indent="0" pn="section-boilerplate.1-3">
            Information about the current status of this document, any
            errata, and how to provide feedback on it may be obtained at
            <eref target="https://www.rfc-editor.org/info/rfc10094" brackets="none"/>.
        </t>
      </section>
      <section anchor="copyright" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.2">
        <name slugifiedName="name-copyright-notice">Copyright Notice</name>
        <t indent="0" pn="section-boilerplate.2-1">
            Copyright (c) 2026 IETF Trust and the persons identified as the
            document authors. All rights reserved.
        </t>
        <t indent="0" pn="section-boilerplate.2-2">
            This document is subject to BCP 78 and the IETF Trust's Legal
            Provisions Relating to IETF Documents
            (<eref target="https://trustee.ietf.org/license-info" brackets="none"/>) in effect on the date of
            publication of this document. Please review these documents
            carefully, as they describe your rights and restrictions with
            respect to this document. Code Components extracted from this
            document must include Revised BSD License text as described in
            Section 4.e of the Trust Legal Provisions and are provided without
            warranty as described in the Revised BSD License.
        </t>
      </section>
    </boilerplate>
    <toc>
      <section anchor="toc" numbered="false" removeInRFC="false" toc="exclude" pn="section-toc.1">
        <name slugifiedName="name-table-of-contents">Table of Contents</name>
        <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1">
          <li pn="section-toc.1-1.1">
            <t indent="0" keepWithNext="true" pn="section-toc.1-1.1.1"><xref derivedContent="1" format="counter" sectionFormat="of" target="section-1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-introduction">Introduction</xref></t>
          </li>
          <li pn="section-toc.1-1.2">
            <t indent="0" keepWithNext="true" pn="section-toc.1-1.2.1"><xref derivedContent="2" format="counter" sectionFormat="of" target="section-2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-clarification">Clarification</xref></t>
          </li>
          <li pn="section-toc.1-1.3">
            <t indent="0" pn="section-toc.1-1.3.1"><xref derivedContent="3" format="counter" sectionFormat="of" target="section-3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-updates-to-rfc-8754">Updates to RFC 8754</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.3.2">
              <li pn="section-toc.1-1.3.2.1">
                <t indent="0" keepWithNext="true" pn="section-toc.1-1.3.2.1.1"><xref derivedContent="3.1" format="counter" sectionFormat="of" target="section-3.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-segments-left-in-section-2-">Segments Left in Section 2 of RFC 8754</xref></t>
              </li>
              <li pn="section-toc.1-1.3.2.2">
                <t indent="0" pn="section-toc.1-1.3.2.2.1"><xref derivedContent="3.2" format="counter" sectionFormat="of" target="section-3.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-segment-list-in-section-2-o">Segment List in Section 2 of RFC 8754</xref></t>
              </li>
              <li pn="section-toc.1-1.3.2.3">
                <t indent="0" pn="section-toc.1-1.3.2.3.1"><xref derivedContent="3.3" format="counter" sectionFormat="of" target="section-3.3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-hmac-processing-in-section-">HMAC Processing in Section 2.1.2.1 of RFC 8754</xref></t>
              </li>
              <li pn="section-toc.1-1.3.2.4">
                <t indent="0" pn="section-toc.1-1.3.2.4.1"><xref derivedContent="3.4" format="counter" sectionFormat="of" target="section-3.4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-icmp-processing-in-section-">ICMP Processing in Section 5.4 of RFC 8754</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.4">
            <t indent="0" pn="section-toc.1-1.4.1"><xref derivedContent="4" format="counter" sectionFormat="of" target="section-4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-operational-considerations">Operational Considerations</xref></t>
          </li>
          <li pn="section-toc.1-1.5">
            <t indent="0" pn="section-toc.1-1.5.1"><xref derivedContent="5" format="counter" sectionFormat="of" target="section-5"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-security-considerations">Security Considerations</xref></t>
          </li>
          <li pn="section-toc.1-1.6">
            <t indent="0" pn="section-toc.1-1.6.1"><xref derivedContent="6" format="counter" sectionFormat="of" target="section-6"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-iana-considerations">IANA Considerations</xref></t>
          </li>
          <li pn="section-toc.1-1.7">
            <t indent="0" pn="section-toc.1-1.7.1"><xref derivedContent="7" format="counter" sectionFormat="of" target="section-7"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-references">References</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.7.2">
              <li pn="section-toc.1-1.7.2.1">
                <t indent="0" pn="section-toc.1-1.7.2.1.1"><xref derivedContent="7.1" format="counter" sectionFormat="of" target="section-7.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-normative-references">Normative References</xref></t>
              </li>
              <li pn="section-toc.1-1.7.2.2">
                <t indent="0" pn="section-toc.1-1.7.2.2.1"><xref derivedContent="7.2" format="counter" sectionFormat="of" target="section-7.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-informative-references">Informative References</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.8">
            <t indent="0" pn="section-toc.1-1.8.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.a"/><xref derivedContent="" format="title" sectionFormat="of" target="name-acknowledgments">Acknowledgments</xref></t>
          </li>
          <li pn="section-toc.1-1.9">
            <t indent="0" pn="section-toc.1-1.9.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.b"/><xref derivedContent="" format="title" sectionFormat="of" target="name-authors-addresses">Authors' Addresses</xref></t>
          </li>
        </ul>
      </section>
    </toc>
  </front>
  <middle>
    <section anchor="introduction" numbered="true" toc="include" removeInRFC="false" pn="section-1">
      <name slugifiedName="name-introduction">Introduction</name>
      <t indent="0" pn="section-1-1">The Segment Routing (SR) architecture is specified in <xref target="RFC8402" format="default" sectionFormat="of" derivedContent="RFC8402"/>.
         SR forwards packets along a series of segments, and it may perform additional
         segment-specific processing on packets. Segments are indicated by Segment Identifiers
         (SIDs).</t>
      <t indent="0" pn="section-1-2">The mechanisms to achieve Segment Routing over IPv6 (SRv6) include the use of the
         Segment Routing Header (SRH) <xref target="RFC8754" format="default" sectionFormat="of" derivedContent="RFC8754"/>, an IPv6 extension header that
         includes a SID list indicating the sequence of segments and any additional processing
         to be performed.</t>
      <t indent="0" pn="section-1-3">This document updates <xref target="RFC8754" format="default" sectionFormat="of" derivedContent="RFC8754"/> by clarifying the processing of SID list
         entries. It does not change any elements of the SRv6 architecture.</t>
    </section>
    <section anchor="details" numbered="true" toc="include" removeInRFC="false" pn="section-2">
      <name slugifiedName="name-clarification">Clarification</name>
      <t indent="0" pn="section-2-1">The SRH is processed per <xref target="RFC8754" section="4" sectionFormat="of" format="default" derivedLink="https://rfc-editor.org/rfc/rfc8754#section-4" derivedContent="RFC8754"/>. One objective of that processing is to determine the
         value to place in the Destination Address field of the IPv6 packet. To this end, the
         next entry in the SID list in the SRH is processed and mapped to the value to place
         in the Destination Address field.</t>
      <t indent="0" pn="section-2-2">The value placed in the 128-bit Destination Address field of an IPv6 packet header needs to be a routable
         IPv6 address since that is required for forwarding the packet.</t>
      <t indent="0" pn="section-2-3">Note that entries in the SID list do not need to be fully formed IPv6 addresses that
         are copied directly to the Destination Address field of the IPv6 packet. The mapping
         from SID list entry to the destination address could be a direct copy (the SID list contains a list of IPv6
         addresses) or could involve a more complex function.</t>
      <t indent="0" pn="section-2-4">An example of such a function is shown in <xref target="RFC9800" format="default" sectionFormat="of" derivedContent="RFC9800"/>, where a REPLACE-CSID
         compressed SID is expanded to be placed in the Destination Address field. Note that
         <xref target="RFC9800" format="default" sectionFormat="of" derivedContent="RFC9800"/> formally updates <xref target="RFC8754" format="default" sectionFormat="of" derivedContent="RFC8754"/> to allow
         this mapping function -- such an update would not have been needed if this document had
         already existed.</t>
    </section>
    <section anchor="updates" numbered="true" toc="include" removeInRFC="false" pn="section-3">
      <name slugifiedName="name-updates-to-rfc-8754">Updates to RFC 8754</name>
      <section anchor="segLeft" numbered="true" toc="include" removeInRFC="false" pn="section-3.1">
        <name slugifiedName="name-segments-left-in-section-2-">Segments Left in Section 2 of RFC 8754</name>
        <t indent="0" pn="section-3.1-1">The definition of the Segments Left field of the SRH is presented as:</t>
        <blockquote pn="section-3.1-2">
          <dl spacing="normal" newline="false" indent="3" pn="section-3.1-2.1">
            <dt pn="section-3.1-2.1.1">Segments Left:</dt>
            <dd pn="section-3.1-2.1.2">Defined in <xref target="RFC8200" sectionFormat="comma" section="4.4" format="default" derivedLink="https://rfc-editor.org/rfc/rfc8200#section-4.4" derivedContent="RFC8200"/>.</dd>
          </dl>
        </blockquote>
        <t indent="0" pn="section-3.1-3">This is clarified by Erratum ID 7102 <xref target="Err7102" format="default" sectionFormat="of" derivedContent="Err7102"/>.
           This clarification is included in this update for completeness. The new text reads:</t>
        <blockquote pn="section-3.1-4">
          <dl spacing="normal" newline="false" indent="3" pn="section-3.1-4.1">
            <dt pn="section-3.1-4.1.1">Segments Left:</dt>
            <dd pn="section-3.1-4.1.2">Defined in <xref target="RFC8200" sectionFormat="comma" section="4.4" format="default" derivedLink="https://rfc-editor.org/rfc/rfc8200#section-4.4" derivedContent="RFC8200"/>.
                Specifically, for the SRH, the number of unprocessed 128-bit entries in the Segment List.</dd>
          </dl>
        </blockquote>
      </section>
      <section anchor="segList" numbered="true" toc="include" removeInRFC="false" pn="section-3.2">
        <name slugifiedName="name-segment-list-in-section-2-o">Segment List in Section 2 of RFC 8754</name>
        <t indent="0" pn="section-3.2-1">The figure in <xref target="RFC8754" section="2" sectionFormat="of" format="default" derivedLink="https://rfc-editor.org/rfc/rfc8754#section-2" derivedContent="RFC8754"/> reads:</t>
        <blockquote pn="section-3.2-2">
          <artwork align="left" pn="section-3.2-2.1">
 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Next Header   |  Hdr Ext Len  | Routing Type  | Segments Left |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|  Last Entry   |     Flags     |              Tag              |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                                                               |
|            Segment List[0] (128-bit IPv6 address)             |
|                                                               |
|                                                               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                                                               |
|                                                               |
                              ...
|                                                               |
|                                                               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                                                               |
|            Segment List[n] (128-bit IPv6 address)             |
|                                                               |
|                                                               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
//                                                             //
//         Optional Type Length Value objects (variable)       //
//                                                             //
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</artwork>
        </blockquote>
        <t indent="0" pn="section-3.2-3">This is updated as follows to clarify that the entries in the Segment List are
           128-bit entries, but not necessarily IPv6 addresses.</t>
        <blockquote pn="section-3.2-4">
          <artwork align="left" pn="section-3.2-4.1">
 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Next Header   |  Hdr Ext Len  | Routing Type  | Segments Left |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|  Last Entry   |     Flags     |              Tag              |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                                                               |
|   Segment List[0] (128-bit entry mapped to IPv6 addresses)    |
|                                                               |
|                                                               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                                                               |
|                                                               |
                              ...
|                                                               |
|                                                               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                                                               |
|   Segment List[n] (128-bit entry mapped to IPv6 addresses)    |
|                                                               |
|                                                               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
//                                                             //
//         Optional Type Length Value objects (variable)       //
//                                                             //
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</artwork>
        </blockquote>
        <t indent="0" pn="section-3.2-5">The text in <xref target="RFC8754" format="default" sectionFormat="of" derivedContent="RFC8754"/> reads:</t>
        <blockquote pn="section-3.2-6">
          <dl spacing="normal" newline="false" indent="3" pn="section-3.2-6.1">
            <dt pn="section-3.2-6.1.1">Segment List[0..n]:</dt>
            <dd pn="section-3.2-6.1.2">128-bit IPv6 addresses representing the nth
                segment in the Segment List.  The Segment List is encoded starting
                from the last segment of the SR Policy.  That is, the first
                element of the Segment List (Segment List[0]) contains the last
                segment of the SR Policy, the second element contains the
                penultimate segment of the SR Policy, and so on.</dd>
          </dl>
        </blockquote>
        <t indent="0" pn="section-3.2-7">This is updated as follows to clarify that the entries in the Segment List are
           128-bit entries, but not necessarily IPv6 addresses.</t>
        <blockquote pn="section-3.2-8">
          <dl spacing="normal" newline="false" indent="3" pn="section-3.2-8.1">
            <dt pn="section-3.2-8.1.1">Segment List[0..n]:</dt>
            <dd pn="section-3.2-8.1.2">128-bit entries representing the nth
                segment in the Segment List.  The Segment List is encoded starting
                from the last segment of the SR Policy.  That is, the first
                element of the Segment List (Segment List[0]) contains the last
                segment of the SR Policy, the second element contains the
                penultimate segment of the SR Policy, and so on.</dd>
          </dl>
        </blockquote>
      </section>
      <section anchor="hmac" numbered="true" toc="include" removeInRFC="false" pn="section-3.3">
        <name slugifiedName="name-hmac-processing-in-section-">HMAC Processing in Section 2.1.2.1 of RFC 8754</name>
        <t indent="0" pn="section-3.3-1">In describing the Hashed Message Authentication Code (HMAC) processing, the text in <xref target="RFC8754" format="default" sectionFormat="of" derivedContent="RFC8754"/> says that
           HMAC verification checks that the destination address of the packet
           matches that indicated by the next entry in the Segment List.</t>
        <blockquote pn="section-3.3-2">
          <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-3.3-2.1">
            <li pn="section-3.3-2.1.1">HMAC Segments Left is less than or equal to Last Entry, and the
               destination address is equal to Segment List[Segments Left].</li>
          </ul>
        </blockquote>
        <t indent="0" pn="section-3.3-3">This is updated to allow a nondirect mapping from the Segment List entry to
           the destination address as follows:</t>
        <blockquote pn="section-3.3-4">
          <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-3.3-4.1">
            <li pn="section-3.3-4.1.1">HMAC Segments Left is less than or equal to the Last Entry, and the
               destination address is equal to the address created by mapping from Segment
               List[Segments Left].</li>
          </ul>
        </blockquote>
        <t indent="0" pn="section-3.3-5">Further, in describing the concatenation of information to generate the
           text field input to the HMAC computation, <xref target="RFC8754" section="2.1.2.1" sectionFormat="of" format="default" derivedLink="https://rfc-editor.org/rfc/rfc8754#section-2.1.2.1" derivedContent="RFC8754"/> says:</t>
        <blockquote pn="section-3.3-6">
          <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-3.3-6.1">
            <li pn="section-3.3-6.1.1">SRH: All addresses in the Segment List (variable octets)</li>
          </ul>
        </blockquote>
        <t indent="0" pn="section-3.3-7">This is updated as follows to indicate that Segment List entries are
           not necessarily IPv6 addresses.</t>
        <blockquote pn="section-3.3-8">
          <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-3.3-8.1">
            <li pn="section-3.3-8.1.1">SRH: All entries in the Segment List (variable octets)</li>
          </ul>
        </blockquote>
      </section>
      <section anchor="icmpProcess" numbered="true" toc="include" removeInRFC="false" pn="section-3.4">
        <name slugifiedName="name-icmp-processing-in-section-">ICMP Processing in Section 5.4 of RFC 8754</name>
        <t indent="0" pn="section-3.4-1">The method for deriving the destination address of the invoking packet in <xref target="RFC8754" format="default" sectionFormat="of" derivedContent="RFC8754"/> reads as:</t>
        <blockquote pn="section-3.4-2">
          <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-3.4-2.1">
            <li pn="section-3.4-2.1.1">The SID at Segment List[0] may be used as the
              destination address of the invoking packet.</li>
          </ul>
        </blockquote>
        <t indent="0" pn="section-3.4-3">To allow for the zeroth entry in the Segment List to be mapped rather than copied to a destination address, this
           is updated to:</t>
        <blockquote pn="section-3.4-4">
          <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-3.4-4.1">
            <li pn="section-3.4-4.1.1">The SID at Segment List[0] may be mapped to derive the
              destination address of the invoking packet.</li>
          </ul>
        </blockquote>
      </section>
    </section>
    <section anchor="operational-considerations" numbered="true" toc="include" removeInRFC="false" pn="section-4">
      <name slugifiedName="name-operational-considerations">Operational Considerations</name>
      <t indent="0" pn="section-4-1">This document does not change any elements of the SRv6 architecture and, as such,
         it makes no change to the operational procedures or management tools of SR.</t>
      <t indent="0" pn="section-4-2">In clarifying the nature of SID list processing, this document also clarifies the
         nature of SID list entries. Operational and management tools that examine the SID
         list in a packet need to be aware of the nature of those entries in order to
         offer maximal clarity to the users of those tools.</t>
    </section>
    <section anchor="security-considerations" numbered="true" toc="include" removeInRFC="false" pn="section-5">
      <name slugifiedName="name-security-considerations">Security Considerations</name>
      <t indent="0" pn="section-5-1">This document makes no changes to the security properties of SRv6. See <xref target="I-D.ietf-spring-srv6-security" format="default" sectionFormat="of" derivedContent="SRv6-SECURITY"/>,
         <xref target="RFC8402" format="default" sectionFormat="of" derivedContent="RFC8402"/>, and <xref target="RFC8754" format="default" sectionFormat="of" derivedContent="RFC8754"/> for more discussion of SRv6 security.</t>
      <t indent="0" pn="section-5-2">Note that describing the SID list entries as being mapped to the destination address of a packet enables potential
         additional security mechanisms, such as encrypting the SID list.</t>
    </section>
    <section anchor="iana-considerations" numbered="true" toc="include" removeInRFC="false" pn="section-6">
      <name slugifiedName="name-iana-considerations">IANA Considerations</name>
      <t indent="0" pn="section-6-1">This document has no IANA actions.</t>
    </section>
  </middle>
  <back>
    <displayreference target="I-D.ietf-spring-srv6-security" to="SRv6-SECURITY"/>
    <references pn="section-7">
      <name slugifiedName="name-references">References</name>
      <references pn="section-7.1">
        <name slugifiedName="name-normative-references">Normative References</name>
        <reference anchor="RFC8200" target="https://www.rfc-editor.org/info/rfc8200" quoteTitle="true" derivedAnchor="RFC8200">
          <front>
            <title>Internet Protocol, Version 6 (IPv6) Specification</title>
            <author fullname="S. Deering" initials="S." surname="Deering"/>
            <author fullname="R. Hinden" initials="R." surname="Hinden"/>
            <date month="July" year="2017"/>
            <abstract>
              <t indent="0">This document specifies version 6 of the Internet Protocol (IPv6). It obsoletes RFC 2460.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="86"/>
          <seriesInfo name="RFC" value="8200"/>
          <seriesInfo name="DOI" value="10.17487/RFC8200"/>
        </reference>
        <reference anchor="RFC8402" target="https://www.rfc-editor.org/info/rfc8402" quoteTitle="true" derivedAnchor="RFC8402">
          <front>
            <title>Segment Routing Architecture</title>
            <author fullname="C. Filsfils" initials="C." role="editor" surname="Filsfils"/>
            <author fullname="S. Previdi" initials="S." role="editor" surname="Previdi"/>
            <author fullname="L. Ginsberg" initials="L." surname="Ginsberg"/>
            <author fullname="B. Decraene" initials="B." surname="Decraene"/>
            <author fullname="S. Litkowski" initials="S." surname="Litkowski"/>
            <author fullname="R. Shakir" initials="R." surname="Shakir"/>
            <date month="July" year="2018"/>
            <abstract>
              <t indent="0">Segment Routing (SR) leverages the source routing paradigm. A node steers a packet through an ordered list of instructions, called "segments". A segment can represent any instruction, topological or service based. A segment can have a semantic local to an SR node or global within an SR domain. SR provides a mechanism that allows a flow to be restricted to a specific topological path, while maintaining per-flow state only at the ingress node(s) to the SR domain.</t>
              <t indent="0">SR can be directly applied to the MPLS architecture with no change to the forwarding plane. A segment is encoded as an MPLS label. An ordered list of segments is encoded as a stack of labels. The segment to process is on the top of the stack. Upon completion of a segment, the related label is popped from the stack.</t>
              <t indent="0">SR can be applied to the IPv6 architecture, with a new type of routing header. A segment is encoded as an IPv6 address. An ordered list of segments is encoded as an ordered list of IPv6 addresses in the routing header. The active segment is indicated by the Destination Address (DA) of the packet. The next active segment is indicated by a pointer in the new routing header.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8402"/>
          <seriesInfo name="DOI" value="10.17487/RFC8402"/>
        </reference>
        <reference anchor="RFC8754" target="https://www.rfc-editor.org/info/rfc8754" quoteTitle="true" derivedAnchor="RFC8754">
          <front>
            <title>IPv6 Segment Routing Header (SRH)</title>
            <author fullname="C. Filsfils" initials="C." role="editor" surname="Filsfils"/>
            <author fullname="D. Dukes" initials="D." role="editor" surname="Dukes"/>
            <author fullname="S. Previdi" initials="S." surname="Previdi"/>
            <author fullname="J. Leddy" initials="J." surname="Leddy"/>
            <author fullname="S. Matsushima" initials="S." surname="Matsushima"/>
            <author fullname="D. Voyer" initials="D." surname="Voyer"/>
            <date month="March" year="2020"/>
            <abstract>
              <t indent="0">Segment Routing can be applied to the IPv6 data plane using a new type of Routing Extension Header called the Segment Routing Header (SRH). This document describes the SRH and how it is used by nodes that are Segment Routing (SR) capable.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8754"/>
          <seriesInfo name="DOI" value="10.17487/RFC8754"/>
        </reference>
      </references>
      <references pn="section-7.2">
        <name slugifiedName="name-informative-references">Informative References</name>
        <reference anchor="Err7102" quoteTitle="false" target="https://www.rfc-editor.org/errata/eid7102" derivedAnchor="Err7102">
          <front>
            <title>Erratum ID 7102</title>
            <author>
              <organization showOnFrontPage="true">RFC Errata</organization>
            </author>
          </front>
          <refcontent>RFC 8754</refcontent>
        </reference>
        <reference anchor="RFC9800" target="https://www.rfc-editor.org/info/rfc9800" quoteTitle="true" derivedAnchor="RFC9800">
          <front>
            <title>Compressed SRv6 Segment List Encoding</title>
            <author fullname="W. Cheng" initials="W." role="editor" surname="Cheng"/>
            <author fullname="C. Filsfils" initials="C." surname="Filsfils"/>
            <author fullname="Z. Li" initials="Z." surname="Li"/>
            <author fullname="B. Decraene" initials="B." surname="Decraene"/>
            <author fullname="F. Clad" initials="F." role="editor" surname="Clad"/>
            <date month="June" year="2025"/>
            <abstract>
              <t indent="0">Segment Routing over IPv6 (SRv6) is the instantiation of Segment Routing (SR) on the IPv6 data plane. This document specifies new flavors for the SRv6 endpoint behaviors defined in RFC 8986, which enable the compression of an SRv6 segment list. Such compression significantly reduces the size of the SRv6 encapsulation needed to steer packets over long segment lists.</t>
              <t indent="0">This document updates RFC 8754 by allowing a Segment List entry in the Segment Routing Header (SRH) to be either an IPv6 address, as specified in RFC 8754, or a REPLACE-CSID container in packed format, as specified in this document.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9800"/>
          <seriesInfo name="DOI" value="10.17487/RFC9800"/>
        </reference>
        <reference anchor="I-D.ietf-spring-srv6-security" target="https://datatracker.ietf.org/doc/html/draft-ietf-spring-srv6-security-20" quoteTitle="true" derivedAnchor="SRv6-SECURITY">
          <front>
            <title>Segment Routing over IPv6 (SRv6) Security Considerations</title>
            <author fullname="Nick Buraglio" initials="N." surname="Buraglio"/>
            <author fullname="Tal Mizrahi" initials="T." surname="Mizrahi"/>
            <author fullname="Tian Tong" initials="T." surname="Tong"/>
            <author fullname="Luis M. Contreras" initials="L. M." surname="Contreras"/>
            <author fullname="Fernando Gont" initials="F." surname="Gont"/>
            <date month="November" day="17" year="2026"/>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-spring-srv6-security-20"/>
          <refcontent>Work in Progress</refcontent>
        </reference>
      </references>
    </references>
    <section anchor="acknowledgments" numbered="false" toc="include" removeInRFC="false" pn="section-appendix.a">
      <name slugifiedName="name-acknowledgments">Acknowledgments</name>
      <t indent="0" pn="section-appendix.a-1">Thanks to <contact fullname="Éric Vyncke"/> and <contact fullname="Erik Kline"/> for
         inspiring the authors to write this document. Thanks to <contact fullname="Bob Hinden"/>,
         <contact fullname="Mohamed Boucadair"/>, <contact fullname="Joel Halpern"/>,
         <contact fullname="Yao Liu"/>, <contact fullname="Bruno Decraene"/>,
         <contact fullname="Brian Carpenter"/>, <contact fullname="Russ Housley"/>,
         <contact fullname="Peter Yee"/>, <contact fullname="Yingzhen Qu"/>,
         <contact fullname="Deb Cooley"/>, and <contact fullname="Mike Bishop"/> for their
         reviews and comments that improved this document.</t>
    </section>
    <section anchor="authors-addresses" numbered="false" removeInRFC="false" toc="include" pn="section-appendix.b">
      <name slugifiedName="name-authors-addresses">Authors' Addresses</name>
      <author initials="A." surname="Farrel" fullname="Adrian Farrel">
        <organization showOnFrontPage="true">Old Dog Consulting</organization>
        <address>
          <postal>
            <country>United Kingdom</country>
          </postal>
          <email>adrian@olddog.co.uk</email>
        </address>
      </author>
      <author fullname="Suresh Krishnan" initials="S." surname="Krishnan">
        <organization showOnFrontPage="true">Cisco Systems, Inc.</organization>
        <address>
          <postal>
            <country>United States of America</country>
          </postal>
          <email>suresh.krishnan@gmail.com</email>
        </address>
      </author>
    </section>
  </back>
</rfc>
