Gyan, Thank you very much for the explanation. If PE-CE is the only feature enabled by the draft, can you make it more clear in the introduction section? The following statement in the Abstraction doesn't quite clearly say about PE-CE using RFC8950. "This document describes the critical use case and OPEX savings of being able to leverage the MP-BGP capability exchange usage as a pure transport, allowing both IPv4 and IPv6 to be carried over the same (Border Gateway Protocol) BGP TCP session."
Thank you. Linda From: Gyan Mishra <hayabusa...@gmail.com> Sent: Tuesday, April 13, 2021 2:59 PM To: Linda Dunbar <linda.dun...@futurewei.com> Cc: Bocci, Matthew (Nokia - GB) <matthew.bo...@nokia.com>; bess@ietf.org Subject: Re: [bess] WG Adoption and IPR Poll for draft-mishra-bess-deployment-guide-ipv4nlri-ipv6nh-03 Hi Linda Responses in-line Kind Regards Gyan On Tue, Apr 13, 2021 at 3:42 PM Linda Dunbar <linda.dun...@futurewei.com<mailto:linda.dun...@futurewei.com>> wrote: I supported the WG adoption for draft-mishra-bess-deployment-guide-ipv4nlri-ipv6nh-03. However, I have some questions about the draft, hope the authors can address them: * Section 3 (Page 5) states "The goal of this document is to provide operators interoperability test result data from ..." But I can't find any section in the draft describing the "interoperability test result". Gyan> The test results are in the appendix which we plan to move it up to section 3. * RFC8950 already allows IPv4 NLRI with next hop address being IPv6, and RFC4684 allows the Next Hop address to be either IPv4 or IPv6. It is not very clear to me of the additional features enabled by this draft. Is it PE-CE? The draft did mention the value of applying RFC8950 to PE-CE, but I am not sure if it is the only feature. Can authors clarify? Gyan> Yes PE-CE is the only feature. This drafts goal is focused on PE-CE Core and Data Center or any flavor edge peering and provide vendor interoperability results using RFC 8950 next hop encoding extension to carry control plane IPv4 NLRI over an IPv6 next hop. Best regards, Linda Dunbar ---------- Forwarded message --------- From: Bocci, Matthew (Nokia - GB) <matthew.bo...@nokia.com<mailto:matthew.bo...@nokia.com>> Date: Tue, Apr 13, 2021 at 5:37 AM Subject: [bess] WG Adoption and IPR Poll for draft-mishra-bess-deployment-guide-ipv4nlri-ipv6nh-03 To: draft-mishra-bess-deployment-guide-ipv4nlri-ipv...@ietf.org<mailto:draft-mishra-bess-deployment-guide-ipv4nlri-ipv...@ietf.org> <draft-mishra-bess-deployment-guide-ipv4nlri-ipv...@ietf.org<mailto:draft-mishra-bess-deployment-guide-ipv4nlri-ipv...@ietf.org>>, bess@ietf.org<mailto:bess@ietf.org> <bess@ietf.org<mailto:bess@ietf.org>> Hello, This email begins a two-weeks WG adoption poll for draft-mishra-bess-deployment-guide-ipv4nlri-ipv6nh-03 [1]. Please review the draft and post any comments to the BESS working group list. 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, copying the BESS mailing list. The document will not progress without answers from all of the authors and contributors. Currently, there are no IPR disclosures against this document. If you are not listed as an author or a contributor, then please explicitly respond only if you are aware of any IPR that has not yet been disclosed in conformance with IETF rules. This poll for adoption closes on April 27th 2021. Regards, Matthew and Stephane [1] https://datatracker.ietf.org/doc/draft-mishra-bess-deployment-guide-ipv4nlri-ipv6nh/<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-mishra-bess-deployment-guide-ipv4nlri-ipv6nh%2F&data=04%7C01%7Clinda.dunbar%40futurewei.com%7C45d53282841b4bcb4de408d8feb68a8b%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637539407255284889%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ldtU%2Fe4da4JKOXJHbQ0FKlnonmySuHDvu7w7T5iefBg%3D&reserved=0> _______________________________________________ BESS mailing list BESS@ietf.org<mailto:BESS@ietf.org> https://www.ietf.org/mailman/listinfo/bess<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fbess&data=04%7C01%7Clinda.dunbar%40futurewei.com%7C45d53282841b4bcb4de408d8feb68a8b%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637539407255294883%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=TNrnLHITuLPy9CpIbGJhIkahJRxtBSBctUxIcCCJFnw%3D&reserved=0> -- [http://ss7.vzw.com/is/image/VerizonWireless/vz-logo-email]<https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.verizon.com%2F&data=04%7C01%7Clinda.dunbar%40futurewei.com%7C45d53282841b4bcb4de408d8feb68a8b%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637539407255304883%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=hL5vkXtg1W0WPbBPF4NdeNiVeVbnGddfhCwYSfcejKg%3D&reserved=0> Gyan Mishra Network Solutions Architect Email gyan.s.mis...@verizon.com<mailto:gyan.s.mis...@verizon.com> M 301 502-1347 _______________________________________________ BESS mailing list BESS@ietf.org<mailto:BESS@ietf.org> https://www.ietf.org/mailman/listinfo/bess<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fbess&data=04%7C01%7Clinda.dunbar%40futurewei.com%7C45d53282841b4bcb4de408d8feb68a8b%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637539407255304883%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=qyW7LlCC59Vlv%2Fplpe5xC9%2FXoYTgm6sRP6yUk7KeGmc%3D&reserved=0> -- [http://ss7.vzw.com/is/image/VerizonWireless/vz-logo-email]<https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.verizon.com%2F&data=04%7C01%7Clinda.dunbar%40futurewei.com%7C45d53282841b4bcb4de408d8feb68a8b%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637539407255314875%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=lO%2Byi4rovhNTcvXRhIL%2B5Q5GMuWkr4gPv8TcZuGr5Jk%3D&reserved=0> Gyan Mishra Network Solutions Architect Email gyan.s.mis...@verizon.com<mailto:gyan.s.mis...@verizon.com> M 301 502-1347
_______________________________________________ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
