IETF Logo Mail Archive

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

Christoph Loibl <c@tix.at> Mon, 29 June 2020 15:46 UTC

Return-Path: <c@tix.at>
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 7AF803A00E0; Mon, 29 Jun 2020 08:46:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=tix.at
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 czfmamcOnXP1; Mon, 29 Jun 2020 08:46:47 -0700 (PDT)
Received: from mail.fbsd.host (mail.fbsd.host [IPv6:2001:858:58::22]) (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 DFEE83A00D4; Mon, 29 Jun 2020 08:46:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tix.at; s=rev1; h=To:References:Message-Id:Content-Transfer-Encoding:Cc:Date: In-Reply-To:From:Subject:Mime-Version:Content-Type:Sender:Reply-To:Content-ID :Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To: Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe :List-Post:List-Owner:List-Archive; bh=WHlofyQfFpVY7SVCYOLCfPqegnkOOIjP3WKeRq3cAPc=; b=qQbUgskGgJOtnICyB40S/JBfmB O8UcQd4Odp7m/PRpnGNhDIjx8/C9V4DdzGmk7oemkT1IXje6Hx3fsgfHrXHAZmhZhE9uVwojGHW3u LyhRK4n2UhukfQVyZGY9KZO/fz6bdkCTtQYM1lgTSLs92/mblAcAyfwNjM9EJgXI1eWe0442SdwID TL5ZLcb8Jd+j6rjBpqgcyrEi80YXAB3Jz9R6N2MfO3HwT+bmIqby1rKgUj9ObHAhqj+rovlkV59hQ tTsqA/Tvf31F/Dc/FFNKpEE7/h7Gtb2ndYXrooRb3MLQEWjaVQvW6KFF2CFZUME2TXISnD/fLaFFY okvEL7uQ==;
Received: from 80-110-113-91.cgn.dynamic.surfer.at ([80.110.113.91] helo=[192.168.66.207]) by mail.fbsd.host with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92.3) (envelope-from <c@tix.at>) id 1jpvzX-0003Kx-GC; Mon, 29 Jun 2020 17:46:45 +0200
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
From: Christoph Loibl <c@tix.at>
In-Reply-To: <009f01d64a8e$c0c907e0$425b17a0$@ndzh.com>
Date: Mon, 29 Jun 2020 17:46:42 +0200
Cc: IDR List <idr@ietf.org>, draft-cl-idr-bgp-ext-com-registry-update@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <B125D4CD-650C-4E88-970A-5B555CE3AEB0@tix.at>
References: <009f01d64a8e$c0c907e0$425b17a0$@ndzh.com>
To: Susan Hares <shares@ndzh.com>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
X-Scanned-By: primary on mail.fbsd.host (78.142.178.22); Mon, 29 Jun 2020 17:46:43 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/EOiIx97VWNGYCivGKznt9NDCaqc>
Subject: Re: [Idr] [BULK] 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: Mon, 29 Jun 2020 15:46:50 -0000

Hi Sue, IDR,

I am not aware of any IPR related to this draft.

@WG: 
This is a *very* short draft that, is easy to read (even though it is a little boring). It contains IANA registry changes only and is (an unpopular?) cleanup draft that I have been asked for as a result of my work on BGP Flowspec. 

I think it is our responsibility to cleanup that part of the extended community registry. I support WG adoption and hope for other support as well.

Cheers 

Christoph

-- 
Christoph Loibl
c@tix.at | CL8-RIPE | PGP-Key-ID: 0x4B2C0055 | http://www.nextlayer.at



> On 25.06.2020, at 03:20, Susan Hares <shares@ndzh.com> wrote:
> 
> 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
>      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. 
> 
> Cheerily, Susan Hares

v2.23.0 | Report a Bug | By Email