Hi SPRING,

Just to let you know this is happening.

IMHO, this does not make any change to the SR architecture or technical 
bits-and-bobs. It does not change the SRH encoding.

What it does do is enshrine a small clarification that makes RFC 8754 clearer. 
Had this existed, RFC 9800 would have had a smoother passage. Future work, such 
as draft-du-spring-srv6-function-encryption, might also become clearer.

Comments (of course) to the 6man list.

Cheers,
Adrian 

-----Original Message-----
From: Bob Hinden via Datatracker <[email protected]> 
Sent: 07 September 2025 21:32
To: [email protected]; [email protected]; 
[email protected]
Subject: [IPv6]Call for adoption: draft-farrel-6man-sidlist-clarification-03 
(Ends 2025-09-21)


Subject: Call for adoption: draft-farrel-6man-sidlist-clarification-03  (Ends
2025-09-21)

This message starts a 2-week Call for Adoption for this document.

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.

File can be retrieved from:
https://datatracker.ietf.org/doc/draft-farrel-6man-sidlist-clarification/

Please reply to this message keeping [email protected] in copy by indicating
whether you support or not the adoption of this draft as a WG document.
Comments to motivate your preference are highly appreciated.

Authors, and WG participants in general, are reminded of the Intellectual
Property Rights (IPR) disclosure obligations described in BCP 79 [2].
Appropriate IPR disclosures required for full conformance with the provisions
of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any.
Sanctions available for application to violators of IETF IPR Policy can be
found at [3].

Thank you.
[1] https://datatracker.ietf.org/doc/bcp78/
[2] https://datatracker.ietf.org/doc/bcp79/
[3] https://datatracker.ietf.org/doc/rfc6701/



--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
List Info: https://mailman3.ietf.org/mailman3/lists/[email protected]/
--------------------------------------------------------------------

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

Reply via email to