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.
    YANNA, Yet another new.net announcement | Log in/Create an Account | Top | 72 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.
    Re: YANNA, Yet another new.net announcement
    by Jon_Weinberg on Wednesday August 08 2001, @05:39AM (#1698)
    User #16 Info | www.threecats.net
    In fairness, it seems to me there are two factors that make it much easier for new.net to create TLDs than it is for ICANN. The first is that new.net is not responsible to anyone, and seems to feel no need to play well with others. The second is that new.net domain names are not valuable; it's the perceived high value of names in the (artificially constrained) ICANN root, together with a fundamentally misguided sunrise policy, that's led to the fiasco we're seeing in .INFO. Still . . .
    [ Reply to This | Parent ]
    Re: YANNA, Yet another new.net announcement
    by finee on Wednesday August 08 2001, @06:19AM (#1701)
    User #2781 Info | http://www.FineE.com
    Actually ICANN needs to wake up as to what is really going on.

    Yes today new.net launched many new extensions. Translations of thier current extensions. Then there is another company www.NameSlinger.com that allows you to register in virtually any domain extension creating new TLDs on the fly. And they check to see if the TLD is "taken" ie in use by another registry in the inclusive and legacy namespaces to minimize conflicts. So it is very possible to both co-opperate with other organizations and provide a virtually unlimited selection in TLDs.

    When there is plenty to choose from you do not have the issues that have faced .biz, and .info.

    I can see the opposition to the few stunned mice coming from at least two different sources growing and growing fast.
    [ Reply to This | Parent ]
    SANNA, Still another new.net announcement
    by fnord (groy2kNO@SPAMyahoo.com) on Wednesday August 08 2001, @10:11PM (#1724)
    User #2810 Info
    1

    Read the rest of this comment...

    [ Reply to This | Parent ]
    Re: YANNA, Yet another new.net announcement
    by fnord (groy2kNO@SPAMyahoo.com) on Wednesday August 08 2001, @07:24AM (#1705)
    User #2810 Info
    Then you can use chandelier.shop.new.net. Not so difficult. BTW, I've had zero problems with the plugin, with Realplayer or anything else, since installing it the day new.net went live. Of course YMMV, and I've seen other reports of problems, but I've also been impressed with new.net's willingness to listen to complaints and respond in a timely fashion, just to do a bit more comparing and contrasting. -g
    [ Reply to This | Parent ]
    Re: YANNA, Yet another new.net announcement
    by ldg on Thursday August 09 2001, @04:34AM (#1739)
    User #2935 Info | http://example.com/
    While I am not necessarily a proponent of new.net, I have to say that you are incorrect. New.net domains are, in fact, SLDs and not 3lds. They have set it up so that those who do not wish to use the plug-in or do not subscribe to those ISPs who resolve their TLDs can still see those sites by appending .new.net. It does not in any fashion change the fact that those who "point" to their TLD servers via a participating ISP do not need to append .new.net. They have simply added a convenient method for resolution.

    [ Reply to This | Parent ]
    • 1 reply beneath your current threshold.
  • 6 replies beneath your current threshold.

  • 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