Re: [Idr] IPR call for draft-ietf-idr-rpd-11.txt (7/23 to 8/6/2021)

Aijun Wang <wangaijun@tsinghua.org.cn> Thu, 29 July 2021 05:49 UTC

Return-Path: <wangaijun@tsinghua.org.cn>
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 499323A102F for <idr@ietfa.amsl.com>; Wed, 28 Jul 2021 22:49:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.798
X-Spam-Level:
X-Spam-Status: No, score=-1.798 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vLuwBDg2RCTN for <idr@ietfa.amsl.com>; Wed, 28 Jul 2021 22:49:06 -0700 (PDT)
Received: from mail-m17638.qiye.163.com (mail-m17638.qiye.163.com [59.111.176.38]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E0D393A102D for <idr@ietf.org>; Wed, 28 Jul 2021 22:49:03 -0700 (PDT)
Received: from DESKTOP2IOH5QC (unknown [219.142.69.75]) by mail-m17638.qiye.163.com (Hmail) with ESMTPA id BF4651C00B8; Thu, 29 Jul 2021 13:48:55 +0800 (CST)
From: "Aijun Wang" <wangaijun@tsinghua.org.cn>
To: "'Huaimo Chen'" <huaimo.chen@futurewei.com>, "'Susan Hares'" <shares@ndzh.com>, <idr@ietf.org>
References: <025001d77fe7$64d93b50$2e8bb1f0$@ndzh.com>, <017401d78391$78d3ec10$6a7bc430$@tsinghua.org.cn> <BY3PR13MB5044FAF807DA15A89736CBF3F2EB9@BY3PR13MB5044.namprd13.prod.outlook.com>
In-Reply-To: <BY3PR13MB5044FAF807DA15A89736CBF3F2EB9@BY3PR13MB5044.namprd13.prod.outlook.com>
Date: Thu, 29 Jul 2021 13:48:54 +0800
Message-ID: <00c301d7843d$6af9db70$40ed9250$@tsinghua.org.cn>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00C4_01D78480.79222480"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQGJLEXQH1D7DSrOUIvxKzyLBPQTjgGso5A2AfxLRRCr2Nmq0A==
Content-Language: zh-cn
X-HM-Spam-Status: e1kfGhgUHx5ZQUtXWQgPGg8OCBgUHx5ZQUlOS1dZCBgUCR5ZQVlLVUtZV1 kWDxoPAgseWUFZKDYvK1lXWShZQUpMS0tKN1dZLVlBSVdZDwkaFQgSH1lBWUIaTUpWTB0dGhkZQ0 xMHRpNVRMBExYaEhckFA4PWVdZFhoPEhUdFFlBWU9LSFVKSktISkxVS1kG
X-HM-Sender-Digest: e1kMHhlZQR0aFwgeV1kSHx4VD1lBWUc6MTo6OBw5Qz9RKTlWEw0uEzUR HAkwCQtVSlVKTUlMTkhMTEhNT0lMVTMWGhIXVQwaFRwaEhEOFTsPCBIVHBMOGlUUCRxVGBVFWVdZ EgtZQVlJSkJVSk9JVU1CVUxOWVdZCAFZQU9JTUpKNwY+
X-HM-Tid: 0a7af0cf00d2d993kuwsbf4651c00b8
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/MA3knfHeU2gzo80k-RsLNH_BApA>
Subject: Re: [Idr] IPR call for draft-ietf-idr-rpd-11.txt (7/23 to 8/6/2021)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
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, 29 Jul 2021 05:49:11 -0000

OK, I support its publication.  

The answer to the questions from the Chairs are the followings:

 

Please consider in your review of this draft: 

1)      if this draft is ready for deployment

[WAJ] Yes.

2)      if the BGP extensions for routing policy distribution Help
deployments of BGP in the Internet. 

[WAJ] I think rpd can help the deployment of routing policy via BGP
protocol.

 

 

Best Regards

 

Aijun Wang

China Telecom

 

From: Huaimo Chen <huaimo.chen@futurewei.com> 
Sent: Thursday, July 29, 2021 1:03 PM
To: Aijun Wang <wangaijun@tsinghua.org.cn>cn>; 'Susan Hares' <shares@ndzh.com>om>;
idr@ietf.org
Subject: Re: [Idr] IPR call for draft-ietf-idr-rpd-11.txt (7/23 to 8/6/2021)

 

Hi Aijun,

 

    Thank you very much for your comments. 

 

    My responses are inline below with [HC].

 

Best Regards,

Huaimo

 

  _____  

From: Idr <idr-bounces@ietf.org <mailto:idr-bounces@ietf.org> > on behalf of
Aijun Wang <wangaijun@tsinghua.org.cn <mailto:wangaijun@tsinghua.org.cn> >
Sent: Wednesday, July 28, 2021 5:18 AM
To: 'Susan Hares' <shares@ndzh.com <mailto:shares@ndzh.com> >; idr@ietf.org
<mailto:idr@ietf.org>  <idr@ietf.org <mailto:idr@ietf.org> >
Subject: Re: [Idr] IPR call for draft-ietf-idr-rpd-11.txt (7/23 to 8/6/2021)


 

Hi, All:

 

I think there are some points should be addressed before it publication:

1)     Will the draft-ietf-idr-wide-bgp-communities-05
<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatrack
er.ietf.org%2Fdoc%2Fhtml%2Fdraft-ietf-idr-wide-bgp-communities-05%23page-12&
data=04%7C01%7Chuaimo.chen%40futurewei.com%7Cb67d9b53c2244e6381a008d951a8afe
8%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637630607226848366%7CUnknown%
7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn
0%3D%7C1000&sdata=5ZpdHDve2j0dLW%2BkW90OyEwNfluQT3D7wXqXnZrHL5M%3D&reserved=
0> [Wide Community], which is one of normative reference documents for the
draft-ietf-idr-rpd-11.txt, be forwarded later? I think the [Wide Community]
document will influence the final publication of this draft.  If [Wide
Community] will not be forwarded, would it better to define its own
container for the attached attributes sub-TLV?

[HC]: Wide Community is very powerful. It will eventually

become a RFC. In addition to this document, there are other

working group documents that use Wide Community. The authors

of the Wide Community document also work on it.

2)     Should the "RouteAttr" described in
https://datatracker.ietf.org/doc/html/draft-ietf-idr-rpd#section-4.2.1
<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatrack
er.ietf.org%2Fdoc%2Fhtml%2Fdraft-ietf-idr-rpd%23section-4.2.1&data=04%7C01%7
Chuaimo.chen%40futurewei.com%7Cb67d9b53c2244e6381a008d951a8afe8%7C0fee8ff2a3
b240189c753a1d5591fedc%7C1%7C0%7C637630607226848366%7CUnknown%7CTWFpbGZsb3d8
eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sd
ata=aSFPm1btQgvbCHdsGJumAMCsL6ohrM1u9ZNU%2Fa9bLg0%3D&reserved=0>  be Sub-TLV
of Target TLV, and other associated Sub-TLV be sub-sub TLV?

[HC]: We have changed "TLV/Sub-TLV" to "Sub-TLV" and rephrased the related
text accordingly.

3)     https://datatracker.ietf.org/doc/html/draft-ietf-idr-rpd#section-9.2
<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatrack
er.ietf.org%2Fdoc%2Fhtml%2Fdraft-ietf-idr-rpd%23section-9.2&data=04%7C01%7Ch
uaimo.chen%40futurewei.com%7Cb67d9b53c2244e6381a008d951a8afe8%7C0fee8ff2a3b2
40189c753a1d5591fedc%7C1%7C0%7C637630607226858324%7CUnknown%7CTWFpbGZsb3d8ey
JWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdat
a=jtCxWAlBaUGtAwowgUTEmLLnlCLkUAIQwshtgoD9vkk%3D&reserved=0>  describes the
"Routing Policy Type" registry, is it necessary? 

In https://datatracker.ietf.org/doc/html/draft-ietf-idr-rpd#section-4.1
<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatrack
er.ietf.org%2Fdoc%2Fhtml%2Fdraft-ietf-idr-rpd%23section-4.1&data=04%7C01%7Ch
uaimo.chen%40futurewei.com%7Cb67d9b53c2244e6381a008d951a8afe8%7C0fee8ff2a3b2
40189c753a1d5591fedc%7C1%7C0%7C637630607226858324%7CUnknown%7CTWFpbGZsb3d8ey
JWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdat
a=IDMdeBVRm4koo3Bwlo3c8N2bMxk0qcc8hPh34y5KJj8%3D&reserved=0> , it describes:

"Policy Type:  1 octet indicates the type of a policy.  1 is for Export
policy. 2 is for Import policy.  If the Policy Type is any other value, the
NLRI is corrupt and the enclosing UPDATE message MUST be ignored."  

Is this the place to use the "Routing Policy Type"? If so, it is
unreasonable to use other values as required by the IANA considerations.

[HC]: You are right. There is no other policy type except

for export and import. The "Routing Policy Type" registry 

is not needed. We have removed it.

4)     https://datatracker.ietf.org/doc/html/draft-ietf-idr-rpd#section-9.5
<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatrack
er.ietf.org%2Fdoc%2Fhtml%2Fdraft-ietf-idr-rpd%23section-9.5&data=04%7C01%7Ch
uaimo.chen%40futurewei.com%7Cb67d9b53c2244e6381a008d951a8afe8%7C0fee8ff2a3b2
40189c753a1d5591fedc%7C1%7C0%7C637630607226868271%7CUnknown%7CTWFpbGZsb3d8ey
JWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdat
a=0wvPK%2BNvk7V8UsowNyKqFNAton5b9aYO5dB9rl%2FnGgo%3D&reserved=0>  is named
as "Attribute Change Sub-TLV" Registry, should it be "Parameter TLV" as
indicated in
https://datatracker.ietf.org/doc/html/draft-ietf-idr-rpd#section-4.2.2
<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatrack
er.ietf.org%2Fdoc%2Fhtml%2Fdraft-ietf-idr-rpd%23section-4.2.2&data=04%7C01%7
Chuaimo.chen%40futurewei.com%7Cb67d9b53c2244e6381a008d951a8afe8%7C0fee8ff2a3
b240189c753a1d5591fedc%7C1%7C0%7C637630607226868271%7CUnknown%7CTWFpbGZsb3d8
eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sd
ata=xqOrDBG3UWbMvzJmSKPSNnee%2Bn1pNbBJclM7kHXmazw%3D&reserved=0> 

[HC]: The "Attribute Change Sub-TLV" is within the "Parameter TLV".

 

 

Best Regards

 

Aijun Wang

China Telecom

 

 

 

 

 

From: idr-bounces@ietf.org <mailto:idr-bounces@ietf.org>
<idr-bounces@ietf.org <mailto:idr-bounces@ietf.org> > On Behalf Of Susan
Hares
Sent: Saturday, July 24, 2021 1:23 AM
To: idr@ietf.org <mailto:idr@ietf.org> 
Subject: [Idr] IPR call for draft-ietf-idr-rpd-11.txt (7/23 to 8/6/2021)

 

This begins a 2 week WG last call on draft-ietf-idr-rpd-11.txt. 

 

There is one missing IPR statement from Liang Ou. 

Liang should send the IPR statements in response to this WG LC.  

 

The implementation report is at: 

https://trac.ietf.org/trac/idr/wiki/draft-ietf-idr-rpd%20impolementations%20
<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftrac.ietf
.org%2Ftrac%2Fidr%2Fwiki%2Fdraft-ietf-idr-rpd%2520impolementations%2520&data
=04%7C01%7Chuaimo.chen%40futurewei.com%7Cb67d9b53c2244e6381a008d951a8afe8%7C
0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637630607226868271%7CUnknown%7CTW
FpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D
%7C1000&sdata=ITkstVwx5lYqsyihPPr5S13Z81Qk0tvV5ypcRSPTTNE%3D&reserved=0>   

 

The two implementations are different implementations from Huawei. 

 

This document describes BGP Extensions for Routing

   Policy Distribution (BGP RPD) to support this.

 

Please consider in your review of this draft: 

1) if this draft is ready for deployment, 

2) if the BGP extensions for routing policy distribution 

Help deployments of BGP in the Internet. 

 

Cheerily, Susan Hares