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.
    There is NO ROOT - There is NO Registry ? How ?
    by Anonymous on Monday May 23 2005, @05:16AM (#15334)
    There is NO ROOT - There is NO Registry ? How ?

    Remember when ISOC-IETF "experts" said this
    could not be done ?

    BitTorrent Goes Trackerless: Publishing with BitTorrent gets easier!

    As part of our ongoing efforts to make publishing files on the Web painless and disruptively cheap, BitTorrent has released a 'trackerless' version of BitTorrent in a new release.

    Suppose you bought a television station, you could broadcast your progamming to everyone in a 50 mile radius. Now suppose the population of your town tripled. How much more does it cost you to broadcast to 3 times as many people? Nothing. The same is not true of the Web. If you own a website and you publish your latest video on it, as popularity increases, so does your bandwidth bill! Sometimes by a lot! However, thanks to BitTorrent the website owner gets almost near-broadcast economics on the web by harnessing the unused upstream bandwidth of his/her users.

    In prior versions of BitTorrent, publishing was a 3 step process. You would:

       1. Create a ".torrent" file -- a summary of your file which you can put on your blog or website
       2. Create a "tracker" for that file on your webserver so that your downloaders can find each other
       3. Create a "seed" copy of your download so that your first downloader has a place to download from

    Many of you have blogs and websites, but dont have the resources to set up a tracker. In the new version, we've created an optional 'trackerless' method of publication. Anyone with a website and an Internet connection can host a BitTorrent download!

    While it is called trackerless, in practice it makes every client a lightweight tracker. A clever protocol, based on a Kademlia distributed hash table or "DHT", allows clients to efficiently store and retrieve contact information for peers in a torrent.
    [ Reply to This | Parent ]
    Re:There is NO ROOT - There is NO Registry ? How ?
    by Anonymous on Monday May 23 2005, @07:47AM (#15336)
    While it is called trackerless, in practice it makes every client a lightweight tracker. A clever protocol, based on a Kademlia distributed hash table or "DHT", allows clients to efficiently store and retrieve contact information for peers in a torrent.

    While it is called rootless, in practice it makes every client a lightweight root. A clever protocol, based on a Kademlia distributed hash table or "DHT", allows clients to efficiently store and retrieve contact information for peers in a registry.
    [ Reply to This | Parent ]
    Re:There is NO ROOT - There is NO Registry ? How ?
    by Anonymous on Monday May 23 2005, @07:58AM (#15337)
    HINT: There are only about 200,000 static 32-bit
    IP addresses commonly in operation doing the bulk
    of DNS services.

    A bit torrent file can be created that lists those
    200,000 addresses. It can then be launched. As
    long as that file is circulated in the caches, it
    *exists*.

    Those 200,000 addresses can be used to randomly
    locate a DNS server. That is better than trying
    one out of 4 billion or more addresses.

    Once a DNS server or two is located, it can be
    asked if it "knows" where the .COM servers are
    located. That produces a small list of IP
    addresses. Several random DNS servers can be
    asked to see if they agree.

    When a consensus is formed of where the .COM
    servers are located, then THOSE .COM servers can
    be asked who their "partners" are. One would
    hope they all have the same answer. Some TLDs
    are not coherent in that regard. They are not
    even configured properly. The .COM servers may
    not be perfect but they provide a "seed" a
    starting point, a boot-strap.

    Once the .COM servers are located, then common
    "hooks" can be used to locate the other TLD
    servers. At each stage, a bit torrent file can
    be created with the information found. Those
    files start to circulate in the caches to assist
    other nodes in locating what some call The ROOT.

    At no time are any root servers needed or used.
    [ 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