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

Ou Liang <ouliang@chinatelecom.cn> Fri, 24 July 2020 12:56 UTC

Return-Path: <ouliang@chinatelecom.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 80B653A0A06 for <idr@ietfa.amsl.com>; Fri, 24 Jul 2020 05:56:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=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 hWzRmhPCAjPC for <idr@ietfa.amsl.com>; Fri, 24 Jul 2020 05:56:03 -0700 (PDT)
Received: from chinatelecom.cn (prt-mail.chinatelecom.cn [42.123.76.220]) by ietfa.amsl.com (Postfix) with ESMTP id 5CFFC3A0A02 for <idr@ietf.org>; Fri, 24 Jul 2020 05:56:01 -0700 (PDT)
HMM_SOURCE_IP: 172.18.0.48:15591.761262508
HMM_ATTACHE_NUM: 0000
HMM_SOURCE_TYPE: SMTP
Received: from clientip-14.18.146.162?logid-97a46647656e4140a24aee0c51259579 (unknown [172.18.0.48]) by chinatelecom.cn (HERMES) with SMTP id CEF1028010F; Fri, 24 Jul 2020 20:55:47 +0800 (CST)
X-189-SAVE-TO-SEND: 44089258@chinatelecom.cn
Received: from ([172.18.0.48]) by App0024 with ESMTP id 97a46647656e4140a24aee0c51259579 for idr@ietf.org; Fri Jul 24 20:55:48 2020
X-Transaction-ID: 97a46647656e4140a24aee0c51259579
X-filter-score: filter<0>
X-Real-From: ouliang@chinatelecom.cn
X-Receive-IP: 172.18.0.48
X-MEDUSA-Status: 0
Sender: ouliang@chinatelecom.cn
From: "Ou Liang" <ouliang@chinatelecom.cn>
To: "'Susan Hares'" <shares@ndzh.com>, <idr@ietf.org>
References: <003701d65aa9$689a64d0$39cf2e70$@ndzh.com>
In-Reply-To: <003701d65aa9$689a64d0$39cf2e70$@ndzh.com>
Date: Fri, 24 Jul 2020 20:55:51 +0800
Message-ID: <000001d661b9$c54250f0$4fc6f2d0$@chinatelecom.cn>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01D661FC.D3687720"
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AdZaqFM+IHByNV2FRBK1MLVtR2zN/AHENV+w
Content-Language: zh-cn
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/QF4fHO1Sujh0RDkxEC9otCCqKqM>
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 12:56:06 -0000

Hi Everyone,

 

    I support the WGLC of the draft.

 

Best Regards,

Liang Ou as a co-author

 

发件人: 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