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.
    How to get a new top-level domain approved by ICANN | 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
    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:32 Symbol DotNetAlphabet
    by Anonymous on Monday May 03 2004, @06:42AM (#13471)
    If you own a .NET domain name, with 5 characters or less, comprised only of the letters A to Z, the numbers 0, 8, 1 or 3 and/or Dash, then you automatically have full ownership rights in one or more blocks of .NET Address Space. There is NO CHARGE for these rights. There are no annual fees (cyberspace taxes) to be paid to so-called Regional Registries. There are no secret societies that have to be paid, either above the table or under the table.

    The rights are tied to your ownership of your Fully-Registered .NET domain name. A 32 Symbol DotNetAlphabet is used to map the letters of your domain name to 5-Bit Values. Using a fixed-width size of 5 characters results in a 25-Bit Prefix, which may contain some zeroes (00000). The ® Symbol is used to denote a void (space or blank) and it has the 5-Bit Value zero (00000).

    One example would be ApnicNet. .NET names with less than 5 characters fill the left fields with ® symbols. .NET names with less than 5 characters own the rights to more than one block of .NET Address Space because they also own all combinations of their unique name positioned in the 5-character field with ® and/or Dash (-) symbols on the right and/or left.

    With a 25-Bit Prefix, there can be 33,554,432 unique values. The ®®®®® Address Space Prefix (00000 00000 00000 00000 00000) is not owned by anyone and can be used for internal network addressing. Address Space Prefixes derived from .NET names with leading or trailing Dashes (-) and/or ®s are owned by the .NET name owner of the interior name.

    The ----- Address Space Prefix (11111 11111 11111 11111 11111) is also not owned by anyone and can be used for internal addressing. Likewise, names which are a combination of only ® and dash symbols are also available for internal addressing. One example is the 255.254.0.0 (31.31.31.0.0) Prefix, which results in the name ---®®. The Prefix 0.0.0.0 (0.0.0.0.0) has the name ®®®®® and can also be used for internal addressing.

    The 25-Bit Prefix can be used in a variety of ways in packet network addressing. One key concept to remember is that each 25-Bit Prefix is Unique. There is NO CHARGE for the usage of the 25-Bit Prefix, it is tied to the ownership of a Fully-Registered .NET domain name. The owner is free to use or lease all or part of the address space allocated.

    The 25-Bit Prefix can be easily expressed as a Dotted-QUINT as opposed to a Dotted-QUAD. A Dotted-QUINT only contains decimal values from 0 to 31. Software can easily tell the difference between a Dotted-QUINT and a Dotted-QUAD because there are 5 numeric fields with a Dotted-QUINT. Even though there are 5 fields instead of 4, the Dotted-QUINT often takes less characters to type than a Dotted-QUAD. With the 32-Symbol Alphabet, all of the 25-Bit Prefixes can be coded in 5 characters.

    A given 25-Bit Prefix has one and only one reverse-name-look-up. You can rapidly determine who is responsible for managing a specific .NET Address Space. No DNS service needs to be running with reverse look-ups. There is no management of complex reverse look-up zones required.

    When used as part of a 32-bit Routing Prefix, the 25-Bit Prefix reserves room for 7-Bits.
    The 25-Bit Prefix is placed between 2-Bits on
    the far left and 5-Bits on the far right.
    [ Reply to This | Parent ]
    Re:32 Symbol DotNetAlphabet by Anonymous


    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