Re: [Idr] draft-cli-bgp-ext-com-registry-update: WG adoption and IPR Call and WG adoption (6/24 to 7/8)

"Dongjie (Jimmy)" <jie.dong@huawei.com> Wed, 01 July 2020 07:24 UTC

Return-Path: <jie.dong@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 4BE023A094A; Wed, 1 Jul 2020 00:24:48 -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 KFfXiTLUq-Al; Wed, 1 Jul 2020 00:24:46 -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 81E0D3A0949; Wed, 1 Jul 2020 00:24:46 -0700 (PDT)
Received: from lhreml708-chm.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 6E2FC6B5928687C429CB; Wed, 1 Jul 2020 08:24:43 +0100 (IST)
Received: from dggeme753-chm.china.huawei.com (10.3.19.99) by lhreml708-chm.china.huawei.com (10.201.108.57) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1913.5; Wed, 1 Jul 2020 08:24:42 +0100
Received: from dggeme754-chm.china.huawei.com (10.3.19.100) by dggeme753-chm.china.huawei.com (10.3.19.99) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1913.5; Wed, 1 Jul 2020 15:24:40 +0800
Received: from dggeme754-chm.china.huawei.com ([10.6.80.77]) by dggeme754-chm.china.huawei.com ([10.6.80.77]) with mapi id 15.01.1913.007; Wed, 1 Jul 2020 15:24:40 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
CC: "draft-cl-idr-bgp-ext-com-registry-update@ietf.org" <draft-cl-idr-bgp-ext-com-registry-update@ietf.org>
Thread-Topic: [Idr] draft-cli-bgp-ext-com-registry-update: WG adoption and IPR Call and WG adoption (6/24 to 7/8)
Thread-Index: AdZKjt6fvkdbRltbTAOZXPnmqDJLJQE5au1w
Date: Wed, 01 Jul 2020 07:24:40 +0000
Message-ID: <70d92cbb5a7e401a9913d888dc80701f@huawei.com>
References: <00b701d64a8e$e7196160$b54c2420$@ndzh.com>
In-Reply-To: <00b701d64a8e$e7196160$b54c2420$@ndzh.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.148.231]
Content-Type: multipart/alternative; boundary="_000_70d92cbb5a7e401a9913d888dc80701fhuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/ZdVXKZ81j5DrUdQEWsbHh_hvXRQ>
Subject: Re: [Idr] draft-cli-bgp-ext-com-registry-update: WG adoption and IPR Call and WG adoption (6/24 to 7/8)
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: Wed, 01 Jul 2020 07:24:48 -0000

I support the adoption and also agree with John's comments.

Best regards,
Jie

From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Thursday, June 25, 2020 9:21 AM
To: idr@ietf.org
Cc: draft-cl-idr-bgp-ext-com-registry-update@ietf.org
Subject: [Idr] draft-cli-bgp-ext-com-registry-update: WG adoption and IPR Call and WG adoption (6/24 to 7/8)

This begins a 2 week WG adoption call for:
draft-cl-idr-bgp-ext-com-registry-01.txt

You can download the draft at:
https://datatracker.ietf.org/doc/draft-cl-idr-bgp-ext-com-registry-update/

This document updates several BGP Extended Community registries in
   order to replace the "Experimental Use" registration procedure in
   some entries, since their use is clearly not experimental and thus
   misleading.

This draft should be consider as part of the group of drafts that are trying to clarify and speed up the registry process.

Christoph  you should send an IPR statement regarding this draft to the IDR WG.   Since you normally prompt with your email, I am running the IPR call and WG Adoption call in parallel.

The other drafts which are in process for registry clean-up are:

1) draft-ietf-idr-capabilities-registry-change-09<https://datatracker.ietf.org/doc/draft-ietf-idr-capabilities-registry-change/>
      John Scudder: in RFC editor's queue
2) https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-ls-registry/
     Adrian Farrell: In Shepherd's queue, top of list.

These two drafts provide clean-up to the IDR capabilities and the BGP LS registry process.    This draft provides a set-up clean-up instructions for the Extended Communities registries.

Please consider if this clean-up will lessen confusion and help us streamline the process.  If you have other ideas for cleaning up the BGP registries, you are welcome to include the information on this thread.

Thank you, Sue