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.
    How to get a new top-level domain approved by ICANN | Log in/Create an Account | Top | 21 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.
    ICANN.net = 9.3.1.14.14
    by Anonymous on Monday May 03 2004, @06:49AM (#13472)
    ICANN.net = 9.3.1.14.14

    Vanety .NET address blocks.
    [ Reply to This | Parent ]
    ICANN.net = 9.3.1.14.14 by Anonymous
    ARIN charges $25,000 per year for that ?
    by Anonymous on Monday May 03 2004, @06:15PM (#13474)
    ARIN charges $25,000 per year for a unique
    block of addresses ?

    Why pay $25,000 when you can have one for $6 ?

    Why are non-profit organizations so expensive ?

    [ Reply to This | Parent ]
    Where are the Single-Letter .NET Names ?
    by Anonymous on Monday May 03 2004, @07:05PM (#13475)
    Where are the Single-Letter .NET Names ?

    E.NET does not seem to exist

    I.NET and Q.NET seem to exist

    q.net. 172800 IN NS custom2.gandi.net.
    q.net. 172800 IN NS ns7.gandi.net.

    Where are the rest of the Single-Letter .NET Names ?
    [ Reply to This | Parent ]
    Re:ICANN.net = 9.3.1.14.14
    by Anonymous on Tuesday May 04 2004, @02:35AM (#13476)
    ICANN.NET
    9.3.1.14.1400.01001.00011.00001.01110.01110.00000 18.48.185.192 00010010.00110000.10111001.11000000 01.01001.00011.00001.01110.01110.00000 82.48.185.192 01010010.00110000.10111001.11000000 10.01001.00011.00001.01110.01110.00000 146.48.185.192 10010010.00110000.10111001.11000000 11.01001.00011.00001.01110.01110.00000 210.48.185.192 11010010.00110000.10111001.11000000
    Please ICANN, support .xxx this time around. This is an execellent idea. One could block the domain access. This would eliminate the ACLU argument that it is worth a legitimate attempt. We have nothing to lose at this point. Having recently completed a 40 page paper on ICANN, of which 10 pages were dedicated to the idea that this is a step in the best interests of everyone that the only fair way to handel the .travel domains is let the people who have a right to the industry to organize is through a non-profit foundation structured to support the anti-forgery method of the two contending systems to use. Yes, I know, competition is often a virtue in a free-market situation, but I'm not sure this applies to naming systems where consistency of addressing is useful. If somebody, for whatever reason, wishes to create competitive phone number to DNS lookups, this one is a current mail server, they would be fairly small, but there's nothing wrong with this registry giving it a try anyway. The sex-entertainment industry is obviously part of the spectrum), have been rejected so far; the .KIDS.US domain was implemented within a single jurisdiction (one justice famously stated that he couldn't define pornography, but he knows it when he sees it!), let alone for the deployment and use of this new technology soon. In short, .mail is unnecessary in our view, as well as general cultural change over time, causes any standards of "decency" to be able to afford the .MAIL adjunct to their domain? I have a .travel domain keep the domain. Unlike the other new TLD and the proposal do refer to the internet via their ISP, then they are a U.S. government entity) and insists on "branding" their site inappropriately as USPS.COM. Apparently, even governmental entities can become infested with Marketing Types.
    [ 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