http://www.icann.org/topics/dns-sta...per-06feb08.pdf
Here is the latest draft on what is being done by Icann at this time. Feel free to submit comments on the possible implications. Any input I am sure is greatly appreciated.
As for me I remain steadfast on the principles of DNS security and the de- exploitation of the inherent vulnerabilities that exist in the current schema.
One just has to remember the dos attacks of 2002 or 2004 or even 2007 to und3rstand what a sudden surge of data directed toward a root server can do.
I still do not believe that there is enough redundancy in the network at this time to allow for the mass influx of all of the new gcctlds and file extension domains along with the increase in traffic. (Its my opinion deal with it)
ICANN suggest themselves that this may be an issue but only goes into an operational level. They are basing their data on the testing of only 2 servers in a beta protocol environment on stable tested servers. They are putting their faith in anycasting (which has it limitations and issues as well as set up).
The true test is going to come with the full implementation of all the new (tld) across the world. I don't think anyone really knows at this time what the total effects are going to be.
It has been too often that an admin or an organization has prepped for an event without sound data and just theory to back it up leading to multiple problems.
No one likes the speed with which idn.idn is taking but in reality it is probably very necessary.
Then again what do I know. I gave up my network engineering cert paths in 2003 after 10 years to pursue medicine.
Going back to the thread topic. Some of those single character domains aren't worth regging. I have many from some time ago. They get no traffic except for the occasional bot. If things go as they say they are I would let them drop.
