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

zhuyq8@chinatelecom.cn Tue, 28 July 2020 08:12 UTC

Return-Path: <zhuyq8@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 07EAF3A095A for <idr@ietfa.amsl.com>; Tue, 28 Jul 2020 01:12:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.799
X-Spam-Level:
X-Spam-Status: No, score=-1.799 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, 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 FAzjz_y98kjU for <idr@ietfa.amsl.com>; Tue, 28 Jul 2020 01:12:02 -0700 (PDT)
Received: from chinatelecom.cn (prt-mail.chinatelecom.cn [42.123.76.226]) by ietfa.amsl.com (Postfix) with ESMTP id 73B473A0878 for <idr@ietf.org>; Tue, 28 Jul 2020 01:12:01 -0700 (PDT)
HMM_SOURCE_IP: 172.18.0.48:47469.684280384
HMM_ATTACHE_NUM: 0001
HMM_SOURCE_TYPE: SMTP
Received: from clientip-14.25.159.225?logid-dd7b214de9cc4941aefa8ca6f6ef4a9e (unknown [172.18.0.48]) by chinatelecom.cn (HERMES) with SMTP id 432272800FF for <idr@ietf.org>; Tue, 28 Jul 2020 16:11:30 +0800 (CST)
X-189-SAVE-TO-SEND: 44031110@chinatelecom.cn
Received: from ([172.18.0.48]) by App0024 with ESMTP id dd7b214de9cc4941aefa8ca6f6ef4a9e for idr@ietf.org; Tue Jul 28 16:11:36 2020
X-Transaction-ID: dd7b214de9cc4941aefa8ca6f6ef4a9e
X-filter-score: filter<0>
X-Real-From: zhuyq8@chinatelecom.cn
X-Receive-IP: 172.18.0.48
X-MEDUSA-Status: 0
Sender: zhuyq8@chinatelecom.cn
From: <zhuyq8@chinatelecom.cn>
To: "'idr wg'" <idr@ietf.org>
Date: Tue, 28 Jul 2020 16:11:43 +0800
Message-ID: <01e901d664b6$bf3b5350$3db1f9f0$@chinatelecom.cn>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPart_000_01EA_01D664F9.CD5FCBD0"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AdZktlM/KIsNdodkROKaDOohyp9g6g==
Content-Language: zh-cn
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/vOBP4xi6ZanFKkPijRY2Npt7f00>
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: Tue, 28 Jul 2020 08:12:11 -0000

Hi,

I support the WGLC of  this draft.

BR.

Zhu Yongqing

  _____  

From: Idr <idr-bounces@ietf.org <mailto:idr-bounces@ietf.org> > on behalf of
Susan Hares <shares@ndzh.com <mailto:shares@ndzh.com> >
Sent: Wednesday, July 15, 2020 9:11 AM
To: idr@ietf.org <mailto:idr@ietf.org>  <idr@ietf.org <mailto: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/
<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatrack
er.ietf.org%2Fdoc%2Fdraft-ietf-idr-rpd%2F&data=02%7C01%7Chuaimo.chen%40futur
ewei.com%7Cdb72a70170244f5c73a208d828c0980e%7C0fee8ff2a3b240189c753a1d5591fe
dc%7C1%7C0%7C637304154968576692&sdata=fGpMx9NBxsL%2FRfP%2BAImmb4R2hbxFmaAn%2
FpOWXmapQ10%3D&reserved=0> 

 

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?  

It is acceptable.

 

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

It is ready. 

3) Do you know of implementations of this draft?  

Two implementations.

4) Do you know of deployments of this draft?  

If so, is this feature useful in the deploy ments. 

It is useful. 

5) Do you feel that Wide Communities is ready for 

Publication?  

 It is ready.

 

Cheerily, Susan Hares