Re: [bess] WG Adoption and IPR Poll for draft-mishra-bess-deployment-guide-ipv4nlri-ipv6nh-03

Hi Aijun

Responses in-line

Many Thanks for your valuable feedback!

Gyan

On Wed, Apr 14, 2021 at 11:50 PM Aijun Wang <wangaijun@tsinghua.org.cn>
wrote:

> Yes，Support its adoption.
>
> I think this draft gives the operator confidences to deploy pure IPv6
> transport network in coming days.
>
>
>
> Some comments for the drafts are below:
>
> 1.     Should the test scenarios, test items and test results be
> described in more detail in the body of this draft?
>
>      Gyan> Yes this will be moved from Appendix to section 3
interoperability testing in the next revision

> 2.     I think such guidelines can also be used within the operator’s
> network domain(PE-RR, or PE-PE), not only the emphasized PE-CE edge.
>

     Gyan> From the feedback and test use cases as the PE-CE IPv6 only
peering applies to all IPv6-only  IP / MPLS / SR core scenarios and is an
integral part of the testing.  So I will add PE-RR or PE-PE (No RR)
IPv6-only peering with SAFI stacking as well to section 3.  I will expand
the BCP to cover IPv6 only core software mesh framework RFC 5565 and
reasons why the “BGP free” P core is not recommended to be dual stacked and
should be IPv6-Only and in that section will add the control plane
IPv6-Only PE-RR peering.  From some of the feedback we will test both per
prefix VPN and Per CE next hop label allocation modes.  Also many more
permutations.

> 3.     Is it necessary for the section 4?  I think changing that content
> to describe some guidelines for how to using the RFC 8950 may be more
> beneficial?
>
>  Gyan> Agreed. I can add some pertinent verbiage that relates to the
> testing.
>
> Some Nits:
>
> 1.     Section 8  Security Considerations:
>
> “The extensions defined in this document allow BGP to propagate
> reachability information about IPv6 routes over an MPLS IPv4 core network.”
>
> Should it be:
>
> “The extensions defined in this document allow BGP to propagate
> reachability information about IPv4 routes over an IPv6 core network.”
>
>  Gyan> Typo.  Good catch!
>
> 2.     Section 6 “Operational Consideration”  said “Both IPv4 and IPv6
> peer now exists under the IPv6 address family configuration.”
>
> Should it be “Both IPv4 and IPv6 prefixes reachable information now exists
> under the IPv6 address family configuration.”
>
>  Gyan> Yes will fix. The IPv4 and IPv6 NLRI AFI/SAFI is now under the
> IPv6 address family.
>
> 3.     A.1 Router and Switch Vendors Support and Quality Assurance:
>
> GUI----》GUA
>
          Gyan> Will fix typo

>
>
>
>
>
>
> Best Regards
>
>
>
> Aijun Wang
>
> China Telecom
>
>
>
> *From:* bess-bounces@ietf.org <bess-bounces@ietf.org> *On Behalf Of *Bocci,
> Matthew (Nokia - GB)
> *Sent:* Tuesday, April 13, 2021 5:37 PM
> *To:* draft-mishra-bess-deployment-guide-ipv4nlri-ipv6nh@ietf.org;
> bess@ietf.org
> *Subject:* [bess] WG Adoption and IPR Poll for
> draft-mishra-bess-deployment-guide-ipv4nlri-ipv6nh-03
>
>
>
> 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/
>
>
>
>
> _______________________________________________
> BESS mailing list
> BESS@ietf.org
> https://www.ietf.org/mailman/listinfo/bess
>
-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *

*Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>*

*M 301 502-1347*