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 DNSSEC trust anchors
- Previous message (by thread): [dns-wg] RIPE NCC DNSSEC trust anchors
- Next message (by thread): [dns-wg] RIPE NCC DNSSEC trust anchors
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Lutz Donnerhacke
lutz at iks-jena.de
Tue Nov 18 22:38:02 CET 2014
* Nick Hilliard wrote: > On 18/11/2014 11:16, Niall O'Reilly wrote: >> Let's have RIPE.INT removed. > > tbh, I see no reason to remove ripe.int. > > If ICANN has concerns about the delegation, then they should raise them > formally with the RIPE NCC. I second that. And for the DLV issue, I'd like to see any zone, which can't be validated straight from the root (following the DS chain), ahandles in the following way: 1) put the validation info in a DLV (i.e. ISC). 2) push as hard as possible to get the missing zones signed. 3) remove the DLV as soon as the DS chain is complete. And forget about ripen.cc. If you think, this is a geeky idea, apply for the community TLDs .NCC as well as .RIPE.
- Previous message (by thread): [dns-wg] RIPE NCC DNSSEC trust anchors
- Next message (by thread): [dns-wg] RIPE NCC DNSSEC trust anchors
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]