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.
    1.ENUM | Log in/Create an Account | Top | 15 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: 1.ENUM
    by RFassett on Wednesday May 01 2002, @05:50AM (#6103)
    User #3226 Info | http://www.enum.info
    let me take a stab, if you will - (and I am no authority on the subject):

    Consider 2 parrallel lines of communication. One being for voice and the other for data. ENUM allows these parallel lines to intersect. DNS, per RFC 2916, is the intersection. The theory is that every phone number on the planet could be poplulated into ENUM. Under this ENUM DNS model favored by the IETF, every phone number would then produce a fully qualified domain name. That's a lot of zone files. One end result is a voice call being routed over data networks via the behind-the-scenes DNS mapping scheme that points the domain name to the phone number when the call is initiated by an end-user. This can work in the opposite direction for e-mail.

    What does ICANN have to with this? Personally, I am not sure but you would think there is a place especially as this relates to the recommended .arpa TLD. It appears, for the U.S., that the Department of State is going to have greater influence upon ENUM implementation than DoC. So, I am personally unclear regarding the intended role of ICANN as this relates to ENUM. Hope this helps.
    [ Reply to This | Parent ]
    Re: 1.ENUM by RFassett
    Re: 1.ENUM
    by jamielove (james.love at cptech.org) on Wednesday May 01 2002, @06:52AM (#6106)
    User #3323 Info | http://www.cptech.org/jamie
    That was quite helpful. How does .arpa relate to all of this. I know next to nothing about .arpa.
    [ Reply to This | Parent ]
    • Re: 1.ENUM by dtobias Wednesday May 01 2002, @07:58AM
      • Re: 1.ENUM by jamielove Wednesday May 01 2002, @01:16PM
        • Re: 1.ENUM by Anonymous Wednesday May 01 2002, @01:22PM
          • Re: 1.ENUM by jamielove Thursday May 02 2002, @06:33AM
            • Re: 1.ENUM by dtobias Thursday May 02 2002, @06:57AM
            • Re: 1.ENUM by joppenheimer Thursday May 02 2002, @04:04PM


    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