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

Francois, Xiaohu, I fully agree with you. s. > On Mar 8, 2018, at 11:20 AM, Francois Clad (fclad) wrote: > > 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

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

[spring] Fwd: [PANRG] PAN(P)RG Agenda for IETF101

FYI… There is a presentation on Segment Routing in the agenda. Alvaro. On March 8, 2018 at 10:13:48 AM, Brian Trammell (IETF) (i...@trammell.ch) wrote: Greetings, all, I've posted a draft meeting agenda for PAN(P)RG at IETF 101 at

Re: [spring] Fwd: New Version Notification for draft-ietf-spring-segment-routing-mpls-12.txt

As you mentioned draft-ietf-spring-conflict-resolution has already expired. draft-ietf-spring-segment-routing-mpls covers local label collision only that is totally independent of any routing protocols and is a lot simpler. Ahmed On 3/8/2018 9:28 AM, Rob Shakir wrote: Hi Ahmed, Thanks for

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

I second the concerns raised by Xiaohu, Francois, and Zafar. From: mpls on behalf of "Zafar Ali (zali)" Date: Thursday, March 8, 2018 at 7:02 PM To: "Francois Clad (fclad)" , "徐小虎(义先)" Cc: mpls

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

Dear MPLS WG Chairs and the authors of draft-farrel-mpls-sfc, I would like to draw your attention to the serious issue raised by Xiaohu and Francois. Summary: Please note that this working group adaption against the IETF process and its spirit. Please recall the adaption call. Details: Just