Comments on Verisign wildcard additions to the root DNS
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Dear Sirs,
My opinion is that Verisign has grossly overstepped their boundaries by
instituting the wildcard for non-existent domains.
Verisign's actions have caused numerous problems. A few of our concerns
are given here.
My public e-mail server has been disrupted by their actions.
Some of my clients have trademark concerns arising from Verisign's
misuse of domain names that don't yet exist. We feel that Verisign
benefits financially in a way that no one else is able, and much of this
benefit will be from a direct mis-use or outright abuse of corporate
trademarks. Even our attempts to remedy the situation by purchasing all
possible mis-spellings of corporate domains benefits Verisign by way of
the registration fee they given as the registry maintainer, even if we
purchase these domains from another registrar. This double jeopardy
should not be allowed to exist.
Verisign should not be Registry maintainers AND Registrars. With this
action they have proved they are unsuited to be Registry maintainers so
they should be forced to play on the same field as all other registrars,
if they are even allowed to retain their status of registrar.
We are also concerned about the way Verisign claims to be handling
mis-directed mail. The security implications are mind-boggling and
Verisign's bluster that they are not going to trap or mis-appropriate
the data that may exist in that bouncing e-mail cannot be given any
credence what-so-ever given their apparent disregard for the ethical
standards the world expects.
We are through dealing in any way with Verisign. My company will advise
all our clients to refrain from doing business with Verisign. In fact
that has been our policy for nearly three years now, but only in a
passive since. We made our recommendations with out condemning Verisign.
~From this point on, we will be _actively_ advising all our clients to
cease all business relations with Verisign
- --
Diana Brake
Crest Communications, Inc.
http://www.crestcomm.com/diana/gnupg.txt for GnuPG public key
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE/djDNLb2jcLzmaqQRAjxVAJ9Jguk60/moMPYcXgoEFTNfZtpVpwCgjMFj
AfVN6jcsEFXtdtH2UVn3OWY=
=Xgrv
-----END PGP SIGNATURE-----