we. LIR de.government, had already a discussion about secure and encrypted
communication with RIPE NCC.
I would propose not to limit the secure channels to RIPE NCC, but to support
them all. In case of E-Mail PGP / GPG and S/MIME. Encrypted (bidirectional)
e-mail should be the default like it is for most of the websites with SSL.
Second question is then how 3rd party data is secured while it is processed by
RIPE NCC? A transparent data protection concept of RIPE NCC could support trust.
Perhaps it needs a person exclusively responsible for these issues at RIPE NCC?
Best regards / Mit freundlichen Grüßen
Cassini Consulting GmbH
T +49 (0) 151 11 44 38 75
F +49 (0) 211 65 85 41 34
Think green - keep it on the screen!
Cassini Consulting GmbH | Bennigsen-Platz 1 | 40474 Düsseldorf
Geschäftsführer: Sven Wiedenhöfer | Michael Schmitz
Sitz der Gesellschaft: Düsseldorf | Registergericht Düsseldorf HRB 53235
Guiding ahead - Cassini ist Management- und Technologieberatung
Von: ripe-list [mailto:ripe-list-boun...@ripe.net] Im Auftrag von Andy Davidson
Gesendet: Freitag, 2. März 2018 08:53
An: Shane Kerr <sh...@time-travellers.org>
Betreff: Re: [ripe-list] RIPE NCC PGP-Key expired
Good morning, Shane, all —
On 1 Mar 2018, at 21:48, Shane Kerr <sh...@time-travellers.org> wrote:
> One might say that since you are the first to notice and report this, almost
> a month after it expired, perhaps we should abandon PGP as a communication
One might say that since Dominic was the first to notice, almost a month after
it expired, perhaps we already HAVE.