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 ]
Carsten Schiefner
ripe-wgs.cs at schiefner.de
Tue Nov 18 17:17:03 CET 2014
Hi Jim, On 18.11.2014 16:34, Jim Reid wrote: >On 18 Nov 2014, at 14:59, Rob Evans <rhe at nosc.ja.net> wrote: >> If they want to sit on a domain that bears a resemblance to the >> company identity, I'll leave that up to them... > > That way lies madness: ripe.$TLD-of-the-week. > > IMO one domain name is enough. If someone can make a convincing case > to use more than that or why ripe.whatever can achieve something not > possible with ripe.net, please speak up. I know at least one TLD that serves a completely orthogonal purpose to any "regular" TLD - and I am sure you know this one too. :-) I'd be almost immediately convinced if the NCC decided to register under this particular TLD - for the services that come with it. Cheers, -C.
- 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 ]