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

There is a typo in the below which if not understood as a typo would be quite confusing. I wrote that I raised the issue with "with the Internet ADs and SPRING chairs". That should have read "with the Internet ADs and 6man chairs". The SPRING co-chairs are recused, and the charter requirement l

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

Joel, On 13-Oct-21 20:37, Joel M. Halpern wrote: >> 1) Does the placement of a list of sids in the IPv6 DA field change the >> IPv6 architectural description of that field. That's why I recently asked for a set of examples of the resulting "addresses". I don't understand enough of SRV6 to und

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

Brian E Carpenter wrote: > So I'm not concerned that srv6-srh-compression has any more fundamental > impact than basic SRV6 or RFC8986. (However, this aspect of SRV6 was > one of my primary motivations for RFC8799. What happens in SRV6 stays > in SRV6.) You said it better than I.

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

On Wed, Oct 13, 2021 at 9:28 PM Brian E Carpenter < brian.e.carpen...@gmail.com> wrote: > > > Including semantics *of any kind* in an IP address is a very fundamental > change to the concept of IP. Would you mind elaborating what you mean by semantics

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

On 13. Oct 2021, at 22:26, Brian E Carpenter wrote: > > Including semantics *of any kind* in an IP address is a very fundamental > change to the concept of IP. I may be wrong, but I'm not aware that any > RFCs prior to SRV6 have done this, and the founding reference for what > an address *is* s

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

On 14-Oct-21 22:41, Ted Hardie wrote: > On Wed, Oct 13, 2021 at 9:28 PM Brian E Carpenter > mailto:brian.e.carpen...@gmail.com>> wrote: > > > > Including semantics *of any kind* in an IP address is a very fundamental > change to the concept of IP.

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

On Thu, Oct 14, 2021 at 2:07 PM Brian E Carpenter wrote: > > On 14-Oct-21 22:41, Ted Hardie wrote: > > On Wed, Oct 13, 2021 at 9:28 PM Brian E Carpenter > > mailto:brian.e.carpen...@gmail.com>> wrote: > > > > > > > > Including semantics *of any kind* in an IP address is a very fundamental > >

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

Hi Joel , all, C-SID is no more than another mechanism that relies on some algorithmic mapping embedded in the IPv6 address. We do have already many of such algorithmic approaches: RFC6052, RFC7597, etc. The internal structure would be problematic if it requires that every intermediate node

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

On Fri, 15 Oct 2021, 17:18 , wrote: > Hi Joel , all, > > C-SID is no more than another mechanism that relies on some algorithmic > mapping embedded in the IPv6 address. We do have already many of such > algorithmic approaches: RFC6052, RFC7597, etc. That's not correct. DAs aren't expected to

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

Hi Mark, Not sure what is incorrect in what I mentioned. Checksum neutrality is a distinct issue than the original question from Joel. That was discussed in the RFCs cited in the previous message. That’s said, I’m not sure that’s an issue for SRH given that the encap will need to be updated an

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

On Thu, Oct 14, 2021 at 10:06 PM Brian E Carpenter < brian.e.carpen...@gmail.com> wrote: > On 14-Oct-21 22:41, Ted Hardie wrote: > > On Wed, Oct 13, 2021 at 9:28 PM Brian E Carpenter < > brian.e.carpen...@gmail.com > wrote: > > > > > > > > Including semantic

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

On Fri, Oct 15, 2021 at 12:14 AM Mark Smith wrote: > > > > On Fri, 15 Oct 2021, 17:18 , wrote: >> >> Hi Joel , all, >> >> C-SID is no more than another mechanism that relies on some algorithmic >> mapping embedded in the IPv6 address. We do have already many of such >> algorithmic approaches: R

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

Mark Smith wrote: > In fight changing DAs also will break AH protection of the IPv6 header. AH is dead. It's been dead for decades. I say this as an IPsec enthusiast who wishes this wasn't true. But it is. ___ spring mailing list spring@ietf.org ht

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

Ted, On 15-Oct-21 23:39, Ted Hardie wrote: > On Thu, Oct 14, 2021 at 10:06 PM Brian E Carpenter > mailto:brian.e.carpen...@gmail.com>> wrote: > > On 14-Oct-21 22:41, Ted Hardie wrote: > > On Wed, Oct 13, 2021 at 9:28 PM Brian E Carpenter > mailto:brian.e.carpen...@gmail.com> >

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

Hi Brian, Thanks for the additional clarification. I've cut below to the meat of what I understand to be your question: On Sat, Oct 16, 2021 at 10:19 PM Brian E Carpenter < brian.e.carpen...@gmail.com> wrote: > I want to draw a distinction between unicast address bits that are > arbitrary nu

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

Ted, On 18-Oct-21 20:22, Ted Hardie wrote: > Hi Brian, > > Thanks for the additional clarification.  I've cut below to the meat of what > I understand to be your question: > > > On Sat, Oct 16, 2021 at 10:19 PM Brian E Carpenter > mailto:brian.e.carpen...@gmail.com>> wrote: >   > >  I wan

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

Hi, After reading a lot of messages, I'm going to offer my considered opinion as a direct response to Joel's OP. Firstly, I don't believe that in the end this draft raises any concerns that are *significantly* different than those raised when RFC 8986 was in draft. As Ted Hardie mentioned, sectio

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

Hi Brian, On Tue, 19 Oct 2021 at 15:51, Brian E Carpenter wrote: > > Hi, > > After reading a lot of messages, I'm going to offer my considered > opinion as a direct response to Joel's OP. > > Firstly, I don't believe that in the end this draft raises any > concerns that are *significantly* differ

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

On Tue, Oct 19, 2021, 12:10 AM Mark Smith wrote: > Hi Brian, > > On Tue, 19 Oct 2021 at 15:51, Brian E Carpenter > wrote: > > > > Hi, > > > > After reading a lot of messages, I'm going to offer my considered > > opinion as a direct response to Joel's OP. > > > > Firstly, I don't believe that in

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

On 20-Oct-21 05:02, Tom Herbert wrote: > > > On Tue, Oct 19, 2021, 12:10 AM Mark Smith > wrote: > > Hi Brian, > > On Tue, 19 Oct 2021 at 15:51, Brian E Carpenter > mailto:brian.e.carpen...@gmail.com>> wrote: > > > > Hi, > > > > After r

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

Hi Brian, I've got some questions about what you've said: For that reason, the fact that the bottom 64 bits in the "address" look funny or change is simply irrelevant. They are invisible to routing (which is done based on the prefix) and invisible to neighbor discovery (because it never happens).

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

Greg, I would much prefer that one of the SRv6 experts answers that question. Regards Brian On 21-Oct-21 09:13, Greg Mirsky 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 > > "address" look funny or c

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] 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 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

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] 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 Chengli Please see my reply to Darren about the pseudocode update to the draft. I highly recommend updating the draft per Darren’s updates, as this change will really helps us understand the next and replace pseudocode processing as most of the questions all related to indexing of the bits wi

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

Hi Daren, thank you for responding to my question. Is 64-bits routable prefix in the DA an implicit prerequisite of the C-SID solution? As to my question about what Brian referred to as a "funny" part. In Section 6 we read: The NEXT-C-SID flavor supports both 16- and 32-bit C-SID lengths. A

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

Hi Greg. You ask “Is 64-bits routable prefix in the DA an implicit prerequisite of the C-SID solution?” The answer is no. In the rest of your query i think you are asking how IPv6 packet forwarding works (I.e, based on prefix). Recall the compressed SIDs in the draft are SRv6 SID with a locat

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

[replying on this thread as is has more folks cc'd] Joel, First: thank you to everyone who has commented, clarified, sat for meetings, and reviewed and edited text, often repeatedly. It is very much appreciated. This reply is on behalf of the 6MAN chairs and INT ADs. -- Erik, Éric, Bob, Ole [

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

Joel, One thing that could have been more clear (of many such things, no doubt)... On Mon, Oct 25, 2021 at 3:39 PM Erik Kline wrote: > [replying on this thread as is has more folks cc'd] > --- > > Next steps for consideration: > > [A] A separate 6MAN document to clarify and categorize SRv6 SIDs