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/[email protected]/
[routing-wg] New on RIPE Labs: Resource Certification (RPKI) Data Quality and Usage
- Previous message (by thread): [routing-wg] New on RIPE Labs: Resource Certification (RPKI) Data Quality and Usage
- Next message (by thread): [routing-wg] New on RIPE Labs: Resource Certification (RPKI) Data Quality and Usage
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Randy Bush
randy at psg.com
Fri Feb 24 11:18:40 CET 2012
ok, so that was not what one would call a delicate statement of the problem. :) my apologuies to alex. he just finished applying the clue by four in IM. of course, there is a serious problem he is trying to address. long fixed, but in early versions of the ncc and rpki.net software, when you created a roa, it did not tell you "whoopsie, if you create this one the following bgp announcement we see in today's global routing data woule be invalidated. do you really want to do this?" so folk have created a lot of roas that are really ill-advised. alex says he sent email to those folk to ask them to fix things. very very low response rate. there are real routers on the real net running rpki-based origin validation software. those with funky roas can not get past them. as they are few and not (yet) core, folk will not notice. but the frog will be boiled. so how do we dig out of this hole? i have some ideas, but i am even more bored with hearing me than you are. randy
- Previous message (by thread): [routing-wg] New on RIPE Labs: Resource Certification (RPKI) Data Quality and Usage
- Next message (by thread): [routing-wg] New on RIPE Labs: Resource Certification (RPKI) Data Quality and Usage
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]