Re: [Idr] WGLC on draft-ietf-idr-as-private-reservation-00 concluded, extended to consider ASN range

Jon Mitchell <jrmitche@puck.nether.net> Wed, 19 December 2012 15:20 UTC

Return-Path: <jrmitche@puck.nether.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 9BC4921F87AE for <idr@ietfa.amsl.com>; Wed, 19 Dec 2012 07:20:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.551
X-Spam-Level:
X-Spam-Status: No, score=-6.551 tagged_above=-999 required=5 tests=[AWL=0.048, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 S3B4-QzqRO58 for <idr@ietfa.amsl.com>; Wed, 19 Dec 2012 07:20:22 -0800 (PST)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) by ietfa.amsl.com (Postfix) with ESMTP id C2DCC21F87A6 for <idr@ietf.org>; Wed, 19 Dec 2012 07:20:22 -0800 (PST)
Received: from puck.nether.net (puck.nether.net [204.42.254.5]) by puck.nether.net (8.14.4/8.14.4) with ESMTP id qBJFKMer017626 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 19 Dec 2012 10:20:22 -0500
Received: (from jrmitche@localhost) by puck.nether.net (8.14.4/8.14.4/Submit) id qBJFKM5D017625; Wed, 19 Dec 2012 10:20:22 -0500
Date: Wed, 19 Dec 2012 10:20:22 -0500
From: Jon Mitchell <jrmitche@puck.nether.net>
To: Robert Raszuk <robert@raszuk.net>
Message-ID: <20121219152021.GB3846@puck.nether.net>
References: <B6B72499-E9D0-4281-84EB-6CA53694866E@juniper.net> <B9358F0B-6AFC-4971-94E9-2C7E44F405AA@juniper.net> <50D1C7F5.6030406@umn.edu> <CA+b+ERnuYpBDaLr2A1WvLzMNXRJW7awGB41H_0sddWsN4+s9PQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CA+b+ERnuYpBDaLr2A1WvLzMNXRJW7awGB41H_0sddWsN4+s9PQ@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.6 (puck.nether.net [204.42.254.5]); Wed, 19 Dec 2012 10:20:22 -0500 (EST)
Cc: "idr@ietf. org" <idr@ietf.org>
Subject: Re: [Idr] WGLC on draft-ietf-idr-as-private-reservation-00 concluded, extended to consider ASN range
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: Wed, 19 Dec 2012 15:20:23 -0000

On Wed, Dec 19, 2012 at 03:41:08PM +0100, Robert Raszuk wrote:
> Hello David,
> 
> > So, if someone can provide a reasonable justification for 100M private use
> > ASNs, or even 10M for that matter, I'm all ears
> 
> I think we are all observing exponential rate of office backends being
> outsourced. Also notice that grow of public AS numbers is not that
> steep. Through last 12 years we allocated 50K !
> http://www.potaroo.net/tools/asns/

I agree that this is the case.

> So IMHO it is not that unrealistic that some global SP (maybe Google,
> Microsoft, Apple2 etc... :) could offer free Internet access
> everywhere they could reach or where law mandates free "last mile".
> Would we want to limit number of their global customers ? Would we
> really need to invent new hacks to work around private AS number
> starvation ? Of course it is dead clear that Internet access does not
> mandate use of BGP even for multihomed sites (example: LISP). But this
> is IDR so I guess talking about BGP here is ok.
> 
> My seemingly wild suggestions to offer half of the space as private or
> think about make AS hierarchical were aiming precisely in such new
> EBGP (or EBGP-lite) peerings for large numbers of IPv4/IPv6/VPNs
> customers.
> 
> If someone would to use this new RFC for such applications let me
> reverse the question .. do we have sufficient reasons to limit the
> space to 1M customers ? Are we afraid that even if we reserve 31 bits
> the public AS will experience shortage anytime soon considering
> current grow rate of public as number assignments ?

I think there is hope that there will be interesting growth on the
Internet or globally unique identifier use cases with Public ASN
registrations and that RIR policies may change to encourage these use
cases over time.

It's hard to tell if you are seriously suggesting a 50% proposal still,
but I would consider this is a substantive change to the intent,
motivation and content of the draft which is for a single organization
(and Private Use) and would probably require a new draft.  I can't
accept a proposal to move to 50% in the draft and there seemed to be no
energy from anyone that this is the right direction.  It also seems to
then remove the possibility that these types of allocations would be
from Public space, and disallow other proposals such as the one you
started a seperate thread about by consuming too much of the overall
space to make them acceptable any longer (there by forcing more use
cases with large number of ASN needs into Private Use space).

However if your overall point is that 10M - 100M is not unreasonable for
this draft as is, I agree and think certain variations of use cases
(more the backend ones) you identified above would be Private Use if a
single organization is allocating and managing the ASNs (in my mind more
likely the large office backend customers than a provider, or a provider
using BGP in these scenarios transparently / not managed by the customer).

Jon