Re: Example of stupid inconsistencies between registries

On 5 mar 2012, at 16:05, Andrew Sullivan wrote:

> Your complaint seems to be that a registrant has to provide different
> data for different names.  I fail completely to see why that is a
> problem.  (To put this slightly differently, you seem to be arguing
> that a registrant shouldn't need to understand that example.com and
> example.org are different domains.  This seems a little bit at odds
> with your views on the many things people call "variants".)

No, I am just talking about how to design for example a web interface and instructions to the one that is to paste data into it. You have a number of fields, and different fields are mandatory depending on what TLD it is.

Same with for example an API. If you run a DNS hosting, would it not be easier if you can pass the same information to all registrars, and not have to do different depending on which one it is?

I am just talking about how much more difficult it is for everyone but the registry if it asks for something else than the DS, and in many cases it can also fetch the Key from the auth server if it want to validate the DS... Part from some cases where one want DS pre-published in the parent zone when the parent simply must trust whatever the registrar send anyway as it can not validate the data passed to it. As nothing is in the child zone that the data can be validated against.

   Patrik

_______________________________________________
provreg mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/provreg

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)

iD8DBQFPVTbWrMabGguI180RAiPtAJ9RHGqcqYkSm80DsA7SO9klvX2KVACdFYcB
j4rbWEW7z//sUr0siid+tpw=
=d24i
-----END PGP SIGNATURE-----