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.
    Too much pressure from the industry... | Log in/Create an Account | Top | 22 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.
    IANA Decides to Take Back **SPECTRUM** ?
    by Anonymous on Wednesday December 15 2004, @01:19AM (#14576)
    IANA Decides to Take Back **SPECTRUM** ?

    Backed by CISCO, the IANA, that nameless, faceless
    wizard-of-oz-like persona behind the curtain,
    decides the numbers you used to use, are now
    their numbers and YOU have to defend your use
    [giving IPR rights to the ISOC of course].

    Will CISCO be doing the same with the .LAN TLD
    which is now programmed into millions of wireless
    access-point routers ?

    Will the Chair of the ISOC (employed by CISCO)
    and the Chair of the IETF (employed by CISCO)
    be making other demands ?

    ===

    A new RFC has just been issued, RFC 3942
    (http://www.ietf.org/rfc/rfc3942.txt): "Reclassifying DHCPv4 Options". The
    document is a product of the IETF DHC WG and expands the range of DHCPv4
    option numbers that are in the IETF/IANA assignable range. The expanded
    public range reduces the site-specific options range that was originally
    defined in RFC 2132..

                                                  Old ranges New ranges
    IETF/IANA assignable: 1-127 1-223
    Site-specific: 128-254 224-254

    So, why might you care about this?

    Many vendors have used "site-specific" options in the range 128-254 for
    vendor-specific purposes in shipping products. And, now that IANA can assign
    options numbers in the range 128-223 to future Internet Standard options, we
    need your assistance to prevent potential conflicts in the use of option
    codes in the newly expanded range.

    RFC 3942 has a mechanism whereby IANA will not assign any option codes in
    the newly expanded range, 128-223, for 6 months (this period will end in May
    2005). During this 6 month period, vendors using options in the 128-223
    range should come forward to let IANA and the DHC WG know of their use. IANA
    can be contacted at mailto:iana at iana.org and the IETF DHC WG can be
    contacted at mailto:dhcwg at ietf.org.

    The vendor will also need to write an Internet Draft documenting that usage
    and advance that draft to an RFC. The Internet Draft can either be written
    by the vendor or by the vendor providing the material for documenting their
    usage to Bernie Volz (mailto:volz at cisco.com) for inclusion in a general
    draft documenting several options.

    Once the Internet Draft has been published, it will be, at the vendor's
    discretion, published as an Informational RFC or entered into standards
    track for publication as an Internet Standard RFC.
    [ 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