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 ]
Jim Reid
jim at rfc1035.com
Tue Nov 18 16:22:00 CET 2014
On 18 Nov 2014, at 14:59, Rob Evans <rhe at nosc.ja.net> wrote: > Isn't this really, as Romeo puts it, "an operational decision" for the RIPE NCC? Er no. It's a decision for the community which domain names it needs or wants to use to identify itself. After all the NCC should respond to the needs of the RIPE community and the NCC membership. It's an operational matter for the NCC how to register those domain names, which registrar(s) to use, provision the names, choose the name servers, etc, etc. YMMV. Nobody here knew about ripe.int until recently and it doesn't seem to be used. Since it does not appear to have community support -- for some definition of both community and support -- the case for retaining the domain is poor at best.
- 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 ]