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.
    Building the alternative to DNS | Log in/Create an Account | Top | 26 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: Working out details of decentralized handle se
    by Anonymous on Friday August 02 2002, @01:23PM (#8332)
    I made it up, though I may not be the first.
    I'm unaware of any references.

    Key size shouldn't have any effect on latency.
    Latency is an effect of how many computers you need to go through
    to get the answer. This is mostly determined by cache time, and delegation.
    Cache time would be longer with this scheme, so that would reduce latency.
    There would be more authoritative handle servers, which means more
    geographically diversity, which would reduce latency.
    There would also be less delegation, which means fewer lookups
    which means less latency. But this is dependent on the distribution
    model chosen. You could map it onto DNS, in which case
    it would have the same amount of delegation that DNS does now.
    Or you could use the Usenet model, in which case the local
    caching server is likely to have a complete copy at all times.
    Overall, a lot less latency, and a lot less network traffic.

    Larger keys are more secure, but require more space to store.
    These days, people recommend at least 2048 bits (256 bytes) of key
    for RSA. Actually, that's pretty small by today's standards -
    a 20 Gig drive could hold all the keys for every domain currently registered.
    There are no known attacks that are successful against even 756 bit RSA keys,
    but Bernstien thinks it may be possible to crack 1024 bit keys with a few
    million dollars worth of hardware.

    The chance of any two MD5 hashes colliding is
    340,282,366,920,938,463,463,374,607,431,768,211,456 to 1 against.
    Even with 5 billion handles, the odds against any two colliding
    is still several septillion to 1 against. But if you are incapable of accepting
    any risk at all, no matter how infinitesimal, (or you just think you can't sell
    "acceptable risk") then say the first person to publish a key "wins".

    It might be desirable to have a central repository that stored them so
    that the list didn't have to be replicated across thousands of severs.
    On the other hand, I would expect all ISPs over a certain size to set up a
    cache (repository) for entries, since they do it now with DNS for
    performance reasons. If the handles are verified with use,
    then they could be cached indefinitely, so every caching server
    becomes a central repository. The downside to verification is that
    each endpoint server must do more work, and the total amount
    of work that is done is slightly higher. But the upside is that
    changes can propagate instantly, and it scales much better.



    [ Reply to This | Parent ]
    Re: Working out details of decentralized handle se by Anonymous
    Re: Working out details of decentralized handle se
    by odonnell (michael_odonnell@acm.org) on Friday August 02 2002, @07:10PM (#8337)
    User #3447 Info | http://people.cs.uchicago.edu/~odonnell/
    1

    Read the rest of this comment...

    [ Reply to This | Parent ]
    Please identify yourself for credit
    by odonnell (michael_odonnell@acm.org) on Saturday August 03 2002, @05:20AM (#8342)
    User #3447 Info | http://people.cs.uchicago.edu/~odonnell/

    I hope that you (Anonymous) will identify yourself, so I can credit you with these ideas when I work up some sort of article. At present, I'm thinking towards writing an Internet Draft aiming to become an RFC.



    Mike O'Donnell
    [ 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