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

Jeff Wheeler <jsw@inconcepts.biz> Tue, 11 December 2012 11:37 UTC

Return-Path: <jsw@inconcepts.biz>
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 6C5B721F87BC for <idr@ietfa.amsl.com>; Tue, 11 Dec 2012 03:37:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.464
X-Spam-Level:
X-Spam-Status: No, score=-2.464 tagged_above=-999 required=5 tests=[AWL=-0.087, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_14=0.6, 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 XlDP41mdTTCC for <idr@ietfa.amsl.com>; Tue, 11 Dec 2012 03:37:42 -0800 (PST)
Received: from mail-ia0-f172.google.com (mail-ia0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id A2B7A21F8532 for <idr@ietf.org>; Tue, 11 Dec 2012 03:37:42 -0800 (PST)
Received: by mail-ia0-f172.google.com with SMTP id z13so7409044iaz.31 for <idr@ietf.org>; Tue, 11 Dec 2012 03:37:39 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=/0sTxSJNA9O8kuutrMiXz5TVFxDgTyk50SrZxlfuD78=; b=YcvuqkHU4lFcfOsUItWoFUKTfYuLFjGkDlQXJP73lXlfgCrYpsPlpFJAdm504vQEJ4 cBTGjbUanOAnBZE2rUwF6behgXjXviqlpPrXLkn6+4DicX6e6qokP+JoKX6L4OAll9da f8JV8ljX6u9E67xjlXLIkzROUJDPXVXJFaMAcgqLu/XUwuxREz88r7eYYysxxBdGQuzG BkDI7zscytsDo4xFpgJVW4ROYS/1gZFR9Z5Q9mY04+tRpmdtIz+aCyuSFDeDTavMT7BE oOy2ZI5T4+Poa/bNfBhYy6+WLC+C11nO0R1TZRtU+yWhzthqPpwO6+k87o6g7MiZLxXl BkYg==
MIME-Version: 1.0
Received: by 10.42.180.65 with SMTP id bt1mr13688067icb.41.1355225858822; Tue, 11 Dec 2012 03:37:38 -0800 (PST)
Received: by 10.64.132.33 with HTTP; Tue, 11 Dec 2012 03:37:38 -0800 (PST)
X-Originating-IP: [74.134.22.105]
In-Reply-To: <50C686F3.9030100@umn.edu>
References: <CAL9jLaZdX_jem0JdSGHzuhc3GDZXMDR0kvMKq5xr3D-EWYbNVQ@mail.gmail.com> <CA+b+ER=rL6WAMuu5cJUQk94ObUrhKKgmiNuxRhMGJbavCg6S3A@mail.gmail.com> <CAL9jLaa27PZwa+fj_okSHTjjnxQeR8q67Nb5V0aYKOBbqcHtjQ@mail.gmail.com> <CA+b+ERnBAOU5sbtjnPcfzmw2ieu7UPEXWbGCpsY=5hcfSUToFg@mail.gmail.com> <CAL9jLab4WZa-QA2pwhD7cuCk8iNca3xSUeJkQDxJyy4dS37WSg@mail.gmail.com> <9DCD1872-F11D-4B08-9B0B-834C05D7D0FF@tony.li> <m2pq2uzl2i.wl%randy@psg.com> <FCB6E858-F190-46AF-8BA5-F4C92F590505@tony.li> <m2ehjazgmg.wl%randy@psg.com> <50B986F2.5060405@umn.edu> <20121210225019.GA24937@puck.nether.net> <50C686F3.9030100@umn.edu>
Date: Tue, 11 Dec 2012 06:37:38 -0500
Message-ID: <CAPWAtbJQT=5xbB=2RwRb2Ag4Ho5dD8Sn8bNM9g2UFiDAVvdxLQ@mail.gmail.com>
From: Jeff Wheeler <jsw@inconcepts.biz>
To: David Farmer <farmer@umn.edu>
Content-Type: text/plain; charset="ISO-8859-1"
X-Gm-Message-State: ALoCoQmrB2r8auF3faocKVcXJl1qLzgLitcaIpQvUnMXr6PYe2OHxxBtpMMfLAEOh8gLt743bDWb
Cc: idr wg <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: Tue, 11 Dec 2012 11:37:43 -0000

On Mon, Dec 10, 2012 at 8:05 PM, David Farmer <farmer@umn.edu> wrote:
> Also, even if we revise RFC 1930 and/or the RIR's revise their policies, to
> easily allow large publicly registered ASN blocks; There is a perception

I have read that argument a few times.  I don't think it would be wise
to try to invent RIR policy for handing out potentially large blocks
of ASNs to orgs without a lot of specific debate about what uses are
"acceptable" and what aren't, which will ultimately result in RIR
policy that does one of two things:

* limits applications by making it hard to get huge ranges

* makes it easy to get huge ranges, so everyone will ask for a huge
one, and then we will face a 32-bit ASN depletion problem, and decide
to revise the policy, but there will be a bunch of early-adopters who
have these gigantic blocks; and then a huge block of private ASNs will
be created ANYWAY as a half-way measure to "level the playing field"
and avoid squatting

My view is that changing RIR policy to address this is quite stupid,
and it is unrealistic to think that the RIR membership would be stupid
enough to do it without first saying, "why isn't the private ASN space
expanded?"

There are some reasons why you may want unique public ASNs instead of
private, re-usable ASNs inside of service provider L3VPNs but only if
you can convince your customers to actually utilize them, and then
hand-hold your customers through requesting those blocks so they can
be assigned to sites.

Randy has plenty of history trying to force his view of what is
"optimal" to become the only possible option, instead of offering
choices and flexibility.  RIRs can still decide to give big ASN blocks
out if their memberships want that, whether the private ASN range is
expanded or not.  In fact, proposing to RIR membership that a private
resource is being exhausted thus it must be made easier to acquire
public resources for private uses, is not a smart way to convince RIR
members to vote in favor of that proposal.

$0.02.
-- 
Jeff S Wheeler <jsw@inconcepts.biz>
Sr Network Operator  /  Innovative Network Concepts