Re: [Idr] Call for adoption of draft-mitchell-idr-private-as-reservation-01 as IDR WG document

[Jon Mitchell <[e-mail]>]

On Tue, Aug 28, 2012 at 09:29:34AM +0700, Randy Bush wrote:
> > Sure, RFC2270 seems to be one reasonable solution for the use case of an
> > ISP providing ASNs to single homed customers that do not require route
> > connectivity to each other except via default, and yes, I'm aware of it
> > and seen it deployed at multiple places I've worked.  Of course, the
> > unsaid thing in this draft is that using a seperate (private) ASN per
> > customer site was not viable due to limited private use ASN space
> 
> 2270 is widely deployed.  i have not run across the case where we wanted
> more than one private asn.  any sane provider is doing templated or
> generated config, and using a single asn is simpler and just works.
> 
> i am sure i can dream up convoluted uses for a mass of as numbers.  but
> what i can not do is come up with convoluted case which is worth the end
> run on having good registration of the use/assignment of those asns.

I agreed that this seems like a fine use case for a single ASN at the
top of the thread, but I guess the convulted use cases you mention here
include the rest of my email which specify why using a single private
ASN in a large single organization (not an ISP) with many sites that may
need to connect to each other (not always through one central AS) would
not be optimal, hence you choose not to respond to that part.  I think
we've also determined you are not supportive of the use of private ASNs
at this point and that you believe every use case is similar enough to
RFC2270 or a network design you believe is convulted.  I'm not sure
continuing debate will do much to change either of our positions.  I
think the quote you replied to David with would have fit better if I was
proposing a change in protocols or how to design networks, when this
draft does neither.  What it does propose is expanding the range of
available asn numbers for private use, a commonly used numbering
resource, in a extremely large available pool.  I admit this may not
pertain to a use case you are familiar with.

Jon