Re: [Idr] WGLC on draft-ietf-idr-as-private-reservation-00 concluded, extended to consider ASN range

[David Farmer <[e-mail]>]

On 12/19/12 08:57 , Jon Mitchell wrote:

> Maybe some others would like to weigh in on one of the above options now
> that it's a focused discussion (otherwise I plan to make the small edits
> discussed in previous threads and move the start of range to
> 42xxxxxxxx so we can close this out...)

OK, I'll relent, 4.2B it is.  But, we need to be clear about why we are 
selecting this; which is to make regexp matching of private use ASNs 
easier.

The idea is to allow the simple regexp of 42???????? to match private 
use ASNs.  However, this makes a few assumptions.

1. While not part of the Private Use ASN range, the intended regexp also 
matches the reserved ASN 4294967295, and therefore 4294967295 can never 
be a valid ASN in an AS_PATH.

2. The intended regexp would select ASNs beyond the 32bit ASN range, if 
they were valid, that is 4294967296 through 4299999999. Therefore, if 
the ASN range were ever expanded to make these valid ASNs, the private 
use ASN range would also need to be expanded to be included these ASNs 
as well.

If we want to use 4.2B as the starting point to simplify regexp matching 
of the private use range then these assumptions need to be explicitly 
stated in the draft.

Thanks.
-- 
================================================
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
================================================