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

Jingrong Xie <xiejingrong@huawei.com> Thu, 05 October 2023 02:28 UTC

Return-Path: <xiejingrong@huawei.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C492DC14CE4A for <idr@ietfa.amsl.com>; Wed, 4 Oct 2023 19:28:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level:
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lx9WlXURdUps for <idr@ietfa.amsl.com>; Wed, 4 Oct 2023 19:28:08 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A029FC14CE46 for <idr@ietf.org>; Wed, 4 Oct 2023 19:28:07 -0700 (PDT)
Received: from lhrpeml100003.china.huawei.com (unknown [172.18.147.226]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4S1Fmc0tD9z6K64q for <idr@ietf.org>; Thu, 5 Oct 2023 10:26:24 +0800 (CST)
Received: from kwepemi500001.china.huawei.com (7.221.188.114) by lhrpeml100003.china.huawei.com (7.191.160.210) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.31; Thu, 5 Oct 2023 03:28:03 +0100
Received: from kwepemi500004.china.huawei.com (7.221.188.17) by kwepemi500001.china.huawei.com (7.221.188.114) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.31; Thu, 5 Oct 2023 10:28:02 +0800
Received: from kwepemi500004.china.huawei.com ([7.221.188.17]) by kwepemi500004.china.huawei.com ([7.221.188.17]) with mapi id 15.01.2507.031; Thu, 5 Oct 2023 10:28:02 +0800
From: Jingrong Xie <xiejingrong@huawei.com>
To: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [Idr] Working Group Adoption call and IPR Call for draft-xie-idr-mpbgp-extension-4map6-05 (9/26 - 10/10/2023)
Thread-Index: Adnw2QDx/n+lUhfiQi+z34iIENpzBgGVuYzw
Date: Thu, 05 Oct 2023 02:28:01 +0000
Message-ID: <abe10cb3976a40619343002f26d9fc0d@huawei.com>
References: <BYAPR08MB4872BA0BC06F5646742B4CD2B3C2A@BYAPR08MB4872.namprd08.prod.outlook.com>
In-Reply-To: <BYAPR08MB4872BA0BC06F5646742B4CD2B3C2A@BYAPR08MB4872.namprd08.prod.outlook.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.84.67.65]
Content-Type: multipart/alternative; boundary="_000_abe10cb3976a40619343002f26d9fc0dhuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/qaH5DcfJCHHpuUh8sxlp0M7vAhM>
Subject: Re: [Idr] Working Group Adoption call and IPR Call for draft-xie-idr-mpbgp-extension-4map6-05 (9/26 - 10/10/2023)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Oct 2023 02:28:11 -0000

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.

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”.

Thanks,
Jingrong

本邮件及其附件可能含有华为公司的保密信息,仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、或散发)本邮件中的信息。如果您错收了本邮件,请您立即电话或邮件通知发件人并删除本邮件!
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:idr-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Wednesday, September 27, 2023 8:31 AM
To: idr@ietf.org
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