Re: [GROW] Making BMP registries FCFS

Christopher Morrow <christopher.morrow@gmail.com> Thu, 20 September 2018 20:34 UTC

Return-Path: <christopher.morrow@gmail.com>
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 47F861200D7 for <grow@ietfa.amsl.com>; Thu, 20 Sep 2018 13:34:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 gOW7fW2LAIHr for <grow@ietfa.amsl.com>; Thu, 20 Sep 2018 13:34:12 -0700 (PDT)
Received: from mail-vs1-xe35.google.com (mail-vs1-xe35.google.com [IPv6:2607:f8b0:4864:20::e35]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 23E9A1200D6 for <grow@ietf.org>; Thu, 20 Sep 2018 13:34:12 -0700 (PDT)
Received: by mail-vs1-xe35.google.com with SMTP id h23-v6so3617225vsk.13 for <grow@ietf.org>; Thu, 20 Sep 2018 13:34:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=nnATo9r0IITsp2kXzWEQhcOgX8QEY/gC7het78UXuGs=; b=mr5MmT3q9+oDnfRH/nZqk2e4W+KeKPZACMXYGrutvjOfqxSk/e2gzWsg/Udi7GRy3e SY3kS+PCq9y3I7hCBI3ay71B8lgwJkM8J1fKveV3WxiHFe90vAKFl5g/GnLsBVNaYw86 3YzFIXZgE/G7zaY7LB8URYgZpTzJUqPqzhJ1oibA1zA58jGoMTWiJuV8cQouaNX/wz/D F32ar/4F98Z3M2MylL9P4ck2UkWLqgoq4cbOOq31crfM4fIorHzEz6mxml+TxUdNCIZ+ 0VTXWkrlKwy8Qe/ro3Odq2L8fqUECI2VHpueuJckgSAzzd5zoJlc7HgFqy1hbvSOD2ao DaLg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=nnATo9r0IITsp2kXzWEQhcOgX8QEY/gC7het78UXuGs=; b=LO3M8UaN1LwgvTjUViK1fUTbpPIXAB5DN9J2wYEQ4F0ibwzb4bBEEDsi+60Y9aPFCG 0zxG6Fuh/PxOKplRx7BYAW316V8KhogZ5U2IhvQr9z3XRSazux6MasLMmB6yCeQeSn9/ jGLyYSGu8mWOufmhclAw1NAoCwahGUNRWBJ2Q+EpeDKWPNScOq+5XBs8e1XBCIPGxYpi cEbcfkBuiY73FLUhRdfJy8TtzvIPztmspjgiPnWXHr/KB+YGnDI0eQdAcQ6cHaSmIyJw z6ko2SR4pRohhz+H7MMwGCav3lfsozHAUha4AzIwjqNEvhOVSTk2ofwfZsdpmwwFGQfT 1+kg==
X-Gm-Message-State: APzg51CQwO22uT3OsQxlVEVxYAuVWYwcOeR61Ht1Cv+TA+BvIwdkfeZQ mZDejSE8/X7RlwJ+VVadBN/3fxUoa+0wIZQBfs8=
X-Google-Smtp-Source: ANB0VdYEPVs5vgxhC36ccrI/XRKYwEk/ZyghcY6yqLjFfliM7rVfJcT6PS86v1pU0yeiBElef53xAPK3i5MPSbjZW8c=
X-Received: by 2002:a67:cfcc:: with SMTP id h12-v6mr11804758vsm.118.1537475650866; Thu, 20 Sep 2018 13:34:10 -0700 (PDT)
MIME-Version: 1.0
References: <F0D1CFA1-5E5B-473D-94B4-CADD14294BD7@juniper.net>
In-Reply-To: <F0D1CFA1-5E5B-473D-94B4-CADD14294BD7@juniper.net>
From: Christopher Morrow <christopher.morrow@gmail.com>
Date: Thu, 20 Sep 2018 13:33:53 -0700
Message-ID: <CAL9jLabxGLOt9tV_4dKEUSbC+mWmO_RF=uf9W1zFN7guegXe9A@mail.gmail.com>
To: "John G. Scudder" <jgs@juniper.net>
Cc: "grow@ietf.org grow@ietf.org" <grow@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000005533505765372e8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/4F-yuQkzXx1wrpOuhtefWzZuYC8>
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 20:34:14 -0000

Hello Grow Folks,
This seems like a sane plan ... I or Job can either unilaterally accept
this, or ask for adoption...

If there's enough immediate call to avoid the 2wk call for adoption I'd be
happy to just put it on the docket...



On Thu, Sep 20, 2018 at 1:12 AM John Scudder <jgs@juniper.net> wrote:

> Hi All,
>
> 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).
>
> Thanks,
>
> --John
>
> P.S.: I'm one of the designated experts for those registries
> ("Specification Required" requires designated experts who review all
> requests). So I have the ulterior motive of trying to get rid of work. :-)
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
>