[dns-wg] RIPE NCC DNSSEC trust anchors
- Previous message (by thread): [dns-wg] RIPE NCC DNSSEC trust anchors
- Next message (by thread): [dns-wg] {Use of} the INT TLD {by the NCC and others} [Re: RIPE NCC DNSSEC trust anchors]
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
David Conrad
drc at virtualized.org
Thu Nov 13 21:28:32 CET 2014
On Nov 13, 2014, at 7:44 AM, Randy Bush <randy at psg.com> wrote: >> I'd rather not see the RIPE NCC further endorse the DLV technology and >> service by continuing to submit key material there. > > thank you > >> DLV was meant as a temporary deployment aid and might have been a good >> idea at its time. > > or not > > randy > +1 On Nov 13, 2014, at 8:05 AM, Doug Barton <dougb at dougbarton.us> wrote: > 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.) +1 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: <https://lists.ripe.net/ripe/mail/archives/dns-wg/attachments/20141113/f0cbcc8a/attachment.sig>
- Previous message (by thread): [dns-wg] RIPE NCC DNSSEC trust anchors
- Next message (by thread): [dns-wg] {Use of} the INT TLD {by the NCC and others} [Re: RIPE NCC DNSSEC trust anchors]
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]