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 ]
Jaap Akkerhuis
jaap at NLnetLabs.nl
Tue Nov 18 21:34:05 CET 2014
Wilfried Woeber writes: > Thanks, Jaap! > > Jaap Akkerhuis wrote: > > [...] > > PS. The last time I looked, all contracts with (g)TLD registries > > has various names reserved, among them, RIPE. So, default RIPE.$TLD > > is reserved. I guess that is to stop delegations like ripe.org. > > Fair enough. > So we'll pay for some 1000 or more RIPE.$new-gTLD reservations pretty soon now? Nope. I think the idea to have this "verboten to delegate list" is that obe doesn't has to do defensive registratins. So the ICANN contracts protects RIPE for "abuse of ripe's domain label". jaap
- 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 ]