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.
    Telecordia Responds to (Some) Critics | Log in/Create an Account | Top | 20 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.
    On the .BIND and .SERVER Top Level Domains
    by Anonymous on Thursday May 05 2005, @05:13AM (#15105)
    http://darkwing.uoregon.edu/~llynch/dnsop/msg03436 .html

    "Apologies in advance for the length of this message. As a person 'somewhat' involved in inflicting this topic into dnsop in the first place and being listed as a co-author (although Suzanne should get the credit for keeping this alive), I have to admit I'm confused.

    My intent in writing the original draft was to document existing practice and behavior (a txt query in the chaos class for {version,hostname}.bind) and suggest an alternative with minimal changes that would be less offensive to other vendors (a txt query in the chaos class for {version,id}.server).

    The reason I suggested the approach I did was that I figured the folks who implemented chaos/txt *.bind (which, surprisingly enough, isn't just BIND) would find it trivial to change the string queried for. Mucking about with anything any more complicated than that (e.g., OPT RRs, the status opcode, multiple questions per query, or whatever) would imply code changes and thus, require significantly more work (in a relative sense). In fact, as I was coming up with my original draft, I asked some other DNS server implementors if they'd be willing to do chaos/txt id.server and they had indicated that it wouldn't be out of the question.

    The reason I thought this functionality would be useful was because the root servers were then just beginning (!) to be anycasted and one of the concerns expressed about this approach for strengthening the roots was that if an anycast root server instance went off into the weeds, it would be nice to be able to identify the culprit instance.

    In other words, my goal was to suggest something _simple_ to meet an actual and immediate _operational_ need. A novel and heretical thought, I know. I was and am perfectly well aware that my original proposal was far from optimal, however I felt it had the best chance of actually being implemented in real live operational servers before hell froze over.

    Unfortunately, after a particularly unpleasant public exchange with Randy Bush (for which I belatedly apologize to dnsop participants who had to wade through it), I gave up in disgust. Subsequently, Suzannne took on the responsibility of continuing tilting at this particular windmill."
    [ 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