IETF Logo Mail Archive

Re: [GROW] Making BMP registries FCFS

Jared Mauch <jared@puck.nether.net> Thu, 20 September 2018 10:14 UTC

Return-Path: <jared@puck.nether.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BD90130EA5 for <grow@ietfa.amsl.com>; Thu, 20 Sep 2018 03:14:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 ugWKZhyBpS5o for <grow@ietfa.amsl.com>; Thu, 20 Sep 2018 03:14:01 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [204.42.254.5]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6EE49130E50 for <grow@ietf.org>; Thu, 20 Sep 2018 03:14:01 -0700 (PDT)
Received: from [IPv6:2600:380:a510:d464:88aa:be7d:6d52:bd4] (unknown [IPv6:2600:380:a510:d464:88aa:be7d:6d52:bd4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by puck.nether.net (Postfix) with ESMTPSA id 8304D5405D9; Thu, 20 Sep 2018 06:13:58 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
From: Jared Mauch <jared@puck.nether.net>
X-Mailer: iPhone Mail (16A366)
In-Reply-To: <m2k1ngmv5r.wl-randy@psg.com>
Date: Thu, 20 Sep 2018 06:13:57 -0400
Cc: John Scudder <jgs@juniper.net>, "grow@ietf.org" <grow@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <A4E39514-5190-4756-9B2F-B0DBCE33F078@puck.nether.net>
References: <F0D1CFA1-5E5B-473D-94B4-CADD14294BD7@juniper.net> <m2k1ngmv5r.wl-randy@psg.com>
To: Randy Bush <randy@psg.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/TSpe09Twtp4aFtZ5yEWDn0BwfYo>
Subject: Re: [GROW] Making BMP registries FCFS
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Sep 2018 10:14:05 -0000

I would also support adoption on the part of the WG if the chairs were to ask for it. 

Jared Mauch

On Sep 20, 2018, at 4:26 AM, Randy Bush <randy@psg.com> wrote:

>> A while ago we talked about this. I finally wrote a draft for it,
>> https://www.ietf.org/id/draft-scudder-grow-bmp-registries-change-00.txt:
>> 
>> Abstract
>> 
>>   This document updates RFC 7854, BGP Monitoring Protocol (BMP) by
>>   making a change to the registration procedures for several
>>   registries.  Specifically, any BMP registry with a range of
>>   32768-65530 designated "Specification Required" has that range re-
>>   designated as "First Come First Served".
>> 
>> It's super short, 3 pages including all the boilerplate. I'd like to
>> propose it as a WG item (and ideally, move it quickly to WGLC).
> 
> make it so
> 
> randy
> 
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow

v2.23.0 | Report a Bug | By Email