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

Haoweiguo <haoweiguo@huawei.com> Fri, 24 July 2020 09:40 UTC

Return-Path: <haoweiguo@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 C60083A0DC5 for <idr@ietfa.amsl.com>; Fri, 24 Jul 2020 02:40:40 -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 nhjZ9-S4c3K2 for <idr@ietfa.amsl.com>; Fri, 24 Jul 2020 02:40:38 -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 0903B3A0E04 for <idr@ietf.org>; Fri, 24 Jul 2020 02:40:38 -0700 (PDT)
Received: from lhreml711-chm.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 1B88B67E39A74208387D for <idr@ietf.org>; Fri, 24 Jul 2020 10:40:34 +0100 (IST)
Received: from nkgeml708-chm.china.huawei.com (10.98.57.160) by lhreml711-chm.china.huawei.com (10.201.108.62) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Fri, 24 Jul 2020 10:40:33 +0100
Received: from nkgeml706-chm.china.huawei.com (10.98.57.153) by nkgeml708-chm.china.huawei.com (10.98.57.160) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Fri, 24 Jul 2020 17:40:31 +0800
Received: from nkgeml706-chm.china.huawei.com ([10.98.57.153]) by nkgeml706-chm.china.huawei.com ([10.98.57.153]) with mapi id 15.01.1913.007; Fri, 24 Jul 2020 17:40:31 +0800
From: Haoweiguo <haoweiguo@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/AG9dwMQ
Date: Fri, 24 Jul 2020 09:40:31 +0000
Message-ID: <3e7d130e62524abbbfe681d2df88fa60@huawei.com>
References: <003701d65aa9$689a64d0$39cf2e70$@ndzh.com>
In-Reply-To: <003701d65aa9$689a64d0$39cf2e70$@ndzh.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.81.160]
Content-Type: multipart/alternative; boundary="_000_3e7d130e62524abbbfe681d2df88fa60huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/FVZGZt8tJ55p7aeRQWrQNGS_wxQ>
Subject: [Idr] =?gb2312?b?tPC4tDogIFdHIExDIG9uIGRyYWZ0LWlldGYtaWRyLXJw?= =?gb2312?b?ZC0wNS50eHQgICg3LzE1IHRvIDcvMjkvMjAyMCk=?=
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:40:41 -0000

Hi,
I support the WG last call. I think the draft is in good shape and is ready for the publication.

Thanks,
Weiguo

发件人: Idr [mailto:idr-bounces@ietf.org] 代表 Susan Hares
发送时间: 2020年7月15日 21:11
收件人: 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?

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

3) Do you know of implementations of this draft?

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

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

Cheerily, Susan Hares