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

Jon Mitchell <jrmitche@puck.nether.net> Sun, 16 December 2012 03:25 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 045CD21F8584 for <idr@ietfa.amsl.com>; Sat, 15 Dec 2012 19:25:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.538
X-Spam-Level:
X-Spam-Status: No, score=-6.538 tagged_above=-999 required=5 tests=[AWL=0.061, 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 3+uonp0pPR1n for <idr@ietfa.amsl.com>; Sat, 15 Dec 2012 19:25:55 -0800 (PST)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) by ietfa.amsl.com (Postfix) with ESMTP id 56F9B21F84D4 for <idr@ietf.org>; Sat, 15 Dec 2012 19:25:55 -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 qBG3OiPe015651 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 15 Dec 2012 22:24:44 -0500
Received: (from jrmitche@localhost) by puck.nether.net (8.14.4/8.14.4/Submit) id qBG3OiY6015649; Sat, 15 Dec 2012 22:24:44 -0500
Date: Sat, 15 Dec 2012 22:24:44 -0500
From: Jon Mitchell <jrmitche@puck.nether.net>
To: Martin Millnert <millnert@gmail.com>
Message-ID: <20121216032444.GB14168@puck.nether.net>
References: <50C78C29.3070406@foobar.org> <50C8B8D9.4090903@umn.edu> <50C9039E.1050104@foobar.org> <20121213144147.GB4524@puck.nether.net> <50CB52E0.7080602@foobar.org> <20121214174012.GA18502@puck.nether.net> <50CBB294.1000300@umn.edu> <B5907AE4-F639-4CC7-B522-B9AD92E61A51@kumari.net> <50CCFD49.1060307@foobar.org> <1355614542.6115.19.camel@galileo.millnert.se>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <1355614542.6115.19.camel@galileo.millnert.se>
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]); Sat, 15 Dec 2012 22:24:44 -0500 (EST)
Cc: IETF IDR Working Group <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: Sun, 16 Dec 2012 03:25:56 -0000

On Sun, Dec 16, 2012 at 12:35:42AM +0100, Martin Millnert wrote:
> On Sat, 2012-12-15 at 22:44 +0000, Nick Hilliard wrote:
> > On 15/12/2012 01:40, Warren Kumari wrote:
> > > (and I sure hope I'm not the poor sod who gets allocated 4200000 or 42000000 or 420000000??? :-P )
> > 
> > or anything in the range between 420000 -> 429999.  This falls bang in the
> > middle of the likely range that will be assigned to ARIN.  Let me hold my
> > nose for a moment and use asdot format:  as420000 == 6.26784, and I can see
> > this asn being assigned in the foreseeable future in the ARIN service region.
> > 
> > 900000-999999 seems to be well outside the range of any of the current RIRs
> > (using current allocation techniques, there could be 6 more RIRs before
> > there would be any interference).
> 
> This is a very valid point; operational simplicity let's youtube stay
> reachable at night.

We just were worrying about someone dropping 3 digits from the number
and having a conflict, and now we drop or typo one and we are in the
middle of space currently in use or soon to be assigned... hmmm, failing
to see the validity of some of the arguments being made here.  Also -
the one impacted due to a mis-configuration of the number of their
private ASN is only themselves... 

> A more clear motivation of why 100000 private ASNs would be insufficient
> would be interesting to read.
> 

The motivation of the draft is over 1K ASN's, various folks have
suggested their needs ranged in the 10K numbers today.  The motivation
for going beyond this is only not having to do this again (this has been
repeated in the threads).  The criteria for reasonable in my mind should
be not consuming a large portion of the addressable space for private
ASNs.  I think the current draft and new proposal Warrend made still
meet these criteria.

Jon