Re: [spring] I-D Action: draft-ietf-spring-srv6-srh-compression-01.txt

gt; Zhenbin Li > Bruno Decraene > Dennis Cai > Daniel Voyer > Francois Clad > Shay Zadok >

Re: [spring] I-D Action: draft-ietf-spring-srv6-srh-compression-02.txt

List Encoding in SRH > Authors : Weiqiang Cheng > Clarence Filsfils > Zhenbin Li > Bruno Decraene > Dennis Cai > Daniel Voyer &g

Re: [spring] I-D Action: draft-ietf-spring-srv6-srh-compression-02.txt

Zhenbin Li > >Bruno Decraene > > Dennis Cai > >Daniel Voyer > >Francois Clad > >Shay Zadok > >

Re: [spring] I-D Action: draft-ietf-spring-srv6-srh-compression-02.txt

container is not fully used - Clarified in Sec 6.3 the meaning of GIB and LIB Thanks, Francois On Tue, Jul 19, 2022 at 6:38 PM Francois Clad wrote: > Hi Joel, > > It is correct that this revision is mostly editorial. I sent an email on > the list at the time the new revision was post

Re: [spring] I-D Action: draft-ietf-spring-srv6-srh-compression-04.txt

Clarence Filsfils > Zhenbin Li > Bruno Decraene > Francois Clad >Filename: draft-ietf-spring-srv6-srh-compression-04.txt >Pages : 45 >Date: 2023-03-31 > > Abstrac

Re: [spring] I-D Action: draft-ietf-spring-srv6-srh-compression-04.txt

new text in Sec. 9 clarifies that an SR source node requires SID structure information to perform the compression of a segment list provided in uncompressed format. Thanks, Francois (on behalf of the C-SID co-authors) On Tue, Apr 4, 2023 at 7:00 PM Francois Clad wrote: > Dear WG, > >

Re: [spring] I-D Action: draft-ietf-spring-srv6-srh-compression-04.txt

NEXT-C-SID and REPLACE-C-SID flavor apply to these other SIDs in the same way that they apply to End and End.X. Thanks, Francois (on behalf of the C-SID co-authors) On Tue, Apr 4, 2023 at 7:00 PM Francois Clad wrote: > Dear WG, > > > > This revision includes significant text ch

Re: [spring] I-D Action: draft-ietf-spring-srv6-srh-compression-05.txt

Clarence Filsfils > Zhenbin Li > Bruno Decraene > Francois Clad > Filename: draft-ietf-spring-srv6-srh-compression-05.txt > Pages : 49 > Date: 2023-06-20 > > Abstract: > T

[spring] Update on draft-ietf-spring-srv6-srh-compression issues

Dear WG, The authors of draft-ietf-spring-srv6-srh-compression have updated the GitHub issue tracker ( https://github.com/ietf-wg-spring/draft-ietf-spring-srv6-srh-compression/issues), indicating what was done to address the issues #1 to #5. Please let us know if any further action is needed on a

Re: [spring] A question about draft-ietf-spring-srv6-srh-compression

Hi Adrian, Thanks a lot for your feedback. We have received the assignments from IANA and updated the draft to reflect the same. My understanding is that all shipping implementations are using the assigned values from IANA. For the values just assigned, there are early implementations or POC co

Re: [spring] I-D Action: draft-ietf-spring-srv6-srh-compression-06.txt

TF. > > Title : Compressed SRv6 Segment List Encoding in SRH > Authors : Weiqiang Cheng > Clarence Filsfils > Zhenbin Li > Bruno Decraene > Francois Clad > Filename: draft-ietf-sprin

Re: [spring] Issue 1 regarding draft-ietf-spring-srv6-srh-compression

Hi Greg, Darren, Many thanks for clarifying this concern and for proposing text to address it. I agree that this would make it more clear. Thanks, Francois On 16 Aug 2023 at 19:12:40, Darren Dukes (ddukes) wrote: > Hi Greg, thanks for clarifying your concerns with proposed text. I like > the

Re: [spring] Issue 1 regarding draft-ietf-spring-srv6-srh-compression

Hi Andrew, Thank you for your feedback and for sharing your concerns. Let me elaborate on top of what Changwang and others have replied. > If there is an implementation done that supports NEXT-C-SID and NOT REPLACE-C-SID – would it inter-operate with an implementation that supports REPLACE-C-SI

Re: [spring] I-D Action: draft-ietf-spring-srv6-srh-compression-07.txt

Encoding in SRH > Authors: Weiqiang Cheng >Clarence Filsfils >Zhenbin Li >Bruno Decraene >Francois Clad > Name:draft-ietf-spring-srv6-srh-compression-07.txt > Pages: 51 > Dates: 2023-08-31 > > Abstract: > > This d

Re: [spring] ICMP and Compressed SIDs

Hi Joel, The receiver in this case is an SR segment endpoint node processing an IPv6 packet that matches a FIB entry locally instantiated as a SID of this document. Therefore, the expected behavior of the receiver is that described in Sec. 4. Thanks, Francois On 6 Sep 2023 at 16:38:30, Joel Hal

Re: [spring] ICMP and Compressed SIDs

ers dropping such packets.) > > Yours, > > Joel > On 9/7/2023 4:09 AM, Francois Clad wrote: > > Hi Joel, > > The receiver in this case is an SR segment endpoint node processing an > IPv6 packet that matches a FIB entry locally instantiated as a SID of this > docu

Re: [spring] ICMP and Compressed SIDs

: > Why is it unspecified what the behavior is if the arg bits are non-zero. > Leaving things unspecified (and getting different behaviors from different > implementations) makes things more complex if we need to build on this > behavior. > > Yours, > > Joel > On 9/7/2

Re: [spring] I-D Action: draft-ietf-spring-srv6-srh-compression-08.txt

> > Title: Compressed SRv6 Segment List Encoding in SRH > Authors: Weiqiang Cheng >Clarence Filsfils >Zhenbin Li > Bruno Decraene >Francois Clad > Name:draft-ietf-spring-srv6-srh-compression-08.txt > Pages: 51 > Da

Re: [spring] I-D Action: draft-ietf-spring-srv6-srh-compression-09.txt

6 Segment List Encoding > Authors: Weiqiang Cheng >Clarence Filsfils >Zhenbin Li > Bruno Decraene >Francois Clad > Name:draft-ietf-spring-srv6-srh-compression-09.txt > Pages: 55 > Dates: 2023-10-23 > > Abstract: >

Re: [spring] Review comments and questions to draft-ietf-spring-srv6-srh-compression-08

Dear Linda, Thank you for your review of this document. Your feedback is much appreciated. We have clarified and amended the text in response to your review, and these modifications were included as part of the recently submitted revision 9 ( https://datatracker.ietf.org/doc/draft-ietf-spring-sr

Re: [spring] Additional SRv6 Compression draft review

Dear Boris, Many thanks for this thorough review! It took us some time to get back to you, but your feedback helped a lot to improve the document. We believe that the changes we made as part of revision -09 ( https://datatracker.ietf.org/doc/draft-ietf-spring-srv6-srh-compression/9/) should addr

Re: [spring] I-D Action: draft-ietf-spring-srv6-srh-compression-10.txt

of > the IETF. > > Title: Compressed SRv6 Segment List Encoding > Authors: Weiqiang Cheng >Clarence Filsfils > Zhenbin Li >Bruno Decraene >Francois Clad > Name:draft-ietf-spring-srv6-srh-compression-10.txt >

Re: [spring] A review of draft-ietf-spring-srv6-srh-compression-08

Hi Adrian, Thank you for this follow-up. Indeed, we were still working on some of your comments when revision -09 was pushed. Those remaining comments should now be addressed in revision -10 ( https://datatracker.ietf.org/doc/draft-ietf-spring-srv6-srh-compression/10/ ). Please see our reply to

Re: [spring] A review of draft-ietf-spring-srv6-srh-compression-08

Hi Adrian, Best wishes to you too. Many thanks again for your most valuable feedback and suggestions on this document. Cheers, Francois On Dec 30, 2023 at 17:24:26, Adrian Farrel wrote: > Hi Francois and best wishes for the New Year. > > Tl;dr This is good work. Thank you for the effort. > >

Re: [spring] draft-ietf-spring-srv6-srh-compression

Dear Joel, WG, I am glad that we were able to close this remaining issue. We have just submitted version -11, which removes Appendix A (Open Issues) from the document. https://datatracker.ietf.org/doc/draft-ietf-spring-srv6-srh-compression/11/ There is no other pending change at this time. Th

Re: [spring] Fwd: IETF WG state changed for draft-ietf-spring-srv6-srh-compression

Dear WG, I support the publication of this document. As an implementer, I believe this document provides a solid reference for interoperable implementation. The large number of commercial and open-source implementations reported in section 10 further confirms the maturity of this solution. As a

Re: [spring] IPR call and Shepherding draft-ietf-spring-srv6-srh-compression

Hi Joel, Pablo, Thanks Joel for having found us a shepherd and thanks Pablo for accepting the role. On the subject of IPR, I am not aware of any undisclosed IPR relevant to this draft. Cheers, Francois On Feb 1, 2024 at 17:36:21, Joel Halpern wrote: > 1) This email initiates an IPR call for

Re: [spring] Fwd: IETF WG state changed for draft-ietf-spring-srv6-srh-compression

Hi Martin, Thanks for your support and for this text suggestion. This seems to me a useful clarification. Thanks, Francois On Feb 2, 2024 at 14:58:48, Martin Vigoureux (Nokia) wrote: > Hi, > > I support this document moving forward. > > As part of the WG LC I'd like to suggest a minor clarifi

Re: [spring] Fwd: IETF WG state changed for draft-ietf-spring-srv6-srh-compression

Dear Dhruv, Thank you for your support and feedback on this document. I’ll work with the other co-authors on integrating your suggestions. Thanks, Francois On Feb 4, 2024 at 11:21:22, Dhruv Dhody wrote: > Hi Joel, WG, > > I support this I-D and would like to see it published. I have a few > s

Re: [spring] draft-ietf-spring-srv6-srh-compression

Hi Andrew, The L4 checksum issue that you have brought up is from the point of view of a “middleware” node. Is my understanding correct? This is not from either the source or destination node point of view which is covered by section 8.1 of RFC 8200. Can you please describe this “middleware” and

Re: [spring] draft-ietf-spring-srv6-srh-compression

Andrew > > Andrew Alston > > Internal All Employees > -- > *From:* Nick Buraglio > *Sent:* Wednesday, February 7, 2024 2:32:22 AM > *To:* Robert Raszuk > *Cc:* Andrew Alston - IETF ; Antoine > FRESSANCOURT ; Francois Clad < > fclad.i...@gmail.com>; Nick Hilliard ;

Re: [spring] I-D Action: draft-ietf-spring-srv6-srh-compression-12.txt

> Bruno Decraene >Francois Clad > Name:draft-ietf-spring-srv6-srh-compression-12.txt > Pages: 73 > Dates: 2024-02-14 > > Abstract: > > Segment Routing over IPv6 (SRv6) is the instantiation of Segment > Routing (SR) on the IPv6 dataplane. T

Re: [spring] Fwd: IETF WG state changed for draft-ietf-spring-srv6-srh-compression

Hi Dhruv, Thank you for your support and suggestions. We have integrated those changes as part of revision -12 of the document. Please find the detailed replies inline. Thanks, Francois > ## Suggestions > > - A general reader might be tempted to know why two flavors exist? Perhaps a few senten

Re: [spring] draft-ietf-spring-srv6-srh-compression

Hi Andrew, Any thoughts on the below? Thanks, Francois On Feb 8, 2024 at 16:03:57, Francois Clad wrote: > Hi Andrew, > > Assuming that Nick is correct and that you are indeed referring to > middleboxes as defined in RFC 3234, can you describe the problem that a > network oper

Re: [spring] I-D Action: draft-ietf-spring-srv6-srh-compression-13.txt

ilable. > It is a work item of the Source Packet Routing in Networking (SPRING) WG of > the IETF. > > Title: Compressed SRv6 Segment List Encoding > Authors: Weiqiang Cheng >Clarence Filsfils >Zhenbin Li > Bruno Decraene >

Re: [spring] Chair Review of draft-ietf-spring-srv6-srh-compression-11

Hi Alvaro, Thank you for your review and comments. We have integrated those changes as part of revisions -12 and -13 of the document. Please find our detailed replies inline. Thanks, Francois > Dear authors: > > In parallel with the WGLC I have reviewed this document. Thank you > for the work

Re: [spring] Chair Review of draft-ietf-spring-srv6-srh-compression-11

On February 29, 2024 at 12:50:46 PM, Francois Clad wrote: > > Francois: > > Hi! > > We have integrated those changes as part of revisions -12 and -13 of the > > document. Please find our detailed replies inline. > > > I have put comments below as well, and deleted

Re: [spring] I-D Action: draft-ietf-spring-srv6-srh-compression-14.txt

outing in Networking (SPRING) WG of > the IETF. > > Title: Compressed SRv6 Segment List Encoding > Authors: Weiqiang Cheng >Clarence Filsfils >Zhenbin Li > Bruno Decraene >Francois Clad > Name:draft-ietf-spring-s

Re: [spring] Chair Review of draft-ietf-spring-srv6-srh-compression-11

Dear Alvaro, We have integrated the remainder of your feedback in revision -14. Detailed replies inline. These include your follow-up comments as well as the review items that we missed in the first pass. Please let us know if you have any further feedback. Thanks, Francois > ... > > > Operati

Re: [spring] C-SIDs and upper layer checksums (draft-ietf-spring-srv6-srh-compression)

Hi all, Section 6.5 of draft-ietf-spring-srv6-srh-compression specifies how an SR source node originating a packet with an upper layer checksum determines the Destination Address for use in the IPv6 pseudo-header. As a co-author, I’d say that the current text of 6.5 is good. This text is aligne

Re: [spring] [IPv6] Subject: Mandating SRH when using C-SIDs (draft-ietf-spring-srv6-srh-compression)

Hi Alvaro, all, RFC 8754 allows the SR source node to omit the SRH when it contains redundant information with what is already carried in the base IPv6 header. Mandating its presence for C-SID does not resolve any problem because it will not provide any extra information to the nodes along the pa

Re: [spring] [IPv6] Subject: Mandating SRH when using C-SIDs (draft-ietf-spring-srv6-srh-compression)

Hi Mark, Tcpdump/wireshark decodes the IPv6 header just fine. I do not see any issue here. Cheers, Francois On 4 Apr 2024 at 14:09:43, Mark Smith wrote: > > > On Thu, 4 Apr 2024, 22:50 Francois Clad, wrote: > >> Hi Alvaro, all, >> >> RFC 8754 allows the SR so

Re: [spring] C-SIDs and upper layer checksums (draft-ietf-spring-srv6-srh-compression)

kets as standard Ipv6 packets. > > > > This is broken – severely broken. > > > > Andrew > > > > > > * Internal All Employees From: *spring on > behalf of Francois Clad > *Date: *Thursday, 4 April 2024 at 14:49 > *To: *Joel Halpern > *Cc: *SPRING WG List , Robe

Re: [spring] C-SIDs and upper layer checksums (draft-ietf-spring-srv6-srh-compression)

ase software routers are > acting as middle boxes. > > > > Thanks > > > > Andrew > > > > > > > > > > * Internal All Employees From: *Francois Clad > *Date: *Thursday, 4 April 2024 at 16:59 > *To: *Andrew Alston - IETF > *Cc: *SPRING

Re: [spring] C-SIDs and upper layer checksums (draft-ietf-spring-srv6-srh-compression)

SRv6 > domain, and I am trying to verify a uSID path between them, so I issue the > command ping , it will fail? Given that we have documents > describing the use of ping and traceroute with SRv6, shouldn't the > comrpession document say someething about this? > > Your,s >

Re: [spring] [IPv6] Subject: Mandating SRH when using C-SIDs (draft-ietf-spring-srv6-srh-compression)

Hi Tom, Tcpdump can determine that this packet is steered onto an SRv6 path by checking if the DA matches the SRv6 SID block. Thanks, Francois On 4 Apr 2024 at 16:59:59, Tom Herbert wrote: > > > On Thu, Apr 4, 2024, 9:39 AM Francois Clad wrote: > >> Hi Mark, >> >

Re: [spring] C-SIDs and upper layer checksums (draft-ietf-spring-srv6-srh-compression)

is not obvious to me how that would be achieved? > And does seem to imply that an unmodified ping will get incompatible and > unexpected results? > > Yours, > > Joel > On 4/4/2024 10:23 AM, Francois Clad wrote: > > Hi Joel, > > The ping behavior is described in s

Re: [spring] [IPv6] Subject: Mandating SRH when using C-SIDs (draft-ietf-spring-srv6-srh-compression)

Hi Tom, draft-ietf-6man-sids takes care of that [1]. As Michael suggested, tcpdump could use this block as a default with a CLI override for operators using a different one. [1] https://www.ietf.org/archive/id/draft-ietf-6man-sids-06.html#section-6 Thanks, Francois On 4 Apr 2024 at 19:12:26,

Re: [spring] C-SIDs and upper layer checksums (draft-ietf-spring-srv6-srh-compression)

> > clicking links or opening attachments. See the URL nok.it/ext for > > > additional information. > > > > > > So you can't ping a uSID list by just specifying the uSID as the DA? > > > Yours, > > > Joel > > > > > > > &g

Re: [spring] C-SIDs and upper layer checksums (draft-ietf-spring-srv6-srh-compression)

compatible with existing deployments of any > software based routers out there based on bsd, linux and other such kernels > – and is therefore – a direct violation of the spring charter which says > that compatibility with existing deployments cannot be affected. > > > > Andre

Re: [spring] C-SIDs and upper layer checksums (draft-ietf-spring-srv6-srh-compression)

Hi Joel, One small clarification. Knowledge of the SRv6 SID block (either by configuration or using the new SRv6 block specified in draft-ietf-6man-sids as a default) is sufficient for an “observer node” to identify SRv6 traffic and potentially skip verifying the checksum. An SRv6 and C-SID awa

Re: [spring] I-D Action: draft-ietf-spring-srv6-srh-compression-15.txt

etworking (SPRING) WG of > the IETF. > > Title: Compressed SRv6 Segment List Encoding > Authors: Weiqiang Cheng >Clarence Filsfils >Zhenbin Li > Bruno Decraene >Francois Clad > Name:draft-ietf-spring-srv6-sr

Re: [spring] I-D Action: draft-ietf-spring-srv6-srh-compression-16.txt

G) WG of > the IETF. > > Title: Compressed SRv6 Segment List Encoding > Authors: Weiqiang Cheng >Clarence Filsfils >Zhenbin Li > Bruno Decraene >Francois Clad > Name:draft-ietf-spring-srv6-srh-compression-16.txt >

[spring] Re: I-D Action: draft-ietf-spring-srv6-srh-compression-17.txt

he Source Packet Routing in Networking (SPRING) WG of > the IETF. > >Title: Compressed SRv6 Segment List Encoding >Authors: Weiqiang Cheng > Clarence Filsfils > Zhenbin Li > Bruno Decraene > Francois Clad >

[spring] Re: I-D Action: draft-ietf-spring-srv6-srh-compression-18.txt

> available. > It is a work item of the Source Packet Routing in Networking (SPRING) WG of > the IETF. > > Title: Compressed SRv6 Segment List Encoding > Authors: Weiqiang Cheng >Clarence Filsfils >Zhenbin Li > Bruno Decraene

[spring] Re: WG Adoption Call for draft-agrawal-spring-srv6-mpls-interworking

Hi Bruno, all, I support the WG adoption of this document. SRv6 and MPLS interworking is critical for co-existence of these technologies as well as migration from MPLS to SRv6. Thanks, Francois On 11 Jul 2024 at 06:26:57, bruno.decra...@orange.com wrote: > Dear WG: > > > > This message starts a

[spring] Re: [Shepherding AD review] review of draft-ietf-spring-srv6-srh-compression-18

Hi Gunter, Many thanks for your detailed review. I will work on your comments with the co-authors and hope to provide a reply during the week of Oct/14. Thanks, Francois On 2 Oct 2024 at 15:58:10, Gunter van de Velde (Nokia) < gunter.van_de_ve...@nokia.com> wrote: > # Gunter Van de Velde, RTG

[spring] Re: Erik Kline's Discuss on draft-ietf-spring-srv6-srh-compression-19: (with DISCUSS and COMMENT)

Dear Erik, Many thanks for reviewing this document. I am talking with my co-authors about your first DISCUSS item and will get back to you shortly. We also made several changes in revision -20 to address the remaining points of your review. These changes are listed below. Thanks, Francois On

[spring] Re: Éric Vyncke's No Objection on draft-ietf-spring-srv6-srh-compression-19: (with COMMENT)

Dear Eric, Many thanks for reviewing this document. As noted in my reply to Erik, I am talking with my co-authors about your comment on Section 4.2 and will get back to you soon. We also made several changes in revision -20 to address the remaining points of your review. These changes are liste

[spring] Re: John Scudder's Discuss on draft-ietf-spring-srv6-srh-compression-20: (with DISCUSS and COMMENT)

Dear John, Many thanks for reviewing this document. I just pushed a -21 that should address your DISCUSS point (see inline below). https://datatracker.ietf.org/doc/draft-ietf-spring-srv6-srh-compression/21/ We are also working on your remaining comments and hope to address them later today. T

[spring] Re: Erik Kline's Discuss on draft-ietf-spring-srv6-srh-compression-19: (with DISCUSS and COMMENT)

changes in revision -20, addresses all of your concerns on this document. Thanks, Francois On 4 Feb 2025 at 22:46:40, Francois Clad wrote: > Dear Erik, > > Many thanks for reviewing this document. > > I am talking with my co-authors about your first DISCUSS item and will get > b

[spring] Re: John Scudder's Discuss on draft-ietf-spring-srv6-srh-compression-20: (with DISCUSS and COMMENT)

:26:54, Francois Clad wrote: > Dear John, > > Many thanks for reviewing this document. > > I just pushed a -21 that should address your DISCUSS point (see inline > below). > > https://datatracker.ietf.org/doc/draft-ietf-spring-srv6-srh-compression/21/ > > We are

[spring] Re: IPR confirmation for draft-ietf-spring-cs-sr-policy

Hi Joel, WG, I am not aware of any undisclosed IPR relevant to this draft. Cheers, Francois On 21 Feb 2025 at 16:17:12, Joel Halpern wrote: > My apologies, I skipped a step, which if it turns up something could > require additional attention from the WG. > > Editors and named contributors to

[spring] Resuming discussion on draft-ietf-spring-sr-service-programming

(to: SPRING WG; cc: MPLS and 6MAN WGs) Dear WG, With the renewed interest in service programming at recent IETF meetings, we would like to resume discussion on draft-ietf-spring-sr-service-programming (“Service Programming with Segment Routing”) to progress and complete this work as a solid found

[spring] Re: Resuming discussion on draft-ietf-spring-sr-service-programming

ppy if you are interested in it and could give any > feedback, comments, or suggestions. > > > > *Thanks* > -- > > *Best regards,* > *叶佳铭/Jiaming Ye* > 中国移动通信有限公司研究院/China Mobile Research Institute > Email: yejiam...@chinamobile.com > Mobile: 18810735331 > > &g

[spring] Re: [mpls] Resuming discussion on draft-ietf-spring-sr-service-programming

lso pointed out). It shouldn’t be too much work to integrate it, though. > > > Thanks, > > Cheng > > > > > > > > *From:* Francois Clad > *Sent:* Monday, May 12, 2025 12:25 PM > *To:* spring > *Cc:* m...@ietf.org; 6man > *Subject:* [mpls] Resumi

[spring] Re: [mpls] Resuming discussion on draft-ietf-spring-sr-service-programming

y be taken into > consideration. > [FC ] The text in the draft is based on the options that were available at the time. You’re absolutely right that it needs to be updated to take MNA into consideration. > > Regards, > > Yao > > > > > > Original > *From: *Che

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

Hello Erik, You may find some examples here: https://datatracker.ietf.org/doc/draft-clad-spring-srv6-srh-compression-illus/ Hope this helps. Thanks, Francois From: spring on behalf of Erik Kline Date: Thursday, 14 October 2021 at 19:06 To: Joel M. Halpern Cc: spring@ietf.org , i...@ietf.or

Re: [spring] IPR poll for draft-ietf-spring-srv6-network-programming

Hi, As a contributor, I am not aware of any undisclosed IPR related to this document. Thanks, Francois On 05/12/2019 17:54, "spring on behalf of bruno.decra...@orange.com" wrote: Hi SPRING WG, In parallel to the WGLC for draft-ietf-spring-srv6-network-programming, we would lik

Re: [spring] draft-ietf-spring-srv6-network-programming - 2 week Early Allocation Call

Hi, Support. Thanks, Francois Le 3 janv. 2020 à 03:01, Pablo Camarillo (pcamaril) a écrit :  Happy New Year. I support. Thanks, Pablo. From: spring on behalf of "bruno.decra...@orange.com" Date: Thursday, 19 December 2019 at 17:54 To: SPRING WG Subject: [spring] draft-ietf-spring-srv6

Re: [spring] Can features described by draft-ietf-spring-sr-service-programming-01 be supported by draft-ietf-spring-srv6-network-programming-08?

Dear Linda, Thank you for your email. Please see inline. Thanks, Francois From: Linda Dunbar Date: Friday 17 January 2020 at 01:31 To: "draft-ietf-spring-sr-service-programm...@ietf.org" Cc: SPRING WG Subject: Can features described by draft-ietf-spring-sr-service-programming-01 be suppor

Re: [spring] I-D Action: draft-ietf-spring-sr-service-programming-02.txt

net-Drafts directories. This draft is a work item of the Source Packet Routing in Networking WG of the IETF. Title : Service Programming with Segment Routing Authors : Francois Clad Xiaohu Xu

[spring] Compressed SRv6 Segment List Encoding in SRH

Segment List encoding in the SRH. The compressed encoding is achieved through two new flavors of the base Network Programming behaviors (End, End.X and End.T), named NEXT-C-SID and REPLACE-C-SID. Thanks, Weiqiang Cheng Clarence Filsfils Zhenbin Li Dennis Cai Daniel Voyer Francois Clad (editor) Shay

Re: [spring] WG Adoption Call for draft-raza-spring-srv6-yang

Hi, I support the adoption of this draft. The definition of a YANG data model for SRv6 is an important work item and this draft is well aligned with draft-ietf-spring-srv6-network-programming. Thanks, Francois From: spring on behalf of James Guichard Date: Monday 13 July 2020 at 23:54 To: "

Re: [spring] WG Adoption Call for draft-raza-spring-sr-policy-yang

Hi, I support the adoption of this draft. The definition of a YANG data model for the SR policy architecture is an important work item for this WG. Thanks, Francois From: spring on behalf of James Guichard Date: Monday 13 July 2020 at 17:38 To: "spring@ietf.org" Cc: "spring-cha...@ietf.org

Re: [spring] WG Adoption Call for draft-dong-spring-sr-for-enhanced-vpn

Hi, As a co-author, I support the adoption of this draft. Thanks, Francois From: spring on behalf of James Guichard Date: Wednesday 15 July 2020 at 13:17 To: "spring@ietf.org" Cc: "spring-cha...@ietf.org" Subject: [spring] WG Adoption Call for draft-dong-spring-sr-for-enhanced-vpn Dear WG:

Re: [spring] Dynamic Proxy in SR service programming

Hi Joel, Thank you for your email. At high-level, the dynamic proxy combines a caching mechanism with a mapping scheme that associates cache entries to packets or flows. There are many possible mapping schemes, each has pros and cons that make it more suitable in some environments and less in

Re: [spring] General Proxy behavior in SR Service Programming

Hi Joel, Thank you for your email. A proxy and its associated SF can be seen from the network as a single entity: a packet enters this entity from the network, gets processed by the SF, and exits towards the network. The packet modifications that occur between the entry and exit of this entity

Re: [spring] WG Adoption Call for draft-dong-spring-sr-for-enhanced-vpn

Hi chairs, WG, Support as a co-author. Thanks, Francois From: spring on behalf of James Guichard Date: Wednesday, 27 January 2021 at 12:47 To: spring@ietf.org Cc: spring-cha...@ietf.org Subject: [spring] WG Adoption Call for draft-dong-spring-sr-for-enhanced-vpn Dear WG: This message start

Re: [spring] Completion of WG Adoption Call for draft-dong-spring-sr-for-enhanced-vpn

Hi Jim, chairs, I am not aware of any IPR related to this document. Thanks, Francois From: spring on behalf of James Guichard Date: Thursday, 11 February 2021 at 18:06 To: James Guichard , spring@ietf.org Cc: spring-cha...@ietf.org Subject: [spring] Completion of WG Adoption Call for draf

Re: [spring] SRv6 Service Programming using TLV

Hi Luc-Fabrice, This demo is an illustration of the Segment Routing Service Programming capabilities defined in draft-ietf-spring-sr-service-programming (https://datatracker.ietf.org/doc/draft-ietf-spring-sr-service-programming/). In this demo, the metadata was first carried as a SID argument,

Re: [spring] IPR Call for draft-ietf-spring-segment-routing-policy

Hi Jim, chairs, I am not aware of any undisclosed IPR related to this document. Thanks, Francois From: spring on behalf of James Guichard Date: Sunday, 11 April 2021 at 12:34 To: SPRING WG Cc: spring-cha...@ietf.org Subject: [spring] IPR Call for draft-ietf-spring-segment-routing-policy Hi

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

I support the working group adoption. The C-SID solution described in this I-D builds on the SRv6 data plane defined in RFC 8754 and 8986 to provide a flexible, SRv6-native compression solution. It has been implemented by several vendors, with interoperability testing reported in section 11. F

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

Hi Greg, A node that supports this draft in its entirety can instantiate SRv6 SIDs (e.g., End and End.X SIDs) with any of the three C-SID flavors. In particular, a node can instantiate multiple SRv6 SIDs bound to different C-SID flavors, possibly with different C-SID lengths. It can also instan

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

. Thanks, Francois From: Greg Mirsky Date: Wednesday, 6 October 2021 at 19:19 To: Francois Clad (fclad) Cc: Robert Raszuk , Ron Bonica , James Guichard , SPRING WG , spring-cha...@ietf.org Subject: Re: [spring] WG Adoption call for https://datatracker.ietf.org/doc/draft-filsfilscheng

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

Hi Greg, Thank you for the confirmation. I am glad that the matter of combining C-SIDs of different flavors is clear now. Thanks, Francois From: Greg Mirsky Date: Thursday, 7 October 2021 at 20:15 To: Francois Clad (fclad) Cc: Robert Raszuk , Ron Bonica , James Guichard , SPRING WG

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

Hi Tarek, I am assuming that the border node is an SR segment endpoint node in your question. This node processes the packet according to the behavior bound to the locally instantiated SID that was matched (see Section 4.3 of RFC 8754). There is no interpretation required. It is the responsib

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

Hi Gyan, It is possible to combine SIDs of different C-SID flavors and C-SID lengths in the same SRH, along with those defined in RFC 8986 After all, they leverage the same SRv6 data plane. Let me give you an example. Assume that an SR source node wants to send a packet onto an SR path through

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

and makes it difficult for me to understand your questions. Thanks, Francois From: Gyan Mishra Date: Sunday, 10 October 2021 at 22:23 To: Chengli (Cheng Li) , Francois Clad (fclad) Cc: James Guichard , SPRING WG , Yisong Liu , spring-chairs Subject: Re: [spring] RE： WG Adoption call for

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

endpoint node identifies a SID. Could you provide an example showing the kind of inference or collision you are referring to? Thanks, Francois From: Tarek Saad Date: Sunday, 10 October 2021 at 06:06 To: Francois Clad (fclad) , James Guichard , SPRING WG Cc: spring-cha...@ietf.org Subject: Re

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

carry a C-SID bound to any behavior, including one with another C-SID flavor. Thanks, Francois From: Greg Mirsky Date: Friday, 8 October 2021 at 22:21 To: Francois Clad (fclad) Cc: Robert Raszuk , Ron Bonica , James Guichard , SPRING WG , spring-cha...@ietf.org Subject: Re: [spring] WG

[spring] FW: New Version Notification for draft-clad-spring-segment-routing-service-chaining-00.txt

has been successfully submitted by Francois Clad and posted to the IETF repository. Name: draft-clad-spring-segment-routing-service-chaining Revision: 00 Title: Segment Routing for Service Chaining Document date: 2017-10-06

Re: [spring] New Version Notification for draft-clad-spring-segment-routing-service-chaining-00.txt

stack on a per-packet basis so that you reapply the correct outgoing SR stack? Thanks, Jim -Original Message- From: spring [mailto:spring-boun...@ietf.org] On Behalf Of Francois Clad (fclad) Sent: Wednesday, October 18, 2017 10:47 AM To: spring@ietf.org<mailto:spring@ietf.org

Re: [spring] [mpls] The MPLS WG has placed draft-farrel-mpls-sfc in state "Call For Adoption By WG Issued"

Hi Xiaohu, all, I agree with the point raised by Xiaohu. The draft-farrel-mpls-sfc is copying ideas described in draft-xu-mpls-service-chaining. Please note that the work in draft-xu-mpls-service-chaining started one year before draft-farrel-mpls-sfc. At IETF100, three drafts in this area were

Re: [spring] [sfc] [mpls] The MPLS WG has placed draft-farrel-mpls-sfc in state "Call For Adoption By WG Issued"

n NSH only - The MPLS WG is chartered to work on MPLS - This draft asks for MPLS code points so can only be in MPLS - This draft must be reviewed in SFC and SPRING as it progresses and certainly at WG last call Adrian From: mpls [mailto:mpls-boun...@ietf.org] On Behalf Of Zafar Ali (zali) Sent: 09

Re: [spring] IPR Poll for draft-filsfils-spring-segment-routing-policy

I’m not aware of any IPR other than already disclosed at https://datatracker.ietf.org/ipr/search/?submit=draft&id=draft-filsfils-spring-segment-routing-policy Francois On 16 May 2018, at 18:15, bruno.decra...@orange.com wrote: [+ authors] I'm not aware of any

Re: [spring] IPR Poll for draft-filsfils-spring-srv6-network-programming

Hi, I am not aware of any IPR other than already disclosed. Thanks, Francois From: spring on behalf of Bruno Decraene Date: Wednesday 13 March 2019 at 19:50 To: SPRING WG Cc: "draft-filsfils-spring-srv6-network-programm...@ietf.org" Subject: [spring] IPR Poll for draft-filsfils-spring-srv6

Re: [spring] IPR Poll: draft-xuclad-spring-sr-service-programming

I am not aware of any undisclosed IPR related to this draft. Thanks, Francois From: Rob Shakir Date: Thursday 27 June 2019 at 08:15 To: "draft-xuclad-spring-sr-service-programm...@ietf.org" , SPRING WG List Subject: IPR Poll: draft-xuclad-spring-sr-service-programming Resent-From: Resent-To:

Re: [spring] WG Adoption Call: draft-guichard-spring-nsh-sr

Support adoption. Thanks, Francois From: spring on behalf of Rob Shakir Date: Thursday 27 June 2019 at 08:15 To: SPRING WG List Subject: [spring] WG Adoption Call: draft-guichard-spring-nsh-sr Hi SPRING WG, This email initiates a two week working group adoption call for draft-guichard-spri

Re: [spring] hop limit decrement on SRv6 proxies

Dear Nakamura-san, Many thanks for reviewing this draft and experimenting on SRv6 service chaining. I understand that the current version of the draft is not very clear regarding IPv6 hop limit updates and will work towards improving this aspect in the next revision of the draft. In the specif

  1   2   >