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] FW: FW: discussion about rogue database objects
- Previous message (by thread): [routing-wg] FW: FW: discussion about rogue database objects
- Next message (by thread): [routing-wg] FW: FW: discussion about rogue database objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Lutz Donnerhacke
lutz at iks-jena.de
Thu Nov 13 12:29:59 CET 2014
> No, I won't do that! I'm against the methods of resolving "problems" > which are not exist and I will make all my efforts for not allowing the > RPKI to be the only method of doing business. Then you should invest your time and energy to promote other solutions than rPKI. You may start with using DNSSEC for securing routing information ... There was an IETF draft long long ago.
- Previous message (by thread): [routing-wg] FW: FW: discussion about rogue database objects
- Next message (by thread): [routing-wg] FW: FW: discussion about rogue database objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]