[Idr] reply: WG LC on draft-ietf-idr-rpd-05.txt (7/15 to 7/29/2020)

Wangshuqiang <wangshuqiang@huawei.com> Fri, 24 July 2020 09:14 UTC

Return-Path: <wangshuqiang@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 6A4DB3A0CCC for <idr@ietfa.amsl.com>; Fri, 24 Jul 2020 02:14:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 6lofOq3a6apW for <idr@ietfa.amsl.com>; Fri, 24 Jul 2020 02:14:03 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0B233A0CCB for <idr@ietf.org>; Fri, 24 Jul 2020 02:14:02 -0700 (PDT)
Received: from lhreml709-chm.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 798D1C3045F557A2AEF6 for <idr@ietf.org>; Fri, 24 Jul 2020 10:14:00 +0100 (IST)
Received: from lhreml709-chm.china.huawei.com (10.201.108.58) by lhreml709-chm.china.huawei.com (10.201.108.58) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1913.5; Fri, 24 Jul 2020 10:14:00 +0100
Received: from DGGEMM402-HUB.china.huawei.com (10.3.20.210) by lhreml709-chm.china.huawei.com (10.201.108.58) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1913.5 via Frontend Transport; Fri, 24 Jul 2020 10:13:59 +0100
Received: from DGGEMM511-MBX.china.huawei.com ([169.254.1.172]) by DGGEMM402-HUB.china.huawei.com ([10.3.20.210]) with mapi id 14.03.0487.000; Fri, 24 Jul 2020 17:13:55 +0800
From: Wangshuqiang <wangshuqiang@huawei.com>
To: "idr@ietf.org" <idr@ietf.org>
Thread-Topic: reply: [Idr] WG LC on draft-ietf-idr-rpd-05.txt (7/15 to 7/29/2020)
Thread-Index: AdZhmr7/z8TdtUG5RKiI6RGnBcnQlA==
Date: Fri, 24 Jul 2020 09:13:54 +0000
Message-ID: <D8F36B70D8FCB7459CF866C2B8E1872671329E77@dggemm511-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.69.174.206]
Content-Type: multipart/alternative; boundary="_000_D8F36B70D8FCB7459CF866C2B8E1872671329E77dggemm511mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/EnvtkTYeSKOwkDLsGFe5lQKOOpQ>
Subject: [Idr] reply: WG LC on draft-ietf-idr-rpd-05.txt (7/15 to 7/29/2020)
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: Fri, 24 Jul 2020 09:14:04 -0000


Hi Sue,

I support the WG LC of this document.

Best regards,
Shuqiang Wang
发件人: Idr [mailto:idr-bounces@ietf.org] 代表 Susan Hares
发送时间: 2020年7月15日 21:11
收件人: idr@ietf.org<mailto:idr@ietf.org>
主题: [Idr] WG LC on draft-ietf-idr-rpd-05.txt (7/15 to 7/29/2020)

This begins a 2 week WG LC on draft-ietf-idr-rpd
from 7/15 to 7/29/2020.  You can obtain this draft at:
https://datatracker.ietf.org/doc/draft-ietf-idr-rpd/

This draft defines a new AFI/SAFI and new atoms
for the Wide Communities.  This WG LC has been delayed
as I waited for a resubmission of the Wide Communities draft.
I had hoped to do these 2 WG LC in parallel.

I’ve not received the Wide Communities draft, but we will
start this WGLC to provide feedback to the authors.
We may have to run a short follow-up to this WG LC
If there are changes to the Wide Communities draft during
Its WG LC.

There is an IPR statement on this draft.

In your responses please answer the following questions:

1) Do you feel this draft has an solution that is acceptable
   With the IPR as a WG RFC?

Answer: Yes, I think it’s acceptable.

2) Do you feel this draft is ready to publish?

Answer: Yes, I think this draft is ready.

3) Do you know of implementations of this draft?

Answer: Yes, I know at least two implementations of the draft.

4) Do you know of deployments of this draft?
If so, is this feature useful in the deploy ments.

Answer: Yes, we can use this feature to help the operators to modify the attributes of BGP routes more efficiency.

5) Do you feel that Wide Communities is ready for
Publication?

Answer: Yes,I think the Wide Communities  is ready for Publication and deployment.

Cheerily, Susan Hares