Re: WG Last Call on IANA Considerations (was Re: [Idr] IDR WG Minutes)

Jeffrey Haas <jhaas@nexthop.com> Mon, 15 August 2005 16:30 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E4hrT-0007oi-3F; Mon, 15 Aug 2005 12:30:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E4hrR-0007oa-3h for idr@megatron.ietf.org; Mon, 15 Aug 2005 12:30:53 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11996 for <idr@ietf.org>; Mon, 15 Aug 2005 12:30:50 -0400 (EDT)
Received: from gateout01.mbox.net ([165.212.64.21] helo=gwo1.mbox.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E4iQb-00030R-Fl for idr@ietf.org; Mon, 15 Aug 2005 13:07:13 -0400
Received: from gateout01.mbox.net (gateout01.mbox.net [165.212.64.21]) by gwo1.mbox.net (Postfix) with SMTP id 9606712D655; Mon, 15 Aug 2005 16:30:38 +0000 (GMT)
Received: from gateout01.mbox.net [165.212.64.21] by gateout01.mbox.net via mtad (C8.MAIN.3.17K) with ESMTP id 713JHoqEl0244Mo1; Mon, 15 Aug 2005 16:30:37 GMT
Received: from gw2.EXCHPROD.USA.NET [165.212.116.254] by gateout01.mbox.net via smtad (C8.MAIN.3.21U); Mon, 15 Aug 2005 16:30:37 GMT
X-USANET-Source: 165.212.116.254 IN jhaas@nexthop.com gw2.EXCHPROD.USA.NET
X-USANET-MsgId: XID949JHoqEl9731Xo1
Received: from localhost ([65.247.36.31]) by gw2.EXCHPROD.USA.NET over TLS secured channel with Microsoft SMTPSVC(6.0.3790.211); Mon, 15 Aug 2005 10:30:37 -0600
Date: Mon, 15 Aug 2005 12:30:36 -0400
From: Jeffrey Haas <jhaas@nexthop.com>
To: Yakov Rekhter <yakov@juniper.net>
Subject: Re: WG Last Call on IANA Considerations (was Re: [Idr] IDR WG Minutes)
Message-ID: <20050815163036.GC5530@nexthop.com>
References: <20050815153744.GZ5530@nexthop.com> <200508151606.j7FG68G15296@merlot.juniper.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <200508151606.j7FG68G15296@merlot.juniper.net>
User-Agent: Mutt/1.4.2.1i
X-OriginalArrivalTime: 15 Aug 2005 16:30:37.0292 (UTC) FILETIME=[AAE102C0:01C5A1B6]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: idr@ietf.org
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Yakov,

On Mon, Aug 15, 2005 at 09:06:08AM -0700, Yakov Rekhter wrote:
> What is the rationale for having one range for the IETF Consensus
> policy and another range for the FCFS policy ?  In other words, why
> not have just a single block from which IANA could allocate
> either based on the IETF Consensus or on the FCFS policy ?

Just for list reference, we haven't really changed the classes of
allocations we'd be allowing.  We're tweaking the ranges.

As to why we'd want those particular classes, here's my opinion:

We want a range that says, "Here's what IETF wants".  It implies 
organizational "support" for a given mechanism.  This is the IETF
Consensus range.

We want a range that says, "If you want to do something that uses
this mechanism but don't want to get full 'IETF buy-in'", there's
another range.  This is the FCFS range.

We want a range for private experimentation.  This range has a strong
implication that "do what you want here, it probably wont work with
someone else".  This is the private range.  

I think your question is why have blocks at all?  IMO, we want to 
set aside space so that IETF has room to grow in the (unlikely) case
that FCFS gets exhausted too quickly.  It's a shared playground and
there's a limited number of marbles to give away.

> Yakov.

-- 
Jeff Haas 
NextHop Technologies


_______________________________________________
Idr mailing list
Idr@ietf.org
https://www1.ietf.org/mailman/listinfo/idr