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)


     
    gTLDs hoping to enter the legacy root Goodbye, "Structure:" GNSO Council rejects Lynn's "taxonomy" proposal
    posted by Mueller on Friday May 23 2003, @01:24PM

    In December Stuart Lynn asked the Internet community whether the top level name space ought to be made into a taxonomic set of categories. The concept was suggested by a Business/Intellectual Property constituency position paper that proposed that in the future, ALL top-level domain names should be sponsored and restricted and all TLD names part of a rigid, pre-defined set of categories.

    That proposal represented what we all hope was the low point of ICANN's mission creep. Somehow, ICANN's management had moved from mere "technical coordinator" of unique DNS parameters, to a role as central planner of the name space, the imposer of an ontology that all the world's internet users had to fit themselves into.

    On Thursday, the GNSO Council shot that idea down once and for all.



    "In response to the question asked of it by the Board, the GNSO council concludes:

    "Expansion of the gTLD namespace should be a bottom-up approach with names proposed by the interested parties to ICANN. Expansion should be demand-driven. Furthermore, there should be a set of objective criteria to be met in any future expansion. The development of this set of objective criteria should be the subject of a new Policy Development Process (PDP). These ideas are expanded in the a report together with the responses of the GNSO Constituencies and the ALAC which will be forwarded to the Board in June."

    This response passed unanimously. But driving a stake through the heart of Lynn's top-down name space wasn't easy. You see, the committee charged with developing a response to the question was chaired by...Philip Shepherd, the Business Constituency lifer who is deeply wedded to the idea of a top-down, structured and restrictive name space.

    When it became evident that his pet idea had little support, either on the Council or among the broader community, Shepherd fought an exhausting rearguard action. First, he attempted to word the GNSO's response to the question so that support for "structure" could be read into it. The meaning of the word "structure," Shepherd's draft claimed, could be interpreted to mean any conformance to policy objectives, and hence the answer to the Board's question was really "yes", because all Council members had some policies in mind regarding the name space.

    Second, he tried to attach to the response a long list of policy recommendations taken from the BC wish list, touching on everything from registry failure to auctions. As numerous members pointed out, this constituted a major policy development process, and were not required by the Board's question. And yet, Shepherd tried to get these policy recommendations developed and passed without any opportunity for public comment.

    In a last-ditch attempt to salvage his control over the draft, and aided by a procedurally troublesome intervention from "observer" Louis Touton (who made his support for Shepherd's efforts tacitly clear), a motion to delay the release of the response for another month was made. This would have given Shepherd another month to play language games. That motion was defeated in a very close vote (13-11), with Council Chair Bruce Tonkin of the registrars providing the decisive vote. The vote split on user-supplier grounds, with the Noncommercials acting as the swing vote and siding with the suppliers in favor of an open, demand-driven name space. Once the procedural motion was lost, the opponents threw in the towel and voted unanimously for a clear negative answer to the Board's question about name space structure.

    The final resolution was thus a total defeat for the Business/Intellectual Property interests on procedural and substantive grounds. It called for the TLD name space to be expanded through "bottom-up, demand driven" applications; it called for "objective" criteria for selecting applicants rather than discretionary beauty contests; and it clearly stated that the development of any criteria should be left to a policy development process, which will allow public comment, rather than the ad hoc committee of the whole thrown together to answer Lynn's question.

     
      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  
  • At Large Advisory Committee
  • ICANN
  • ICANN Business Constituency
  • More on gTLDs hoping to enter the legacy root
  • Also by Mueller
  •  
    This discussion has been archived. No new comments can be posted.
    Goodbye, "Structure:" GNSO Council rejects Lynn's "taxonomy" proposal | Log in/Create an Account | Top | 7 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.
    Recommendation
    by PeterBarron (pebarron@hotmail.com) on Saturday May 24 2003, @12:01AM (#11733)
    User #3240 Info | http://www.icannwatch.org/
    Bravo. ++Peter
    [ Reply to This | Parent ]
    say what?
    by fnord (reversethis-{moc.oohay} {ta} {k2yorg}) on Saturday May 24 2003, @01:10PM (#11739)
    User #2810 Info
    This still comes down to who defines the taxonomy, Someone has to. Does one do it at the level of .book or at the level of .literature or at the level of .fiction. One cannot have it all unless one wants the same level of drek that now infests .com et al.

    Strangely enough, I do not think it is beyond the range of possibilitie that this is within ICANN's purview. Someone has to do it, one doesn't leave the organization of the yellow pages up to a citizen's committee (not that that would necessarily be a bad thing, but it doesn't happen and the world hasn't spun off its axis). I think it should be ICANN making these decisions, of course I think it should be a properly constituted subcommittee that actually has a clue and that will never happen, but simply leaving it up to market forces doesn't work. What say ICANN OK'd all 46 or whatever applicants at MdR2k, that just amounts to more consumer confusion, read CHAOS. Better that there is some logic behind it, in the same way that .com and .org and .mil used to be a taxonomy until Veri$ign and latterly ICANN got greedy. -g

    [ Reply to This | Parent ]
    Proposal or Question
    by RFassett on Saturday May 24 2003, @07:54PM (#11740)
    User #3226 Info | http://www.enum.info
    I am not sure that Dr. Lynn's document was a proposal of a taxonomy as much is it was to form a task force to ask this question to, though I will admit Dr. Lynn's document was a bit leading in this regard. But, let's also not forget the concept of parallel processing, originally recommended by the NTEPPTF and an underlying theme to Dr Lynn's document to begin with. So, while all this "new PDP of objective criteria" as proposed by the GNSO council is being figured out (likely to take how many more years rehashing yet again much of what has already been documented), there should be nothing stopping the Board from moving forward with parallel processing (of the sTLD variety).

    Ray
    [ 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