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/[email protected]/

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

Nick Hilliard nick at foobar.org
Tue Nov 18 15:38:48 CET 2014

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.

If ICANN has concerns about the delegation, then they should raise them
formally with the RIPE NCC.

If the "registration is out of (current) policy with respect to registrants
in that domain", it's unclear why this is a RIPE NCC problem.  The domain
has been around since 2001 so if there's been a problem, why has it taken
13 years for people to get worked up about it?

Please leave it alone.

Nick

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 ]