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)


     
    The Big Picture Root Servers
    How many TLDs safely fit in the DNS?
    posted by michael on Wednesday April 09 2008, @10:37AM

    Simon Higgs writes "I recently came across the question "How many TLDs safely fit in the DNS?". It, was, not surprisingly, in the context of ICANN doing some due diligence with their $30 million budget and actually answering the same questions that the IAB have been cowering behind for over a decade. Well, here's my answer for it's 2 cents of bandwidth:

    In all fairness to ICANN, the reason why I think it hasn't answered the question is because it simply DOES NOT have a calculator that can calculate a number that big. You would think that ICANN should be able to go down to the corner store in Marina Del Ray and buy one, just like all the other high speed networking physicists in the Admiralty building. But the number's so big even the mighty Google refused to calculate it until a just few days ago.

    So what are these huge numbers that ICANN is hiding from us? Using the current ASCII-based character strings used in DNS we get the following big numbers:




    * Number of possible TLDs = (36 * (37 * 10^63)) = 1.332 × 10^66

    * Number of possible domain names = (36 * (37 * 10^255)) = 1.332 × 10^258

    The .COM zone pales by comparison. It only has 70,000,000 domain names (7 * 10^7 domains). By comparing these numbers, we know that the DNS, which is also recursive (see RFC1591), can hold an awful lot more of everything. More domain names, more TLDs, and even more sub-domains.

    My question, in response, is if IPv6 can increase the number of IP addresses exponentially, why can't the DNS be allowed to grow in a similar manner too?

    It is clearly no problem, at least to the integrity of the name space, for ICANN to give out all the TLDs that have ever been requested since RFC882 was published in 1983. It might not even break 10^3 and that's a ridiculously small number in the grand scheme of things.

    * For those wondering where all those numbers come from, there are 26 characters for A-Z, 10 characters for 0-9 plus the hyphen making 37 characters. Because you can't start a domain name with a hyphen, it limits the first character to a choice of 36 possible characters. The rest can choose from the full 37 possibilities."

     
      ICANNWatch Login  
    Nickname:

    Password:

    [ Don't have an account yet? Please create one. It's not required, but as a registered user you can customize the site, post comments with your name, and accumulate reputation points ("karma") that will make your comments more visible. ]

     
      Related Links  
    · ICANN
    · Simon Higgs
    · More The Big Picture stories
    · Also by michael
     
    This discussion has been archived. No new comments can be posted.
    How many TLDs safely fit in the DNS? | Log in/Create an Account | Top | 6 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.
    It's even bigger...
    by SimonHiggs on Thursday April 10 2008, @09:17AM (#16977)
    User #2898 Info
    I've been taken to task by ex-ICANN Board member Karl Auerbach because the big numbers I reported in the article above are wrong. They are, for want of a better way of putting it, embarrassingly small.

    It seems that those numbers apply only to the number of domain names that are 255 characters long or have a 63 character TLD suffix. Clearly, I missed all the domain names that are 2 to 254 characters long and all the TLDs that are 1 to 62 characters long. The name space even bigger than I thought and I was out by a few billion billion.

    It turns out that the number of possible TLDs is a very large number that is 96 characters long and, if you are viewing on a *nix 80-character screen or in an email client, one that will wrap around the page.

    It's clearly obvious that anytime a number wraps around the page, well, it's simply much too big for ICANN (or anyone else) to ever claim as a scarce resource.

    45740948715197463019198522067201064982535022753971 2687373445461577228502491435130988231174974800 TLDs don't lie.
    [ 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