SPRING WG was already copied by 6MAN chairs for the Working Group Last Call of 
this 6MAN draft, but as this IETF draft is related to SPRING work, I am also 
forwarding the IETF Last Call to SPRING.

Your reviews will be welcome.

Regards,

-éric     

From: The IESG <[email protected]>
Date: Friday, 10 April 2026 at 18:22
To: IETF-Announce <[email protected]>
Cc: [email protected] <[email protected]>, 
[email protected] 
<[email protected]>, [email protected] 
<[email protected]>, Eric Vyncke (evyncke) <[email protected]>, [email protected] 
<[email protected]>
Subject: Last Call: <draft-ietf-6man-sidlist-clarification-01.txt> (Clarifying 
SRv6 SID List Processing) to Proposed Standard


The IESG has received a request from the IPv6 Maintenance WG (6man) to
consider the following document: - 'Clarifying SRv6 SID List Processing'
  <draft-ietf-6man-sidlist-clarification-01.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
[email protected] mailing lists by 2026-04-24. Exceptionally, comments may
be sent to [email protected] instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   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.

   This document updates RFC 8754 by clarifying the processing of SID
   list entries.  It does not change any elements of the SRv6
   architecture.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-6man-sidlist-clarification/



No IPR declarations have been submitted directly on this I-D.





_______________________________________________
spring mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to