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

Robert Raszuk <robert@raszuk.net> Wed, 19 December 2012 14:41 UTC

Return-Path: <rraszuk@gmail.com>
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 6496821F84FF for <idr@ietfa.amsl.com>; Wed, 19 Dec 2012 06:41:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.945
X-Spam-Level:
X-Spam-Status: No, score=-2.945 tagged_above=-999 required=5 tests=[AWL=0.032, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
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 toQOcoli7e9A for <idr@ietfa.amsl.com>; Wed, 19 Dec 2012 06:41:09 -0800 (PST)
Received: from mail-ie0-f171.google.com (mail-ie0-f171.google.com [209.85.223.171]) by ietfa.amsl.com (Postfix) with ESMTP id 8374621F84ED for <idr@ietf.org>; Wed, 19 Dec 2012 06:41:09 -0800 (PST)
Received: by mail-ie0-f171.google.com with SMTP id 17so2819944iea.16 for <idr@ietf.org>; Wed, 19 Dec 2012 06:41:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=+Q9j7dr6Sb+7ZuIphbVToyq6RUsNbgAGCjGyyPAQRuA=; b=kf79mZ7jofqV/tVsOpk2XoUeuyPYpILg0NURT6BBpJmc3HpqgTT2Ae1RfAYKRIGT4y dyysN/jTfQwGLiGn5+0cOuU4vO8fU+rf6ImfjGarQMUKmRfSZFfNjXxRZ1X1QY9Yjv2t Kt250Bna1HkfbzV6G5rGeYFlE6TAJO5Bfgp/7fAd/20hHzG1q1vtRG2ayCOi0YpdhaOr d4PXn+ZVX6UZub0t56zgGGTW7mperg/j1tchR56J5k1TQSdPMnvzF+NL1KfXiqPrDVUz ee9GyTeGE61xHN68aSSmvRwLVWO0T/igBJbn2g8aChNjqHh13o2/kl26zozHr/n/9er9 4kEQ==
MIME-Version: 1.0
Received: by 10.42.118.13 with SMTP id v13mr5922847icq.44.1355928069059; Wed, 19 Dec 2012 06:41:09 -0800 (PST)
Sender: rraszuk@gmail.com
Received: by 10.64.167.204 with HTTP; Wed, 19 Dec 2012 06:41:08 -0800 (PST)
In-Reply-To: <50D1C7F5.6030406@umn.edu>
References: <B6B72499-E9D0-4281-84EB-6CA53694866E@juniper.net> <B9358F0B-6AFC-4971-94E9-2C7E44F405AA@juniper.net> <50D1C7F5.6030406@umn.edu>
Date: Wed, 19 Dec 2012 15:41:08 +0100
X-Google-Sender-Auth: ZlQba1gIAifNpbhfm66lF97IjoQ
Message-ID: <CA+b+ERnuYpBDaLr2A1WvLzMNXRJW7awGB41H_0sddWsN4+s9PQ@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
To: David Farmer <farmer@umn.edu>
Content-Type: text/plain; charset="ISO-8859-1"
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 14:41:10 -0000

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/

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 ?

Best wishes,
R.