[j-nsp] asn32: as-path formatting ?

[kura at iij.ad.jp]

From: kura at iij.ad.jp
Date: Sat May 17 2008 04:31:56 JST
>
> Hello,
> 
> 'asdot' representation isn't supported.
> 
> http://www.juniper.net/techpubs/software/junos/junos91/swconfig-policy/defining-as-path-regular-expressions.html
> "Beginning with JUNOS Release 9.1, the range for AS numbers has been
>  extended to provide BGP support for 4-byte AS numbers as defined in
>  RFC 4893, BGP Support for Four-octet AS Number Space. The range that
>  you can now configure is from 1 through 4,294,967,295."
> 
> AS3.3 (asdot) == AS196611 (asplain)
> 
> 'as-path as33 "196611$"' will work for your case.

Sorry. 'as-path as33 ".* 196611"' is correct.

> Regards,
> -- 
> Tomohiko Kurahashi <kura at iij.ad.jp>
> 
> 
> From: snar at paranoia.ru
> Date: Fri May 16 2008 23:43:07 JST
> > 
> > Hi!
> > 
> > Since JunOS 9.1, Juniper supports 32-bit AS Numbers (RFC 4893), and release 
> > notes states that: 
> > <cite>
> > Support for 4-byte AS numbers is also extended to the AS extended-community 
> > attribute and AS-path regular expressions 
> > </cite>
> > but documentation on defining AS Path regular expressions does not provide 
> > any examples using 32-byte asn's. 
> > 
> > So, I'm just curious, how should they be formatted ? 
> > 
> > For example, If I want to filter paths originated by Gert Doering's AS3.3,
> > should I set up filter as 'as-path as33 "3.3$", or it will be interpreted
> > by old rules as '<anything> 3 <any as> 3' and I need to use some other 
> > syntax ? 
> > 
> > PS: and, Gert, thanks for providing AS3.3, AS-SPACENET and route-object
> > with origin: AS3.3 for real-life testing :)