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

[Jon Mitchell <[e-mail]>]

On Thu, Dec 20, 2012 at 01:07:19PM -0500, Jared Mauch wrote:
> On Thu, Dec 20, 2012 at 12:50:46PM -0500, Jeff Wheeler wrote:
> > On Thu, Dec 20, 2012 at 12:04 PM, Jared Mauch <[e-mail]> wrote:
> > >         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.
> > 
> > This already exists in major implementations.  Most of us are so used to
> > how regexps work in other environments, we don't realize there is more than
> > one way.  For example, on a Juniper box, do this:
> > root@Juniper> show route aspath-regex ".* [3000-3999] .*" terse
> >  ... matches plenty of routes like you'd hope ...
> > 
> > Similar thing works on Cisco.  Unfortunately the regexp engines used for
> 
> 	Not likely:
> 

This is my experience as well, I believe that was XR output which even
has the CLI say ios-regex for their as-path filters even, implying this
is true for most if not all Cisco implementations.  The range operator
appears to be a single character/digit function only.  I agree better
tools in general are warranted from lot's of vendors but don't think
this document is the right place for specifying those.

Jon