Nick I fully agree that IF SRv6 were requiring non-backward-compatible changes this would be a contradiction to the definitions of RFC 8402.
So, let's prevent SRv6 from requesting such changes and, where necessary, extend IPv6 in a backward-compatible way. I believe this is doable. My 2c, Sasha Get Outlook for Android<https://aka.ms/AAb9ysg> ________________________________ From: spring <spring-boun...@ietf.org> on behalf of Nick Hilliard <n...@foobar.org> Sent: Thursday, March 28, 2024 5:42:44 PM To: Alexander Vainshtein <alexander.vainsht...@rbbn.com> Cc: Alvaro Retana <aretana.i...@gmail.com>; int-a...@ietf.org <int-a...@ietf.org>; spring-cha...@ietf.org <spring-cha...@ietf.org>; SPRING WG List <spring@ietf.org> Subject: Re: [spring] [EXTERNAL] Separating Threads (draft-ietf-spring-srv6-srh-compression) Alexander Vainshtein wrote on 28/03/2024 15:03: > Alvaro and all, > > Regarding the proposal for using a dedicated Ethertype for SRv6: > > Please note that RFC explicitly “introduces two data-plane > instantiations of SR: SR over MPLS (SR-MPLS) and SR over IPv6 (SRv6)” > and defines SRv6 as the instantiation of SR on the IPv6 data plane. > > From my POV using a dedicated Ethertype for SRv6 would directly > contradict these definitions. Sasha, If srv6 is going to demand non backwards-compatible changes to the ipv6 protocol, then it's no longer the ipv6 data plane. What this means in practice is that it's the requirement for these changes that contradicts the definitions in rfc8204, rather than the suggestion to use a different ethertype. Nick _______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring<https://www.ietf.org/mailman/listinfo/spring> Disclaimer This e-mail together with any attachments may contain information of Ribbon Communications Inc. and its Affiliates that is confidential and/or proprietary for the sole use of the intended recipient. Any review, disclosure, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please notify the sender immediately and then delete all copies, including any attachments.
_______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
