On Mon, Aug 2, 2010 at 9:13 PM, Eduardo Santoyo <eduardo@cointernet.com.co> wrote:
While, of course, each ccTLD represents the interests of a sovereign nation state,
The DNS is not the UN, and the UN is not the DNS.
. implemented a "thick whois" and restricted the availability of proxy Registrations;
== pete@tango:~$ whois apple.co == This TLD has no whois server, but you can access the whois database at == https://www.nic.co/ ie no thick neither thin. HTTPS to www.nic.co which is a CNAME to cointernet.com.co 205.186.131.224 returns: == There is a problem with this website's security certificate. == == The security certificate presented by this website was not issued by a trusted certificate authority. == The security certificate presented by this website was issued for a different website's address. == == Security certificate problems may indicate an attempt to fool you or intercept any data you send to the server. Seems that the correct URL is http://whois.co/ or http://www.whois.co/. https://whois.co also has a certificate problem.
We have and will continue to work hard to ensure that .CO is a good trustee of both the local and global Internet community. Discussions such as these only serve to help us to focus and refine our efforts over time -- and in the spirit of constant and never-ending improvement -- your continued input is welcomed and encouraged.
You should seriously consider telling your registrars to stop misleading end users by promoting dotCO as the new dotCOM for example. As I said before the fuss is not about the changes and improvements on the .CO ccTLD management and opening of the domain to everybody for which I congratulate you and the rest of the team and people involved in a complicated process that in my personal opinion was fair and transparent. Regards Jorge