but nothing has stopped dialing a .com from happening. All you'd need is a special file like phone.txt in the top level directory.
DubDubDubDot,
Their is a simple reasons why .tel better suit TELecom usage that .com :
-> It is simplier, easyer and cheaper to set with .tel. This is because .tel was thought at very first for telecom usage.
Let s admit the fact, .tel and .com are simply not intended for the same usage.
One day, phone numbers will become phone names.
The question is what technology will better fill that need ?
It could be your proposal (phone.txt + https request), but it also could be .tel
I think .tel is atually the best finalized techno/standard for that needs.
Moreover http request takes too much time to resolve name to number. Just can't fit.
Regards
---------- Post added at 04:22 PM ---------- Previous post was at 04:13 PM ----------
In one case (http), you rely on DNS + webhosting,
In the other case (.tel), you rely on DNS only.
So .tel will globally be more thought (better uptime).
Anyway, let s think differently:
Does ANYONE here can offer a technology to provide phone names in a more simple, fast & secure way than .tel does ?
More globally,
One day, phone name ( Juan.tel) will replace phone number (+71.54687945), where will you be that day ? will you miss that turn ?