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/dns-wg@ripe.net/

[dns-wg] RIPE NCC DNS operations update

• Previous message (by thread): [dns-wg] RIPE NCC DNS operations update
• Next message (by thread): [dns-wg] Experiences in Deploying and Scaling Support for Encrypted DNS

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Jim Reid jim at rfc1035.com
Wed May 11 14:21:25 CEST 2022

> On 11 May 2022, at 13:20, Anand Buddhdev <anandb at ripe.net> wrote:
> 
> Our main reason is that we do not have separate storage for the KSKs and ZSKs. They were all stored together on the signer. Additionally, our ECDSA KSKs and ZSKs were of the same size. Therefore, there is no additional protection offered by separating them, and so it is reasonable to use a CSK.

Makes sense. Like everything else you do. Thanks Anand.

• Previous message (by thread): [dns-wg] RIPE NCC DNS operations update
• Next message (by thread): [dns-wg] Experiences in Deploying and Scaling Support for Encrypted DNS

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ dns-wg Archives ]