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: discussion about rogue database objects
- Previous message (by thread): [routing-wg] [training] RIPE NCC Training Courses January-March 2015
- Next message (by thread): [routing-wg] FW: discussion about rogue database objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
poty at iiat.ru
poty at iiat.ru
Mon Nov 10 14:07:33 CET 2014
-----Original Message----- From: routing-wg-bounces at ripe.net [mailto:routing-wg-bounces at ripe.net] On Behalf Of Ronald F. Guilmette Sent: Monday, November 10, 2014 1:56 AM To: routing-wg at ripe.net Subject: Re: [routing-wg] discussion about rogue database objects In message <545FDE27.7030702 at velea.eu>, Elvis Daniel Velea <elvis at velea.eu> wrote: >*Regarding the future process:** >* >I do not think it will be that easy to come up with a process. RPKI may >not be available for legacy (or independent) resources in all the >regions. I think this means the RIRs will first need to speed up the >deployment of RPKI for all the resources in their registries... ... Can anyone speak to this? What resources in what registries cannot currently be covered by RPKI? If the answer is "none", then there is no problem with requiring that right now, correct? ---------------- There are actually not only technical matters, but sort to say political, law, ... As about what resources currently can't be covered by RPKI - they had already been mentioned: legacy as an example. Regards, Vladislav
- Previous message (by thread): [routing-wg] [training] RIPE NCC Training Courses January-March 2015
- Next message (by thread): [routing-wg] FW: discussion about rogue database objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]