[dns-wg] RIPE NCC DNSSEC trust anchors

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 11/13/14 6:54 AM, Anand Buddhdev wrote:
| Dear colleagues,
|
| Most of the zones that the RIPE NCC signs with DNSSEC have trust
| anchors in their parent zones, with the exception of these three
| zones:
|
| 151.76.62.in-addr.arpa ripe.int ripen.cc

As others have already pointed out, I would love to see explanations
of why the first and third zones cannot have proper trust anchors.

The NCC should simply release ripe.int, as the historical reasons for
it no longer apply. (FWIW, same goes for apnic.int. None of the other
RIRs have similar domains.)

Doug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJUZPMDAAoJEFzGhvEaGryE3PQIAL1pP7xmGW69C6AC9VzJbupZ
068Dau7lR9RiqXpPPe+sZdpMwXs3Q1Bf+aa8rZ6CNcQw/fTuGYtWd9f9x04DhVgo
dIvNctoxSf0PHbGtCqJ/9pb8a+r29wkY67JwKgNy30x5SGg/Z3yMoit49ftD3DqI
bMfhWL1037J6YuXz7UnaRWe52OhdbPDVMVO1J9jEV8dWqFcO1DDiP2ATWG3YQQ/l
mDSxo7WG9Oja9mgk1zMjldc0NJo1XqmrJRnsy/k6hEkG/F+QJdIWMNH8VDqZC3wB
6l54wvljRgVEbNeZc5ToVGDoWY+nsQ3wJvA+GDkLNjpdzwa1TAXOeoJMP1UT/VM=
=vmmW
-----END PGP SIGNATURE-----