<div style>Shouldn't a phone line service be considered for what it really is supposed to be, a fixed two-way channel of communication? Packet networking is not the same, and so comparing a letter in the post doesn't quite fit the argument as I see it.</div>
<div style><br></div><span style>-ndm</span> <br><br><div class="gmail_quote">On Mon, Apr 16, 2012 at 4:29 PM, Rod Veith <span dir="ltr"><<a href="mailto:rod@rb.net.au">rod@rb.net.au</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Mark,<br>
<br>
I think we're largely in agreement though I do care what about the 'vector'<br>
I use. Would be interesting in market research on what most people think.<br>
<br>
My views and use of end user technology will undoubtedly change with the<br>
technology however with present day technology part of the reason why I care<br>
is due to user interface issues, device operation and the content/message I<br>
want to send. Voice mails tend to rely on someone retrieving the message,<br>
while texting goes straight to a mobile handset. Email is better for<br>
communicating considered and prepared thoughts/ideas, record keeping and<br>
record retrieval. Conversation is great for discussing ideas, Q/A sessions<br>
leading down different paths etc. Have you never been in an email<br>
conversation that took two weeks because business managers or the other<br>
party didn't want to 'talk' to you? Whereas a simple 10 min phone call<br>
would have fixed the issue straight away!<br>
<div class="im"><br>
"I'm not so sure. The only reason EBCDIC vs ASCII happened was because<br>
there were people who felt strongly about whether EBCDIC or ASCII was the<br>
</div>best answer." Not so. It depended a lot on what platforms the<br>
business applications were written. As data sharing/interlinking become a<br>
business issue, converting from one to the other platform was a headache for<br>
the IT managers (at least the ones I dealt with).<br>
<div class="im"><br>
" Once the world goes fully IP or has decent, flexible and cost- effective<br>
</div>IP gateways, the ENUM will > come, ... Nope, I think it's already<br>
<div class="im">obsolete. The problem it was supposed to solve has been solved by search<br>
</div>engines." Nah, search engines won't make a call to my son's mobile.<br>
<br>
Number/identifer portability is important. And it will need to do different<br>
things depending on the use being made of it. I don't particularly care if<br>
it SIP indial, PSTN indial or something else. A receiver needs to have<br>
multiple incoming "identifers" and doesn't really care how it happens. But<br>
this is where ENUM or whatever we call it is important, the technology needs<br>
to be told a 'destination' and either deliver a message or open<br>
communications with that destination.<br>
<span class="HOEnZb"><font color="#888888"><br>
Rod<br>
</font></span><div class="im HOEnZb"><br>
<br>
-----Original Message-----<br>
From: Mark Newton [mailto:<a href="mailto:newton@atdot.dotat.org">newton@atdot.dotat.org</a>]<br>
Sent: Monday, 16 April 2012 3:37 PM<br>
To: Rod Veith<br>
Cc: <a href="mailto:ausnog@lists.ausnog.net">ausnog@lists.ausnog.net</a><br>
Subject: Re: [AusNOG] M2 buy Primus<br>
<br>
</div><div class="HOEnZb"><div class="h5">On Mon, Apr 16, 2012 at 03:20:29PM +1000, Rod Veith wrote:<br>
<br>
> Re: Universal ENUM.<br>
> It doesn't really matter if it is a number or name.<br>
<br>
It does if we're talking about enum :)<br>
<br>
> The concept of one<br>
> identifier is what is important. Plus type of contact requested. Do u<br>
want > to talk to the person in real-time, send them a text message, a<br>
voice > message, an email, content (photo, document etc), or text chat.<br>
<br>
I see them all as user-interface issues.<br>
<br>
I'm not sure that the upcoming generation of users really care about which<br>
of those vectors they use either. They're just as happy to continue a<br>
conversation via an SMS every 6 seconds as they are via the spoken word.<br>
Facebook chat is indistinguishable from Facebook messages which are<br>
indistinguishable from email.<br>
Communications facilities *and* use-cases are both separately and<br>
simultaneously converging.<br>
<br>
(what's the difference between a voicemail message, a voice recording<br>
carried by MMS, or an email message with an MP3 MIME attachment?<br>
Answer: The user interface abstracts the differences away; they're all "Send<br>
my voice to someone else" techniques, and the end user doesn't need to know<br>
which one their pricing-model-aware handset chooses to use to facilitate<br>
their communication needs)<br>
<br>
I'm not sure that "the concept of one identifier" is as important as you<br>
think, too. Do end users actually care?<br>
<br>
> The issue has been the different underlying technologies. Remember the ><br>
EBCDIC and ASCII issues in the early days. Messaging (telephony, texting, ><br>
email etc) is like EBCDIC and ASCII in the 1970s.<br>
<br>
I'm not so sure. The only reason EBCDIC vs ASCII happened was because there<br>
were people who felt strongly about whether EBCDIC or ASCII was the best<br>
answer.<br>
<br>
Now we say, "I don't care, send me whatever you want," and use a user<br>
interface abstraction layer to make them both look like text on a page.<br>
<br>
> Once the world goes fully<br>
> IP or has decent, flexible and cost- effective IP gateways, the ENUM will<br>
> come,<br>
<br>
Nope, I think it's already obsolete. The problem it was supposed to solve<br>
has been solved by search engines.<br>
<br>
<br>
<br>
As an aside: If number portability is actually important, how about a "SIP"<br>
address family for BGP4? Route a new 100 number range to your PABX by<br>
having it announce 61885551200/9, and port individual numbers by announcing<br>
more-specific prefixes :)<br>
<br>
- mark<br>
<br>
<br>
<br>
_______________________________________________<br>
AusNOG mailing list<br>
<a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><br>
<a href="http://lists.ausnog.net/mailman/listinfo/ausnog" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
</div></div></blockquote></div><br>