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

[David Farmer <[e-mail]>]

On 12/13/12 08:41 , Jon Mitchell wrote:
...
> I'm sympathetic to the human recognizable (but not use small or lower
> value ranges) and regex arguments to utilize a decimal boundary and the
> original draft started there.  An alternate proposal that is not as
> silly as 4B+ but still does not consume a significant portion of the
> total space (if there was widespread concensus in the WG to change the
> existing one, given that we are in LC already) could be:
>
> 4200000000 - 4294967294
>
> Although this is even larger than the existing range, it still is a a
> very small portion of the existing range, and I think no one is
> seriously concerned it's the size of the new range (versus having one)
> is concerning as there is no belief that will correlate to any specific
> behavior.
>
> Jon

I'm sympathetic to the argument too, even though it may not sound like 
it. :)  But, I can't justify something in the 300M range or even the 
100M range in my head.  Hey, 10M is a stretch, but given that I can 
easily come up with scenarios for a few tens of thousands, cranking that 
up 2 or 3 orders of magnitude means we should have to revisit it for 20 
or 30 years.  There would be one exception, if we were to require 
pseudo-random allocation to help facilitate mergers, similar to IPv6 ULA 
in RFC 4193.  Then I could justify a few 100 million in my head, so you 
get a better spreading function.  But nine random digits preceded by a 4 
isn't going to be very human friendly either.  :(

If we did 4B up most everybody is going to just use a few 10 of thousand 
just above the 4B mark.  And I'm not sure 4.2B mark would be any 
different.  Just like most people use 65000-65010 and 65500-65510 and 
some other combinations in the 1023 we have now.

My recommendation is to specify 4280000000-4289999999 for private use, 
and then suggest to the IESG that they have IANA mark 
4278190080-4279999999 and 4290000000-4294967294 as reserved as opposed 
to unallocated.  That gives private use a block of 10M and sets aside 
some 6M for other future special uses.  Who knows what really cool use 
for million or two ASNs some smart kid will come up with in a few year. :)

And if we wanted to provide another smaller but much more human friendly 
range there is another reserved range at 65552 to 131071, maybe take 
100000-129999 out of that range too.  We don't want to go into 130K, to 
help prevent anyone from accidentally going about 131071 and the ranges 
that the RIRs are using.  Then you would have the original 1023, a 
moderate but mostly human friendly block of 30000, and block of 10000000 
that is probably best for programmatic uses.

Just throwing out some ideas.
-- 
================================================
David Farmer               Email: [e-mail]
Office of Information Technology
University of Minnesota
2218 University Ave SE     Phone: [phone]
Minneapolis, MN 55414-3029  Cell: 1-612-812-9952
================================================