This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/routing-wg@ripe.net/
[routing-wg] RPKI validation problem
- Previous message (by thread): [routing-wg] RPKI validation problem
- Next message (by thread): [routing-wg] RPKI validation problem
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Matthias Waehlisch
m.waehlisch at fu-berlin.de
Mon Dec 16 11:43:37 CET 2019
[1] and [2] use different Trust Anchors. which prefix do you check? Cheers matthias On Mon, 16 Dec 2019, Gondim via routing-wg wrote: > Dear all, > > Friday, here in Brazil, the RPKI was enabled. We have published our ROAs > and are being validated in several places but we found a divergence. > When we query our AS on this link [1] it appears to be valid but when we > query our AS on this link [2], it appears as unknown. > > Is there any difference between the tools that might be causing this? > > [1] http://localcert.ripe.net:8088/bgp-preview > > [2] https://rpki-validator.ripe.net/bgp-preview > > Thanks and best regards. > > -- > ⢀⣴⠾⠻⢶⣦⠀ Marcelo Gondim > ⣾⠁⢠⠒⠀⣿⡁ Sysadmin - https://www.linuxinfo.com.br > ⢿⡄⠘⠷⠚⠋ DA04 922E 78B3 44A5 3C8D 23D0 8DB5 571E E151 4E19 > ⠈⠳⣄⠀⠀⠀⠀ Logic will get you from A to B. Imagination will take you everywhere. (Albert Einstein) > > -- Matthias Waehlisch . Freie Universitaet Berlin, Computer Science .. http://www.cs.fu-berlin.de/~waehl
- Previous message (by thread): [routing-wg] RPKI validation problem
- Next message (by thread): [routing-wg] RPKI validation problem
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]