Re: getting TLDs to fix other people's problems

A few examples of where the world is from my perspective:

As long as...

- ...policy in some registries require NS records for registrations of a domain (i.e. no difference between registration and delegation), there will be lame delegations

- ...policy in some registries require NS records for registrations of a domain (i.e. no difference between registration and delegation), there will be proxy registrations and registrants that lie

- ...data sent to a registry/registrar, regardless of data protection legislation, is available freely "on the net", there will be proxy registrations and registrants that lie

- ...policy make it impossible to register domain names in some registries, there will be proxy registrations to circumvent the very same rules

- ...there is no agreement on what data to send to registries for DNSSEC signed zones, it will be very hard to get lots of DNSSEC signed zones

- ...policy in some registries that the registrant should contact them directly, registrars will lie to the registry during registration period so that they can give the registrant the service the registrant ask for

I.e. the world out there is so messy that what you talk about is a light warm breeze...

Just the notation of "the TLDs" to fix things is confusing to me. Does "the TLD" imply the registry, whoever is the administrative contact for the TLD in the IANA database, or the backend provider, or the technical contact or the one holding the whois record of the delegation the question is about, or...

   Patrik

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

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iD8DBQFUllvKrMabGguI180RAiQgAJ9/cvUXmhjSvrO13lKSn99IGNCZTgCfV5Un
9+Nrh2anRNvnKmlW7d3CMys=
=OpLX
-----END PGP SIGNATURE-----