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 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] RPKI Data Quality and Usage
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Carlos Martinez-Cagnazzo
carlosm3011 at gmail.com
Fri Feb 24 18:37:09 CET 2012
Hello, This is Carlos from LACNIC. We are seeing the same poor RPKI data quality in our region and we share the same concerns that Alex has expressed. Currently our hosted system *does not* renew anything automatically. It will send automatic reminders when expiration times are near, but that's just about it. ROA upkeep is left to the users. The system does not prevent users from creating ROAs with expiry times 100 years in the future, although no one seems to ever change the default value of two years. The most common operational mistake we are seeing has to do with failure to create covering ROAs for BGP downstream customers while having too long maxLen values in the upstream ROAs. While I have personally contacted some of our members regarding the bad ROAs, we have so far met with limited success. Warm regards Carlos
- Previous message (by thread): [routing-wg] New on RIPE Labs: Resource Certification (RPKI) Data Quality and Usage
- Next message (by thread): [routing-wg] RPKI Data Quality and Usage
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]