I'm bewildered by all the buzz surrounding the Internetâ''s new â''.telâ'' top-level domain. This new entity, sponsored by London-based Telnic, is intended to be a global repository of contact information for individuals and businesses. The twist here is that this information will be encoded into DNS (Domain Name System) records, allowing it to be distributed to the 12 million or so name servers around the world. When folks look me upâ''perhaps as BewilderedDave.telâ''the DNS will not direct them to a Website, as it typically does. Rather, they will access my contact information directly from the records that are returned by whatever name servers their computers are using to look up IP addresses.
That much is clear. Itâ''s also apparent from the news coverage and the descriptions on Telnicâ''s Website that the company has put mechanisms in place for those with .tel domains to control access to their contact information, should they not wish all of it to be publicly available. Whatâ''s confusing is why this service would prove all that helpful to either individuals or to businesses.
Consider the scenario Telnic uses to explain how an individual using a .tel domain can guard his or her privacy. In the companyâ''s illustrative example, Alice (alice.tel) meets someone named Gary. (Bob is occupied in another role.) She informs Gary about her .tel address and gives him the URL for a login page at a Website run by Telnic. He then uses Telnicâ''s Website to create a â''friend request message,â'' which gets transmitted to Alice. She receives the message, reading within it a short greeting from Gary reminding her that this â''friendingâ'' request comes from the guy she just met at the local pub. Alice then puts the wheels in motion to allow Gary to obtain access to parts of her contact information that she doesnâ''t share with the general public.
Obviously, Gary didnâ''t impress Alice enough when they first met. If he had, she surely would have just given him her phone number then and there, instead of asking him to jump through hoops.
Telnicâ''s description explains in detail how the friending scheme worksâ''how encrypted contact information is put into a subdomain of alice.tel using Garyâ''s public encryption key so only he can read it. Telnic further explains that if Alice has a falling out with Gary, â''she simply stops publishing private contact dataâ'' at that subdomain. Telnicâ''s explanation is silent, however, on what to do about the fact that Gary may still retain Aliceâ''s phone number, written perhaps in a small black book.
I suppose Alice could change her phone number, cutting off Gary without irritating too many of her other friends because theyâ''ll be using the always-up-to-date alice.tel to reach her from their Internet-enabled mobile phones. But how about Aliceâ''s grandmother?
To me, the friending mechanism seems too cumbersome, and the actions needed to cut someone off are too drastic. I am also skeptical about how useful it might be for reaching businesses, although they will in general publish contact information thatâ''s always freely available to the general public.
The problem is that I wonâ''t know the .tel domain name of the business I want to reach. How can I figure out the .tel name for, say, the new pizza joint that just opened down the street? Even if I remember that the name of the place is Joeâ''s Pizza, using joespizza.tel is more likely to return information about a restaurant in Los Angeles than the one in my home town. So Iâ''d be more inclined to Google Joeâ''s Pizza, using as much information as I have about it to find its Website, where I can look up its contact information easily enough.
Perhaps Iâ''m just too mired in late-20th-century thinking to see the value of the new service. Somebody please tell me what Iâ''m missing.