Yesterday, the ICANN approved the creation of the .TEL top level domain.Â Telnic has been championing the creation of this domain since the late 90’s, and will be the administrar. According to the press release:
The .Tel domain will enable people to reach a business from any Internet enabled device (computer or mobile) simply by typing, for example, â€œHertz.telâ€. The user will then be able to connect directly to a Hertz representative or navigate through a list of services that Hertz may offer. Businesses can easily extend their brands into this new space and enhance the way customer inquiries are handled.
In addition, individuals can use the .Tel domain to publish and update their contact information directly in the DNS. These individuals will decide, in real time, by what means their friends and colleagues will be able to reach them. This could include: VoIP, conventional telephony (fixedline or wireless), email, SMS, Skype, AIM and many more.
Nobody can reasonably argue that a unified contact space is a bad thing.Â Semantically overloading the domain system in this fashion seems like a bad idea to me, though.Â I already have published contact information for email, Skype etc.Â Â Shouldn’t weÂ simply prepend the protocol to an existing URI as we do now?Â sms:firstname.lastname@example.org, mailto:email@example.com, sip:firstname.lastname@example.org, etc?Â It brings up an interesting question when youÂ do something like this: tel:email@example.com — how do you translate the address into aÂ e.164 phone number, and if the user has multiples registered, which doÂ IÂ use?Â
I could be completely wrong, but it looks to me like this is a dead end.Â What are your thoughts?