Re: [spring] Typo correction Re: Question from SPRING regarding draft-filsfilscheng-spring-srv6-srh-compression

Hi Gyan and Greg. Gyan I’m sorry but i don’t see a question in your email. I’ll go back to Greg. While I’m not exactly sure what is being asked, I will say that Brian is correct for every Srv6 SID behavior (not just csid flavors) when he says the following about their arguments (lowest 64 bits

Re: [spring] Typo correction Re: Question from SPRING regarding draft-filsfilscheng-spring-srv6-srh-compression

Hi Gyan, Sorry I don’t understand the case you mentioned. Could you please provide an easy example? How a SID will be shifting in a GSID container? Respect, Cheng From: ipv6 [mailto:ipv6-boun...@ietf.org] On Behalf Of Gyan Mishra Sent: Friday, October 22, 2021 6:58 AM To: Darren Dukes (ddukes)

Re: [spring] WG Adoption call for https://datatracker.ietf.org/doc/draft-filsfilscheng-spring-srv6-srh-compression/

Hi，WG， I am sorry it seems too late to respond to the adoption call. I would like to express my support for the draft. As an operator, We do need a SRH header compression standard. Hence, we’re looking forward to any progress in it. Best regards, Pang Ran. From: James Guichard

Re: [spring] Typo correction Re: Question from SPRING regarding draft-filsfilscheng-spring-srv6-srh-compression

Hi Darren What Greg is asking is if the SID is a prefix SID End and not adjacency SID End.x, so now the common prefix is needed to ECMP steer the flow to the prefix SID which uses the common prefix, which may in this case be mutated due to shifting of SIDs in GSID container. Kind Regards Gyan

Re: [spring] Typo correction Re: Question from SPRING regarding draft-filsfilscheng-spring-srv6-srh-compression

Brian Thank you for very eloquently explaining at least how an adjacency sid strict path end.x endpoint behavior does not violate any IPv6 specification. Also that CSID draft at least for end.x strict paths does not in any way change the IPv6 data plane. Kind Regards Gyan On Tue, Oct 19, 2021

Re: [spring] Typo correction Re: Question from SPRING regarding draft-filsfilscheng-spring-srv6-srh-compression

Hi Greg, Your question is not clear to me. Can you try to restate it with the flavors and behaviors from the draft in question? Darren On 2021-10-20, 4:15 PM, "ipv6" wrote: Hi Brian, I've got some questions about what you've said: For that reason, the fact that the bottom 64 bits in the "addr

Re: [spring] Question from SPRING regarding draft-filsfilscheng-spring-srv6-srh-compression

Hi Stefano, [spring@ re-added to cc:] Stefano Salsano wrote on 20/10/2021 22:36: I can anticipate that it is possible to use wireshark to dissect CSID packets, by providing very simple configuration information. This is exactly the problem though - operators will need to manually instruct a

Re: [spring] WG Adoption call for https://datatracker.ietf.org/doc/draft-filsfilscheng-spring-srv6-srh-compression/

Hi ALL， After a long-term discussion in the WG, we have reached this point today I support the adoption of CSID draft, which describes an efficient solution of SRv6 compression. I understand the document defines several Flavors, and I think it is just like the normal flavors defined in RFC8986

Re: [spring] WG Adoption call for https://datatracker.ietf.org/doc/draft-filsfilscheng-spring-srv6-srh-compression/

Hi ALL， After a long-term discussion in the WG, we have reached this point today I support the adoption of CSID draft, which describes an efficient solution of SRv6 compression. I understand the document defines several Flavors, and I think it is just like the normal flavors defined in RFC8986