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.
    Brazil proposes sweeping Internet Governance reforms | 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.
    BRAZIL is Smart to Not Depend on IANA Hand Jobs
    by Anonymous on Wednesday June 15 2005, @08:03AM (#15587)
    BRAZIL is Smart to Not Depend on IANA Hand Jobs

    This is 2005 and they are STILL attempting to
    do everything by hand ? like the way Jon Postel did it ?

    http://www.ripe.net/ripe/maillists/archives/d ns-wg/2005/msg00098.html

    On Fri, 10 Jun 2005, Doug Barton wrote:
    > Thanks again for the opportunity to discuss these issues. I hope that the
    > group finds these answers satisfactory. We are of course happy to discuss
    > this in further detail if desired.

    In the interests of further explanation and clarification, I'd like to
    add some details of these events from VeriSign's perspective.

    First, to be clear, the VeriSign registry database that generates the
    root zone has supported multiple name server names (i.e., A records)
    with the same IP address for some time.  There was never a technical
    restriction on multiple names with the same IP address during these
    events.

    On November 11, 2005, VeriSign performed a root zone edit as requested
    by an IANA Name Server Change template for the .FR ccTLD.  The
    template requested name server NAME changes.  A request to change the
    name DNS.PRINCETON.EDU. was included in the template.  As a result of
    the execution of the change, the name DNS.PRINCETON.EDU did not exist
    and had been replaced by C.EXT.NIC.FR.  Considering the template
    semantics, this was the correct result.  It was not, however, the
    result that IANA desired.  After VeriSign discovered the undesired
    results, DNS.PRINCETON.EDU was immediately re-added to the root zone
    by ADDing a new name server.
    [ 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