The issue I see with using email addresses;
1. Many people still use their ISP-provided email address. Which would
be fine if people used the VoIP service provided by their ISPs.
2. Those that don't use  use free email services, like Gmail. While
I could foresee Google offering a translation service that was
reliable and decent, what about all the tinfoil hat wearing people who
claim Google is taking over the universe and spying on their call
logs, and so refusing to use it? Also, what happens when Yahoo!Xtra
has to implement a filter for it?
3. Those that don't use [1,2] use their corporate/university email
addresses. I don't know about you, but the IT dept of the megacorp I
work for are very hesitant on implementing anything public-facing.
4. Those on custom domains could implement this, yes. I'd be first in
line. But as it wouldn't be as widespread as options [1-3], and so
imagine the confusion when I told someone "Hey, give me a call on
While a good idea in theory, it is much more dependant on providers,
who may or may not have or want anything to do with VoIP.
On 31/12/2008, at 11:44 , Jasper Bryant-Greene wrote
How about I just tell you my "phone number"
is freddie(a)beer.com, your
software looks up "_sip._udp.beer.com. IN SRV", and places a call to
freddie at the server returned by that record. It's an optimised,
point-to-point connection, and it doesn't involve carrying over
antiquities like PSTN phone numbers.
We already have identifiers on the Internet - email addresses - so why
we would choose to carry over cryptic strings of digits from an
antiquated system and use those for one communication medium - while
continuing to use email addresses as the identifiers for others -
Network Engineer, Unleash
ddi: +64 3 978 1222
mob: +64 21 129 9458
NZNOG mailing list