ICANNWatch
 
  Inside ICANNWatch  
Submit Story
Home
Lost Password
Preferences
Site Messages
Top 10 Lists
Latest Comments
Search by topic

Our Mission
ICANN for Beginners
About Us
How To Use This Site
ICANNWatch FAQ
Slash Tech Info
Link to Us
Write to Us

  Useful ICANN sites  
  • ICANN itself
  • Bret Fausett's ICANN Blog
  • Internet Governance Project
  • UN Working Group on Internet Governance
  • Karl Auerbach web site
  • Müller-Maguhn home
  • UDRPinfo.com;
  • UDRPlaw.net;
  • CircleID;
  • LatinoamerICANN Project
  • ICB Tollfree News

  •   At Large Membership and Civil Society Participation in ICANN  
  • icannatlarge.com;
  • Noncommercial Users Constituency of ICANN
  • NAIS Project
  • ICANN At Large Study Committee Final Report
  • ICANN (non)Members page
  • ICANN Membership Election site

  • ICANN-Related Reading
    Browse ICANNWatch by Subject

    Ted Byfied
    - ICANN: Defending Our Precious Bodily Fluids
    - Ushering in Banality
    - ICANN! No U CANN't!
    - roving_reporter
    - DNS: A Short History and a Short Future

    David Farber
    - Overcoming ICANN (PFIR statement)

    A. Michael Froomkin
    - When We Say US™, We Mean It!
    - ICANN 2.0: Meet The New Boss
    - Habermas@ discourse.net: Toward a Critical Theory of Cyberspace
    - ICANN and Anti-Trust (with Mark Lemley)
    - Wrong Turn in Cyberspace: Using ICANN to Route Around the APA & the Constitution (html)
    - Form and Substance in Cyberspace
    - ICANN's "Uniform Dispute Resolution Policy"-- Causes and (Partial) Cures

    Milton Mueller
    - Ruling the Root
    - Success by Default: A New Profile of Domain Name Trademark Disputes under ICANN's UDRP
    - Dancing the Quango: ICANN as International Regulatory Regime
    - Goverments and Country Names: ICANN's Transformation into an Intergovernmental Regime
    - Competing DNS Roots: Creative Destruction or Just Plain Destruction?
    - Rough Justice: A Statistical Assessment of the UDRP
    - ICANN and Internet Governance

    David Post
    - Governing Cyberspace, or Where is James Madison When We Need Him?
    - The 'Unsettled Paradox': The Internet, the State, and the Consent of the Governed

    Jonathan Weinberg
    - Sitefinder and Internet Governance
    - ICANN, Internet Stability, and New Top Level Domains
    - Geeks and Greeks
    - ICANN and the Problem of Legitimacy

    Highlights of the ICANNWatch Archive
    (June 1999 - March 2001)


     
    This discussion has been archived. No new comments can be posted.
    ICANN Misses Critical MoU Deadline - But Offers Vaporware as a Substitute | Log in/Create an Account | Top | 22 comments | Search Discussion
    Click this button to post a comment to this story
    The options below will change how the comments display
    Threshold:
    Check box to change your default comment view
    The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
    How About Sending ICANN to Australia ?
    by Anonymous on Friday October 01 2004, @09:31PM (#14259)
    Imagine if ICANN was moved to Australia.

    Would people ever hear about it again ?

    Would it serve any purpose ?

    Do you think the millions of broad-band wireless
    vISP access devices in the U.S., which run without
    root servers, would care about what some group
    from Australia has to say ?
    [ Reply to This | Parent ]
    Vinton Cerf, ICANN and the ISOC Facing Their Fate
    by Anonymous on Saturday October 02 2004, @04:45AM (#14260)
    1

    Read the rest of this comment...

    [ Reply to This | Parent ]
    In the future users must be able to...
    by Anonymous on Saturday October 02 2004, @04:49AM (#14261)
    In the future users must be able to have a degree of confidence in the naming on the Internet. DNS was originally developed when the Internet was a trusted environment that didn’t anticipate on the need for authentication as the Internet evolved. New security extensions and other DNS enhancements have been proposed that would allow DNS infrastructure to have a method of verifying the integrity of record being served, in addition to verifying the actual identity of servers claiming to be authoritative DNS servers. A second feature of these enhancements would allow DNS to be used as a central distribution method for public-keys, establishing the DNS system as the global architecture for security information distribution as well as addresses and names. All of these additional enhancements to the DNS system are currently being evaluated by various standards bodies and task forces for implementation. Most notably, the directorate of Science and Technology within DHS is actively developing programs aimed at accelerating development and deployment of DNS security into the Internet infrastructure.
    [ Reply to This | Parent ]
    "there are dozens" ?
    by Anonymous on Saturday October 02 2004, @04:57AM (#14262)
    "there are dozens" ?

    try millions, each Linux-based broadband wireless
    access point handles the traffic for ALL 13
    so-called root servers. That traffic never leaves
    the wireless island. That fixes the "anycast
    problem" that the ISOC/IETF does not want to address.

    -------------------
    Better system design, investments in high performance systems, configuration management, and the implementation of anycast protocols have also increased our national and global capacity to handle many attack scenarios. The development and deployment of anycast has allowed for the replication of the 13 root servers; there are dozens. Having a larger number of high performance systems function as the so that there are multiple instances of those servers. The ability to replicate those root servers allows for faster response times, greater load distribution and diversity, and greater overall infrastructure survivability.
    ----
    [ Reply to This | Parent ]
    U.S. Department of Homeland Security is Clueless
    by Anonymous on Saturday October 02 2004, @05:09AM (#14263)
    U.S. Department of Homeland Security is Clueless

    According to the U.S. Department of Homeland Security the "root servers" know about DHS.GOV.
    That is not the case.

    "Using our previous example, when a user types www.dhs.gov, the computer first contacts the server to determine the IP address of dhs.gov. The system is hierarchical so that the root servers themselves do not have to handle the entirety of all global DNS resolutions. There are other ways that the resolution can occur as well. But, this is the most fundamental method."

    ---

    "most fundamental method" ? or the "most popular" ?

    In modern, wireless systems, when a user types
    DHS.GOV, a secure, reliable TCP connection is
    used to query the .GOV cluster of servers which
    may ask the toy legacy servers for out-dated
    information about the old IPv4 network.
    [ Reply to This | Parent ]
    Just switch from .NET to .NAT
    by Anonymous on Saturday October 02 2004, @05:23AM (#14264)
    "What happens if Verisign encourages those
    developers, by giving them FREE .NET names, and
    by continuing to operate the .NET registry and
    servers ?"

    Just switch from .NET to .NAT

    It is not worth the hassle dealing with ICANN/Verisign and the U.S. Government.
    [ Reply to This | Parent ]
    ICANN's DNS is Built on UDP - U is for Unreliable
    by Anonymous on Saturday October 02 2004, @05:32AM (#14265)
    ICANN's DNS is Built on UDP - U is for Unreliable

    The "anycast root" stunt, which Paul Vixie claims
    Rodney Joffe and Dave Farber orchestrated,
    is aimed at thwarting the move of the DNS to TCP
    and **more secure and reliable service** provided
    by major telecom carriers.

    Read ICANN's lips, "security and stability".
    That is Job Security, not network security.
    [ Reply to This | Parent ]
    .INFO will soon pass .ORG - 652,248 New Names/Day
    by Anonymous on Saturday October 02 2004, @05:58AM (#14266)
    http://www.dailychanges.com/ [dailychanges.com] 2,570,093
    652,248
    [ Reply to This | Parent ]
    "predictable strategy for selecting new TLDs" ?
    by Anonymous on Saturday October 02 2004, @07:03AM (#14268)
    "predictable strategy for selecting new TLDs" ?

    ICANN is very predictable. No new TLDs.

    AT&T (Marylnn Cade) said so.

    Solution, black-hole all of AT&T's IP address blocks.

    [ Reply to This | Parent ]
    The "community" is Having Another Bash
    by Anonymous on Saturday October 02 2004, @09:30AM (#14271)
    The ARIN XIV Social Event
    Wednesday Evening, October 20, 2004
    6:30 - 9:30 PM

    eCITIE Restaurant and Bar
    8500 Block Tyco Rd., Tysons Corner, VA

    Come join ARIN staff and your colleagues from the community at the ARIN XIV Social! The evening will include appetizers and a buffet style dinner, an open bar, and music and dancing.

    eCITIE Restaurant & Bar has, among many similar designations, been selected as "Best New Restaurant" by readers of The Washington Post and "Best Dance Club" by readers of the Washingtonian magazine.
    [ Reply to This | Parent ]
    Voting Would Probably be Too Predictable
    by Anonymous on Saturday October 02 2004, @11:10AM (#14272)
    10514 inc
    9264 online
    7288 NET
    6472 usa
    4481 GROUP
    4101 WEB
    3891 tech
    [ Reply to This | Parent ]
    Let Esther Choose She is Predictable and Wrong
    by Anonymous on Saturday October 02 2004, @11:15AM (#14274)
    Let Esther Choose She is Predictable and Wrong

    Pick TLDs she does not select. .PRO in the basket .COOP in the basket
    [ Reply to This | Parent ]
    ICANN is Simply Stalling Until After the Election
    by Anonymous on Saturday October 02 2004, @07:32PM (#14276)
    http://onthenet.ambler.net/blog/_archives/2004/10/ 2/152984.html
    "I've been waiting patiently for this report, as I saw it as the roadmap to getting .Web into the roots.
    ~~~~~~~~

    ICANN is Simply Stalling Until After the Election

    The DOC is not going to pull ICANN's plug in
    30 days, in fact, the DOC can not do anything to
    ICANN. The DOJ and other USG departments may be
    able to do something. They can not act until
    after the election. If Bush wins, there is one
    set of steps that need to be taken. If one of
    the other candidates wins, you might as well
    forget about .WEB. If .WEB *were* added, it will
    be handed to an ISOC insider, to allow them to
    retire and promote the "party line". As it stands
    now, all of the ISOC insiders are now well-funded
    and .NET will really put them on easy street.
    That is clearly Cerf's agenda. Funding to the
    Apostels.

    http://onthenet.ambler.net/blog/_archives/2004/10/ 2/152984.html

    "I've been waiting patiently for this report, as I saw it as the roadmap to getting .Web into the roots. Whatever criteria ICANN chose to set down, I was prepared (and still am prepared) to simply agree and move forward. Alas, I can't even do that, as ICANN hasn't put any criteria forward. I believe there's little doubt that that was what DoC contemplated this report as being. Obviously, it is not.

    So what to do? In the perfect world, those applicants still waiting would go directly to DoC and demand (ever-so politely) that DoC do something, since ICANN clearly won't.

    Enough. Is. Enough."
    ====
    [ Reply to This | Parent ]
    Comments on lack of compliance and oversight
    by ehasbrouck on Tuesday October 05 2004, @11:28AM (#14293)
    User #3130 Info | http://hasbrouck.org

    I've posted comments [icann.org] in response to the ICANN non-strategy apaper, pointing out that the ICANN document fails to actually define a strategy, and that it misrepresents as comprehensive the consultant's report ICANN had commissioned, which acknowledged my outstanding questions but said they were outside its scope.

    According to e-mail messages I received today from Kent Krispin at ICANN, comments to the public forum are being added to the Web archive manually, after those considered by ICANN staff to be spam or viruses are deleted. The comment forum supposedly opened last Friday, but no comments were actually posted to the ICANN Web site until today, after I queried ICANN about why my comments, twice submitted, still hadn't shown up on the Web after more than 24 hours.

    Additional background on the (as yet unaddressed) issues I've raised, particularly about ".aero", ".travel", and the lack of oversight by ICANN of the exercise of decision-making authority delegated to sTld sponsors, is in the ICANN section of my Web site [hasbrouck.org].

    [ Reply to This | Parent ]


    Search ICANNWatch.org:


    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