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

[Jared Mauch <[e-mail]>]

On Thu, Dec 20, 2012 at 10:47:54AM -0600, David Farmer wrote:
> 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.

	I think this poses the need to have vendors replace regex
with something where you can specify a list or range of the integers
you wish to match.

	I have wanted to tie prefix to the integer string encoded in AS_PATH
for some time and there is no effective way to do this.

	- jared

-- 
Jared Mauch  | pgp key available via finger from [e-mail]
clue++;      | http://puck.nether.net/~jared/  My statements are only mine.