ICANN/GNSO
DNSO and GNSO Mailling lists archives

[ga]


<<< Chronological Index >>>    <<< Thread Index >>>

[ga] Registry Load and WLS: Myth vs. Reality


Hello,

As Chuck failed to answer yes or no as to whether registry load is
still an issue in the WLS debate, I did some checking.

See the most recently released registry report at:

http://www.gtldregistries.org/reports/2003/march_2003.pdf

On page 3, it shows that there's a SLA requirement for the "check"
command of 3 seconds, and for the "add domain" command of 5 seconds.
Verisign's actual performance?? 0.01 seconds for each. 

This means that under the status quo, VGRS has an OVERCAPACITY of 300
to 500 TIMES the required level of performance. Sure sounds like
they're bursting at the seams....NOT! It's not whether the glass is
half-full or half-empty.....the glass has a droplet in it, yet Verisign
would have you believe it's the Pacific ocean!

Given the introduction of RGP on January 25th, there were no domain
drops for a 30 day period, roughly all of February 2003. This gives us
a great opportunity to see what happens to the registry without the
"strain" of registrars attempting to catch deleted domains. Page 8 of
the PDF shows that the average daily transaction range for February
2003 is only *marginally* lower than that of January 2003. Indeed, when
the drops resumed in March 2003, the average daily transaction range
was even *lower* than that of February 2003!

Thus, it's clear that excessive transaction load at the registry level
is a clear myth, used to "frame" the debate and gain sympathy from some
technocrats at ICANN with only cursory knowledge of the true facts. 

The only real registry load is the load of BS that some of the VGRS
employees spew, to confuse decision-makers.

Sincerely,

George Kirikos
http://www.LOFFS.com/
--
This message was passed to you via the ga@dnso.org list.
Send mail to majordomo@dnso.org to unsubscribe
("unsubscribe ga" in the body of the message).
Archives at http://www.dnso.org/archives.html




<<< Chronological Index >>>    <<< Thread Index >>>