| At Large Membership and Civil Society Participation in ICANN |
|
|
|
|
|
This discussion has been archived.
No new comments can be posted.
|
The DoC and XXX
|
Log in/Create an Account
| Top
| 72 comments
|
Search Discussion
|
|
The Fine Print:
The following comments are owned by whoever posted them.
We are not responsible for them in any way.
|
|
 |
Root Server Operators Planning to Add .XXX Anyway
With or without ICANN, the Root Server operators are planning to add .XXX to make it more widely used. About 180,000,000 people, mostly in the .US currently can access it.
Now that there are thousands of root servers all around the world, it is just a matter of time before more and more add .XXX. As it is entered, it spreads like a virus.
http://www.isoc.org/isoc/conferences/wsi s/wgigcomments.shtml
ROOT SERVERS – STABILITY THOURGH DIVERSITY8
A clear benefit of the WGIG process has been the opportunity to share how things such as the root name server system operates. For instance, it now seems to be widely understood that the root name server operators do not determine the content of the root zone file, that no Internet traffic passes through the root name servers at all, and that these servers do not route Internet traffic. Furthermore, many root server operators now provide service from multiple locations using a method called "anycast" which increases the availability and resilience of the DNS system while providing increased benefits “in-region”. In fact, as of December 2004, there were root name servers being operated at more than 80 locations in 34 countries, most of them outside the United States of America. And, this number has grown considerably over the last 6 months and will continue to do so.
This diversity and the distributed authority has been a critical element of the reliability of the root name service. We are happy to see that a consensus seems to be emerging that today’s arrangements have significant value to the Internet, as it is far from clear what value would be added by creating a new authority to oversee the root name server system. In fact, there is a real risk that this could weaken the robustness of the current operations by creating a single point of failure, or a potential target for capture and abuse. The costs of such an exercise, both in direct terms and in terms of the time and energies of those who would need to participate, do not appear to be sufficiently justified.
|
|
|
[ Reply to This | Parent
]
|
|
|
|
1 reply beneath your current threshold. |

Privacy Policy: We will not knowingly give out your personal data -- other than identifying your postings in the way you direct by setting your configuration options -- without a court order. All logos and trademarks in this site are property of their
respective owner. The comments are property of their posters, all the rest © 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 by ICANNWatch.Org. This web site was made with Slashcode, a web portal system written in perl. Slashcode is Free Software released under the GNU/GPL license.
You can syndicate our headlines in .rdf, .rss, or .xml. Domain registration services donated by DomainRegistry.com
|