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 17:38:36 CET 2014

On 18/11/2014 16:27, Jim Reid wrote:
> That said, I think it is reasonable for the community to decide
> "ripe.foo is no longer used or needed. Please let it die.".

just as reasonable as if the ripe ncc management team (or board) were to
decide that as this is purely an operational matter, that the decision
would be theirs entirely.  It's not helpful for the ripe community to
micromanage the ncc.

The entire thread about whether or not to delete ripe.int falls firmly into
the category of micromanagement.  Please can we let them get on with their
jobs without interfering?

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 ]