Sorry I missed that. Thank you!!
On Fri, Sep 24, 2021 at 11:05 AM James Guichard < james.n.guich...@futurewei.com> wrote: > Hi Gyan, > > > > [Chair hat off …] > > > > You asked where in the CSID document it states “CSID draft recommended > NEXT-C-SID use for 16-bit C-SIDs, and REPLACE-C-SID use for 32-bit C-SIDs. “ > > > > Please see: > > > > *6 > <https://datatracker.ietf.org/doc/html/draft-filsfilscheng-spring-srv6-srh-compression-02#section-6>. > C-SID and Block Length* > > > > *6.1 > <https://datatracker.ietf.org/doc/html/draft-filsfilscheng-spring-srv6-srh-compression-02#section-6.1>. > C-SID Length* > > > > The NEXT-C-SID flavor supports both 16- and 32-bit C-SID lengths. A > > C-SID length of 16-bit is recommended. > > > > The REPLACE-C-SID flavor supports both 16- and 32-bit C-SID lengths. > > A C-SID length of 32-bit is recommended. > > > > Jim > > > > > > *From:* Gyan Mishra <hayabusa...@gmail.com> > *Sent:* Friday, September 24, 2021 10:53 AM > *To:* Darren Dukes (ddukes) <ddu...@cisco.com> > *Cc:* SPRING WG <spring@ietf.org>; > draft-filsfilscheng-spring-srv6-srh-compress...@ietf.org; > spring-cha...@ietf.org > *Subject:* Re: [spring] > https://datatracker.ietf.org/doc/html/draft-filsfilscheng-spring-srv6-srh-compression-02#section-4.1.1 > > > > Thank you Darren! > > > > Few comments. > > > > I do see many early allocation for C-SID for various endpoint behaviors. > > > > https://www.iana.org/assignments/segment-routing/segment-routing.xhtml > <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.iana.org%2Fassignments%2Fsegment-routing%2Fsegment-routing.xhtml&data=04%7C01%7Cjames.n.guichard%40futurewei.com%7C02af79e38912473c50e108d97f6b41be%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637680920918409649%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=eWX%2Bhuyl9obuOYLLxQs%2FoH4t7lllEfacUp5C0c5QgNg%3D&reserved=0> > > > > I was trying to find out where in the CSID draft that is stated. Please > provide the section. > > > > “CSID draft recommended NEXT-C-SID use for 16-bit C-SIDs, and > REPLACE-C-SID use for 32-bit C-SIDs. “ > > > > Just based on the CSID draft SRv6 forwarding plane flavors, SID > formatting, the NEXT-C-SID used a 16-bit combined NF -Locator/Function > uSID variant where the REPLACE-C-SID uses a 32-bit combined > NF-Locator/Function. > > > > I did not see explicit verbiage as to one flavor or the other for 16 or 32 > bit SID. > > > > I believe this information is important to be included in the analysis > draft as well. > > > > Section 6 talks about CSID length, Block length and GIB/LIB usage but does > not specify explicitly what you are stating. > > > > As the WG has clearly stated that they would like a single solution, > however CSID is inclusive of 2 SRv6 forwarding compression solutions not > one from the two drafts - uSID & G-SID. > > > > So that would have to be hashed out by the WG taking into account the > interoperability issue that is the key point of contention to having > multiple solutions from an operators perspective. > > > > Kind Regards > > > > Gyan > > > > > > > > On Fri, Sep 24, 2021 at 10:10 AM Darren Dukes (ddukes) <ddu...@cisco.com> > wrote: > > Hi Gyan, as a DT member, I can answer your analysis draft question. > > Consistent with the requirement document, proposals were analyzed with > 16-bit and 32-bit SID lengths, though several supported additional options. > > The CSID draft recommended NEXT-C-SID use for 16-bit C-SIDs, and > REPLACE-C-SID use for 32-bit C-SIDs. The design team followed this > recommendation in its analysis, though the CSID draft notes all flavors > support both 16-bit and 32-bit C-SID length. > > Darren > > > > > > On 2021-09-19, 3:34 PM, "spring" <spring-boun...@ietf.org> wrote: > > > > Dear Authors > > > > After having a few discussions on threads related to the SRv6 compression > analysis draft results, as well as WG coming to consensus on a single SRv6 > compression solution, a few critical questions have come up related to > C-SID draft that requires clarification by the authors. > > > > The C-SID draft has 3 compression solutions below and is a combination of > the two drafts below which introduces 2 of the 3 compression solutions with > the C-SID draft introduction of yet a 3rd compression solution. > > > > Which of the 3 C-SID draft compression solutions was included as part of > the DT analysis draft results and conclusion? > > > > This is a critical question that needs to be answered for clarification on > the C-SID draft solution. > > > > As the WG has consensus on a single solution we need to have clarification > from the authors which of the 3 compression solutions was included in the > analysis. > > > > The three solutions are very different and all would yield different > analysis results. > > > > I understand the authors have called the each solution a endpoint flavor > which I see from the IANA codepoint allocations, however each flavor is a > different solution. > > > > https://www.iana.org/assignments/segment-routing/segment-routing.xhtml > <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.iana.org%2Fassignments%2Fsegment-routing%2Fsegment-routing.xhtml&data=04%7C01%7Cjames.n.guichard%40futurewei.com%7C02af79e38912473c50e108d97f6b41be%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637680920918419645%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=QYAGkTnNs0Bfb768auk2U%2BzykfOw%2BPmF609Dj6gwlIQ%3D&reserved=0> > > > > So the WG as stated would like a single solution so now we need feedback > from the authors which of the three solutions or endpoint flavors was part > of the DT analysis draft that the authors would like to put forward as the > single compression solution. > > > > C-SID is a combination of the two drafts below: > > > > Combination of the two drafts below: > > > > G-SID - Generalized SID “REPLACE-C-SID” > > > https://datatracker.ietf.org/doc/html/draft-cl-spring-generalized-srv6-for-cmpr-03 > <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-cl-spring-generalized-srv6-for-cmpr-03&data=04%7C01%7Cjames.n.guichard%40futurewei.com%7C02af79e38912473c50e108d97f6b41be%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637680920918419645%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=xQXCNLDdSC4XXjdZXrLM05BxJ11M4cSZPtI2pSGURAA%3D&reserved=0> > > > > SRv6 uSID micro-segment “ NEXT-C-SID” > > > https://datatracker.ietf.org/doc/html/draft-filsfils-spring-net-pgm-extension-srv6-usid-10 > <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-filsfils-spring-net-pgm-extension-srv6-usid-10&data=04%7C01%7Cjames.n.guichard%40futurewei.com%7C02af79e38912473c50e108d97f6b41be%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637680920918429635%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=6CispEy1z1jsNI5LzPsbMA3aIlsImAZ4dgWZFrIneYk%3D&reserved=0> > > > > Kind Regards > > > > Gyan > > -- > > > <https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.verizon.com%2F&data=04%7C01%7Cjames.n.guichard%40futurewei.com%7C02af79e38912473c50e108d97f6b41be%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637680920918429635%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=1ByliHlPrZzPB60cwrVTmTOwT2q%2B4%2BUBNDdLA4CC5%2Bs%3D&reserved=0> > > *Gyan Mishra* > > *Network Solutions Architect * > > *Email gyan.s.mis...@verizon.com <gyan.s.mis...@verizon.com>* > > *M 301 502-1347* > > > > -- > > > <https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.verizon.com%2F&data=04%7C01%7Cjames.n.guichard%40futurewei.com%7C02af79e38912473c50e108d97f6b41be%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637680920918439634%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=uXz1BTmNxaOSWuBsAtojA8XcK8oFv27Ptx63%2FU0vSLE%3D&reserved=0> > > *Gyan Mishra* > > *Network Solutions Architect * > > *Email gyan.s.mis...@verizon.com <gyan.s.mis...@verizon.com>* > > *M 301 502-1347* > > > -- <http://www.verizon.com/> *Gyan Mishra* *Network Solutions A**rchitect * *Email gyan.s.mis...@verizon.com <gyan.s.mis...@verizon.com>* *M 301 502-1347*
_______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
