IETF Logo Mail Archive

Re: [GROW] Making BMP registries FCFS

"Acee Lindem (acee)" <acee@cisco.com> Fri, 21 September 2018 14:03 UTC

Return-Path: <acee@cisco.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 F0C21130DC0 for <grow@ietfa.amsl.com>; Fri, 21 Sep 2018 07:03:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.509
X-Spam-Level:
X-Spam-Status: No, score=-14.509 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 zAzAYYJmTkbF for <grow@ietfa.amsl.com>; Fri, 21 Sep 2018 07:03:39 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B79A1129385 for <grow@ietf.org>; Fri, 21 Sep 2018 07:03:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=18542; q=dns/txt; s=iport; t=1537538619; x=1538748219; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=++Tdq2J9ECrETXzcdke51PgkQqC4nraM3cGBXKVUvYI=; b=JfKslZV68j6h9Hy0UTTI9txXJg4m+sRFfVjt4TAT2up7d5tnnWWvdiuB gQnl4GU0PkWMPShLEaGPl2/dzgn0NlXjw33jRcVAPe8NSC48IV8D27mg7 5oTOQombVJ30sqJp8fnomK8CLCMWp1X31Sy6O+e1Bkh5m4imIr63mLZ4K 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AkAAB6+aRb/4ENJK1bGQEBAQEBAQEBAQEBAQcBAQEBAQGBUoEQTSplfygKg2mWTYheiDWFPIF6CxgBCoRJAheDLyE1FwEDAQECAQECbRwMhTgBAQEBAwEBGwZIAwsQAgEIEQMBAigDAgICHwYLFAkIAgQBDQWDIQGBHUwDFQ+iN4EuhHeCNw2CSgWFCYVnF4IAgRInH4JMglZFAQGBeAkWgksxgiYCiCQxZ4QshXSIciwJAo0OgxkXgUWHV4YMjGWHdQIRFIElHgE2gVVwFTsqAYJBCYIcF3sBAYddhT5vAY08gR4BAQ
X-IronPort-AV: E=Sophos;i="5.54,285,1534809600"; d="scan'208,217";a="174218229"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 21 Sep 2018 14:03:38 +0000
Received: from XCH-RTP-013.cisco.com (xch-rtp-013.cisco.com [64.101.220.153]) by alln-core-9.cisco.com (8.15.2/8.15.2) with ESMTPS id w8LE3cnQ022840 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 21 Sep 2018 14:03:38 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-013.cisco.com (64.101.220.153) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Fri, 21 Sep 2018 10:03:38 -0400
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1395.000; Fri, 21 Sep 2018 10:03:37 -0400
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Job Snijders <job@ntt.net>, Joel Jaeggli <joelja@bogus.com>
CC: "grow@ietf.org grow@ietf.org" <grow@ietf.org>
Thread-Topic: [GROW] Making BMP registries FCFS
Thread-Index: AQHUULmwpNWbmWv8iUmBf76Ig3TjkaT55BiAgACwYQCAAFDYgP//4QSA
Date: Fri, 21 Sep 2018 14:03:37 +0000
Message-ID: <B4567ED4-5E01-4C9F-B2A4-A7AF7A92715D@cisco.com>
References: <F0D1CFA1-5E5B-473D-94B4-CADD14294BD7@juniper.net> <CAL9jLabxGLOt9tV_4dKEUSbC+mWmO_RF=uf9W1zFN7guegXe9A@mail.gmail.com> <855482E6-CA63-48C2-AC59-49ABF500EF85@bogus.com> <CACWOCC90Ks4FLWKgWSrTLjq6dcBOjVD0br+EpT711SxGdcn2NA@mail.gmail.com>
In-Reply-To: <CACWOCC90Ks4FLWKgWSrTLjq6dcBOjVD0br+EpT711SxGdcn2NA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.199]
Content-Type: multipart/alternative; boundary="_000_B4567ED45E014C9FB2A4A7AF7A92715Dciscocom_"
MIME-Version: 1.0
X-Outbound-SMTP-Client: 64.101.220.153, xch-rtp-013.cisco.com
X-Outbound-Node: alln-core-9.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/kztoqw2kjpiLJbz_IgaqTMMw65I>
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: Fri, 21 Sep 2018 14:03:43 -0000

I support adoption as well.
Thanks,
Acee

From: GROW <grow-bounces@ietf.org> on behalf of Job Snijders <job@ntt.net>
Date: Friday, September 21, 2018 at 7:55 AM
To: Joel Jaeggli <joelja@bogus.com>
Cc: "grow@ietf.org grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Making BMP registries FCFS

Read the doc, looks fine to me. I support adoption.

Let’s give folks a few more days to comment.

Kind regards,

Job

On Fri, 21 Sep 2018 at 09:06, Joel Jaeggli <joelja@bogus.com<mailto:joelja@bogus.com>> wrote:

Sent from my iPhone

On Sep 20, 2018, at 22:33, Christopher Morrow <christopher.morrow@gmail.com<mailto:christopher.morrow@gmail.com>> wrote:
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...

I think you can adopt it and move on.  Support making registries low effort as a general principle.



On Thu, Sep 20, 2018 at 1:12 AM John Scudder <jgs@juniper.net<mailto: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<mailto:GROW@ietf.org>
https://www.ietf.org/mailman/listinfo/grow
_______________________________________________
GROW mailing list
GROW@ietf.org<mailto:GROW@ietf.org>
https://www.ietf.org/mailman/listinfo/grow
_______________________________________________
GROW mailing list
GROW@ietf.org<mailto:GROW@ietf.org>
https://www.ietf.org/mailman/listinfo/grow

v2.23.0 | Report a Bug | By Email