Re: [Idr] new ID on expansion of private use ASN range

Christopher Morrow <morrowc.lists@gmail.com> Tue, 03 July 2012 04:16 UTC

Return-Path: <christopher.morrow@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 3EA2F11E812C for <idr@ietfa.amsl.com>; Mon, 2 Jul 2012 21:16:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level:
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zlf3u8TROlNB for <idr@ietfa.amsl.com>; Mon, 2 Jul 2012 21:16:09 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7B6C911E8134 for <idr@ietf.org>; Mon, 2 Jul 2012 21:16:09 -0700 (PDT)
Received: by obbwc20 with SMTP id wc20so10602322obb.31 for <idr@ietf.org>; Mon, 02 Jul 2012 21:16:16 -0700 (PDT)
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=hzZy5B5CtiZsEMymyT3/rkw+76MzIjLf7kt1imdUUzM=; b=R0OHzJH40/OrEChHtVC0PEq6HfYHaaLpR7EaQF31Wu9YYCe9JbpXLY0HdBPEWCG1s0 fV797deRBhdU4yETIf3C7gz2bA1KSfneYAQRehIxnctrDlZMiTXQEtOEFcaYvIfV6brv HVvvkHlFJtPH9HwcxpQY83QyHebSnQJdcFPqEJ825lqj2cRF3ynuA8uxp14qp15fVC2f RD0couwio/4w9giw7OOG7M3tGCYKEjPwFRhvK2RRxSz0hLa2OnY0VR90XPHgojTy3T3E V01zSLD5Cbj5JO8yoMgKrd7wgmbmMVGKwWidHbGl7VRweWyZN/HjWRECpQXtcwGzrNqr SRHA==
MIME-Version: 1.0
Received: by 10.182.77.170 with SMTP id t10mr11059282obw.70.1341288975995; Mon, 02 Jul 2012 21:16:15 -0700 (PDT)
Sender: christopher.morrow@gmail.com
Received: by 10.182.191.98 with HTTP; Mon, 2 Jul 2012 21:16:15 -0700 (PDT)
In-Reply-To: <20120703015521.GB22452@puck.nether.net>
References: <20120702164834.GB13713@puck.nether.net> <20120702184737.GV18361@pfrc> <20120703015521.GB22452@puck.nether.net>
Date: Tue, 03 Jul 2012 00:16:15 -0400
X-Google-Sender-Auth: UGKGPpow71snf1T47LReMmkpd5w
Message-ID: <CAL9jLaY3iO7-4v7DUSAy28zEkRpShqgbDBCeBegcy8HsdH2N-A@mail.gmail.com>
From: Christopher Morrow <morrowc.lists@gmail.com>
To: Jon Mitchell <jrmitche@puck.nether.net>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: idr@ietf.org
Subject: Re: [Idr] new ID on expansion of private use 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: Tue, 03 Jul 2012 04:16:10 -0000

On Mon, Jul 2, 2012 at 9:55 PM, Jon Mitchell <jrmitche@puck.nether.net> wrote:
> A good case can be made for either in my opinion, but the IDR WG chairs
> were OK with it being worked here.  I can definitely send it also to
> GROW list for comment either before or after it becomes a WG document,
> or whatever makes the IDR WG chairs most comfortable.  GROW WG chairs
> are aware of it already...

it's probably worthwhile (as a co-chair in GROW) to come clean about this bit:
Jon asked both chair groups, we debated and mr scudder leaped.

As to the whole idea, I think that jon puts forth some valid arguments
for making more private-asns, though I fear the tomfoolery in code
that already exists for special case thiings (private-asn,
private-ip/ULA, accept-own-as, etc...ick)

I'd like to see a good discussion on 'why not just get public asns for
all this sort of stuff'
If there never were private-asns, if asns were as plentiful as rain,
why NOT just use them instead? What would be required to go on as we
want, without making making more private-asns?

-chris