[spring] Re: Call for adoption: draft-yang-spring-sid-as-source-address

[Gyan Mishra <[e-mail]>]

I do not support adoption of this draft for the reasons below:

Major issues with the draft below:

1st major issue with this subject draft is it proposes using the source IP
of SRv6 tunnel to use  the service sid  endpoint behavior which is part of
IP VPN VRF.  That technically won’t work as just as the loopback IGP best
path selection lowest metric tie breaker next hop must be in the global
table so does the source IP for the tunnel must be in the global table.

2nd major issue with this draft is that there is only one source address
you can set for the SRv6 tunnel.

3rd major issue is how would that work if you have many endpoint behaviors
per vrf or CE Sid allocation that many Sid addresses in different vrf which
would you even pick.

4th major issue that the SRv6 tunnel carries all the IP VPN  VRFs and not
just the single VRF service Sid endpoint behavior that you decide to set
the source address per this draft.

Kind Regards

Gyan

On Thu, Jul 23, 2026 at 4:26 PM Robert Raszuk <[e-mail]> wrote:

> Hi,
>
> I have read the draft and support the adoption. It is a well written
> and useful document.
>
> It provides a solution to data plane consistency and symmetry for ICMP.
>
> While the draft is not explicitly discussing it - it also actually solves
> the problem with BGP NEXT_HOP being accidentally different from Service
> SIDs creating all sources of bgp related issues.
>
> The service SID used as source can be in the same time advertised in BGP
> protocol NEXT_HOP via proper use of existing update-source knob.
>
> Kind regards,
> Robert
>
>
> On Fri, Jul 10, 2026 at 2:52 PM <[e-mail]> wrote:
>
>> Dear WG,
>>
>>
>>
>> This message starts a 3-week WG adoption call, ending 2026-07-31, for
>> draft-yang-spring-sid-as-source-address-13 [1]
>>
>>
>> After review of the document, please indicate support (or not) for WG
>> adoption of the document to the mailing list.
>> Please also provide comments/reasons for your support (or lack thereof)
>> as this is a stronger way to indicate your (non) support as this is not a
>> vote.
>> If you are willing to work on or review the document, please state this
>> explicitly. This gives the chairs an indication of the energy level of
>> people in the working group willing to work on the document.
>>
>> Thanks!
>> Alvaro, Bruno, Joel
>>
>>
>>
>> [1]
>> https://datatracker.ietf.org/doc/html/draft-yang-spring-sid-as-source-address-13
>>
>>
>>
>> ____________________________________________________________________________________________________________
>> 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.
>>
>> _______________________________________________
>> spring mailing list -- [e-mail]
>> To unsubscribe send an email to [e-mail]
>>
> _______________________________________________
> spring mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
>