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:34:52 CET 2014

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.

• 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 ]