Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
Hello bess chairs, I support the publication for this draft as a standard track RFC. As a contributor, I am not aware of any IPRs related to the draft. Cheers, --satoru > On Dec 1, 2020, at 2:16, Bocci, Matthew (Nokia - GB) > wrote: > > This email starts a two-week working group last call for > draft-ietf-bess-srv6-services-05 [1] > > Please review the draft and send any comments to the BESS list. Also, please > indicate if you support publishing the draft as a standards track RFC. > > This poll runs until Monday 14th December 2020. > > We are also polling for knowledge of any undisclosed IPR that applies to this > Document, to ensure that IPR has been disclosed in compliance with IETF IPR > rules (see RFCs 3979, 4879, 3669 and 5378 for more details). > > If you are listed as an Author or a Contributor of this document please > respond to this email and indicate whether or not you are aware of any > relevant undisclosed IPR. The Document won't progress without answers from > all the Authors and Contributors. > There is currently one IPR disclosure. > > In addition, we are polling for knowledge of implementations of this draft, > per the BESS policy in [2]. > > Thank you, > Matthew & Stephane > > > [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ > [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
WG I believe there is consensus to publish this draft as a Standards Track RFC. There have been a number of statements expressing knowledge of implementations, in accordance with our implementation policy. There was one comment on the specification of the size of the label field, but this comment was addressed in the subsequent discussion. Please look out for my shepherd’s review. Best regards, Matthew From: Bocci, Matthew (Nokia - GB) Date: Monday, 30 November 2020 at 17:15 To: draft-ietf-bess-srv6-servi...@ietf.org , bess@ietf.org Subject: WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 This email starts a two-week working group last call for draft-ietf-bess-srv6-services-05 [1] Please review the draft and send any comments to the BESS list. Also, please indicate if you support publishing the draft as a standards track RFC. This poll runs until Monday 14th December 2020. We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as an Author or a Contributor of this document please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. The Document won't progress without answers from all the Authors and Contributors. There is currently one IPR disclosure. In addition, we are polling for knowledge of implementations of this draft, per the BESS policy in [2]. Thank you, Matthew & Stephane [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
I support publishing draft-ietf-bess-srv6-services-05 draft as a standard track RFC. This draft is already supported by several operators having deployed SRv6 networks to support real-time traffic for millions of customers. Details are in https://datatracker.ietf.org/doc/draft-matsushima-spring-srv6-deployment-status/ Many thanks to the co-authors and everyone else contributing to draft-ietf-bess-srv6-services draft. Thanks Richard From: BESS mailto:bess-boun...@ietf.org>> on behalf of "Bocci, Matthew (Nokia - GB)" mailto:matthew.bo...@nokia.com>> Date: Monday, November 30, 2020 at 12:16 PM To: "draft-ietf-bess-srv6-servi...@ietf.org<mailto:draft-ietf-bess-srv6-servi...@ietf.org>" mailto:draft-ietf-bess-srv6-servi...@ietf.org>>, "bess@ietf.org<mailto:bess@ietf.org>" mailto:bess@ietf.org>> Subject: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 This email starts a two-week working group last call for draft-ietf-bess-srv6-services-05 [1] Please review the draft and send any comments to the BESS list. Also, please indicate if you support publishing the draft as a standards track RFC. This poll runs until Monday 14th December 2020. We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as an Author or a Contributor of this document please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. The Document won't progress without answers from all the Authors and Contributors. There is currently one IPR disclosure. In addition, we are polling for knowledge of implementations of this draft, per the BESS policy in [2]. Thank you, Matthew & Stephane [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
I support publishing this draft as a standards track RFC. Dongling Duan From: "Bocci, Matthew (Nokia - GB)" Date: Monday, November 30, 2020 at 12:15 PM To: "draft-ietf-bess-srv6-servi...@ietf.org" , "bess@ietf.org" Subject: WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 Resent-From: This email starts a two-week working group last call for draft-ietf-bess-srv6-services-05 [1] Please review the draft and send any comments to the BESS list. Also, please indicate if you support publishing the draft as a standards track RFC. This poll runs until Monday 14th December 2020. We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as an Author or a Contributor of this document please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. The Document won't progress without answers from all the Authors and Contributors. There is currently one IPR disclosure. In addition, we are polling for knowledge of implementations of this draft, per the BESS policy in [2]. Thank you, Matthew & Stephane [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
Hi, all I support publishing the draft as a standards track RFC. Best regards, Pang Ran From: Bocci, Matthew (Nokia - GB)<mailto:matthew.bo...@nokia.com> Date: 2020-12-01 01:15 To: draft-ietf-bess-srv6-servi...@ietf.org<mailto:draft-ietf-bess-srv6-servi...@ietf.org>; bess@ietf.org<mailto:bess@ietf.org> Subject: WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 This email starts a two-week working group last call for draft-ietf-bess-srv6-services-05 [1] Please review the draft and send any comments to the BESS list. Also, please indicate if you support publishing the draft as a standards track RFC. This poll runs until Monday 14th December 2020. We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as an Author or a Contributor of this document please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. The Document won't progress without answers from all the Authors and Contributors. There is currently one IPR disclosure. In addition, we are polling for knowledge of implementations of this draft, per the BESS policy in [2]. Thank you, Matthew & Stephane [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw 如果您错误接收了该邮件，请通过电子邮件立即通知我们。请回复邮件到 hqs-s...@chinaunicom.cn，即可以退订此邮件。我们将立即将您的信息从我们的发送目录中删除。 If you have received this email in error please notify us immediately by e-mail. Please reply to hqs-s...@chinaunicom.cn ,you can unsubscribe from this mail. We will immediately remove your information from send catalogue of our. ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
I Support publication of this draft. Ahmed From: "Bocci, Matthew (Nokia - GB)" Date: Monday, 30 November 2020 at 18:15 To: "draft-ietf-bess-srv6-servi...@ietf.org" , "bess@ietf.org" Subject: WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 Resent from: This email starts a two-week working group last call for draft-ietf-bess-srv6-services-05 [1] Please review the draft and send any comments to the BESS list. Also, please indicate if you support publishing the draft as a standards track RFC. This poll runs until Monday 14th December 2020. We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as an Author or a Contributor of this document please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. The Document won't progress without answers from all the Authors and Contributors. There is currently one IPR disclosure. In addition, we are polling for knowledge of implementations of this draft, per the BESS policy in [2]. Thank you, Matthew & Stephane [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
Hello, I support the publication of draft-ietf-bess-srv6-services-05. We have deployed BGP based L3 service over SRv6 based on this solution, both with Cisco routers and our own implementation, as described in https://datatracker.ietf.org/doc/draft-matsushima-spring-srv6-deployment-status/ (section 2.3. Iliad). Thanks, Sébastien ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
Hello, I support publishing the draft as a standards track RFC. I'm not aware of any undisclosed IPR. Thanks, Shyam Sethuram On Mon, Nov 30, 2020 at 9:15 AM Bocci, Matthew (Nokia - GB) < matthew.bo...@nokia.com> wrote: > This email starts a two-week working group last call for > draft-ietf-bess-srv6-services-05 > [1] > > > > Please review the draft and send any comments to the BESS list. Also, > please indicate if you support publishing the draft as a standards track > RFC. > > > > This poll runs until Monday 14th December 2020. > > > > We are also polling for knowledge of any undisclosed IPR that applies to > this Document, to ensure that IPR has been disclosed in compliance with > IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). > > > > If you are listed as an Author or a Contributor of this document please > respond to this email and indicate whether or not you are aware of any > relevant undisclosed IPR. The Document won't progress without answers from > all the Authors and Contributors. > > There is currently one IPR disclosure. > > > > In addition, we are polling for knowledge of implementations of this > draft, per the BESS policy in [2]. > > > > Thank you, > > Matthew & Stephane > > > > > > [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ > > [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw > > > ___ > BESS mailing list > BESS@ietf.org > https://www.ietf.org/mailman/listinfo/bess > ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
Hi, As a contributor I support the adoption and not aware of any IPR Thanks Dan Bernier From: "Bocci, Matthew (Nokia - GB)" Date: Monday, November 30, 2020 at 12:15 PM To: "draft-ietf-bess-srv6-servi...@ietf.org" , "bess@ietf.org" Subject: WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 Resent-From: This email starts a two-week working group last call for draft-ietf-bess-srv6-services-05 [1] Please review the draft and send any comments to the BESS list. Also, please indicate if you support publishing the draft as a standards track RFC. This poll runs until Monday 14th December 2020. We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as an Author or a Contributor of this document please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. The Document won't progress without answers from all the Authors and Contributors. There is currently one IPR disclosure. In addition, we are polling for knowledge of implementations of this draft, per the BESS policy in [2]. Thank you, Matthew & Stephane [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
I've read the draft and I support publishing it as a standards track RFC. Best Regards, Zhenqiang Li li_zhenqi...@hotmail.com From: Bocci, Matthew (Nokia - GB) Date: 2020-12-01 01:15 To: draft-ietf-bess-srv6-servi...@ietf.org; bess@ietf.org Subject: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 This email starts a two-week working group last call for draft-ietf-bess-srv6-services-05 [1] Please review the draft and send any comments to the BESS list. Also, please indicate if you support publishing the draft as a standards track RFC. This poll runs until Monday 14th December 2020. We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as an Author or a Contributor of this document please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. The Document won't progress without answers from all the Authors and Contributors. There is currently one IPR disclosure. In addition, we are polling for knowledge of implementations of this draft, per the BESS policy in [2]. Thank you, Matthew & Stephane [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
Hi, I support the publication of this document as standards track RFC. As a contributor, I'm not aware of any undisclosed IPR. As reported by others, Cisco has running code in both IOS-XR and NX-OS. This has already been deployed. Additionally, there are opensource implementations in ExaBGP [1] and GoBGP [2] Thank you, Pablo. [1] https://github.com/Exa-Networks/exabgp [2] https://osrg.github.io/gobgp/ From: BESS On Behalf Of Bocci, Matthew (Nokia - GB) Sent: lunes, 30 de noviembre de 2020 18:16 To: draft-ietf-bess-srv6-servi...@ietf.org; bess@ietf.org Subject: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 This email starts a two-week working group last call for draft-ietf-bess-srv6-services-05 [1] Please review the draft and send any comments to the BESS list. Also, please indicate if you support publishing the draft as a standards track RFC. This poll runs until Monday 14th December 2020. We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as an Author or a Contributor of this document please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. The Document won't progress without answers from all the Authors and Contributors. There is currently one IPR disclosure. In addition, we are polling for knowledge of implementations of this draft, per the BESS policy in [2]. Thank you, Matthew & Stephane [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
Hi, Ketan: I prefer to “BGP based SRv6 Overlay Service”. This document defines the SRv6 service SID and its control procedures. Anyway, I know the contents, just want it more understandable. Aijun Wang China Telecom > On Dec 9, 2020, at 12:25, Ketan Talaulikar (ketant) > wrote: > > > Hi Aijun, > > Did you actually mean to say that the title should be “SRv6-based BGP Overlay > Services”? If so, I agree. > > Thanks, > Ketan > > From: BESS On Behalf Of Aijun Wang > Sent: 09 December 2020 08:43 > To: 'Bocci, Matthew (Nokia - GB)' ; > draft-ietf-bess-srv6-servi...@ietf.org; bess@ietf.org > Subject: Re: [bess] WG Last Call, IPR and Implementation Poll for > draft-ietf-bess-srv6-services-05 > > Hi, All: > > Support its publication. > > One comments for the document: > Should the name of document be changed to “BGP based SRv6 overlay services” > to reflect its actual scope? > This document discusses just the distribution of SRv6 service label > distribution via BGP. As also stated in the document, it also applies in the > plain IPv6 forwarding environment. > > > Best Regards > > Aijun Wang > China Telecom > > > From: bess-boun...@ietf.org On Behalf Of Bocci, > Matthew (Nokia - GB) > Sent: Tuesday, December 1, 2020 1:16 AM > To: draft-ietf-bess-srv6-servi...@ietf.org; bess@ietf.org > Subject: [bess] WG Last Call, IPR and Implementation Poll for > draft-ietf-bess-srv6-services-05 > > This email starts a two-week working group last call for > draft-ietf-bess-srv6-services-05 [1] > > Please review the draft and send any comments to the BESS list. Also, please > indicate if you support publishing the draft as a standards track RFC. > > This poll runs until Monday 14th December 2020. > > We are also polling for knowledge of any undisclosed IPR that applies to this > Document, to ensure that IPR has been disclosed in compliance with IETF IPR > rules (see RFCs 3979, 4879, 3669 and 5378 for more details). > > If you are listed as an Author or a Contributor of this document please > respond to this email and indicate whether or not you are aware of any > relevant undisclosed IPR. The Document won't progress without answers from > all the Authors and Contributors. > There is currently one IPR disclosure. > > In addition, we are polling for knowledge of implementations of this draft, > per the BESS policy in [2]. > > Thank you, > Matthew & Stephane > > > [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ > [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw > > ___ > BESS mailing list > BESS@ietf.org > https://www.ietf.org/mailman/listinfo/bess ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
Hi Aijun, Did you actually mean to say that the title should be "SRv6-based BGP Overlay Services"? If so, I agree. Thanks, Ketan From: BESS On Behalf Of Aijun Wang Sent: 09 December 2020 08:43 To: 'Bocci, Matthew (Nokia - GB)' ; draft-ietf-bess-srv6-servi...@ietf.org; bess@ietf.org Subject: Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 Hi, All: Support its publication. One comments for the document: Should the name of document be changed to "BGP based SRv6 overlay services" to reflect its actual scope? This document discusses just the distribution of SRv6 service label distribution via BGP. As also stated in the document, it also applies in the plain IPv6 forwarding environment. Best Regards Aijun Wang China Telecom From: bess-boun...@ietf.org<mailto:bess-boun...@ietf.org> mailto:bess-boun...@ietf.org>> On Behalf Of Bocci, Matthew (Nokia - GB) Sent: Tuesday, December 1, 2020 1:16 AM To: draft-ietf-bess-srv6-servi...@ietf.org<mailto:draft-ietf-bess-srv6-servi...@ietf.org>; bess@ietf.org<mailto:bess@ietf.org> Subject: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 This email starts a two-week working group last call for draft-ietf-bess-srv6-services-05 [1] Please review the draft and send any comments to the BESS list. Also, please indicate if you support publishing the draft as a standards track RFC. This poll runs until Monday 14th December 2020. We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as an Author or a Contributor of this document please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. The Document won't progress without answers from all the Authors and Contributors. There is currently one IPR disclosure. In addition, we are polling for knowledge of implementations of this draft, per the BESS policy in [2]. Thank you, Matthew & Stephane [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
I support publication of this document. This is an important very well written document, and is one of the only Spring documents that describes SRv6-BE w/o SRH and SRv6-TE w/ SRH -SR-TE policy - BGP Prefix SID overlay service route for L2 VPN, L3 VPN label encoded into func/arg. Thanks Gyan On Tue, Dec 8, 2020 at 10:13 PM Aijun Wang wrote: > Hi, All: > > > > Support its publication. > > > > One comments for the document: > > Should the name of document be changed to “BGP based SRv6 overlay services > ” to reflect its actual scope? > > This document discusses just the distribution of SRv6 service label > distribution via BGP. As also stated in the document, it also applies in > the plain IPv6 forwarding environment. > > > > > > Best Regards > > > > Aijun Wang > > China Telecom > > > > > > *From:* bess-boun...@ietf.org *On Behalf Of *Bocci, > Matthew (Nokia - GB) > *Sent:* Tuesday, December 1, 2020 1:16 AM > *To:* draft-ietf-bess-srv6-servi...@ietf.org; bess@ietf.org > *Subject:* [bess] WG Last Call, IPR and Implementation Poll for > draft-ietf-bess-srv6-services-05 > > > > This email starts a two-week working group last call for > draft-ietf-bess-srv6-services-05 > [1] > > > > Please review the draft and send any comments to the BESS list. Also, > please indicate if you support publishing the draft as a standards track > RFC. > > > > This poll runs until Monday 14th December 2020. > > > > We are also polling for knowledge of any undisclosed IPR that applies to > this Document, to ensure that IPR has been disclosed in compliance with > IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). > > > > If you are listed as an Author or a Contributor of this document please > respond to this email and indicate whether or not you are aware of any > relevant undisclosed IPR. The Document won't progress without answers from > all the Authors and Contributors. > > There is currently one IPR disclosure. > > > > In addition, we are polling for knowledge of implementations of this > draft, per the BESS policy in [2]. > > > > Thank you, > > Matthew & Stephane > > > > > > [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ > > [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw > > > ___ > BESS mailing list > BESS@ietf.org > https://www.ietf.org/mailman/listinfo/bess > -- <http://www.verizon.com/> *Gyan Mishra* *Network Solutions A**rchitect * *M 301 502-134713101 Columbia Pike *Silver Spring, MD ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
Hi, All: Support its publication. One comments for the document: Should the name of document be changed to "BGP based SRv6 overlay services" to reflect its actual scope? This document discusses just the distribution of SRv6 service label distribution via BGP. As also stated in the document, it also applies in the plain IPv6 forwarding environment. Best Regards Aijun Wang China Telecom From: bess-boun...@ietf.org On Behalf Of Bocci, Matthew (Nokia - GB) Sent: Tuesday, December 1, 2020 1:16 AM To: draft-ietf-bess-srv6-servi...@ietf.org; bess@ietf.org Subject: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 This email starts a two-week working group last call for draft-ietf-bess-srv6-services-05 [1] Please review the draft and send any comments to the BESS list. Also, please indicate if you support publishing the draft as a standards track RFC. This poll runs until Monday 14th December 2020. We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as an Author or a Contributor of this document please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. The Document won't progress without answers from all the Authors and Contributors. There is currently one IPR disclosure. In addition, we are polling for knowledge of implementations of this draft, per the BESS policy in [2]. Thank you, Matthew & Stephane [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
I support publishing the draft as a standards track RFC.Weiqiang Cheng ---原始邮件--- From: Bocci, Matthew (Nokia - GB) Sent: Monday, November 30, 2020 12:15 PMTo: draft-ietf-bess-srv6-servi...@ietf.org bess@ietf.org Subject: WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 This email starts a two-week working group last call for draft-ietf-bess-srv6-services-05 [1] Please review the draft and send any comments to the BESS list. Also, please indicate if you support publishing the draft as a standards track RFC. This poll runs until Monday 14th December 2020. We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as an Author or a Contributor of this document please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. The Document won't progress without answers from all the Authors and Contributors. There is currently one IPR disclosure. In addition, we are polling for knowledge of implementations of this draft, per the BESS policy in [2]. Thank you,Matthew & Stephane [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/[2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
Support publication of this draft. I am not aware of any undisclosed IPR. -Ali From: BESS on behalf of "Bocci, Matthew (Nokia - GB)" Date: Monday, November 30, 2020 at 12:15 To: "draft-ietf-bess-srv6-servi...@ietf.org" , "bess@ietf.org" Subject: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 This email starts a two-week working group last call for draft-ietf-bess-srv6-services-05 [1] Please review the draft and send any comments to the BESS list. Also, please indicate if you support publishing the draft as a standards track RFC. This poll runs until Monday 14th December 2020. We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as an Author or a Contributor of this document please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. The Document won't progress without answers from all the Authors and Contributors. There is currently one IPR disclosure. In addition, we are polling for knowledge of implementations of this draft, per the BESS policy in [2]. Thank you, Matthew & Stephane [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
I support the publication of this draft as standards track RFC. Thanks, Kausik From: BESS On Behalf Of Bocci, Matthew (Nokia - GB) Sent: Monday, November 30, 2020 9:16 AM To: draft-ietf-bess-srv6-servi...@ietf.org; bess@ietf.org Subject: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 This email starts a two-week working group last call for draft-ietf-bess-srv6-services-05 [1] Please review the draft and send any comments to the BESS list. Also, please indicate if you support publi External (matthew.bo...@nokia.com<mailto:matthew.bo...@nokia.com>) Report This Email<https://shared.outlook.inky.com/report?id=Y29tbXNjb3BlL2thdXNpay5tYWp1bWRhckBjb21tc2NvcGUuY29tLzNjYzQ5YTZjMGFjZTQyNDlkOGRkYWUyZDgzZmExNmFmLzE2MDY3NTY1NjAuODU=#key=6e8bfbb38ea13db40bd03a5ed7856cf6> FAQ<https://www.inky.com/banner-faq/> Protection by INKY<https://www.inky.com> This email starts a two-week working group last call for draft-ietf-bess-srv6-services-05 [1] Please review the draft and send any comments to the BESS list. Also, please indicate if you support publishing the draft as a standards track RFC. This poll runs until Monday 14th December 2020. We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as an Author or a Contributor of this document please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. The Document won't progress without answers from all the Authors and Contributors. There is currently one IPR disclosure. In addition, we are polling for knowledge of implementations of this draft, per the BESS policy in [2]. Thank you, Matthew & Stephane [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/<https://secure-web.cisco.com/14SrBCDjZct5qVf_DNhjUKYVODVqC1G0zOx9od-H6wbAWsHFnVmr_QR60mWsG30sOjx1KubnSFMEOaMjElhitecfV3ZG2Ws1Mv3E_FSiVnrjjeyW1AHA3eFLRv6r5SGqBAB2FaW4tCiTBVkpbnSd-EULsJwYGBdGwUZ2WpLq0GiKTbgRDZie9Ioi8VigydRyRHw9vGjUk06-0CpGUts1KTm06oDxLhpN9h4K8J-TYTI-GCYF6kD-QlDLNJtCGnowvygo7GtRDqg9ATkd8BmcDb4ewkSfxxqLSPa0Ebaa5aOIEO5hiFoz6HSC34lu22yW3/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-bess-srv6-services%2F> [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw<https://secure-web.cisco.com/13Vx0yVM0TwfJP5JObdmoqAxKlFesGSbndT5vWuUoMNY5wMAiLN5yH1YVmdqCobmhJ1RBOsywAQKcA0Lc_BhF0ayYe_HIqT3GwwYlYsjInTdJDVz7G8IwfArxSvct1lOKzAZIyOtUZyNO4P98foavUTsgVdjJA6VtMEN9Q9Ni05nThhaa3wM-d6c0HAuHduLsiF69OYb8SJ4lmRUPD1a4ozPC3vSWsxv50LJJWExTjWZ8tvPplA_c5KYNYV4sCXOzPqqfXQ3BW0YHDfHyIEqDCiWoG_JFcoawHRTiD0Hbtluh2Nlvpz5jsrCnecDtCepd/https%3A%2F%2Fmailarchive.ietf.org%2Farch%2Fmsg%2Fbess%2FcG3X1tTqb_vPC4rg56SEdkjqDpw> ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
Support this important work. I’m not aware of any undisclosed IPR Regards, Patrice Brissette, Principal Engineer Cisco Systems http://e-vpn.io http://go2.cisco.com/evpn From: BESS on behalf of "Bocci, Matthew (Nokia - GB)" Date: Monday, November 30, 2020 at 12:15 To: "draft-ietf-bess-srv6-servi...@ietf.org" , "bess@ietf.org" Subject: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 This email starts a two-week working group last call for draft-ietf-bess-srv6-services-05 [1] Please review the draft and send any comments to the BESS list. Also, please indicate if you support publishing the draft as a standards track RFC. This poll runs until Monday 14th December 2020. We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as an Author or a Contributor of this document please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. The Document won't progress without answers from all the Authors and Contributors. There is currently one IPR disclosure. In addition, we are polling for knowledge of implementations of this draft, per the BESS policy in [2]. Thank you, Matthew & Stephane [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
Support for the publication. Linda Dunbar From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Bocci, Matthew (Nokia - GB) Sent: Tuesday, December 1, 2020 1:16 AM To: draft-ietf-bess-srv6-servi...@ietf.org<mailto:draft-ietf-bess-srv6-servi...@ietf.org>; bess@ietf.org<mailto:bess@ietf.org> Subject: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 This email starts a two-week working group last call for draft-ietf-bess-srv6-services-05 [1] Please review the draft and send any comments to the BESS list. Also, please indicate if you support publishing the draft as a standards track RFC. This poll runs until Monday 14th December 2020. We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as an Author or a Contributor of this document please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. The Document won't progress without answers from all the Authors and Contributors. There is currently one IPR disclosure. In addition, we are polling for knowledge of implementations of this draft, per the BESS policy in [2]. Thank you, Matthew & Stephane [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-bess-srv6-services%2F=04%7C01%7Clinda.dunbar%40futurewei.com%7Cd14939408a2541baa31108d898bac2d8%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637427275185677834%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000=HYo%2BHHhe8bo%2FfkBmNkQ02GDUBKgJMFasINFVc%2FdSaTs%3D=0> [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailarchive.ietf.org%2Farch%2Fmsg%2Fbess%2FcG3X1tTqb_vPC4rg56SEdkjqDpw=04%7C01%7Clinda.dunbar%40futurewei.com%7Cd14939408a2541baa31108d898bac2d8%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637427275185687832%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000=9SsqwNW00sq2hGWJ55nz6N2nGOUvmf4gYM0g8mW6I%2BE%3D=0> ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
I support publishing the draft as a standards track RFC. As a contributor, I am not aware of any relevant undisclosed IPR that applies to this document. Thanks, Darren Dukes From: Bocci, Matthew (Nokia - GB) Sent: Monday, November 30, 2020 12:15 PM To: draft-ietf-bess-srv6-servi...@ietf.org ; bess@ietf.org Subject: WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 This email starts a two-week working group last call for draft-ietf-bess-srv6-services-05 [1] Please review the draft and send any comments to the BESS list. Also, please indicate if you support publishing the draft as a standards track RFC. This poll runs until Monday 14th December 2020. We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as an Author or a Contributor of this document please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. The Document won't progress without answers from all the Authors and Contributors. There is currently one IPR disclosure. In addition, we are polling for knowledge of implementations of this draft, per the BESS policy in [2]. Thank you, Matthew & Stephane [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
Hi Matthew & Stephane, I support publishing this draft as a standards track RFC. Best regards, Jie From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Bocci, Matthew (Nokia - GB) Sent: Tuesday, December 1, 2020 1:16 AM To: draft-ietf-bess-srv6-servi...@ietf.org; bess@ietf.org Subject: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 This email starts a two-week working group last call for draft-ietf-bess-srv6-services-05 [1] Please review the draft and send any comments to the BESS list. Also, please indicate if you support publishing the draft as a standards track RFC. This poll runs until Monday 14th December 2020. We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as an Author or a Contributor of this document please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. The Document won't progress without answers from all the Authors and Contributors. There is currently one IPR disclosure. In addition, we are polling for knowledge of implementations of this draft, per the BESS policy in [2]. Thank you, Matthew & Stephane [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
Hi, all I support publishing the draft as a standards track RFC. Best Regards Zongpeng Du duzongp...@foxmail.com & duzongp...@chinamobile.com From: Bocci, Matthew (Nokia - GB) Sent: Monday, November 30, 2020 6:16 PM To: draft-ietf-bess-srv6-servi...@ietf.org; bess@ietf.org Subject: WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 This email starts a two-week working group last call for draft-ietf-bess-srv6-services-05 [1] Please review the draft and send any comments to the BESS list. Also, please indicate if you support publishing the draft as a standards track RFC. This poll runs until Monday 14th December 2020. We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as an Author or a Contributor of this document please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. The Document won't progress without answers from all the Authors and Contributors. There is currently one IPR disclosure. In addition, we are polling for knowledge of implementations of this draft, per the BESS policy in [2]. Thank you, Matthew & Stephane [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
As a contributor, I am not aware of any undisclosed IPR related to this document. From: Bocci, Matthew (Nokia - GB) mailto:matthew.bo...@nokia.com Date: Monday, November 30, 2020 at 12:15 PM To: draft-ietf-bess-srv6-servi...@ietf.org mailto:draft-ietf-bess-srv6-servi...@ietf.org , bess@ietf.org mailto:bess@ietf.org Subject: WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 Resent-From: < alias-boun...@ietf.org mailto:alias-boun...@ietf.org > This email starts a two-week working group last call for draft-ietf-bess-srv6-services-05 [1] Please review the draft and send any comments to the BESS list. Also, please indicate if you support publishing the draft as a standards track RFC. This poll runs until Monday 14th December 2020. We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as an Author or a Contributor of this document please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. The Document won't progress without answers from all the Authors and Contributors. There is currently one IPR disclosure. In addition, we are polling for knowledge of implementations of this draft, per the BESS policy in [2]. Thank you, Matthew & Stephane [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
Hi Chairs, I'm not aware of any relevant undisclosed IPR and as a contributor, I support the publication of this document as standard track RFC. Regards Bart Sensitivity: Internal Use Only From: Bocci, Matthew (Nokia - GB) Sent: Monday, November 30, 2020 6:16 PM To: draft-ietf-bess-srv6-servi...@ietf.org; bess@ietf.org Subject: WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 This email starts a two-week working group last call for draft-ietf-bess-srv6-services-05 [1] Please review the draft and send any comments to the BESS list. Also, please indicate if you support publishing the draft as a standards track RFC. This poll runs until Monday 14th December 2020. We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as an Author or a Contributor of this document please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. The Document won't progress without answers from all the Authors and Contributors. There is currently one IPR disclosure. In addition, we are polling for knowledge of implementations of this draft, per the BESS policy in [2]. Thank you, Matthew & Stephane [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw This e-mail cannot be used for other purposes than Proximus business use. See more on https://www.proximus.be/maildisclaimer ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
Support for publication Thanks. Shuanglong From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Bocci, Matthew (Nokia - GB) Sent: Tuesday, December 1, 2020 1:16 AM To: draft-ietf-bess-srv6-servi...@ietf.org<mailto:draft-ietf-bess-srv6-servi...@ietf.org>; bess@ietf.org<mailto:bess@ietf.org> Subject: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 This email starts a two-week working group last call for draft-ietf-bess-srv6-services-05 [1] Please review the draft and send any comments to the BESS list. Also, please indicate if you support publishing the draft as a standards track RFC. This poll runs until Monday 14th December 2020. We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as an Author or a Contributor of this document please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. The Document won't progress without answers from all the Authors and Contributors. There is currently one IPR disclosure. In addition, we are polling for knowledge of implementations of this draft, per the BESS policy in [2]. Thank you, Matthew & Stephane [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
Hi WG, I support this adoption, and I am not aware of any non-disclosed IPR except the one has been announced. Thanks, Cheng From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Bocci, Matthew (Nokia - GB) Sent: Tuesday, December 1, 2020 1:16 AM To: draft-ietf-bess-srv6-servi...@ietf.org; bess@ietf.org Subject: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 This email starts a two-week working group last call for draft-ietf-bess-srv6-services-05 [1] Please review the draft and send any comments to the BESS list. Also, please indicate if you support publishing the draft as a standards track RFC. This poll runs until Monday 14th December 2020. We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as an Author or a Contributor of this document please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. The Document won't progress without answers from all the Authors and Contributors. There is currently one IPR disclosure. In addition, we are polling for knowledge of implementations of this draft, per the BESS policy in [2]. Thank you, Matthew & Stephane [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
Support +1 B.R. Michael 发件人: BESS [mailto:bess-boun...@ietf.org] 代表 Wanghaibo (Rainsword) 发送时间: 2020年12月5日 9:12 收件人: Bocci, Matthew (Nokia - GB) ; draft-ietf-bess-srv6-servi...@ietf.org; bess@ietf.org 主题: Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 Hi Matthew & Stephane, Support for publication. Thanks, Haibo From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Bocci, Matthew (Nokia - GB) Sent: Tuesday, December 1, 2020 1:16 AM To: draft-ietf-bess-srv6-servi...@ietf.org<mailto:draft-ietf-bess-srv6-servi...@ietf.org>; bess@ietf.org<mailto:bess@ietf.org> Subject: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 This email starts a two-week working group last call for draft-ietf-bess-srv6-services-05 [1] Please review the draft and send any comments to the BESS list. Also, please indicate if you support publishing the draft as a standards track RFC. This poll runs until Monday 14th December 2020. We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as an Author or a Contributor of this document please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. The Document won't progress without answers from all the Authors and Contributors. There is currently one IPR disclosure. In addition, we are polling for knowledge of implementations of this draft, per the BESS policy in [2]. Thank you, Matthew & Stephane [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
Dear Chairs and the WG, I support publishing the draft as a standards track RFC; I am not aware of any undisclosed IPR (as a contributor). Multiple implementations based on this draft has been deployed in many commercial networks, as detailed in https://datatracker.ietf.org/doc/draft-matsushima-spring-srv6-deployment-status/ Thanks Regards … Zafar From: BESS on behalf of "Bocci, Matthew (Nokia - GB)" Date: Monday, November 30, 2020 at 12:16 PM To: "draft-ietf-bess-srv6-servi...@ietf.org" , "bess@ietf.org" Subject: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 This email starts a two-week working group last call for draft-ietf-bess-srv6-services-05 [1] Please review the draft and send any comments to the BESS list. Also, please indicate if you support publishing the draft as a standards track RFC. This poll runs until Monday 14th December 2020. We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as an Author or a Contributor of this document please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. The Document won't progress without answers from all the Authors and Contributors. There is currently one IPR disclosure. In addition, we are polling for knowledge of implementations of this draft, per the BESS policy in [2]. Thank you, Matthew & Stephane [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
Hi Matthew & Stephane, Support for publication. Thanks, Haibo From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Bocci, Matthew (Nokia - GB) Sent: Tuesday, December 1, 2020 1:16 AM To: draft-ietf-bess-srv6-servi...@ietf.org; bess@ietf.org Subject: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 This email starts a two-week working group last call for draft-ietf-bess-srv6-services-05 [1] Please review the draft and send any comments to the BESS list. Also, please indicate if you support publishing the draft as a standards track RFC. This poll runs until Monday 14th December 2020. We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as an Author or a Contributor of this document please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. The Document won't progress without answers from all the Authors and Contributors. There is currently one IPR disclosure. In addition, we are polling for knowledge of implementations of this draft, per the BESS policy in [2]. Thank you, Matthew & Stephane [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
Hi Rabadan & Ketan, I agree that the present description is clear. At the EANTC 2020 test, we found that the NX-OS has implement the transposition as 24bits for IPv4 VPN, and it will parse a 20bits transposition as a wrong value. If we all agree on this description, I think it's okay. Regards, Haibo From: Rabadan, Jorge (Nokia - US/Mountain View) [mailto:jorge.raba...@nokia.com] Sent: Thursday, December 3, 2020 9:50 PM To: Ketan Talaulikar (ketant) ; Wanghaibo (Rainsword) ; Bocci, Matthew (Nokia - GB) ; draft-ietf-bess-srv6-servi...@ietf.org; bess@ietf.org Subject: Re: WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 Hi Haibo, I agree with Ketan… furthermore, the spec clearly defines the structure sub-sub-TLV, where the transposition length and offset are needed; it also defines how to place those bits into the label field of the NLRI, irrespective of the transposition length being 24 or 20 or anything different. Out of interest, how can that lead to interop issues? Can you please elaborate? Thank you. Jorge From: Ketan Talaulikar (ketant) mailto:ket...@cisco.com>> Date: Thursday, December 3, 2020 at 11:25 AM To: Wanghaibo (Rainsword) mailto:rainsword.w...@huawei.com>>, Bocci, Matthew (Nokia - GB) mailto:matthew.bo...@nokia.com>>, draft-ietf-bess-srv6-servi...@ietf.org<mailto:draft-ietf-bess-srv6-servi...@ietf.org> mailto:draft-ietf-bess-srv6-servi...@ietf.org>>, bess@ietf.org<mailto:bess@ietf.org> mailto:bess@ietf.org>> Subject: RE: WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 Hi Haibo, This is not a change but a clarification to avoid exactly those kind of issues. Thanks, Ketan From: Wanghaibo (Rainsword) mailto:rainsword.w...@huawei.com>> Sent: 03 December 2020 15:39 To: Ketan Talaulikar (ketant) mailto:ket...@cisco.com>>; Bocci, Matthew (Nokia - GB) mailto:matthew.bo...@nokia.com>>; draft-ietf-bess-srv6-servi...@ietf.org<mailto:draft-ietf-bess-srv6-servi...@ietf.org>; bess@ietf.org<mailto:bess@ietf.org> Subject: RE: WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 Hi Ketan, Thanks for your reply. RFC 8277 has clearly described that the label field is only 20 bits. At the beginning, we consider it to use the 20-bits to do the transposition. But in some interconnection tests, some vendors are use the 24-bits to do the transposition. So I’m worried about that the change may cause incompatible interop. Regards， Haibo From: Ketan Talaulikar (ketant) [mailto:ket...@cisco.com] Sent: Thursday, December 3, 2020 5:01 PM To: Wanghaibo (Rainsword) mailto:rainsword.w...@huawei.com>>; Bocci, Matthew (Nokia - GB) mailto:matthew.bo...@nokia.com>>; draft-ietf-bess-srv6-servi...@ietf.org<mailto:draft-ietf-bess-srv6-servi...@ietf.org>; bess@ietf.org<mailto:bess@ietf.org> Subject: RE: WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 Hi Haibo, This clarification was explicitly added based on feedback that the authors received. This document does not change the definition of the Label Field of RFC4364 and so it has always been 20 bits. There has been this text about 24-bit in other parts of the draft since RFC7432 allows that. If you see the previous versions of this document, the encoding of the label was also previously clarified with a reference to RFC8277. Regarding the BOS bit, the clarification is provided by RFC8277. Previously, this was under-specified by RFC3107. There are implementations around that do not check/examine the BOS field and assume a single label. You can see some of this history captured in RFC8277. Thanks, Ketan From: Wanghaibo (Rainsword) mailto:rainsword.w...@huawei.com>> Sent: 03 December 2020 09:13 To: Bocci, Matthew (Nokia - GB) mailto:matthew.bo...@nokia.com>>; draft-ietf-bess-srv6-servi...@ietf.org<mailto:draft-ietf-bess-srv6-servi...@ietf.org>; bess@ietf.org<mailto:bess@ietf.org> Subject: RE: WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 Dear authors and all, I find the following changes in the new version, which may cause incompatible changes in the implemented version. [cid:image001.png@01D6CAE5.829FA370] The label field described in RFC4364: 4.3.4. How VPN-IPv4 NLRI Is Carried in BGP The labeled VPN-IPv4 NLRI itself is encoded as specified in [MPLS-BGP<https://tools.ietf.org/html/rfc4364#ref-MPLS-BGP>], where the prefix consists of an 8-byte RD followed by an IPv4 prefix. RFC 3107 describe the label field: 3. Carrying Label Mapping Information b) Label: The Label field carries one or more labels (that corresponds to the stack of labels [MPLS-ENCAPS<https://tools.ietf.org/html/rfc3107#ref-MPLS-ENCAPS>]). Each label is encoded as 3
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
Hi Matthew, Stephane, I’m not aware of any un-disclosed IPR. I support publishing this draft as a standards track RFC. I would like to report that Cisco has implemented the draft for L3VPNv4/v6, internet ipv4/v6 and EVPN services. Regards Swadesh From: BESS on behalf of "Bocci, Matthew (Nokia - GB)" Date: Monday, November 30, 2020 at 9:16 AM To: "draft-ietf-bess-srv6-servi...@ietf.org" , "bess@ietf.org" Subject: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 This email starts a two-week working group last call for draft-ietf-bess-srv6-services-05 [1] Please review the draft and send any comments to the BESS list. Also, please indicate if you support publishing the draft as a standards track RFC. This poll runs until Monday 14th December 2020. We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as an Author or a Contributor of this document please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. The Document won't progress without answers from all the Authors and Contributors. There is currently one IPR disclosure. In addition, we are polling for knowledge of implementations of this draft, per the BESS policy in [2]. Thank you, Matthew & Stephane [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
Hi, as a contributor I support the publication of this draft as standards track RFC. I am not aware of any undisclosed IPR(s). Thanks, Dirk On Mon, Nov 30, 2020 at 7:15 PM Bocci, Matthew (Nokia - GB) < matthew.bo...@nokia.com> wrote: > This email starts a two-week working group last call for > draft-ietf-bess-srv6-services-05 > [1] > > > > Please review the draft and send any comments to the BESS list. Also, > please indicate if you support publishing the draft as a standards track > RFC. > > > > This poll runs until Monday 14th December 2020. > > > > We are also polling for knowledge of any undisclosed IPR that applies to > this Document, to ensure that IPR has been disclosed in compliance with > IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). > > > > If you are listed as an Author or a Contributor of this document please > respond to this email and indicate whether or not you are aware of any > relevant undisclosed IPR. The Document won't progress without answers from > all the Authors and Contributors. > > There is currently one IPR disclosure. > > > > In addition, we are polling for knowledge of implementations of this > draft, per the BESS policy in [2]. > > > > Thank you, > > Matthew & Stephane > > > > > > [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ > > [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw > > > ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
Hi, I’m not aware of any relevant IPR and as a contributor, I support the publication of this document as standard track RFC. Thanks dan From: "Bocci, Matthew (Nokia - GB)" Date: Monday, November 30, 2020 at 12:15 PM To: "draft-ietf-bess-srv6-servi...@ietf.org" , "bess@ietf.org" Subject: WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 Resent-From: This email starts a two-week working group last call for draft-ietf-bess-srv6-services-05 [1] Please review the draft and send any comments to the BESS list. Also, please indicate if you support publishing the draft as a standards track RFC. This poll runs until Monday 14th December 2020. We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as an Author or a Contributor of this document please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. The Document won't progress without answers from all the Authors and Contributors. There is currently one IPR disclosure. In addition, we are polling for knowledge of implementations of this draft, per the BESS policy in [2]. Thank you, Matthew & Stephane [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
Hi Haibo, I agree with Ketan… furthermore, the spec clearly defines the structure sub-sub-TLV, where the transposition length and offset are needed; it also defines how to place those bits into the label field of the NLRI, irrespective of the transposition length being 24 or 20 or anything different. Out of interest, how can that lead to interop issues? Can you please elaborate? Thank you. Jorge From: Ketan Talaulikar (ketant) Date: Thursday, December 3, 2020 at 11:25 AM To: Wanghaibo (Rainsword) , Bocci, Matthew (Nokia - GB) , draft-ietf-bess-srv6-servi...@ietf.org , bess@ietf.org Subject: RE: WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 Hi Haibo, This is not a change but a clarification to avoid exactly those kind of issues. Thanks, Ketan From: Wanghaibo (Rainsword) Sent: 03 December 2020 15:39 To: Ketan Talaulikar (ketant) ; Bocci, Matthew (Nokia - GB) ; draft-ietf-bess-srv6-servi...@ietf.org; bess@ietf.org Subject: RE: WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 Hi Ketan, Thanks for your reply. RFC 8277 has clearly described that the label field is only 20 bits. At the beginning, we consider it to use the 20-bits to do the transposition. But in some interconnection tests, some vendors are use the 24-bits to do the transposition. So I’m worried about that the change may cause incompatible interop. Regards， Haibo From: Ketan Talaulikar (ketant) [mailto:ket...@cisco.com] Sent: Thursday, December 3, 2020 5:01 PM To: Wanghaibo (Rainsword) mailto:rainsword.w...@huawei.com>>; Bocci, Matthew (Nokia - GB) mailto:matthew.bo...@nokia.com>>; draft-ietf-bess-srv6-servi...@ietf.org<mailto:draft-ietf-bess-srv6-servi...@ietf.org>; bess@ietf.org<mailto:bess@ietf.org> Subject: RE: WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 Hi Haibo, This clarification was explicitly added based on feedback that the authors received. This document does not change the definition of the Label Field of RFC4364 and so it has always been 20 bits. There has been this text about 24-bit in other parts of the draft since RFC7432 allows that. If you see the previous versions of this document, the encoding of the label was also previously clarified with a reference to RFC8277. Regarding the BOS bit, the clarification is provided by RFC8277. Previously, this was under-specified by RFC3107. There are implementations around that do not check/examine the BOS field and assume a single label. You can see some of this history captured in RFC8277. Thanks, Ketan From: Wanghaibo (Rainsword) mailto:rainsword.w...@huawei.com>> Sent: 03 December 2020 09:13 To: Bocci, Matthew (Nokia - GB) mailto:matthew.bo...@nokia.com>>; draft-ietf-bess-srv6-servi...@ietf.org<mailto:draft-ietf-bess-srv6-servi...@ietf.org>; bess@ietf.org<mailto:bess@ietf.org> Subject: RE: WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 Dear authors and all, I find the following changes in the new version, which may cause incompatible changes in the implemented version. [cid:image001.png@01D6C983.919D1D20] The label field described in RFC4364: 4.3.4. How VPN-IPv4 NLRI Is Carried in BGP The labeled VPN-IPv4 NLRI itself is encoded as specified in [MPLS-BGP<https://tools.ietf.org/html/rfc4364#ref-MPLS-BGP>], where the prefix consists of an 8-byte RD followed by an IPv4 prefix. RFC 3107 describe the label field: 3. Carrying Label Mapping Information b) Label: The Label field carries one or more labels (that corresponds to the stack of labels [MPLS-ENCAPS<https://tools.ietf.org/html/rfc3107#ref-MPLS-ENCAPS>]). Each label is encoded as 3 octets, where the high-order 20 bits contain the label value, and the low order bit contains "Bottom of Stack" (as defined in [MPLS-ENCAPS<https://tools.ietf.org/html/rfc3107#ref-MPLS-ENCAPS>]). According to the definition, the label field in RFC 4364 should be 3 bytes, but only 20 bits are used as the label value. So we may also use the entire 3 octets. On the other hand, if only 20 bits are used, do we need to add the BoS flag to the part when do the transposition? Best Regards, Haibo From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Bocci, Matthew (Nokia - GB) Sent: Tuesday, December 1, 2020 1:16 AM To: draft-ietf-bess-srv6-servi...@ietf.org<mailto:draft-ietf-bess-srv6-servi...@ietf.org>; bess@ietf.org<mailto:bess@ietf.org> Subject: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 This email starts a two-week working group last call for draft-ietf-bess-srv6-services-05 [1] Please review the draft and send any comments to the BESS list. Also, please indicate if you support publishing the draft as a standards track RFC. This poll runs un
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
Hi Haibo, This is not a change but a clarification to avoid exactly those kind of issues. Thanks, Ketan From: Wanghaibo (Rainsword) Sent: 03 December 2020 15:39 To: Ketan Talaulikar (ketant) ; Bocci, Matthew (Nokia - GB) ; draft-ietf-bess-srv6-servi...@ietf.org; bess@ietf.org Subject: RE: WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 Hi Ketan, Thanks for your reply. RFC 8277 has clearly described that the label field is only 20 bits. At the beginning, we consider it to use the 20-bits to do the transposition. But in some interconnection tests, some vendors are use the 24-bits to do the transposition. So I’m worried about that the change may cause incompatible interop. Regards， Haibo From: Ketan Talaulikar (ketant) [mailto:ket...@cisco.com] Sent: Thursday, December 3, 2020 5:01 PM To: Wanghaibo (Rainsword) mailto:rainsword.w...@huawei.com>>; Bocci, Matthew (Nokia - GB) mailto:matthew.bo...@nokia.com>>; draft-ietf-bess-srv6-servi...@ietf.org<mailto:draft-ietf-bess-srv6-servi...@ietf.org>; bess@ietf.org<mailto:bess@ietf.org> Subject: RE: WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 Hi Haibo, This clarification was explicitly added based on feedback that the authors received. This document does not change the definition of the Label Field of RFC4364 and so it has always been 20 bits. There has been this text about 24-bit in other parts of the draft since RFC7432 allows that. If you see the previous versions of this document, the encoding of the label was also previously clarified with a reference to RFC8277. Regarding the BOS bit, the clarification is provided by RFC8277. Previously, this was under-specified by RFC3107. There are implementations around that do not check/examine the BOS field and assume a single label. You can see some of this history captured in RFC8277. Thanks, Ketan From: Wanghaibo (Rainsword) mailto:rainsword.w...@huawei.com>> Sent: 03 December 2020 09:13 To: Bocci, Matthew (Nokia - GB) mailto:matthew.bo...@nokia.com>>; draft-ietf-bess-srv6-servi...@ietf.org<mailto:draft-ietf-bess-srv6-servi...@ietf.org>; bess@ietf.org<mailto:bess@ietf.org> Subject: RE: WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 Dear authors and all, I find the following changes in the new version, which may cause incompatible changes in the implemented version. [cid:image001.png@01D6C98C.A575E620] The label field described in RFC4364: 4.3.4. How VPN-IPv4 NLRI Is Carried in BGP The labeled VPN-IPv4 NLRI itself is encoded as specified in [MPLS-BGP<https://tools.ietf.org/html/rfc4364#ref-MPLS-BGP>], where the prefix consists of an 8-byte RD followed by an IPv4 prefix. RFC 3107 describe the label field: 3. Carrying Label Mapping Information b) Label: The Label field carries one or more labels (that corresponds to the stack of labels [MPLS-ENCAPS<https://tools.ietf.org/html/rfc3107#ref-MPLS-ENCAPS>]). Each label is encoded as 3 octets, where the high-order 20 bits contain the label value, and the low order bit contains "Bottom of Stack" (as defined in [MPLS-ENCAPS<https://tools.ietf.org/html/rfc3107#ref-MPLS-ENCAPS>]). According to the definition, the label field in RFC 4364 should be 3 bytes, but only 20 bits are used as the label value. So we may also use the entire 3 octets. On the other hand, if only 20 bits are used, do we need to add the BoS flag to the part when do the transposition? Best Regards, Haibo From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Bocci, Matthew (Nokia - GB) Sent: Tuesday, December 1, 2020 1:16 AM To: draft-ietf-bess-srv6-servi...@ietf.org<mailto:draft-ietf-bess-srv6-servi...@ietf.org>; bess@ietf.org<mailto:bess@ietf.org> Subject: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 This email starts a two-week working group last call for draft-ietf-bess-srv6-services-05 [1] Please review the draft and send any comments to the BESS list. Also, please indicate if you support publishing the draft as a standards track RFC. This poll runs until Monday 14th December 2020. We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as an Author or a Contributor of this document please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. The Document won't progress without answers from all the Authors and Contributors. There is currently one IPR disclosure. In addition, we are polling for knowledge of implementations of this draft, per the BESS policy in [2]. Thank you, Matthew &a
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
Hi Ketan, Thanks for your reply. RFC 8277 has clearly described that the label field is only 20 bits. At the beginning, we consider it to use the 20-bits to do the transposition. But in some interconnection tests, some vendors are use the 24-bits to do the transposition. So I’m worried about that the change may cause incompatible interop. Regards， Haibo From: Ketan Talaulikar (ketant) [mailto:ket...@cisco.com] Sent: Thursday, December 3, 2020 5:01 PM To: Wanghaibo (Rainsword) ; Bocci, Matthew (Nokia - GB) ; draft-ietf-bess-srv6-servi...@ietf.org; bess@ietf.org Subject: RE: WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 Hi Haibo, This clarification was explicitly added based on feedback that the authors received. This document does not change the definition of the Label Field of RFC4364 and so it has always been 20 bits. There has been this text about 24-bit in other parts of the draft since RFC7432 allows that. If you see the previous versions of this document, the encoding of the label was also previously clarified with a reference to RFC8277. Regarding the BOS bit, the clarification is provided by RFC8277. Previously, this was under-specified by RFC3107. There are implementations around that do not check/examine the BOS field and assume a single label. You can see some of this history captured in RFC8277. Thanks, Ketan From: Wanghaibo (Rainsword) mailto:rainsword.w...@huawei.com>> Sent: 03 December 2020 09:13 To: Bocci, Matthew (Nokia - GB) mailto:matthew.bo...@nokia.com>>; draft-ietf-bess-srv6-servi...@ietf.org<mailto:draft-ietf-bess-srv6-servi...@ietf.org>; bess@ietf.org<mailto:bess@ietf.org> Subject: RE: WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 Dear authors and all, I find the following changes in the new version, which may cause incompatible changes in the implemented version. [cid:image001.png@01D6C99E.5738BC00] The label field described in RFC4364: 4.3.4. How VPN-IPv4 NLRI Is Carried in BGP The labeled VPN-IPv4 NLRI itself is encoded as specified in [MPLS-BGP<https://tools.ietf.org/html/rfc4364#ref-MPLS-BGP>], where the prefix consists of an 8-byte RD followed by an IPv4 prefix. RFC 3107 describe the label field: 3. Carrying Label Mapping Information b) Label: The Label field carries one or more labels (that corresponds to the stack of labels [MPLS-ENCAPS<https://tools.ietf.org/html/rfc3107#ref-MPLS-ENCAPS>]). Each label is encoded as 3 octets, where the high-order 20 bits contain the label value, and the low order bit contains "Bottom of Stack" (as defined in [MPLS-ENCAPS<https://tools.ietf.org/html/rfc3107#ref-MPLS-ENCAPS>]). According to the definition, the label field in RFC 4364 should be 3 bytes, but only 20 bits are used as the label value. So we may also use the entire 3 octets. On the other hand, if only 20 bits are used, do we need to add the BoS flag to the part when do the transposition? Best Regards, Haibo From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Bocci, Matthew (Nokia - GB) Sent: Tuesday, December 1, 2020 1:16 AM To: draft-ietf-bess-srv6-servi...@ietf.org<mailto:draft-ietf-bess-srv6-servi...@ietf.org>; bess@ietf.org<mailto:bess@ietf.org> Subject: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 This email starts a two-week working group last call for draft-ietf-bess-srv6-services-05 [1] Please review the draft and send any comments to the BESS list. Also, please indicate if you support publishing the draft as a standards track RFC. This poll runs until Monday 14th December 2020. We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as an Author or a Contributor of this document please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. The Document won't progress without answers from all the Authors and Contributors. There is currently one IPR disclosure. In addition, we are polling for knowledge of implementations of this draft, per the BESS policy in [2]. Thank you, Matthew & Stephane [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
Hi Matthew, Stephane and WG, I support publishing this draft as a standards track RFC. I know that there are many deployment cases that have already been captured in the document: https://tools.ietf.org/id/draft-tian-spring-srv6-deployment-consideration-03.txt Regards, --Zhibo From: Bocci, Matthew (Nokia - GB) [mailto:matthew.bo...@nokia.com] Sent: Tuesday, December 1, 2020 1:16 AM To: draft-ietf-bess-srv6-servi...@ietf.org; bess@ietf.org Subject: WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 This email starts a two-week working group last call for draft-ietf-bess-srv6-services-05 [1] Please review the draft and send any comments to the BESS list. Also, please indicate if you support publishing the draft as a standards track RFC. This poll runs until Monday 14th December 2020. We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as an Author or a Contributor of this document please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. The Document won't progress without answers from all the Authors and Contributors. There is currently one IPR disclosure. In addition, we are polling for knowledge of implementations of this draft, per the BESS policy in [2]. Thank you, Matthew & Stephane [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
Support publication. I am not aware of any undisclosed IPR as co-author. Cheers, Clarence From: Bocci, Matthew (Nokia - GB) Sent: Monday, November 30, 2020 18:16 To: draft-ietf-bess-srv6-servi...@ietf.org; bess@ietf.org Subject: WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 This email starts a two-week working group last call for draft-ietf-bess-srv6-services-05 [1] Please review the draft and send any comments to the BESS list. Also, please indicate if you support publishing the draft as a standards track RFC. This poll runs until Monday 14th December 2020. We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as an Author or a Contributor of this document please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. The Document won't progress without answers from all the Authors and Contributors. There is currently one IPR disclosure. In addition, we are polling for knowledge of implementations of this draft, per the BESS policy in [2]. Thank you, Matthew & Stephane [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
Hi Haibo, This clarification was explicitly added based on feedback that the authors received. This document does not change the definition of the Label Field of RFC4364 and so it has always been 20 bits. There has been this text about 24-bit in other parts of the draft since RFC7432 allows that. If you see the previous versions of this document, the encoding of the label was also previously clarified with a reference to RFC8277. Regarding the BOS bit, the clarification is provided by RFC8277. Previously, this was under-specified by RFC3107. There are implementations around that do not check/examine the BOS field and assume a single label. You can see some of this history captured in RFC8277. Thanks, Ketan From: Wanghaibo (Rainsword) Sent: 03 December 2020 09:13 To: Bocci, Matthew (Nokia - GB) ; draft-ietf-bess-srv6-servi...@ietf.org; bess@ietf.org Subject: RE: WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 Dear authors and all, I find the following changes in the new version, which may cause incompatible changes in the implemented version. [cid:image001.png@01D6C980.4EF05B20] The label field described in RFC4364: 4.3.4. How VPN-IPv4 NLRI Is Carried in BGP The labeled VPN-IPv4 NLRI itself is encoded as specified in [MPLS-BGP<https://tools.ietf.org/html/rfc4364#ref-MPLS-BGP>], where the prefix consists of an 8-byte RD followed by an IPv4 prefix. RFC 3107 describe the label field: 3. Carrying Label Mapping Information b) Label: The Label field carries one or more labels (that corresponds to the stack of labels [MPLS-ENCAPS<https://tools.ietf.org/html/rfc3107#ref-MPLS-ENCAPS>]). Each label is encoded as 3 octets, where the high-order 20 bits contain the label value, and the low order bit contains "Bottom of Stack" (as defined in [MPLS-ENCAPS<https://tools.ietf.org/html/rfc3107#ref-MPLS-ENCAPS>]). According to the definition, the label field in RFC 4364 should be 3 bytes, but only 20 bits are used as the label value. So we may also use the entire 3 octets. On the other hand, if only 20 bits are used, do we need to add the BoS flag to the part when do the transposition? Best Regards, Haibo From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Bocci, Matthew (Nokia - GB) Sent: Tuesday, December 1, 2020 1:16 AM To: draft-ietf-bess-srv6-servi...@ietf.org<mailto:draft-ietf-bess-srv6-servi...@ietf.org>; bess@ietf.org<mailto:bess@ietf.org> Subject: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 This email starts a two-week working group last call for draft-ietf-bess-srv6-services-05 [1] Please review the draft and send any comments to the BESS list. Also, please indicate if you support publishing the draft as a standards track RFC. This poll runs until Monday 14th December 2020. We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as an Author or a Contributor of this document please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. The Document won't progress without answers from all the Authors and Contributors. There is currently one IPR disclosure. In addition, we are polling for knowledge of implementations of this draft, per the BESS policy in [2]. Thank you, Matthew & Stephane [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
Hi Matthew & Stephane, I support the publication of this draft as standards track RFC. As a co-author, I am not aware of any undisclosed IPR(s). Thank you, Robert On Mon, Nov 30, 2020 at 6:15 PM Bocci, Matthew (Nokia - GB) < matthew.bo...@nokia.com> wrote: > This email starts a two-week working group last call for > draft-ietf-bess-srv6-services-05 > [1] > > > > Please review the draft and send any comments to the BESS list. Also, > please indicate if you support publishing the draft as a standards track > RFC. > > > > This poll runs until Monday 14th December 2020. > > > > We are also polling for knowledge of any undisclosed IPR that applies to > this Document, to ensure that IPR has been disclosed in compliance with > IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). > > > > If you are listed as an Author or a Contributor of this document please > respond to this email and indicate whether or not you are aware of any > relevant undisclosed IPR. The Document won't progress without answers from > all the Authors and Contributors. > > There is currently one IPR disclosure. > > > > In addition, we are polling for knowledge of implementations of this > draft, per the BESS policy in [2]. > > > > Thank you, > > Matthew & Stephane > > > > > > [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ > > [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw > > > ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
Hi Matthew/Stephane, I support the publication of this draft as standards track RFC. As a co-author, I am not aware of any IPR other than the one that has already been disclosed on the draft. I would also like to report Cisco having implementations of this draft for L3VPN (IPv4/IPv6), Internet v4/v6 and EVPN services. Some of these implementations are already shipping and deployed in production networks. Some of these implementation and deployment details have been captured in https://datatracker.ietf.org/doc/draft-matsushima-spring-srv6-deployment-status/ Thanks, Ketan From: Bocci, Matthew (Nokia - GB) Sent: 30 November 2020 22:46 To: draft-ietf-bess-srv6-servi...@ietf.org; bess@ietf.org Subject: WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 This email starts a two-week working group last call for draft-ietf-bess-srv6-services-05 [1] Please review the draft and send any comments to the BESS list. Also, please indicate if you support publishing the draft as a standards track RFC. This poll runs until Monday 14th December 2020. We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as an Author or a Contributor of this document please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. The Document won't progress without answers from all the Authors and Contributors. There is currently one IPR disclosure. In addition, we are polling for knowledge of implementations of this draft, per the BESS policy in [2]. Thank you, Matthew & Stephane [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
Hi Chairs, I’m not aware of non-disclosed IPR. As a co-author and editor, I support publishing this draft as a standards track RFC. Gaurav LinkedIn > On Nov 30, 2020, at 9:15 AM, Bocci, Matthew (Nokia - GB) > wrote: > > > This email starts a two-week working group last call for > draft-ietf-bess-srv6-services-05 [1] > > Please review the draft and send any comments to the BESS list. Also, please > indicate if you support publishing the draft as a standards track RFC. > > This poll runs until Monday 14th December 2020. > > We are also polling for knowledge of any undisclosed IPR that applies to this > Document, to ensure that IPR has been disclosed in compliance with IETF IPR > rules (see RFCs 3979, 4879, 3669 and 5378 for more details). > > If you are listed as an Author or a Contributor of this document please > respond to this email and indicate whether or not you are aware of any > relevant undisclosed IPR. The Document won't progress without answers from > all the Authors and Contributors. > There is currently one IPR disclosure. > > In addition, we are polling for knowledge of implementations of this draft, > per the BESS policy in [2]. > > Thank you, > Matthew & Stephane > > > [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ > [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw > ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
Dear authors and all, I find the following changes in the new version, which may cause incompatible changes in the implemented version. [cid:image001.png@01D6C95C.F862B140] The label field described in RFC4364: 4.3.4. How VPN-IPv4 NLRI Is Carried in BGP The labeled VPN-IPv4 NLRI itself is encoded as specified in [MPLS-BGP<https://tools.ietf.org/html/rfc4364#ref-MPLS-BGP>], where the prefix consists of an 8-byte RD followed by an IPv4 prefix. RFC 3107 describe the label field: 3. Carrying Label Mapping Information b) Label: The Label field carries one or more labels (that corresponds to the stack of labels [MPLS-ENCAPS<https://tools.ietf.org/html/rfc3107#ref-MPLS-ENCAPS>]). Each label is encoded as 3 octets, where the high-order 20 bits contain the label value, and the low order bit contains "Bottom of Stack" (as defined in [MPLS-ENCAPS<https://tools.ietf.org/html/rfc3107#ref-MPLS-ENCAPS>]). According to the definition, the label field in RFC 4364 should be 3 bytes, but only 20 bits are used as the label value. So we may also use the entire 3 octets. On the other hand, if only 20 bits are used, do we need to add the BoS flag to the part when do the transposition? Best Regards, Haibo From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Bocci, Matthew (Nokia - GB) Sent: Tuesday, December 1, 2020 1:16 AM To: draft-ietf-bess-srv6-servi...@ietf.org; bess@ietf.org Subject: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 This email starts a two-week working group last call for draft-ietf-bess-srv6-services-05 [1] Please review the draft and send any comments to the BESS list. Also, please indicate if you support publishing the draft as a standards track RFC. This poll runs until Monday 14th December 2020. We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as an Author or a Contributor of this document please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. The Document won't progress without answers from all the Authors and Contributors. There is currently one IPR disclosure. In addition, we are polling for knowledge of implementations of this draft, per the BESS policy in [2]. Thank you, Matthew & Stephane [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
Matthew, Stephane and WG, I'm not aware of any relevant IPR. As a co-author, I support publishing this draft as a standards track RFC. I know that there are many implementations and interoperability tests that have already been listed in the document: https://tools.ietf.org/id/draft-matsushima-spring-srv6-deployment-status-09.txt Regards, --Shunwan From: Bocci, Matthew (Nokia - GB) [mailto:matthew.bo...@nokia.com] Sent: Tuesday, December 1, 2020 1:16 AM To: draft-ietf-bess-srv6-servi...@ietf.org; bess@ietf.org Subject: WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 This email starts a two-week working group last call for draft-ietf-bess-srv6-services-05 [1] Please review the draft and send any comments to the BESS list. Also, please indicate if you support publishing the draft as a standards track RFC. This poll runs until Monday 14th December 2020. We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as an Author or a Contributor of this document please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. The Document won't progress without answers from all the Authors and Contributors. There is currently one IPR disclosure. In addition, we are polling for knowledge of implementations of this draft, per the BESS policy in [2]. Thank you, Matthew & Stephane [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
Hi, Not aware of any relevant IPR. As co-author, I support the publication of this document as standards track RFC. Thank you. Jorge From: Bocci, Matthew (Nokia - GB) Date: Monday, November 30, 2020 at 6:16 PM To: draft-ietf-bess-srv6-servi...@ietf.org , bess@ietf.org Subject: WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 This email starts a two-week working group last call for draft-ietf-bess-srv6-services-05 [1] Please review the draft and send any comments to the BESS list. Also, please indicate if you support publishing the draft as a standards track RFC. This poll runs until Monday 14th December 2020. We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as an Author or a Contributor of this document please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. The Document won't progress without answers from all the Authors and Contributors. There is currently one IPR disclosure. In addition, we are polling for knowledge of implementations of this draft, per the BESS policy in [2]. Thank you, Matthew & Stephane [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
Matthew, Stephane, I'm not aware of non-disclosed IPR. As a co-author, I support publishing this draft as a standards track RFC. Regards, --Bruno From: Bocci, Matthew (Nokia - GB) [mailto:matthew.bo...@nokia.com] Sent: Monday, November 30, 2020 6:16 PM To: draft-ietf-bess-srv6-servi...@ietf.org; bess@ietf.org Subject: WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 This email starts a two-week working group last call for draft-ietf-bess-srv6-services-05 [1] Please review the draft and send any comments to the BESS list. Also, please indicate if you support publishing the draft as a standards track RFC. This poll runs until Monday 14th December 2020. We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as an Author or a Contributor of this document please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. The Document won't progress without answers from all the Authors and Contributors. There is currently one IPR disclosure. In addition, we are polling for knowledge of implementations of this draft, per the BESS policy in [2]. Thank you, Matthew & Stephane [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw _ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
I support for WG adoption. Thanks Krishnaswamy From: BESS on behalf of "Bocci, Matthew (Nokia - GB)" Date: Monday, November 30, 2020 at 9:16 AM To: "draft-ietf-bess-srv6-servi...@ietf.org" , "bess@ietf.org" Subject: [bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05 This email starts a two-week working group last call for draft-ietf-bess-srv6-services-05 [1] Please review the draft and send any comments to the BESS list. Also, please indicate if you support publishing the draft as a standards track RFC. This poll runs until Monday 14th December 2020. We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as an Author or a Contributor of this document please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. The Document won't progress without answers from all the Authors and Contributors. There is currently one IPR disclosure. In addition, we are polling for knowledge of implementations of this draft, per the BESS policy in [2]. Thank you, Matthew & Stephane [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
[bess] WG Last Call, IPR and Implementation Poll for draft-ietf-bess-srv6-services-05
This email starts a two-week working group last call for draft-ietf-bess-srv6-services-05 [1] Please review the draft and send any comments to the BESS list. Also, please indicate if you support publishing the draft as a standards track RFC. This poll runs until Monday 14th December 2020. We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as an Author or a Contributor of this document please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. The Document won't progress without answers from all the Authors and Contributors. There is currently one IPR disclosure. In addition, we are polling for knowledge of implementations of this draft, per the BESS policy in [2]. Thank you, Matthew & Stephane [1] https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
