[Idr] 回复: Re: Working Group Adoption call and IPR Call for draft-xie-idr-mpbgp-extension-4map6-05 (9/26 - 10/10/2023)

[Chongfeng Xie <[e-mail]>]

Hi Jingrong,
Thank you for your support and comments, see my feedback inline [CF], please. 
 
发件人： Jingrong Xie
发送时间： 2023-10-05 10:28
收件人： Susan Hares; [e-mail]
主题： Re: [Idr] Working Group Adoption call and IPR Call for draft-xie-idr-mpbgp-extension-4map6-05 (9/26 - 10/10/2023)
Hi Sue and WG:
 
I support the adoption. 
 
My comments to the questions Sue raised:
1) does the 4map6 attribute help  Operators connect islands of IPv4-only support through IPv6 only core. 
--Yes.
 
2) Does this draft provide technical guidance on how this attribute is formatted and used in BGP? 
--Yes.
 
3) Do you think this is the right direction for To solve this problem? 
--Yes.
 
My Additional comments to the document: 
1. To align with draft-ietf-v6ops-framework-md-ipv6only-underlay , “MD database” should be “Mapping rule Database” in my understanding.
[CF]: Sure, we will the terms to be consistent between the two documents. 
 
2. SAFI/AFI=2/1 should not be the only example in section 3.1. 
As stated in abstract: It defines a new BGP path attribute known as the "4map6" to be used in conjunction with the existing AFI/SAFI for IPv4 and IPv6.
My understanding is that, Section 3.1 is describing some “existing AFI/SAFI for IPv4 and IPv6” as following: 
IPv4-Unicast(SAFI/AFI=1/1) and VPNv4(SAFI/AFI=128/1) may be proper and preferred examples to be the “existing AFI/SAFI for IPv4”.
IPv6-Unicast(SAFI/AFI=1/2) and VPNv6(SAFI/AFI=128/2) may be additional examples to be the “existing AFI/SAFI for IPv6”.

[CF]:  Currently, the  "4map6" attribute is used in conjunction with the existing (AFI/SAFI=1/2) for IPv4 service delivery in IPv6-only underlay. I hope this can be further discussed in the coming future. 

Thanks,
Jingrong


Best regards
Chongfeng
 
本邮件及其附件可能含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
This e-mail and its attachments may contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!
 
From: Idr [mailto:[e-mail]] On Behalf Of Susan Hares
Sent: Wednesday, September 27, 2023 8:31 AM
To: [e-mail]
Subject: [Idr] Working Group Adoption call and IPR Call for draft-xie-idr-mpbgp-extension-4map6-05 (9/26 - 10/10/2023)
 
This begins a 2 week WG adoption call from 9/26/2023 to 10/10/2023 for 
draft-xie-idr-mpbgp-extension-4map6-05.txt
(https://datatracker.ietf.org/doc/draft-xie-idr-mpbgp-extension-4map6/).
 
The authors should respond to this email indicating whether they know of 
any IPR relating to this draft? 
 
In your comments, please provide the following information
“Support” or “no support”. 
 
Please consider these questions: 
1) does the 4map6 attribute help 
Operators connect islands of IPv4-only support through 
IPv6 only core. 
 
2) Does this draft provide technical guidance 
on how this attribute is formatted and used in BGP? 
 
3) Do you think this is the right direction for 
To solve this problem? 
 
Sue Hares