Re: [Idr] WGLC on draft-ietf-idr-as-private-reservation-00

Geoff Huston <gih@apnic.net> Thu, 29 November 2012 18:21 UTC

Return-Path: <gih@apnic.net>
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 5C72821F8AF9 for <idr@ietfa.amsl.com>; Thu, 29 Nov 2012 10:21:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level:
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2+hw2TnTnz2c for <idr@ietfa.amsl.com>; Thu, 29 Nov 2012 10:21:07 -0800 (PST)
Received: from asmtp.apnic.net (asmtp.apnic.net [IPv6:2001:dc0:2001:11::199]) by ietfa.amsl.com (Postfix) with ESMTP id 6861621F8AE1 for <idr@ietf.org>; Thu, 29 Nov 2012 10:21:07 -0800 (PST)
Received: from 2001-44b8-1121-1a00-3448-34ba-4195-613f.static.ipv6.internode.on.net (2001-44b8-1121-1a00-3448-34ba-4195-613f.static.ipv6.internode.on.net [IPv6:2001:44b8:1121:1a00:3448:34ba:4195:613f]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by asmtp.apnic.net (Postfix) with ESMTP id 76154B6745; Fri, 30 Nov 2012 04:21:05 +1000 (EST)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Geoff Huston <gih@apnic.net>
In-Reply-To: <1AF020BC-65F1-4484-AAAD-355A294A7692@kumari.net>
Date: Fri, 30 Nov 2012 05:21:04 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <CEEF8969-16D0-42B9-A093-F058E5D1848F@apnic.net>
References: <B6B72499-E9D0-4281-84EB-6CA53694866E@juniper.net> <2CDB688B-9C24-4AF5-8900-20A88211AC54@apnic.net> <1AF020BC-65F1-4484-AAAD-355A294A7692@kumari.net>
To: Warren Kumari <warren@kumari.net>
X-Mailer: Apple Mail (2.1499)
Cc: "idr@ietf. org" <idr@ietf.org>
Subject: Re: [Idr] WGLC on draft-ietf-idr-as-private-reservation-00
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 29 Nov 2012 18:21:08 -0000

On 30/11/2012, at 3:49 AM, Warren Kumari <warren@kumari.net> wrote:

> 
> On Nov 28, 2012, at 10:07 PM, Geoff Huston <gih@apnic.net> wrote:
> 
>> 
>> On 29/11/2012, at 8:26 AM, John Scudder <jgs@juniper.net> wrote:
>> 
>>> Folks,
>>> 
>>> We have received a request for a working group last call on draft-ietf-idr-as-private-reservation-00. A URL for the draft is http://tools.ietf.org/html/draft-ietf-idr-as-private-reservation-00
>>> 
>>> Please send comments to the list by December 14. [*]
>>> 
>> 
>> I am opposed to this draft - increasing the size of a unordered non-unique identifier space is counter-productive.
> 
> … and I support it -- some folk have a need for more than 1023 "private" ASNs and *really really* don't want to do the "just reuse the same one and then use something like the 'allows-in' and similar hacks".
> 
> Yes, going to an RIR and requesting a few thousand global ASes is possible, but to me seems inelegant.

???

> 
> Close to 100,000 reserved ones feels overly large to me, but it does line up nicely on a (decimal) boundary.

But if there is a single need for 100,000 code points in single coherent space then you have to ask how one could ensure uniqueness within the deployment space, as you are now talking about a large number of entities and a large coder point space, and according to your response, the reason why there is a driving need  duplicate an existing uniqueness framework is because the current framework we have for ensuring uniqueness of AS number code points is ... "inelegant"?

Obviously I'm unconvinced by such as assertion, and remain opposed to the further progress of this document.

Geoff