IETF Logo Mail Archive

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

Zhuangshunwan <zhuangshunwan@huawei.com> Thu, 23 July 2020 06:53 UTC

Return-Path: <zhuangshunwan@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 262733A0937 for <idr@ietfa.amsl.com>; Wed, 22 Jul 2020 23:53:34 -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 Vd6I9zt2GpLP for <idr@ietfa.amsl.com>; Wed, 22 Jul 2020 23:53:32 -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 486943A0938 for <idr@ietf.org>; Wed, 22 Jul 2020 23:53:32 -0700 (PDT)
Received: from lhreml709-chm.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 19E822D2ABF487C39AAF for <idr@ietf.org>; Thu, 23 Jul 2020 07:53:29 +0100 (IST)
Received: from nkgeml706-chm.china.huawei.com (10.98.57.153) 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; Thu, 23 Jul 2020 07:53:28 +0100
Received: from nkgeml708-chm.china.huawei.com (10.98.57.160) by nkgeml706-chm.china.huawei.com (10.98.57.153) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Thu, 23 Jul 2020 14:53:26 +0800
Received: from nkgeml708-chm.china.huawei.com ([10.98.57.160]) by nkgeml708-chm.china.huawei.com ([10.98.57.160]) with mapi id 15.01.1913.007; Thu, 23 Jul 2020 14:53:26 +0800
From: Zhuangshunwan <zhuangshunwan@huawei.com>
To: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [Idr] WG LC on draft-ietf-idr-rpd-05.txt (7/15 to 7/29/2020)
Thread-Index: AdZaqFM+IHByNV2FRBK1MLVtR2zN/AGEu3zQ
Date: Thu, 23 Jul 2020 06:53:25 +0000
Message-ID: <119b48ee3f21447d8f591896cee2af05@huawei.com>
References: <003701d65aa9$689a64d0$39cf2e70$@ndzh.com>
In-Reply-To: <003701d65aa9$689a64d0$39cf2e70$@ndzh.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.202.109]
Content-Type: multipart/alternative; boundary="_000_119b48ee3f21447d8f591896cee2af05huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/oIxt4a9ZhdXuxQJELt_NBAoSyqA>
Subject: Re: [Idr] 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: Thu, 23 Jul 2020 06:53:34 -0000

Hi Everyone,

I support the WGLC of the draft.
Reponses inline with [Shunwan].

Thanks,
Shunwan

From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Wednesday, July 15, 2020 9:11 PM
To: idr@ietf.org
Subject: [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?
[Shunwan] It is acceptable.

2) Do you feel this draft is ready to publish?
[Shunwan] It is ready.

3) Do you know of implementations of this draft?
[Shunwan] At least 2 implementations.

4) Do you know of deployments of this draft?
If so, is this feature useful in the deploy ments.
[Shunwan] At least 5 deployments as far as I know. It is very useful in the scenario where the routing policies need to be dynamically adjusted.
This solution is initially proposed in a network optimization project of OTT, ISP, and vendor.

5) Do you feel that Wide Communities is ready for
Publication?
[Shunwan] Yes, it is ready. Wide Communities is an excellent container for carrying routing policies.

Cheerily, Susan Hares

v2.23.0 | Report a Bug | By Email