Slashdot Mirror


Is It Time For .tel?

Vitaly Friedman writes "ICANN, the body responsible for creating top-level domains, is considering a new one. Conceived as a way to easily manage contact information in an age where many people have numerous contact numbers, the proposed .tel TLD would allow individuals and companies to keep all of their contact information in an easily accessible location. Companies would get companyname.tel while individuals would be able to register firstnamelastname.tel." This idea has been kicked around for quite a while; one of the question is the whole name-space collision issue. For instance, there's me and then there's other me. Lemme tell how strange it is getting fan mail for country music stars.

49 of 292 comments (clear)

  1. Unforseen problems by robyannetta · · Score: 5, Funny
    Companies would get companyname.tel while individuals would be able to register firstnamelastname.tel.

    This may pose a problem with the 526,000+ people sharing the name Michael Smith.

    --
    - Just my $0.02, take with a grain of salt, your mileage may vary.
    1. Re:Unforseen problems by The+Snowman · · Score: 5, Insightful

      This may pose a problem with the 526,000+ people sharing the name Michael Smith.

      Or the people who share names with companies. Or the people who share names with each other. There will be collisions. This plan will not work for its stated purpose. However, its stated purpose and its real purpose most likely are not the same. Odds are, this is just another plan to make more money for the registrars by opening up a new land rush of domain name registrations.

      --
      24 beers in a case, 24 hours in a day. Coincidence? I think not!
    2. Re:Unforseen problems by kryten_nl · · Score: 5, Funny

      Yes, perhaps we should add numbers to the back of the name. Come to think of it, maybe it would be better to define the name by numbers as well, then you wouldn't have to worry about typos and phonetic problems. Maybe this system should look something like:

      2001:0db8:85a3:08d3:1319:8a2e:0370:7334
      Or 8 groups of 4 hexadecimal digits.

      [/sarcasm]

      --
      For the perfect anti-Unix, write an OS that thinks it knows what you're doing better than you do and let it be wrong.
    3. Re:Unforseen problems by Anonymous Coward · · Score: 2, Insightful

      James is the most common first name.
      Smith is the most common last name.
      I don't see anything that guarantees they're the most common combination.

    4. Re:Unforseen problems by thePowerOfGrayskull · · Score: 2, Funny

      Geez, I hadn't thought about the illegals. Guess we'll have to legalize all of them so that they can have .tel domains. And -- did you say there were people outside the US? Huh. What a concept.

    5. Re:Unforseen problems by Anonymous Coward · · Score: 2, Insightful

      Don't try to use Slashdot to prove to others how smart you are.

      Excuse me? I can't believe what I just read... what exactly are you doing? Sounds like you're doing just that, to me...

      You see, actually, it's a public forum, and people will use it for whatever the fuck they please. Get it? That is, I (not the original poster) will use "actually" wherever I see it fit; and there's nothing to stop me, just like there's nothing stopping you from being an incessant asswipe and posting hypocritical bullshit.

      Incidentally, I thought it was very legit use of the word. Here's another example:

      Poster A: "You are a troll."
      Poster B: "Actually, (A)*(B)!0_- is a troll."

      See? Poster A never claimed you weren't a troll, yet still made legitimate use of the word "actually".

      If you have nothing better to do than scorn innocent posters for tiny little nitpicky shit, particularly when your criticisim isn't even correct, then don't post. That is, mind your own advice.

      Fucking dirtbag.

    6. Re:Unforseen problems by Greedo · · Score: 2, Insightful

      while individuals would be able to register firstnamelastname.tel.

      Isn't this what .NAME was for?

      --
      Tuus crepidae innexilis sunt.
    7. Re:Unforseen problems by sslayer · · Score: 2, Insightful
      Or the people who share names with companies. Or the people who share names with each other. There will be collisions.

      I could see a way this would work. Whenever you ask for your namelastname.tel or mycompanyname.tel you won't get that domain for you, instead you would have to fill in a form in which you write a brief description of who you or your company are and write down your contact information, including your real website.
      This way, if I need to contact with some person or company, I'll type itsname.tel on my browser, and I will search for the person I'm looking for, so all people with the same name could get the chance of being found in itsname.tel.
    8. Re:Unforseen problems by Rekolitus · · Score: 2, Informative

      I'm not quite sure if there's a difference, but I think with .ip it's already been done -- .arpa.

      But of course with DNS it's the other way round, so you actually have 1.0.0.127.in-addr.arpa

    9. Re:Unforseen problems by kryten_nl · · Score: 2, Funny

      ... and you haven't turned him over to the FBI yet?

      --
      For the perfect anti-Unix, write an OS that thinks it knows what you're doing better than you do and let it be wrong.
    10. Re:Unforseen problems by Idimmu+Xul · · Score: 2, Informative
      Oh man, good think you dont need a "social security number" or anything for getting a job or paying taxes or that 95% would be *SCREWED*!

      Being British, I dont have a "social security number" you small minded wanker

      --
      The problem with slashdot is that most of its users were bullied and stuffed into lockers as kids!
  2. .tel is ok by caffeination · · Score: 3, Insightful
    At least .tel is slightly international. Loads of European languages have telephone-related words beginning with "tel".

    This is way better than .biz, which I can only guess that they just banged out without thinking twice about.

    1. Re:.tel is ok by evilbuny · · Score: 2, Insightful

      Why do we need yet another TLD, this is purely a political land grab, e164.org already has proven you don't need a special TLD to do this, we have a large dataset already in operation and working. Jeff Pulver has been pushing .tel since 2000 and yet he could have built up his own zone to do this with less effort and money...

    2. Re:.tel is ok by wizrd_nml · · Score: 4, Funny

      In the Middle East we find this hilarious. Biz in Arabic means breast.

    3. Re:.tel is ok by Khuffie · · Score: 2, Funny

      And soon we'll have .zib ;)

    4. Re:.tel is ok by Midnight+Thunder · · Score: 2, Funny

      In the Middle East we find this hilarious. Biz in Arabic means breast.

      That sly bunch, so they did find a way for a .xxx domain to be put in place.

      --
      Jumpstart the tartan drive.
  3. eliminate top-level domains ? by boxlight · · Score: 2, Interesting

    Maybe it's about time we stopped conforming to top level domains?

    If I want a web site, why can't it be www.boxlight -- or www.boxlight.this.is.cool -- why does it have to end in .com, .us, .ca, or dot anything?

    boxlight

    1. Re:eliminate top-level domains ? by a_nonamiss · · Score: 4, Informative

      Actually, it's a function of how the current heirarchical domain system works. I'm not saying that it's absolutely required, but we would have to change quite a bit of the fundamental nature of the Internet if we eliminated all TLD's. I'm going to grossly oversimplify here, but basically, when I submit a query for foo.com, the very first thing queried is the top level domain, in this case, .com. If I were to submit a query to foo.org, the query would take a different path in resolving the name. Same with foo.net, foo.us, foo.biz, etc. The bottom line is that something needs to provide the first basic direction as to how the query is resolved. foo.com is a sub-domain of .com. support.foo.com is a subdomain of foo.com. us.support.foo.com is a subdomain of support.foo.com, etcerera. Without top level domains, we would basically make every DNS query a top-level query, and we would have to change the basic structure for how the Internet works. Note: for a more detailed definition of how DNS queries work, I highly recommend googling the subject. Makes for good nerd reading, and I'm sure the thousands of pages you get will do a better explanation than my single paragraph.

      --
      -Arthur
      Cave ne ante ullas catapultas ambules
    2. Re:eliminate top-level domains ? by The+Snowman · · Score: 5, Funny

      But imagine if the internet was just a vast wasteland of porn and spammers.

      That doesn't require any imagination.

      --
      24 beers in a case, 24 hours in a day. Coincidence? I think not!
    3. Re:eliminate top-level domains ? by hr+raattgift · · Score: 2, Interesting
      how the current heirarchical domain system works ... we would have to change quite a bit


      Well... really what would have to change is (non-recursive-querying) resolver code, and since that is distributed to practically every Internet host, that likely would take time.

      However, the server-side and administrative-side changes would stay largely the same, and there is no need to abandon hierarchical delegation of parts of the global distributed dabase.

      There are two obvious approaches.

      The first possible approach is to group arbitrary strings into three-or-four character groups and look up those substrings hierarchically. For example, "unformatteddomainname" would result in lookups for "name" "main" "eddo" etc., essentially as if it were originally written "u.nfor.matt.eddo.main.name." under the current system, with authoritative nameservers for the root and each subdomain.

      An alternative hierarchicalization of arbitrary domain names -- implemented and demonstrated in practice -- is detailed in RFC 2317 which allows for non-octet-boundary IN-ADDR.ARPA. DNS names, since classless inter-domain routing has a different hierarchy from the legacy DNS.

    4. Re:eliminate top-level domains ? by enjahova · · Score: 2, Funny

      And in Chinese it can mean girl, so if we just cycle the languages we get nu nu nu = naked girl now

      --
      "how can they call it a MINE if everything here is THEIRS?!?!" -Straight Jacket
  4. This is a really good idea by BadAnalogyGuy · · Score: 4, Funny

    We can put it to good use like .coop, .cat, .biz, .arpa, .aero, .info, .jobs, .mobi, .museum, .name, .pro, .travel, and .int.

    God knows it's time for .tel.

  5. Phone sex by thewiz · · Score: 4, Funny

    In the spirit of delicio.us, I can see a porn site called showand.tel being registered.

    --
    If "disco" means "I learn" in Latin, does "discothèque" mean "I learn technology"?
    1. Re:Phone sex by Hogwash+McFly · · Score: 4, Funny

      Apparently De Beers have their eye on www.car.tel

      --
      Mother, do you think they'll like this sig?
  6. Intended purposes by Rob+T+Firefly · · Score: 4, Insightful

    It's pretty fun to watch ICANN and the domain industry constantly come up with new "specific-purpose" domains, which upon release sell to absolutely anyone and everyone regardless of the actual category of the site. Apart from the actually restricted ones like .gov, .mil, and .edu, sites' categories have had little to nothing to do with their domain extensions for ages now.

    Who still remembers when a .com actually meant a for-profit business, or when every .org was an organization of some kind?

    1. Re:Intended purposes by Haeleth · · Score: 4, Interesting

      Thankfully, we in the UK have a relatively sensible system of second level domains. .net.uk, for example, is ISPs only.

      Yes, but that doesn't stop plenty of people in the UK, like me, (ab)using the global .net TLD for personal sites.

      And why not? I'm no more a "com"pany or an "org"anisation than I am a "net"work provider. I'm not a "biz"ness, and I'm not dedicated to providing "info"rmation, and the domain is not my real "name". But nor do I want a country-specific domain -- my site is of very limited interest to the vast majority of people, but the tiny community it interests is spread right across the globe. My site isn't aimed particularly at people in the UK, so why should it have a misleading .uk on the end?

      What it comes down to is, there is no point whatsoever in trying to force an artificial hierarchy onto something like the internet, which is an interconnected network, not a neat and nicely categorised tree. It doesn't work. It's pointless and confusing. Let's just give it up already, okay?

    2. Re:Intended purposes by fossa · · Score: 2, Interesting

      Now that I think about it, the divisions into "com", "net", "org" help avoid collisions, but do so in a most useless manner. Say for example, that McDonalds is a purveyor of fine foods, and registers mcdonalds.com. Now, Old McDonald had a farm but now sells farm equipment and would like to register mcdonalds.com. Trademark law allows McDonald's Fast Food and McDonald's Farm Equipment to coexist, but it is unfair to allow one to register the domain but not the other. One soultion would be to deny mcdonalds.com from everyone, requiring mcdonalds-fast-food and mcdonalds-farm-equipment, but in a brand driven society this would probably fail for brands spanning a wide range of products.

      I propose completely arbitrary TLDs to avoid collisions as an admission of the futility of attempting to classify domains with TLDs while keeping some collision avoidance. The new TLDs might be colors for example. mcdonalds.red and mcdonalds.blue would point to different sites, and McDonald's Farm Equipment would not be allowed to register in more than one TLD. The TLDs would need to be great enough in number and generic enough so that one TLD would not become more desireable than any other. That may be impossible to solve... Colors may not work, alphabets have an order (is mcdonalds.a superior to mcdonalds.b?), numbers have both an order and are not easy to remember, and any words might combine fortunately or unfortunately with the domain a la del.icio.us.

      But, if an arbitrary TLD scheme could be come up with, typing "mcdonalds" in a browser would find all registered mcdonaldses and display them possibly along with a short description (from a meta html tag scraped from the website? or a new DNS entry?). If there was only one mcdonalds, then the browser would simply go there. This might be an unfair advantage to unique trademarks that are then able to keep out any business with the same name...

      And for those who need domain to IP address lookups without going through a disambiguation process, they'd simply need to remember the correct TLD (red, blue, etc.) much as is done now.

  7. Pretty pointless imo... by c0l0 · · Score: 2, Insightful

    Of course that's another chance for ICANN, VeriSign and domain name resellers to cash in without much of a hassle, due to DNS' easily extensible and robust nature - however, much like .info and .name, this TLD presumeably won't be a big hit.
    The problem with all these newly introduced TLDs is that they don't ring a bell for the average joe on teh intarweb, since most casual users are familiar with .com, .net and maybe .org only, plus maybe their country's TLD.

    --
    :%s/Open Source/Free Software/g

    YTARY!
  8. MichaelBolton.Tel by JeanBaptiste · · Score: 5, Funny

    No way. Why should I change? He's the one who sucks!

  9. Another dumb idea by Billosaur · · Score: 4, Insightful

    When is everyone going to stop assuming that issuing new TLDs is going to solve all their problems? What, is it impossible for people to update the contact information on their personal web sites now, or has their been some fundamental change to HTML/XML of which I am unaware?

    This is a dumb idea. I won't even touch the personal namespace problem, which should be evident to anyone with a brain. The only way that would work is if everyone had five names. You know there are going to be squabbles over company names, as old and new companies jockey for the .tel names that offer them the best marketing bang for the buck.

    Need a place to put your contact information? Try www.contact.your-web-site-name-here.whatever. ICANN needs to stop polluting the TLD pool.

    --
    GetOuttaMySpace - The Anti-Social Network
    1. Re:Another dumb idea by RemovableBait · · Score: 2, Insightful

      The whole thing is dumb. Surely it isn't all that difficult to use subdomains, like tel.foo.com or tel.foo.net?

      If everyone adopted the format: tel.{company}.{tld} for their contact page, rather than bitching about new TLDs, then the number of collisions will be fewer (like foo.com, foo.net) and the world would be just as happy.

      Disclaimer: I haven't read (nor will I read) TFA.

  10. Those who do not understand 'finger' by Gothmolly · · Score: 5, Insightful

    Are doomed to reinvent it.

    So lets see, we create a whole separate _TLD_ that people/companies must register, just so people can have www.foo.tel, which is essentially a directory of who's who at www.foo.com?

    This is completely idiotic. How about "finger @foo.com | grep -i 'your name'" Obviously wrap it into some kind of GUI, or do something as simple as a web front end to an existing in-house address book?

    Geesh. Next someone will invent the ".mail" TLD, which is the address for foo.com, that you use to send email to. what about ".web" ?

    --
    I want to delete my account but Slashdot doesn't allow it.
  11. How odd by Wellington+Grey · · Score: 2, Funny

    Todd Masonis, a co-founder of contact management service Plaxo Inc., is familiar with the hassles of keeping track of everyone. His parents have had the same house and phone number for some 30 years, and "for a long time that was how they are identified," Masonis said.

    Really? Your parents are called Mr and Mrs 945 Chestnut Street? How odd.

    -Grey

  12. Boy does this sound dumb by hrieke · · Score: 2, Insightful

    .tel provides nothing that currently isn't available right now- Companies have contact pages with the information that you need to fax, phone, or email them your enquiries, people have their email and myspace pages, and all that I can see a .tel page doing is a refer URL forwarding.

    I see this as another $35 per year revenue for the domain registers.

    --
    III.IIVIVIXIIVIVIIIVVIIIIXVIIIXIIIIIIIIVIIIIVVIIIV IIVIIIIIIVIII...
  13. Hey! My Contact Info's Online by aplusjimages · · Score: 2, Insightful

    I don't get why an individual would want to buy a domain name and server space just to park their contact information. Are they aiming for the business individual? Why couldn't I just put it on my regular website? I don't see the point in getting a domain name for this. Like the artical stated, this is overkill for something that is already done. Search engines already find contact information for companies that have it on their regular site. Plus if a company did do this it would take a while before the search engines would be it up. Googles sandbox time is like 6 months, so for about 6 months people wouldn't be able to find a companies contact info unless they found it through the company site.

    --
    Can I bum a sig?
  14. Too little too late by suv4x4 · · Score: 2, Interesting

    It's not that I don't want to see ".tel" happen, but what is taking them so long to approve and implement new top-level domains anyway.

    It's because they were so late to introduce a large variety that ".com" become synonymous with "web" and everybody wanted his site to be a ".com"

    Should've they introduced domains like .tv, .biz and .tel (and .xxx) from the very beginning and at least a dozen more for each specific area of interest/business, we'd not have the ridiculous situation with domain scarcity we have today (even if, as I wrote earlier, it's still possible, although frustrating, to find a good .com domain nowadays).

  15. This is a wonderful idea! by Tim+C · · Score: 4, Insightful

    companyname.tel is so much better than companyname.com/contact.html!

    Man, I'm in the wrong business; if only I could get paid for coming up with ideas like this...

  16. Since I'm a pimp by aplusjimages · · Score: 3, Funny

    I was thinking of buying ho.tel. That way clients can easily find the number for a pro they like.

    --
    Can I bum a sig?
  17. An idiotic idea that shows domain names are broken by earthbound+kid · · Score: 2, Interesting

    This is a moronic idea. I'm sure someone else in the thread has explained why by now. Here's my beef though: domain names are a fundamentally bad idea.

    Think about it. Do we still need domain names? People made up the "I'm feeling lucky" ifl: protocol as a joke, but isn't it true? Can't we find anything with Google anyway? Why should we have to remember a particular address with a complicated system of slashes and characters to get to a particular page? Right now, my URL is http://slashdot.org/comments.pl?sid=183301&thresho ld=3&mode=thread&commentsort=0&op=Reply. But this is an implementation detail. Why am I, a consumer, being exposed to this? Irrelevant implementation details should be hidden from the user! Is what we're seeing now really so far removed from showing me slashdot's IP address? We cover up IP addresses with domain names, because we know it's too hard for people to remember a series of random numbers, but why can't we go the next logical step after this?

    Here's what I'm proposing:

    Let's extend ifl: or something like into a real protocol. A trusted source, or better a network of user selectable sources, assigns keywords to URLs based on tagging by users via hyperlinks to the source and delicious-like tags. Normally, the URL bar shows nothing but the title the site has given itself (in our case, "Slashdot") and the particular page being viewed ("Reply to thread"), but on request, the URL bar can generate a user shareable set of keyword tags for the site with hash codes for pages to prevent collision (think about the addresses generated snipurl and the like; "ifl:Slashdot/4bacc23"). For the purposes of bookmarks, traditional URLs can be stored, but since these URLs won't be exposed to users, Ford Motor company can use a23rf2.ifl and Ford Modeling Agency can use j737bdh.ifl, and no one will care, since it won't be possible to hijack a keyword without the agreement of the majority of users. (No more Whitehouse.coms!) Domain names can stick around, so that people are free to assign multiple IPs to the same site, but the concept will become a background detail that users need to know nothing about. Until the technology is built into all browsers, URL-to-ifl translator sites can fill in the gap: "go to http://ifl.com/Slashdot/4bacc23 or just ifl:Slashdot/4bacc23..." but since this won't be hard to integrate into browsers as a plug-in, I imagine it can be implemented quickly.

    So, what do you guys think? Am I being naive about the possibility of the keyword space being kept pure without a registrar? Need I point out that the keyword space is *already* polluted, inspite of that barrier?

  18. All contact info in one place - FOR TELEMARKETERS by wowbagger · · Score: 3, Interesting

    Yes, so I can have FirstnameLastname.tel, with my telephone number, so the telemarketing scum can associate my name with my number and bother me.

    Yes, that sounds like a GREAT idea - I think I'll also put my social security number, my alarm codes, a Google maps link to my house, a picture of my house key, and my bank account numbers up there as well.

    Look, if my company wants to set up a contact page they can set up a web page under their already existing domain name. If I want a contact page, I can set it up under my already existing personal web space. What does a new TLD add to this?

    Now, *IF* they were talking about a new transport class (like http:// and ftp://) for encapsulating telephone numbers, such that a link to tel://8675309 would get me Jenny on the line, that *might* be useful.

    But hell - I haven't even signed up for MYCALL@arrl.net to avoid being spammed by any asshole who scrapes my callsign (and I already have this one jackass who has done exactly that - he scraped my callsign and now he keeps adding me to stupid services like plaxo and the like, even though I've told this tool quite sharply that I don't want him bothering me.)

  19. Something similar is already avaliable in the UK by BluhDeBluh · · Score: 2, Insightful

    The domain name .me.uk was originally design for firstname.lastname.me.uk but I only know of one site to use it, and that's a big torrent site. This domain name is pointless except for making companies buy yet another TLD, which really isn't required.

  20. I know by jimktrains · · Score: 2, Insightful

    Why not:

    ur-domain.ur-tld/contact.ext !?!?!?!?!?

    Whooooo the simplicity....

    --
    "You will do foolish things, but do them with enthusiasm." - S. G. Colette
  21. Whole top-level domains concept flawed by screaser · · Score: 2, Insightful

    Why do we need even more top level domains? So that companies must register yet another TLD to keep people from claiming pepsi.tel?

    In the minds of the vast majority of internet users, the extension is an afterthought at best. The company I work for is a .net, but of course we had to buy the .com because everyone types it... and the .org just in case... and what's this I hear about .co and .biz??? (comment from the PHB)

    Real progress would be in moving to simplify things; less top level domains. How about just one for governments, one for schools, and one for absolutely everything else?

  22. Contact info in an easily accessible location? by Theatetus · · Score: 3, Funny
    the proposed .tel TLD would allow individuals and companies to keep all of their contact information in an easily accessible location.

    Wow! If only someone had thought of that before!

    --
    All's true that is mistrusted
  23. Back to the future by metamatic · · Score: 3, Informative

    What you describe is, in fact, the original way the web was supposed to work. URLs were supposed to be a hidden layer of server-specific information; users would refer to pages via URIs, Uniform Resource Identifiers, and there would be a mapping layer from URI to the current URL.

    Unfortunately, URLs and DNS hacks turned out to be "good enough", nobody saw the need for a global location-independent naming system for web pages, and we ended up with today's system.

    --
    GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
  24. Re:Carefully Thoughtout? by NoSalt · · Score: 3, Insightful
    We may have finally defeated the stupid .xxx idea, and here comes the next brain fart.

    How can you say that a .xxx TLD a stupid idea??? I think it is a great idea. It seems like a fairly easy idea to keep porn out of the hands of kids while at the same time, letting those who want to look at porn do so without jumping through hoops OR having the government sue Google for our search practices!!!

    I have always believed it be a law that there be a new "META" tag in HTML. Something of the sorts

    <meta http-equiv="Content-Type" content="adult">


    Then ... the parents could set it up in the browser to lock out any page with that tag. It's that simple. No muss, no fuss.

    I am not in favor of censorship in any way but I am totally in favor of the choice of individuals and the choice of parents to protect their children. Censorship is bad but individual control is good.
  25. Bad analogy, BadAnalogyGuy by wowbagger · · Score: 4, Informative
    We can put it to good use like .coop, .cat, .biz, .arpa, .aero, .info, .jobs, .mobi, .museum, .name, .pro, .travel, and .int.


    Excuse me, but while I agree with 92% of your examples, .arpa is used any time you do a reverse DNS lookup - so it is VERY useful.
  26. Re:Surname is Last Name, not Family Name by clarkcox3 · · Score: 2, Informative

    Used a dictionary much?

    From www.m-w.com: "the name borne in common by members of a family". That sure seems to indicate that a "surname" is a "family name."

    From dictionary.cambridge.org: "the name that you share with other members of your family."

    According to www.etymonline.com: "Meaning 'family name' is first found 1375."

    --
    There are no tiger attacks in my area and it's all because this rock I'm holding keeps the tigers away.
  27. Cynical churning of market by NetSettler · · Score: 4, Insightful

    Odds are, this is just another plan to make more money for the registrars

    I don't see how it could be otherwise.

    First, the phone company already knows that the best way to index phone number is by soundex, to avoid massive problems caused by the fact that many people don't know the correct spellings of their friends' and associates' names. And they certainly aren't sounding like this will be the first domain indexed by soundex.

    Second, it's unlikely that domain ownership will be a prerequisite to having a phone number. I don't think they could sell that. (In fact, they might realistically make more by saying they were going to give away the domain with your name and invent a service called ... hmmm, let's see... how about the "unlisted domain" where the customer pays money to keep from being locatable.)

    Third, phone numbers have the virtue of being uncorrelated with a name. That's what makes them resolvable in ambiguity--they act as a cross-check to make sure you got it right. When you can't quite remember a number and think it's either 555-1234 or 555-1235 and then check information to find the first is for "Sam Smith" and the second for "Alex Jones", there's little doubt how to resolve things. But if you thought the number was 1387.Sam.Smith.com or 1386.Sam.Smith.com or maybe 1387.Samuel.Smith.com or maybe 1386.Samuel.Smith or 1387.Sam.Smythe.com or... Obviously finding out that the mis-remembered number matches a lot of same-named people won't help at all. (If you believe in correlating names with telephones this way, it's a short conceptual hop to believing that a .pw domain would help you remember your password.)

    If you can't autogenerate good phone numbers (i.e., tell people what name they're supposed to use), as I and many others here have argued you can't, what's the alternative? Allow people to choose? Gads, with all the domain squatting it's clear that this would allow much choice to a rich few and little choice to most people. And so it would not be fair at all. The fairest thing I can imagine is to not involve ICANN at all.

    And besides, back to the original point about this being a ploy to sell domain registries, if I wanted to have the domain system already remember my phone number, why wouldn't I just have people do nslookup on the names I already own? They already require domain owners to list their phone numbers.

    --

    Kent M Pitman
    Philosopher, Technologist, Writer