Re: Example of stupid inconsistencies between registries
Antoin Verschuren <[email protected]>
| Newsgroups | gmane.ietf.provreg |
|---|---|
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 08-03-12 11:52, Mark Elkins wrote: > Once signed, a simple trigger should be enough though? The Registry can > ask via DNSSEC for any new DNSKEY records as then the DNS transaction is > signed (as in the AD bit is set)... OK - It'll still be a DS Record > trigger. We have discussed such a principle some time ago, but it is/will be rejected by the politics of ICANN registrars. In our technical vision, EPP only needs to be used for bootstrapping the original delegation and chain of trust. After that, all technical stuff can be done over (secure) DNS, and EPP is only needed for administrative data. ICANN registrars disagree. According to their contract, ALL changes to the delegation may only be done by submission by the registrar over EPP to the registry, so that they are aware and can intercept technical changes. Even if that means the delegation is technically incorrect. NS changes can also be done over DNS if that is a secure channel, but registrars want to be able to block technical changes when f.e. a bill has not been paid. The motivation they use is that provisioning the registry data then comes from 2 channels, DNS and EPP, and the discussion may arise which one is authoritative. - -- 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) iQEcBAEBAgAGBQJPWJ1mAAoJEDqHrM883Agn5V8H/jXRFzOgnZMFsbVKUcYOC9wF l9g2sZ2BQ/hZZEA3dXLQy6dMiJ+MlnmHSUSow3r1pM59SX3la7gsYmvlKUO+8Rpd OSy/R/7yO09zyO8+Ia5P18LGn2FJ+nnrWY+ARuCoUOCh8DyS/gsoABvDA47p+4hU JvtXVsyg6mppjqocS/d37uQhLqYoLDMqDTtVQz91+UhVkncUcSJrVHtnbkNMIUtF pjSYEq/yMXOcZQrW8HI3avL0UvomZoDMJAmYoynVjy/gSfUlKvw8Lhcv+jAp/hXT 8mLJEKacV6nE5OCYr1kWI3TwDo+U7CjItuDCfRH1D5b8dTGN9CjC3Zw789aOue4= =FaUI -----END PGP SIGNATURE----- _______________________________________________ provreg mailing list [email protected] https://www.ietf.org/mailman/listinfo/provreg