[dns-wg] RIPE NCC DNSSEC trust anchors

On Tue, Nov 18, 2014 at 11:16:19AM +0000, Niall O'Reilly wrote:

>   I'm reading that as a call from one of the co-chairs for (more)
>   voices from the WG, so here's mine.
> 
>   Let's have RIPE.INT removed.

this isn't f*cebook. As a co-chair of this wg I doubt it is reasonable
for the WG to micro manage the NCC in what domain names and which TLD(s)
it uses. It is also not clear to me why the DNS WG would be formally competent
w.r.t. the subject matter.

> > > 4/ Ripen.cc is a historical artifact. RIPE NCC is not currently using it
> > > and we are not planning any future use. Releasing the domain is an
> > > operational decision that we may take in the future.
> > 
> > Just kill it! IMO the domain should get removed from DLV as soon as
> > it is prudent to do so: which probably means immediately. ripen.cc
> > can die on its renewal date. Though these too should be consensus
> > decisions for the WG.
> 
>   Let's have RIPEN.CC removed also.

Again, I doubt that a voting is helpful here.  No matter what, even
if the NCC gave up on the use of "ripen.cc", releasing the domain name
is probably a bad idea.

Also, simply removing those domains without a signed parent doesn't
ultimately help solving the DLV issue.  Why can't a zone be signed
(for reasons of symmetry or streamlined processes) without the TA
being published?

-Peter