Hello List, Few days ago I found something weird that I would like to share with you. I might be doing something wrong or probably I found a bug. I installed quagga with RPKI support and I'm using RIPE NCC Validator. The case is that when checking the network 200.85.64.0/20 in Quagga it appears as Invalid. I think it should be Valid as you can check yourself using he.net whois. Anyhow, I don't think there should be two different rpki states out there. Here is the output of what I found. 1) 200.85.64/20 prefix: a) In Quagga (Invalid): I*> 200.85.64.0/20 200.7.84.2 0 64512 28007 6939 7908 i b) In he.net (Valid): root@squat:/tmp# whois -h whois.bgpmon.net " --roa 7908 200.85.64.0/20" 0 - Valid ------------------------ ROA Details ------------------------ Origin ASN: AS7908 Not valid Before: 2013-12-24 06:52:26 Not valid After: 2018-12-24 06:52:26 Expires in 4y210d3h5m20.4000000059605s Trust Anchor: repository.lacnic.net Prefixes: 2001:1350::/32 (max length /48) 200.85.64.0/20 (max length /24) I checked in the ROA section using the RIPE Validator and the prefix has two valid ROAs, one correctly indicating AS7908 as origin and other indicating AS 52358. This scenario is permissible. I found this case using the Quagga from https://github.com/rtrlib/quagga-rtrlib/tree/feature/rtrlib I don't recall this behavior in another version but I could pass it without noticing it. Am I doing something wrong?, did I miss something? is it a bug? Thanks, Alejandro,