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

Our Mission
ICANN for Beginners
About Us
How To Use This Site
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.
    Canadian.biz -- Round Two ! | 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
    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.
    An off-topic rant
    by fnord (groy2kNO@SPAMyahoo.com) on Thursday July 11 2002, @06:38AM (#7773)
    User #2810 Info
    I get the Canadian federal government site at gc.ca. That is using google.ca so your mileage may vary. Google snifs out my incoming IP address and knows it is from Canada so it feeds me google.ca. I can try google.com specifically but it doesn't matter, I get google.ca. I can get around this by masking my IP or in other ways, but that's a lot of bother.

    A number of sites do this, Yahoo for example, and in that case if I try to sign up for an email address it wants to give me @yahoo.ca even if I want @yahoo.com. This practice is taking some power away from the end user to choose what they access online based on national boundaries, and isn't a trend I particularily care for. In the above examples it is just search engines trying to be helpful and relevant and even that causes problems. How do I know if I give a link that others will receive the content I intended? But as was suggested in the yahoo.fr case, it could be used to control content flow across national boundaries.

    This does have one perhaps unintended side-effect. I used to type google.com to get to google.ca, but it's easier to type google.ca so that's what I now use. This means that Google and other highly used sites are probably educating Canadians on the existence and use of their ccTLD, and this may also be true in some other countries. I suspect an analysis of ccTLDs like .ca, .de (Germany), .uk (United Kingdom, .jp (Japan), .au (Australia), etc. would find that a greater percentage of addresses are in actual use than in gTLDs, that is, less speculation and cybersquatting, less defensive registrations. With dropjackers picking up expired names and pointing them elsewhere, and with the WLS about to turn this into a major industry for .com and .net, I expect websurfers will receive ever-increasing lessons that the use of domain names to find things isn't very accurate, and that .com and .net are generally worse that country codes (at least those of countries like the above). Not only is the DNS not very accurate, in the case of dropjackers serving up mousetrapping multiple pop-up pr0n sites, it can be downright annoying. This could transfer some power from ICANN to the ccTLDs, if ICANN and the GAC haven't taken them over.

    I also think websurfers will increasingly learn that using Google is preferable to using the DNS if one is unsure of one's destination. This would put Google in a powerful position that could be misused. -g

    [ Reply to This | Parent ]
    An off-topic rant by fnord
    Re: An off-topic rant
    by dtobias (dan@tobias.name) on Thursday July 11 2002, @07:34AM (#7776)
    User #2967 Info | http://domains.dan.info/
    I got the same site on searching for "canadian" on google.com from the United States, where my access isn't redirected to a different Google site.

    google.us is registered by Google, but doesn't resolve to a Web site; it would be a sensible address for them to deploy for the use of those who want to go to the U.S. site no matter where in the world they are (leaving the auto-redirections in the .com site).

    Redirecting by what country they think you're in based on IP address is pretty iffy, as people might be dialing up from anywhere via any provider, and some are transnational in scope. More sensible is content type and language negotiation based on HTTP headers sent by your browser, a feature that's been in the protocols for many years; those are responsive to user configurations (you can set your browser to prefer Spanish over English, for instance), and thus not forced on anybody without possibility of overriding.
    [ 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