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:46 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 EC01D12016D for <idr@ietfa.amsl.com>; Mon, 3 Jun 2019 10:46:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=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 TJkweAISfVpF for <idr@ietfa.amsl.com>; Mon, 3 Jun 2019 10:46:10 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 039C0120142 for <idr@ietf.org>; Mon, 3 Jun 2019 10:46:10 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 6C79D1E2D8; Mon, 3 Jun 2019 13:47:02 -0400 (EDT)
Date: Mon, 03 Jun 2019 13:47:02 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: bruno.decraene@orange.com
Cc: tom petch <ietfc@btconnect.com>, "idr@ietf.org" <idr@ietf.org>, John Scudder <jgs=40juniper.net@dmarc.ietf.org>
Message-ID: <20190603174702.GD22224@pfrc.org>
References: <155860518236.3859.4116481267193969204@ietfa.amsl.com> <F34580D3-0033-45CA-B90A-78A37DE22F9B@juniper.net> <015701d51184$a55712c0$4001a8c0@gateway.2wire.net> <32397_1558691400_5CE7BE48_32397_20_1_53C29892C857584299CBF5D05346208A48AE14BF@OPEXCAUBM43.corporate.adroot.infra.ftgroup>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <32397_1558691400_5CE7BE48_32397_20_1_53C29892C857584299CBF5D05346208A48AE14BF@OPEXCAUBM43.corporate.adroot.infra.ftgroup>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/3DR_xQqStDLpfJt70bqtNFv1jmw>
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:46:12 -0000

Bruno, Tom,

On Fri, May 24, 2019 at 09:49:59AM +0000, bruno.decraene@orange.com wrote:
> > John
> > 
> > I see it as a question of security.  The Internet used to consist of
> > friendly, helpful people who worked together to make it happen.  Now
> > there is a whole raft of evil people, some state actors, some
> > individual, some corporate - in fact, actors of any kind.
> 
> Two months ago, I would have said go for "2.a. Make 1-238 all FCFS" but as of today, I think Tom as a point.
> 
> A few random comments:
> - If an actor requests all the code points, we probably still have the ability to write an RFC and reclaim those code points. We also have one reserved code point which would allow for extensions (but with a higher incremental cost, and possibly raising the same question for the allocation policy)

I think what you're suggesting is a conversation needs to happen with IANA
about how to prevent a DoS on the FCFS range.  Providing a standards
rate-limiting mechanism (our other policies) does indeed address that.

However, I think we're better off having the conversation with IANA on how
to keep low-process while at the same time wisely assigning things.

-- Jeff