This document discusses the evolution of communication technologies from PBX systems to modern IP-based systems like SIP. It argues that current proprietary communication apps have moved "backwards" away from the open interoperability of TCP/IP. The document urges customers to take control and require open standards and interoperability when procuring real-time communication systems, referencing SIP specifications from 2002-2012 that define requirements for a modern, distributed, extensible system.

1. The hidden secret of
TCP/IP and the
Internet.
And how it affects your realtime platform.
Olle E. Johansson * oej@edvina.net * Twitter oej
Copyright Edvina AB, Sollentuna, Sweden 2012.All rights reserved.
1995.
The revolution starts.
17 years later and we’re
still imitating a PBX.
Time to change.

2. The PBX
• Key line systems was
introduced in the 50’s
• One phone, multiple lines
• The enterprise PBX
was introduced in the
1960’s
• Lowered the cost
• internal calls where free
• reduced need for outside
lines
Photo: Joseph A. Carr
The PBX was the heart
of the company.
And the receptionist knew everything
worth knowing in the company.
• This is old stuff.
Photo: City Light Photographic Negatives (Record Series 1204-01),
Seattle Municipal Archives

3. And the PBX is no
longer in the center.
Cell phones
Skype
Facebook
IM / Chat
Presense
E-mail
What’s the theme here?
The glue that makes this architecture work.

4. TCP/IP
What powers TCP/IP?
INTEROPERABILITY

5. What does this
long word mean?
INTEROPERABILITY
The glue that keeps the Internet going.
EROPERABILITY
INTEROPERABILI
INTEROPERABILITY
An agreement.
INTEROPERABILITY.

6. A promise.
INTEROPERABILITY.
A lot of work.
INTEROPERABILITY.
What drives it?

7. Customers.
Without customers controlling us, we can do whatever we
want.And what our marketing people want.
Results in the 90’s:
After many years of work.
TCP/IP
E-mail
WWW
LDAP
TLS

8. TCP/IP
E-mail
WWW
LDAP
TLS
Solutions we rely on.
Every day, every minute.
Where and when
did it go wrong?
Facebook
Twitter
Skype
XXYY
FaceTime

9. Trademarks.
Companies with one service. No interoperability. No
distribution.Total dependency.
We’ve gone backwards.
I’m old enough to remember the past.
IBM SNA
Novell IPX
Microsoft
Lan Manager
CC mail
MS Mail
DecNet

10. IBM SNA
Novell IPX
Microsoft
Lan Manager
CC mail
MS Mail
DecNet
This is exactly what
customers wanted to
avoid.
Customer pressure delivered the PC, Unix and TCP/IP
networks. Freedom from lock-ins from vendors.
Saving money by protecting your investment.
Who took over?
Venture capital. Large companies.Ask yourself.
How does this affect
the PBX?

11. We’re moving
backwards in time.
No focus on
interoperability.
Lync. Skype. Many others.
Failed interoperability.
For years.
SIP SIMPLE Presense and IM.

12. Proprietary telephone
provisioning protocols.
Digium - the ”open” telephony company
WebRTC won’t help.
WebRTC just makes it easier to provide proprietary
communication systems.
It’s time for all of
you to wake up.
Good morning!

13. WAKE UP!
Stop blaming the
vendors.
They sell what you buy. It’s in their best interest to lock
you in. Keep you in control.
The one with
money has control.
You are the customers. Use your power!

14. <break>
Think about it for a while. Do you really want to be
controlled in your business? Limit your choices?
What has
happened in the
world of SIP?
Quite a lot.And nothing.
RFC 3261 was
published in 2002.
Implemented to 80%.
2002
2012

15. SIP is based on the IETF
architecture for TCP/IP.
10 years.And we still need to learn.
2002
2012
Distributed.
Domain-based federation. A network of networks.
2002
2012
Scalable.
Stupid core. Intelligent endpoints.
2002
2012

16. Connected.
All hosts should be able to contact any other
connected host.
2002
2012
Extensible.
SIP solves one problem: Session management.
What you do with it is up to you.
2002
2012
Where and when were
these rules defined?
Stupid core. Intelligent endpoints.
Connectivity end2end.

17. the goal is full "open system
interconnection": an Internet host must
be able to interoperate robustly and
effectively with any
other Internet host, across diverse
Internet paths.
RFC 1122, 1989
However, isolated LANs seldom stay isolated
for long; they are soon gatewayed to each
other, to organization-wide internets, and
eventually to the global Internet system.
In the end, neither the customer nor the
vendor is served by incomplete or
substandard Internet host software.
RFC 1122, 1989
RFC 1122, 1989
So where did we go wrong?
We’re stuck with a 50 year old PBX architecture.
A telco model forced onto the TCP/IP architecture.

18. I have at least five chat
apps, six voip apps.
Using separate islands of communications. It’s way too
complicated for someone soon 50 years old.
E-mail doesn’t
work that way.
Take control of our
communication.
After 50 years with the PBX, we need to think in new
ways for IP based realtime communication.
1. No inside/outside
BYOD and 3G devices killed that paradigm.

19. 2. Be able to
trust the system.
Apply Security.
3. No vendor lock-ins
Be in control of your communication system.
4. Don’t trust yourself.
Be open for innovation and evolution.

20. 5. It’s personal.
Focus on the individuals.
6.Video everywhere.
With WebRTC two-way video will be in every browser.
7. Build for global
communication.
TCP/IP is both IPv4 and IPv6 today. Internet growth in
Europe will only happen in IPv6.

21. Keywords:
Realtime applications
Client diversity
SIP in the organization
Open SIP federation
TLS/DTLS
IP
”Computer! Localize
Chief O’Brien”
Speech is an important
part of the future.

22. ”We need
something SIP-ish”
Best effort procurement with poor specs.
Known and proven to give bad results.
SIP 2012.
Much more than RFC 3261.
GRUU.
OUTBOUND.
ICE. SRTP/DTLS. SIP Identity
And more...
Opus.
WebRTC. Session timers.
Stuff I’ve never seen in
call for tenders.
It’s time for change.
GRUU.
OUTBOUND.
ICE. SRTP/DTLS. SIP Identity
And more...
Opus.
WebRTC. Session timers.

23. SIP2012 :: Defining
modern requirements
Helping customers procure better systems.
Interoperability in
realtime communications.
SIP done right.As required by customers.
Here’s what
I want
you to do.

24. Aim to retire the PBX.
Your company will survive.
Migrate away from
one-company-one-
brand systems.
Require interoperability.
Update your
specifications.
Refer to the SIP2012 reference profile when
buying SIP equiment and software.

25. For SIP trunks:
Refer to SIP Connect from the SIP Forum.
Customers:
Please take
control.
www.open-stand.org
I want to be free.
If you don’t want to be free, call your nearest
<large company> representative today and
ask him what you should buy next.
And give him full access to your credit card too.

26. Thank You.
TACK! Mina damer och herrar!
http://edvina.net/sip2012