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

Shane Amante <shane@castlepoint.net> Sat, 01 December 2012 16:38 UTC

Return-Path: <shane@castlepoint.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 8771821F8BE5 for <idr@ietfa.amsl.com>; Sat, 1 Dec 2012 08:38:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.02
X-Spam-Level:
X-Spam-Status: No, score=-0.02 tagged_above=-999 required=5 tests=[AWL=0.417, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.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 YFFqV1box37X for <idr@ietfa.amsl.com>; Sat, 1 Dec 2012 08:38:55 -0800 (PST)
Received: from mail.friendswithtools.org (unknown [64.78.239.70]) by ietfa.amsl.com (Postfix) with ESMTP id ADD8B21F8640 for <idr@ietf.org>; Sat, 1 Dec 2012 08:38:34 -0800 (PST)
Received: from dspam (unknown [127.0.0.1]) by mail.friendswithtools.org (Postfix) with SMTP id 625BF2399 for <idr@ietf.org>; Sat, 1 Dec 2012 16:38:34 +0000 (UTC)
Received: from mbp.castlepoint.net (174-29-211-99.hlrn.qwest.net [174.29.211.99]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.friendswithtools.org (Postfix) with ESMTPSA id B67E62387; Sat, 1 Dec 2012 09:38:33 -0700 (MST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Shane Amante <shane@castlepoint.net>
In-Reply-To: <C02B62F1-DCBD-42D0-921A-A44B4E784142@juniper.net>
Date: Sat, 01 Dec 2012 09:38:32 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <17B0E950-A275-401A-BD05-D1DEC05845D5@castlepoint.net>
References: <B6B72499-E9D0-4281-84EB-6CA53694866E@juniper.net> <1354296877.9381.YahooMailNeo@web162902.mail.bf1.yahoo.com> <C02B62F1-DCBD-42D0-921A-A44B4E784142@juniper.net>
To: "John G. Scudder" <jgs@juniper.net>
X-Mailer: Apple Mail (2.1499)
X-DSPAM-Result: Innocent
X-DSPAM-Processed: Sat Dec 1 09:38:34 2012
X-DSPAM-Confidence: 1.0000
X-DSPAM-Improbability: 1 in 98689409 chance of being spam
X-DSPAM-Probability: 0.0023
X-DSPAM-Signature: 50ba328a199633310621106
X-DSPAM-Factors: 27, Extended+#+#+#+forcing, 0.40000, if+#+have, 0.40000, especially+#+in, 0.40000, palatable+#+me, 0.40000, Obviously+#+#+#+would, 0.40000, The+#+hacks, 0.40000, if+#+#+an, 0.40000, if+#+#+an, 0.40000, really+#+#+If, 0.40000, X+year, 0.40000, draft+Not, 0.40000, Chandra+#+chandra, 0.40000, draft+#+#+#+this, 0.40000, appear+#+#+#+not, 0.40000, if+#+became, 0.40000, have+#+#+#+the, 0.40000, even+#+private, 0.40000, The+#+#+to, 0.40000, speaking+#+#+#+encourage, 0.40000, justification+#+#+by, 0.40000, an+#+#+the, 0.40000, figure+the, 0.40000, of+#+bottle, 0.40000, Private+#+#+squat, 0.40000, of+#+anycast, 0.40000, the+#+I, 0.40000, I+#+#+private, 0.40000
Cc: "idr@ietf. org" <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: Sat, 01 Dec 2012 16:38:55 -0000

On Nov 30, 2012, at 12:22 PM, John G. Scudder <jgs@juniper.net> wrote:
> On Nov 30, 2012, at 12:34 PM, Chandra Appanna <chandra.appanna@yahoo.com> wrote:
> 
>> I figure the chairs might want to hear from some of us who are reading but silent so far..
> 
> Indeed. Thanks for speaking up and I encourage others to do the same if you have an opinion on the subject.

FWIW, I support advancing/publishing this document.

While I personally find private ASN's distasteful and I try to avoid them whenever possible (especially/even in private network contexts), the facts of the matter are:
1) The genie is already out of the bottle with the existing range of private ASN's (64512 - 65534).
2) The, <ahem>, "hacks" to deal with them are already in code and would, hopefully, just need a trivial modification to recognize the new range.
3) We operators already have methods of filtering private ASN's and those filters should also require trivial _one-time_ modifications, shortly after this is published.

And, at the end of the day, I would much rather see that the IETF adopt a standard range of "Extended, Private ASN's" than forcing operators who need a large set of Private ASN's to squat on legitimate space.  That would that create a mess.

-shane

P.S. -- Frankly, for folks who don't support this proposal I'd say this is really about economics.  If RIR's supported a model of leasing ASN's in bulk, e.g.: N x 10,000 4-Byte ASN's for $X/year, (where $X was an extremely small fraction of: N ASN's x $500/ASN) for the whole block.  Obviously such bulk allocations would require needs based justification, as defined by RIR policies.  If such a proposal were to be adopted, it would /potentially/ *also* make it more palatable to anycast operators on the Internet to use a globally unique ASN per anycast instance/node, for reasons outlined in this draft:
http://tools.ietf.org/html/draft-mcpherson-unique-origin-as-00
(Not sure if this became an RFC).  IMO, this course of action would be a much more palatable to me, because it would address the needs of both anycast operators and DataCenters/Enterprises.  
   All this really begs the question: when will we recognize that numbers are not a precious commodity, especially ASN's that only appear in the RIB, not the FIB?