[IPv6]Re: Call for adoption: draft-farrel-6man-sidlist-clarification-03 (Ends 2025-09-21)

[Brian E Carpenter <[e-mail]>]

I support adoption.

Should [I-D.ietf-spring-srv6-security] be a normative reference?

Regards/Ngā mihi
    Brian Carpenter

On 09-Sep-25 00:42, [e-mail] wrote:
> Hi all,
> 
> As indicated in [1], I do think this is useful work. I support adoption.
> 
> Cheers,
> Med (as contributor)
> 
> [1] https://mailarchive.ietf.org/arch/msg/ipv6/afr_EDo5CWMXzeEidMRZH7j9AI4/
> 
>> -----Message d'origine-----
>> De : Bob Hinden via Datatracker <[e-mail]>
>> Envoyé : dimanche 7 septembre 2025 22:32
>> À : [e-mail]; draft-farrel-6man-sidlist-
>> [e-mail]; [e-mail]
>> Objet : [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://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F
>> datatracker.ietf.org%2Fdoc%2Fdraft-farrel-6man-sidlist-
>> clarification%2F&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C7
>> e75056019e842e81fe908ddee4dd570%7C90c7a20af34b40bfbc48b9253b6f5d20
>> %7C0%7C0%7C638928740238808846%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1h
>> cGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIl
>> dUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=oXH%2B9iwsrbOT8gjiorBwzLZ54LvM7f
>> GH6FOPOORUIVg%3D&reserved=0
>>
>> Please reply to this message keeping [e-mail] 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://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F
>> datatracker.ietf.org%2Fdoc%2Fbcp78%2F&data=05%7C02%7Cmohamed.bouca
>> dair%40orange.com%7C7e75056019e842e81fe908ddee4dd570%7C90c7a20af34
>> b40bfbc48b9253b6f5d20%7C0%7C0%7C638928740238838846%7CUnknown%7CTWF
>> pbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zM
>> iIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=T9Ls2hvua2y
>> wymM%2BJvYioHBxyBYNlqeDSx6JsFxWP%2FU%3D&reserved=0
>> [2]
>> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F
>> datatracker.ietf.org%2Fdoc%2Fbcp79%2F&data=05%7C02%7Cmohamed.bouca
>> dair%40orange.com%7C7e75056019e842e81fe908ddee4dd570%7C90c7a20af34
>> b40bfbc48b9253b6f5d20%7C0%7C0%7C638928740238854144%7CUnknown%7CTWF
>> pbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zM
>> iIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=caQqOzXWP13
>> Ba16kSE5AgpsIWbN72PVawriyRd%2F6Sos%3D&reserved=0
>> [3]
>> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F
>> datatracker.ietf.org%2Fdoc%2Frfc6701%2F&data=05%7C02%7Cmohamed.bou
>> cadair%40orange.com%7C7e75056019e842e81fe908ddee4dd570%7C90c7a20af
>> 34b40bfbc48b9253b6f5d20%7C0%7C0%7C638928740238868082%7CUnknown%7CT
>> WFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4
>> zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=oBfL7pWPU
>> Emj0tmaBloTP7lgeQJ0MKf15%2FAv0Vc2HRY%3D&reserved=0
>>
>>
>>
>> ------------------------------------------------------------------
>> --
>> IETF IPv6 working group mailing list
>> [e-mail]
>> List Info:
>> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F
>> mailman3.ietf.org%2Fmailman3%2Flists%2Fipv6%40ietf.org%2F&data=05%
>> 7C02%7Cmohamed.boucadair%40orange.com%7C7e75056019e842e81fe908ddee
>> 4dd570%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C63892874023888
>> 1526%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuM
>> DAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%
>> 7C&sdata=QWnGb7i%2F73%2FYG2zLY4zs2N0AzwATOvy8ji7J3zYurVg%3D&reserv
>> ed=0
>> ------------------------------------------------------------------
>> --
> ____________________________________________________________________________________________________________
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
> 
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> [e-mail]
> List Info: https://mailman3.ietf.org/mailman3/lists/[e-mail]/
> --------------------------------------------------------------------