MIME-Version: 1.0
References: 
 <176174515897.948978.14879689502344296495@dt-datatracker-6744d78b75-cgfz8>
In-Reply-To: 
 <176174515897.948978.14879689502344296495@dt-datatracker-6744d78b75-cgfz8>
From: allan michael <michaelallenietf@gmail.com>
Date: Wed, 29 Oct 2025 22:38:50 +0800
Message-ID: 
 <CAJsZG2SSA28CttXCPMNeqLh2TM5Qh-AzhX8YQfjycBHVxk=XaQ@mail.gmail.com>
To: Bruno Decraene <bruno.decraene@orange.com>
Content-Type: multipart/alternative; boundary="000000000000e698bc06424d1798"
Message-ID-Hash: MX47ASSRTQ3J4572T7VM4MRUJZWBUHEY
CC: draft-ali-spring-srv6-policy-sid-list-optimization@ietf.org,
 spring-chairs@ietf.org, spring@ietf.org
Precedence: list
Subject: =?utf-8?q?=5Bspring=5D_Re=3A_Call_for_adoption=3A_draft-ali-spring-srv6-poli?=
 =?utf-8?q?cy-sid-list-optimization-01_=28Ends_2025-11-19=29?=
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/spring/oQur1FaZc4xosqo2AmEnTrJQMhQ>

--000000000000e698bc06424d1798
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi WG,

I support this adoption.

The SID list can be optimized by excluding the endpoint Node SID when
installing the policy.
It can significantly improve the forwarding performance of the egress node.

Thanks,
Allan



On Wed, Oct 29, 2025 at 9:41=E2=80=AFPM Bruno Decraene via Datatracker <
noreply@ietf.org> wrote:

>
> Subject: Call for adoption:
> draft-ali-spring-srv6-policy-sid-list-optimization-01  (Ends 2025-11-19)
>
> This message starts a 3-week Call for Adoption for this document.
>
> Abstract:
>    Segment Routing (SR) allows a node to steer a packet flow along any
>    path.  SR Policy is an ordered list of segments (i.e., instructions)
>    that represent a source-routed policy.  The packets steered into an
>    SR Policy carry an ordered list of segments associated with that SR
>    Policy.  An SR Policy can be instantiated SR-MPLS and SRv6 data
>    planes.
>
>    In some use cases, an SRv6 Policy's SID list ends with the policy
>    endpoint's node SID, and the traffic steered (over policy) already
>    ensures that it is taken to the policy endpoint.  In such cases, the
>    SID list can be optimized by excluding the endpoint Node SID when
>    installing the policy.  This draft specifies procedures to indicate
>    whether the endpoint's node SID needs to be included or excluded when
>    installing the SRv6 Policy.
>
> File can be retrieved from:
>
> https://datatracker.ietf.org/doc/draft-ali-spring-srv6-policy-sid-list-op=
timization/
>
> Please reply to this message keeping spring@ietf.org in copy by indicatin=
g
> 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 b=
e
> 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/
>
>
>
> _______________________________________________
> spring mailing list -- spring@ietf.org
> To unsubscribe send an email to spring-leave@ietf.org
>

--000000000000e698bc06424d1798
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi WG,<br><br>I support this adoption. <br><br>The SID lis=
t can be optimized by excluding the endpoint Node SID when installing the p=
olicy.<br>It can significantly improve the forwarding performance of the eg=
ress node.<br><br>Thanks,<br>Allan<br></div><div dir=3D"ltr"><pre style=3D"=
white-space:pre-wrap;box-sizing:border-box;font-family:var(--bs-font-monosp=
ace);direction:ltr;unicode-bidi:bidi-override;margin-top:0px;margin-bottom:=
1rem;overflow:auto;word-break:normal;padding:0px;color:rgb(33,37,41)"><br><=
/pre></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_a=
ttr">On Wed, Oct 29, 2025 at 9:41=E2=80=AFPM Bruno Decraene via Datatracker=
 &lt;<a href=3D"mailto:noreply@ietf.org" target=3D"_blank">noreply@ietf.org=
</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:=
0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">=
<br>
Subject: Call for adoption:<br>
draft-ali-spring-srv6-policy-sid-list-optimization-01=C2=A0 (Ends 2025-11-1=
9)<br>
<br>
This message starts a 3-week Call for Adoption for this document.<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0Segment Routing (SR) allows a node to steer a packet flow alon=
g any<br>
=C2=A0 =C2=A0path.=C2=A0 SR Policy is an ordered list of segments (i.e., in=
structions)<br>
=C2=A0 =C2=A0that represent a source-routed policy.=C2=A0 The packets steer=
ed into an<br>
=C2=A0 =C2=A0SR Policy carry an ordered list of segments associated with th=
at SR<br>
=C2=A0 =C2=A0Policy.=C2=A0 An SR Policy can be instantiated SR-MPLS and SRv=
6 data<br>
=C2=A0 =C2=A0planes.<br>
<br>
=C2=A0 =C2=A0In some use cases, an SRv6 Policy&#39;s SID list ends with the=
 policy<br>
=C2=A0 =C2=A0endpoint&#39;s node SID, and the traffic steered (over policy)=
 already<br>
=C2=A0 =C2=A0ensures that it is taken to the policy endpoint.=C2=A0 In such=
 cases, the<br>
=C2=A0 =C2=A0SID list can be optimized by excluding the endpoint Node SID w=
hen<br>
=C2=A0 =C2=A0installing the policy.=C2=A0 This draft specifies procedures t=
o indicate<br>
=C2=A0 =C2=A0whether the endpoint&#39;s node SID needs to be included or ex=
cluded when<br>
=C2=A0 =C2=A0installing the SRv6 Policy.<br>
<br>
File can be retrieved from:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ali-spring-srv6-policy-si=
d-list-optimization/" rel=3D"noreferrer" target=3D"_blank">https://datatrac=
ker.ietf.org/doc/draft-ali-spring-srv6-policy-sid-list-optimization/</a><br=
>
<br>
Please reply to this message keeping <a href=3D"mailto:spring@ietf.org" tar=
get=3D"_blank">spring@ietf.org</a> in copy by indicating<br>
whether you support or not the adoption of this draft as a WG document.<br>
Comments to motivate your preference are highly appreciated.<br>
<br>
Authors, and WG participants in general, are reminded of the Intellectual<b=
r>
Property Rights (IPR) disclosure obligations described in BCP 79 [2].<br>
Appropriate IPR disclosures required for full conformance with the provisio=
ns<br>
of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any.<br>
Sanctions available for application to violators of IETF IPR Policy can be<=
br>
found at [3].<br>
<br>
Thank you.<br>
[1] <a href=3D"https://datatracker.ietf.org/doc/bcp78/" rel=3D"noreferrer" =
target=3D"_blank">https://datatracker.ietf.org/doc/bcp78/</a><br>
[2] <a href=3D"https://datatracker.ietf.org/doc/bcp79/" rel=3D"noreferrer" =
target=3D"_blank">https://datatracker.ietf.org/doc/bcp79/</a><br>
[3] <a href=3D"https://datatracker.ietf.org/doc/rfc6701/" rel=3D"noreferrer=
" target=3D"_blank">https://datatracker.ietf.org/doc/rfc6701/</a><br>
<br>
<br>
<br>
_______________________________________________<br>
spring mailing list -- <a href=3D"mailto:spring@ietf.org" target=3D"_blank"=
>spring@ietf.org</a><br>
To unsubscribe send an email to <a href=3D"mailto:spring-leave@ietf.org" ta=
rget=3D"_blank">spring-leave@ietf.org</a><br>
</blockquote></div>

--000000000000e698bc06424d1798--