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.
    VeriSign Domain Report Shows Criticality of .net | Log in/Create an Account | Top | 12 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.
    Re:AAAA DNS Records Carry TEXT Strings for .NET
    by Anonymous on Saturday September 18 2004, @07:38AM (#14162)
    Check out the new .MAN TLD

    Another issue is the aspect of mobility, which is different from what
          has traditionally been termed "IP mobility". The concept in IP
          Mobility is that a device has a normal home in some topological part
          of a stable network, as indicated by its address, but may temporarily
          move somewhere else. That "address" then becomes something more like
          a name. A home agent translates it into a second address, which
          represents the device's current actual topological location, and the
          packet stream is forwarded there. The device may then advise its
          correspondent of its current topological "care-of" address,
          facilitating more direct routing. In a MANET, the address is tied to
          the device, not a topological location, as there is no fixed network
          infrastructure. When the addressed device moves, therefore, the
          motion changes the routing infrastructure. There is no question of
          the correspondent transmitting to the new care-of address, or of a
          home agent forwarding traffic from "the right place" to "somewhere
          else" along a dog-leg path; standard routing will get the packets
          there as a direct outcome as routing tracks the motion of the device.

          Mobility is not an aspect of all MANETs; some varieties of sensor
          networks (such as forest fire sensors scattered by airdrop in the
          region of a fire) can be expected to be stationary once deployed.
          However, even in this case, topological relationships are arbitrary
          and unengineered. In applications where node mobility is in view, it
          can be haphazard, and in extreme cases can result in entire networks
          randomly partitioning and joining together.

          The fundamental behavior of a manet is that a routing node carries
          with it an address or address prefix, and when it moves, it moves the
          actual address. When this happens, routing must be recalculated in
          accordance with the new topology.
    [ Reply to This | Parent ]
    Re:AAAA DNS Records Carry TEXT Strings for .NET
    by Anonymous on Saturday September 18 2004, @11:19AM (#14169)
    Note: DNS AAAA Records Contain 128 Bits. With a 5-bit Alphabet, 32 Characters (Symbols) can be supported. Each 128-bit AAAA Record can contain up to 25 Characters with 3 bits for Record Type. The 32 Characters can be ® A to Z dash under-score @ © and of course DOT (.). Using the right-most 2 bits of the TTL field on legacy 32-bit A Records, a 128-bit AAAA Record can be constructed from one to four A Records.
    ===

    It may be hard to get Milton's ego into 25 characters.

    MILTON.MUELLER@SYR.EDU®NET.MAN
    [ Reply to This | Parent ]
    Re:AAAA DNS Records Carry TEXT Strings for .NET
    by Anonymous on Monday September 20 2004, @06:51PM (#14183)
    Not all AAAA records will contain IPv6 addresses.
    The A6 DNS record type is designed for IPv6.

    IPv6 support for com/net zones on October 19, 2004

            * From: Matt Larson
            * Date: Mon Sep 20 17:09:58 2004

    VeriSign will add support for accessing the com/net zones using IPv6
    transport on October 19, 2004. On that day, AAAA records for
    a.gtld-servers.net and b.gtld-servers.net will be added to the root
    and gtld-servers.net zones.

    We do not anticipate any problems resulting from this change, but
    because these zones are widely used and closely watched, we want to
    let the Internet community know about the changes in advance.

    Matt
    --
    Matt Larson
    VeriSign Naming and Directory Services

    [ 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