[j-nsp] Please push Juniper to implement RFC6907

Weber, Markus Markus.Weber at kpn.de
Thu Oct 10 06:25:40 EDT 2019


> If I'm not mistaken, the RIPE validator uses
> 	http://www.ris.ripe.net/dumps/
> which lists for the two /24 test prefixes:
> 	{517}           194.45.182.0/24 242
>	{517,12469}     194.45.183.0/24 241
> and seems to use - Asn.parse of net.ripe.ipresource.Asn - when loading
> this dump. Asn.parse uses "(?:AS)?(\\d+)(\\.(\\d+))?" to match on ASes
> ... and returns 517? Just a quick check ... not that good with Java ...

Wrong reading. The parser for the dumps in the RIPE validator matches input
lines against
    "^\\s*([0-9]+)\\s+([0-9a-fA-F.:/]+)\\s+([0-9]+)\\s*$"
- above lines don't match and thus are not seen at all in the BGP preview
(these announcements simply don't exists in this preview ... with the
first reading they should have been visible).

Thus the absence of these announcements in the RIPE validator are not 
because RFC6907 ... 

> But let me publish a ROA for 194.45.183.0/24-24,AS517 ... then we know.

Still in to see if Cisco XR would not accept this.

Sorry again for the non j-nsp noise, should shift this conversation away
from here ... but I couldn't leave this wrong-with-first-shot code reading
uncommented.

Markus
-- 
AS286 - for the time being



More information about the juniper-nsp mailing list