Re: [Idr] Can we eliminate the "IETF Review" Capablities range? [was: Re: I-D Action: draft-ietf-idr-capabilities-registry-change-04.txt]
Jeffrey Haas <jhaas@pfrc.org> Mon, 03 June 2019 17:48 UTC
Return-Path: <jhaas@slice.pfrc.org>
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 2DE86120181 for <idr@ietfa.amsl.com>; Mon, 3 Jun 2019 10:48:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=unavailable 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 LwCx6bnUb6GH for <idr@ietfa.amsl.com>; Mon, 3 Jun 2019 10:48:13 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 77B23120730 for <idr@ietf.org>; Mon, 3 Jun 2019 10:48:13 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 4BA061E2D8; Mon, 3 Jun 2019 13:49:05 -0400 (EDT)
Date: Mon, 03 Jun 2019 13:49:05 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: John Scudder <jgs=40juniper.net@dmarc.ietf.org>
Cc: "idr@ietf.org" <idr@ietf.org>
Message-ID: <20190603174905.GE22224@pfrc.org>
References: <155860518236.3859.4116481267193969204@ietfa.amsl.com> <F34580D3-0033-45CA-B90A-78A37DE22F9B@juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <F34580D3-0033-45CA-B90A-78A37DE22F9B@juniper.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/OzWShvuXFno_Tp8bTLSUzKo1Qyg>
Subject: Re: [Idr] Can we eliminate the "IETF Review" Capablities range? [was: Re: I-D Action: draft-ietf-idr-capabilities-registry-change-04.txt]
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, 03 Jun 2019 17:48:15 -0000
John, On Thu, May 23, 2019 at 10:10:35AM +0000, John Scudder wrote: > 2.c. Leave it as written in version 04, 1-63 IETF Review, 64-238 FCFS. > Pro: it’s what we’ve already been discussing and nobody (other than me, in this note) has raised an objection so far. > Con: authors are required to choose between the two ranges, experience shows that many assume that IETF Review is “better” for some reason. This holds up number allocation, retards implementation, and invokes additional administrative overhead without returning any concrete benefit. My preference is to stay with this option. The FCFS range is sufficiently large that we're not impeding progress. We also reserve the right to re-classify the IETF review range at a later date. -- Jeff
- [Idr] I-D Action: draft-ietf-idr-capabilities-reg… internet-drafts
- [Idr] Can we eliminate the "IETF Review" Capablit… John Scudder
- Re: [Idr] Can we eliminate the "IETF Review" Capa… tom petch
- Re: [Idr] Can we eliminate the "IETF Review" Capa… Donald Eastlake
- Re: [Idr] Can we eliminate the "IETF Review" Capa… John Scudder
- Re: [Idr] Can we eliminate the "IETF Review" Capa… bruno.decraene
- Re: [Idr] Can we eliminate the "IETF Review" Capa… Jeffrey Haas
- Re: [Idr] Can we eliminate the "IETF Review" Capa… Jeffrey Haas