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.
    Secret, Closed WHOIS Meeting Excludes Privacy Advocates | Log in/Create an Account | Top | 70 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.
    On Over-Builds, Bandwidth and Pulling in Fences
    by Anonymous on Sunday May 22 2005, @05:57PM (#15329)
    On Over-Builds, Bandwidth and Pulling in Fences

    Hard-core Internet believers (ICANNites?) are
    apparently un-aware about the coming movement
    which will re-shape what they view as The .NET.
    They may also just want to ignore that which
    they do not like.

    Newbie VOIP providers are just starting to learn
    about the harsh realities of "who pays for the
    legs of the calls". The same educational process
    which will open VOIP's eyes, will also open their
    eyes to the global myth of a FREE high-bandwidth
    Internet.

    U.S.-centric providers will start to pull in
    their fences. They have plenty of eye-balls
    willing to pay for local North American services.
    They can start cutting off routing to undersirable
    ISPs and foreign locations.

    Ultimately, network providers will be asking,
    "why are we wasting bandwidth on routing packets
    addressed to some irrelevant [in their eyes]
    place ?". Web-site owners sometimes ask the same
    question, why are they paying for hosting for
    viewers they have no desire to support ?

    It largely comes down to bandwidth, how it is
    wasted or used, and how pulling in the fences
    **improves** service for those paying the bills.

    With the emerging over-build evolution, this
    migration becomes even more compelling because
    local (high-bandwidth) users are obviously the
    target market for over-build services. Kids
    want to do LAN gaming with their friends from
    school, not from timbuktu.

    As network providers start to prune their routes,
    huge amounts of network address space will be
    idled. That will help the over-build evolution
    as it moves in on non-routable address space,
    previously locked up in the IANA-ICANN regime.

    While ICANN works to open 8 offices around the
    world, local ISPs work to open 8 offices or
    colos in each major city. ISPs see their market
    and sell to the market, which can walk in the
    door. With ICANN, they have to rely on flying
    to obscure places and they will find when they
    get there, that place has become non-routed
    from the U.S. There is no financial incentive
    to pay for other people's fun and games.

    Academics, governments, and ISOC free-riders will
    of course attempt to keep the .NET global and
    growing. In order to do that, they of course
    have to tax the local people to pay for a global
    network they have less-and-less interest in using.

    On the other side of the ocean the same thing
    is of course happening. Their users see more and
    more need to communicate locally and less and
    less on a global scale. Bandwidth is a factor
    the ISOC-IETF ignores in their designs. It is
    not free.

    This of course is where the ITU traditionaly
    enters the scene to help facilitate settlement
    fees to keep nations connected. Unfortunately,
    the ITU can not fabricate bandwidth from thin
    air. No matter how much they may cajole people
    to communicate, there is a limit to what people
    will pay, and can pay. Also, some services will
    just not work as the distance between end-points
    is extended.

    The fences will be pulled in to sell to the
    market. People will be forced to move to locations
    with high-bandwidth or face being part of the
    have-nots. As people move closer together it
    will be easier to meet and collaborate. The
    ICANN road-show will then be easily replaced.
    The up-coming domain roundtable meeting in
    Seattle.WA is just one example of the coming
    migration away from the global ICANN strategy.
    The participants there will realize they are
    all capable of supporting enough infrastructure
    to sell to the North American markets. They can
    either limit themselves and play the ICANN game
    or step up to the new opportunities. If they
    do not, someone will. The market is expanding
    by pulling in the fences.
    [ Reply to This | Parent ]
    Re:On Over-Builds, Bandwidth and Pulling in Fences
    by Anonymous on Monday May 23 2005, @04:35AM (#15333)
    The short summary is that the new low-cost routers
    being placed in people's homes and small businesses
    are being programmed to NOT route to undesirable
    sub-nets. Very fine-grained filtering is now
    possible and virtual-ISPs deploying the over-build
    networks decide who gets routed and who does not.

    All of the /8s from APNIC, RIPE, LACNIC and AFRINIC are re-allocated to North American use. Australians
    can now PAY very large sums of money to ISPs to
    become routed. The price of admission to the
    U.S. market is going way up for people outside
    who have enjoyed a free ride. In some cases,
    there is no price because packets can not get
    there from here. The distance is too far. The
    economics of pulling a fiber from Washington
    D.C. to Sydney favor a solution where everyone
    in Sydney is re-located to the U.S. It is cheaper
    to move people to band-width.
    [ 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