<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<font face="Calibri" size="2"><span style="font-size:11pt;">
<div> </div>
<div>-----Original Message-----<br>
From: ausnog-bounces@lists.ausnog.net [<a href="mailto:ausnog-bounces@lists.ausnog.net">mailto:ausnog-bounces@lists.ausnog.net</a>] On Behalf Of Rod Veith<br>
Sent: Monday, 16 April 2012 4:30 PM<br>
To: ausnog@lists.ausnog.net<br>
Subject: Re: [AusNOG] M2 buy Primus</div>
<div> </div>
<div>I think we're largely in agreement though I do care what about the 'vector'</div>
<div> </div>
<div><font color="red">I’m not so sure.</font></div>
<div> </div>
<div>My views and use of end user technology will undoubtedly change with the technology however with present day technology part of the reason why I care is due to user interface issues, device operation and the content/message I want to send. Voice mails
tend to rely on someone retrieving the message, while texting goes straight to a mobile handset.</div>
<div> </div>
<div><font color="red">Texting? You probably mean the old version of messaging right? How much traffic has iMessage stolen? What is the forecast for messaging in 2015 to be SMS based rather than IP? How many people don’t even know the transport has changed
on their iPhone/iMessage except for the Blue text bubble? Does anyone think iCall is not around the corner? It’s funny how iMessage (message medium) then Facetime (video-conf medium) are here but the elephant in the room being traditional voice is still left
along. I wonder how long those deals between Apple and the US carriers last….?</font></div>
<div> </div>
<div>Email is better for communicating considered and prepared thoughts/ideas, record keeping and record retrieval. Conversation is great for discussing ideas, Q/A sessions leading down different paths etc. Have you never been in an email conversation that
took two weeks because business managers or the other party didn't want to 'talk' to you? Whereas a simple 10 min phone call would have fixed the issue straight away!</div>
<div> </div>
<div><font color="red">Talking face to face it better, but generally the least convenient. At the other end of the spectrum “Messaging” is probably not as good, but mostly more convenient than face to face.</font></div>
<div> </div>
<div>Number/identifer portability is important. And it will need to do different things depending on the use being made of it. I don't particularly care if it SIP indial, PSTN indial or something else. A receiver needs to have multiple incoming "identifers"
and doesn't really care how it happens. But this is where ENUM or whatever we call it is important, the technology needs to be told a 'destination' and either deliver a message or open communications with that destination.</div>
<div> </div>
<div><font color="red">Company/person identifier at the application is what matters. We don’t call a number, we call a person or a company (well except for IVR’s:)) Numbers were the teclo equivalent of the Duey Decimal system we used to find a person. The
rest is academic. I had a similar discussion with someone here recently (not dev) when they were explaining to me the importance of having a structured identifying system in the Contract_ID for our Contracts Register. So that “ABC_QLD_0001” would represent
the obvious. I explained that would be correct except we have these things called computers now and you don’t need an alpha version of duey-decimal to find things. You just have to make the connection at the application level. The rest is noise best handled
by silicon.</font></div>
<div><font color="red"> </font></div>
<div><font color="red">[b]</font></div>
<div><font color="red"> </font></div>
<div><font color="red">Sorry for the ugliness of the font/colours. Will sort this bloody Look0ut tonight.</font></div>
<div> </div>
<div><font face="Times New Roman" size="3"><span style="font-size:12pt;"><br>
<br>
<font size="1"><span style="font-size:7pt;">The information contained in this email and any attachments may be confidential. This email and any attachments are also subject to copyright. No part of them may be reproduced, adapted or transmitted without the
written permission of the copyright owner. If you are not the intended recipient, any use, interference with, disclosure or copying of this information is unauthorised and prohibited. If you have received this email in error, please immediately advise the sender
by return email and delete the message from your system. All email communications to and from NEXTDC Limited are recorded for the purposes of archival and storage.</span></font> </span></font></div>
</span></font>
</body>
</html>