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.
    "We're Moving Backwards" on ICANN Transparency | Log in/Create an Account | Top | 105 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.
    204.152.*.* Now Available For Re-Allocation
    by Anonymous on Sunday August 07 2005, @06:06AM (#15828)
    204.152.*.* Now Available For Re-Allocation

    When the new software detects that people have
    moved to IPv6 they clearly no longer need their
    IPv4 address space (land). It can be reallocated.

    ns.lah1.vix.com. 1171 IN A 204.152.188.234
    ns.lah1.vix.com. 1171 IN AAAA 2001:4f8:2::9
    ns.sql1.vix.com. 1171 IN A 204.152.184.135
    ns.sql1.vix.com. 1171 IN AAAA 2001:4f8:3::9
    ns-ext.vix.com. 1803 IN A 204.152.184.64
    ns-ext.vix.com. 1171 IN AAAA 2001:4f8:0:2::13

    The Community appreceates the donation.

    .PS One way to avoid this is to use the multiple A Record format where 2 A Records form the 64 bit IPv6 address. You can then be reached via one of
    FOUR ways, via IPv4 on either of the 32-bit
    prefixes or via IPv6 on either of the 64-bit
    prefixes. It is common to have one prefix on
    your DSL and the other on your cable modem.
    [ Reply to This | Parent ]
    Re:204.152.*.* Now Available For Re-Allocation
    by Anonymous on Sunday August 07 2005, @06:17AM (#15829)
    In the send-only [best-effort] Internet, the Source and Destination fields are BOTH used for Destination or at least prefixes. That allows for a 64-bit Destination field. The Source information is carried in other bits. ICMP is mostly removed from the protocol stack. Less is more and more reliable and secure. Less code, more secure, more reliable.

    ICANN is all about security and reliability right ?
    [ Reply to This | Parent ]
    IETF Says NO to IPv6 Virus on Their Servers
    by Anonymous on Sunday August 07 2005, @07:08AM (#15830)
    Yesterday in the plenary in response to a request for making the IETF servers IPv6-capable, I believe Leslie said we shouldn't use IETF servers for testing.

    In and of itself I fully agree with that statement. However, the assumption that IPv6 is an experimental protocol and enabling it on the various IETF servers should be considered "testing" isn't exactly a glowing endorsement of 10 years of IETF work.

    It sounds distasteful, but we should really be eating your own dog food.

    Limiting myself to the www.ietf.org webservers (yes, this address points to two different hosts) it appears this site runs on:

    Server: Apache/2.0.46 (Red Hat)
    Server: Apache/2.0.40 (Red Hat Linux) DAV/2 mod_ssl/2.0.40 OpenSSL/ 0.9.7a

    Even though these Apache versions are 2 - 3 years old (with many vulnerabilities found and fixed in the mean time), they're fully capable of supporting IPv6, as are Red Hat Linux versions of around the same age.

    It would be a nice way to mark 7 years of RFC 2460 (or 10 years of RFC 1883, both were published in december) and the closing of the IPv6 wg with addition of IPv6 to at least the IETF WWW servers.

    (BTW a big "yuck" for being behind two-faced DNS here at the IETF meeting venue.)
    [ 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