[dns-wg] RIPE NCC DNSSEC trust anchors

Romeo,

On Nov 17, 2014, at 7:49 AM, Romeo Zwart <romeo.zwart at ripe.net> wrote:
> 2/ The RIPE NCC has been publishing this key material out of band for
> historical reasons. If there is a consensus in the WG that this is no
> longer needed, or even undesirable, we are happy to phase out the use of
> the DLV.

Yay!

> 3/ RIPE NCC has been assigned ripe.int in the early 2000's. We are
> currently not using ripe.int, other than by redirecting to ripe.net. If
> the community advises the RIPE NCC to request IANA to sign .int, we can
> spend some effort on this, but we'd like to follow up on this separately.

Since .INT is currently not signed and RIPE is not using RIPE.INT, signing RIPE.INT would seem to be a bit ... silly (particularly in the light of #2).

Since RIPE is not using RIPE.INT and that registration is out of (current) policy with respect to registrants in that domain, is there any reason why RIPE-NCC doesn't simply request RIPE.INT to be removed from the INT zone?

Regards,
-drc

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: </ripe/mail/archives/dns-wg/attachments/20141117/129e4b71/attachment.sig>