Re: Standard Extensions
Antoin Verschuren <[email protected]>
| Newsgroups | gmane.ietf.provreg |
|---|---|
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 22-08-12 13:58, Patrik Fältström wrote: > If your question is "what where you forced to implement differently > with different registries" the answer is so far for me: > > - DNSSEC, clarification if DS or DNSKEY is to be passed to > registry Apart from the DS/DNSKEY question for the delegation, there is also a request to have an EPP extension for registrars to send ZSK information (a KEY) to be relayed by the registry in case of a dns-operator change (http://tools.ietf.org/html/draft-koch-dnsop-dnssec-operator-change-04). As this is a rather new topic, after some registries made their initial decision to use DS in stead of DNSKEY, I think this might influence consensus on using DNSKEY. We actually need the "key to be relayed" as an EPP extension to facilitate automated DNSSEC secure transfers, and will implement it regardless of standardisation. But if it needs a request: We would like the "key to be relayed" as a standard EPP extension. It contains a KEY. - -- Antoin Verschuren Technical Policy Advisor SIDN Meander 501, PO Box 5022, 6802 EA Arnhem, The Netherlands P: +31 26 3525500 F: +31 26 3525505 M: +31 6 23368970 mailto:[email protected] xmpp:[email protected] http://www.sidn.nl/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEcBAEBAgAGBQJQNM2eAAoJEDqHrM883AgnYDAH/0Q/DtSrt4PPxxHGYM1CwwG9 9w79Vqp0t1K7H5bPaUUBF9uggzwxD341FPjqbRz2EJM9Djwj9L0WjqLZ7WmACH7U Lo4W7S1NvLlX3Vcw7VvCsfoqaPqOfV7nD0UlxqArMsN3aLR/m1EUJXnhqvMEZV96 r+VhxYSNjkLIoYRbyjXmzKPsTd2SmfzeUfqE5HheKk93OA7N+2m/ERNnzyCj2zHo RKS+arKJs+lRyNoNTdfgYKmvaconvFRhfREtWEXrlJJ8Kb2Srz4oP6MnqKNWQ41M Ifc2XTE24evxUSP4D+vxCVTFkYXcHjZUuoJocvI1BggQwwqS8S+dqNTgcar+Eds= =Jp+n -----END PGP SIGNATURE----- _______________________________________________ provreg mailing list [email protected] https://www.ietf.org/mailman/listinfo/provreg