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 18:44:41 CET 2014

 Wilfried Woeber writes:

 > 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.  [...] >
 > Please leave it alone.
 > 
 > In order to achieve or conserve - what?
 > 

Energy.

	jaap

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.

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