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.
    ccNSO Bylaws correction and ccTLD unrest | Log in/Create an Account | Top | 15 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.
    65,536 Filter Decisions [0]=OFF [1]=ON
    by Anonymous on Tuesday April 20 2004, @06:08AM (#13412)
    It only takes 65,536 Filter Decisions to decide on whether sub-nets such as 66.33.0.0 should be routed.

    route add -net 66.33.0.0 netmask 255.255.0.0 gw 127.0.0.1

    00.00.00.00
    00.01.00.00
    00.02.00.00 ...
    66.32.00.00
    66.33.00.00
    66.34.00.00 ...
    255.254.00.00
    255.255.00.00

    If you take one bit with a value of [0] or [1], then it takes 8K or 8,192 bytes to send a map of filter bits to all of the IPv4 routing devices to condition them.

    On the Broadband, always-on, Internet, where wealthy subscribers pay a premium, that 8K of information can be sent to all of the users in a few seconds.

    Marking large blocks as being part of the Broadband, always-on, Internet or not part of it is easy via software. The .TRAVEL and .XXX TLDs may end up "existing" on that Broadband, always-on, Internet for years, for the pleasure of those subscribers. Geeks on dial-ups and other off-line systems can jump up and down about .TRAVEL and .XXX not existing, but, for the Broadband, always-on, Internet users, they will be hard to persuade.

    If Geeks want to see how far they get, they might want to run down to the local grocery store, wearing their underware outside of their jeans, and run up and down the aisles telling everyone that .TRAVEL and .XXX do not exist. See if any of the shoppers listen. Better yet, subscribe to some of the .TRAVEL and .XXX forums and tell all of the people there, that they do not exist.
    [ Reply to This | Parent ]
    When Address Space is RECLAIMED, there is plenty
    by Anonymous on Tuesday April 20 2004, @06:37AM (#13413)
    http://www1.ietf.org/mail-archive/ietf/Current/msg 24920.html

    I was wondering if there are any plans to change the status of the class E address space (240.0.0.0 - 255.255.255.255).

    Currently, there are approximately 221 usable /8s: classes A (125), B (64) and C (32). (0.0.0.0/8, 10.0.0.0/8 and 127.0.0.0/8 aren't usable at this time.) Adding 16 /8s from class E space would increase this by 7%, and increase the unused address space with something like 20%.

    However, it's almost certain that there are implementations out there that won't accept 224.0.0.0/4 as regular unicast address space. So if we want to be able to use class E space as such, it is imperative that we announce this a *very* long time in advance.

    Two other possible uses:

    It seems that there are now organizations who want/need more private address space than is available as per RFC 1918. Using class E space for this would make a lot of sense as this allows for a lot of private space without sacrificing usable unicast space.

    In large networks, a lot of address space is used up and/or fragmented for point to point links and other infrastructure use. Using class E space for this could be a good compromise between using regular unicast space on the one hand or RFC 1918 space on the other hand.

    Thoughts?

    And is there a wg that deals / should deal with this issue?
    [ 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