The document outlines the SIP 2016 initiative to create updated reference profiles for SIP implementations and adapt to current technological advancements. It highlights the evolution of SIP usage beyond hard phones, the necessity of new standards for mobile SIP, and various technical RFCs and guidelines essential for implementation as the industry moves forward. Legal notes underscore the confidentiality of the presentation and the need for organizational focus on software development and vendor engagement.

1. SIP 2016
Setting the standard for SIP implementations
@oej @saghul
SIP
2016
SDSCFFUOS

2. SIP
2016
SDSCFFUOS
Copyright 2016 SDSCFFUOS, Amsterdam, Netherlands. All rights reserved. All parts of this presentation is CONFIDENTIAL. This means you are not allowed
to remember it, quote it or even acknowledge that you even was there when it happened. Nothing really happened. Move on. Get a life. SIP a drink. Enjoy!
Internal note: Our lawyers have too little to do. Can we get a lawyer to renegotiate their contract? REALLY?
SPEAKER INTRO
➤ Olle E. Johansson
➤ CEO of Edvina AB since 1987
➤ IETF RFC Author
➤ Saúl Ibarra Corretgé
➤ Director R&D, AG Projects
➤ IETF RFC Author
➤ Strange ties to the Mafia
➤ Both members of the steering group of the WG.76QP of
the SDSCFFUOS, Olle being the chair of the WG.

3. SIP
2016
SDSCFFUOS
Copyright 2016 SDSCFFUOS, Amsterdam, Netherlands. All rights reserved. All parts of this presentation is CONFIDENTIAL. This means you are not allowed
to remember it, quote it or even acknowledge that you even was there when it happened. Nothing really happened. Move on. Get a life. SIP a drink. Enjoy!
Internal note: Our lawyers have too little to do. Can we get a lawyer to renegotiate their contract? REALLY?
BACKGROUND
➤ SIP 2012 - one man effort by @oej
➤ Attempt to create a reference profile for purchase of SIP
implementations
➤ Base for founding the new organisation SDSCFFUOS
➤ SIP DEVELOPER S(PANISH|WEDISH) COMMUNITY FOR
FUTURE USE OF SIP
➤ Organisation goal: Create reference profile for SIP purchases one
year from now: In active use January 1, 2018
➤ Status meeting at Voip2day 2017
➤ Interop tests and certification tests at Voip2day 2017
➤ Internal note: Can we add more text to this slide? It’s kind of empty.
SIP
2016
SDSCFFUOS

4. SIP
2016
SDSCFFUOS
Copyright 2016 SDSCFFUOS, Amsterdam, Netherlands. All rights reserved. All parts of this presentation is CONFIDENTIAL. This means you are not allowed
to remember it, quote it or even acknowledge that you even was there when it happened. Nothing really happened. Move on. Get a life. SIP a drink. Enjoy!
Internal note: Our lawyers have too little to do. Can we get a lawyer to renegotiate their contract? REALLY?
SIP 2016 - WHY
➤ SIP RFCs are more than ten years old
➤ The industry and standard forums have continued solving problems
➤ SIP is now used in web browsers, mobile phones and desktop apps,
not only in hard phones like ten years ago
➤ The move to mobile SIP, hosted PBX solutions and Internet-based
SIP trunks require new solutions
➤ The industry needs a new reference profile to base sales and
purchases on
➤ Motto: SIP moving forward!
➤ Internal note: Can speakers have t-shirts with motto and our cool logotype?
SIP
2016
SDSCFFUOS

5. SIP
2016
SDSCFFUOS
Copyright 2016 SDSCFFUOS, Amsterdam, Netherlands. All rights reserved. All parts of this presentation is CONFIDENTIAL. This means you are not allowed
to remember it, quote it or even acknowledge that you even was there when it happened. Nothing really happened. Move on. Get a life. SIP a drink. Enjoy!
Internal note: Our lawyers have too little to do. Can we get a lawyer to renegotiate their contract? REALLY?
INTRODUCTION
➤ SIP 2016 is based on the core SIP RFCs
➤ RFC 3261
➤ RFC 3263
➤ RFCs for SDP and RTP/RTCP
➤ etc etc (Internal note: We can’t list all those RFC numbers on one
single slide)
➤ In addition we have a set of additional standards added which
will be presented on coming slides
SIP
2016
SDSCFFUOS

6. SIP
2016
SDSCFFUOS
Copyright 2016 SDSCFFUOS, Amsterdam, Netherlands. All rights reserved. All parts of this presentation is CONFIDENTIAL. This means you are not allowed
to remember it, quote it or even acknowledge that you even was there when it happened. Nothing really happened. Move on. Get a life. SIP a drink. Enjoy!
Internal note: Our lawyers have too little to do. Can we get a lawyer to renegotiate their contract? REALLY?
ICE - INTERACTIVE CONNECTIVITY ESTABLISHMENT
➤ RFC 5245 plus dependencies (TURN, STUN)
➤ Why?
➤ To establish media according to best media path
➤ To allow media traversal over firewalls by using TURN
servers
➤ Future note: Trickle ICE for SIP will be part of SIP 2017
profile, as well as TURN re-establishment for mobile (RFC
8016)

7. SIP
2016
SDSCFFUOS
Copyright 2016 SDSCFFUOS, Amsterdam, Netherlands. All rights reserved. All parts of this presentation is CONFIDENTIAL. This means you are not allowed
to remember it, quote it or even acknowledge that you even was there when it happened. Nothing really happened. Move on. Get a life. SIP a drink. Enjoy!
Internal note: Our lawyers have too little to do. Can we get a lawyer to renegotiate their contract? REALLY?
SIP OUTBOUND
➤ RFC 5626
➤ Only with one flow
➤ Required to handle TLS connections from end-points to
service
➤ Includes NAT keepalives
➤ Will improve support for clients on mobile phones (Note: still
under discussion)

8. SIP
2016
SDSCFFUOS
Copyright 2016 SDSCFFUOS, Amsterdam, Netherlands. All rights reserved. All parts of this presentation is CONFIDENTIAL. This means you are not allowed
to remember it, quote it or even acknowledge that you even was there when it happened. Nothing really happened. Move on. Get a life. SIP a drink. Enjoy!
Internal note: Our lawyers have too little to do. Can we get a lawyer to renegotiate their contract? REALLY?
IPV6 SINGLE AND DUAL STACK SUPPORT
➤ RFC 7984 and RFC 3261
➤ To avoid carrier grade IPv4 NAT in mobile networks
➤ To support migration path to IPv6
➤ Please note SIP Forum implementation note on IPv6 for IPv4-
only devices

9. SIP
2016
SDSCFFUOS
Copyright 2016 SDSCFFUOS, Amsterdam, Netherlands. All rights reserved. All parts of this presentation is CONFIDENTIAL. This means you are not allowed
to remember it, quote it or even acknowledge that you even was there when it happened. Nothing really happened. Move on. Get a life. SIP a drink. Enjoy!
Internal note: Our lawyers have too little to do. Can we get a lawyer to renegotiate their contract? REALLY?
OPUS NEW MANDATORY CODEC
➤ In addition to G.711 alaw/ulaw in RFC 3261
➤ To support interoperability with WebRTC
➤ To better support Internet-based calls
➤ Needs to be adaptive and use RTCP feedback

10. SIP
2016
SDSCFFUOS
Copyright 2016 SDSCFFUOS, Amsterdam, Netherlands. All rights reserved. All parts of this presentation is CONFIDENTIAL. This means you are not allowed
to remember it, quote it or even acknowledge that you even was there when it happened. Nothing really happened. Move on. Get a life. SIP a drink. Enjoy!
Internal note: Our lawyers have too little to do. Can we get a lawyer to renegotiate their contract? REALLY?
DTLS - SRTP
➤ SRTP with DTLS key exchange mandatory
➤ TOFU (Trust on first use) implementation recommended
➤ MANDATORY to use on Internet-based calls (which will
mean ALL calls)

11. SIP
2016
SDSCFFUOS
Copyright 2016 SDSCFFUOS, Amsterdam, Netherlands. All rights reserved. All parts of this presentation is CONFIDENTIAL. This means you are not allowed
to remember it, quote it or even acknowledge that you even was there when it happened. Nothing really happened. Move on. Get a life. SIP a drink. Enjoy!
Internal note: Our lawyers have too little to do. Can we get a lawyer to renegotiate their contract? REALLY?
TLS
➤ TLS implementation according to IETF BCP
➤ Elliptic Curve certificates recommended
➤ SHA 256 signatures in certificates
➤ Support for EC certificates required
➤ Certificates following SIP Domain Certificates RFC
➤ TLS 1.0 minimum base level, TLS 1.2 RECOMMENDED
➤ For SIP 2017, TLS 1.2 minimum base level, TLS 1.3
RECOMMENDED
➤ Early warning: Use of UDP will be deprecated in SIP 2018 latest

12. SIP
2016
SDSCFFUOS
Copyright 2016 SDSCFFUOS, Amsterdam, Netherlands. All rights reserved. All parts of this presentation is CONFIDENTIAL. This means you are not allowed
to remember it, quote it or even acknowledge that you even was there when it happened. Nothing really happened. Move on. Get a life. SIP a drink. Enjoy!
Internal note: Our lawyers have too little to do. Can we get a lawyer to renegotiate their contract? REALLY?
RING TONES
➤ Implementations should only use 180+SDP for ring tones
➤ 183 + SDP reserved for early media messages from operator
➤ To enable alert devices for hearing impaired
➤ Early warning: SIP 2020 will disable early media. Billing will
be flat rate anyway.

13. SIP
2016
SDSCFFUOS
Copyright 2016 SDSCFFUOS, Amsterdam, Netherlands. All rights reserved. All parts of this presentation is CONFIDENTIAL. This means you are not allowed
to remember it, quote it or even acknowledge that you even was there when it happened. Nothing really happened. Move on. Get a life. SIP a drink. Enjoy!
Internal note: Our lawyers have too little to do. Can we get a lawyer to renegotiate their contract? REALLY?
CALLER IDS
➤ The primary caller ID signalled to and from end-users is the
From: header
➤ Service providers may internally use others, like PAID
➤ For SIP 2017, service providers will be required to implement
STIR Passport with digital signatures on caller IDs
(Ref: The IETF STIR working group)

14. SIP
2016
SDSCFFUOS
Copyright 2016 SDSCFFUOS, Amsterdam, Netherlands. All rights reserved. All parts of this presentation is CONFIDENTIAL. This means you are not allowed
to remember it, quote it or even acknowledge that you even was there when it happened. Nothing really happened. Move on. Get a life. SIP a drink. Enjoy!
Internal note: Our lawyers have too little to do. Can we get a lawyer to renegotiate their contract? REALLY?
TCP SIP RETRANSMITS
➤ (Note: Still under discussion)
➤ SIP on mobile devices suffer from TCP proxys
➤ In order to handle this retransmits is REQUIRED for SIP over
connection-oriented transports in the same way as specified
in RFC 3261 for UDP
➤ Early warning: May be part of SIP 2017

15. SIP
2016
SDSCFFUOS
Copyright 2016 SDSCFFUOS, Amsterdam, Netherlands. All rights reserved. All parts of this presentation is CONFIDENTIAL. This means you are not allowed
to remember it, quote it or even acknowledge that you even was there when it happened. Nothing really happened. Move on. Get a life. SIP a drink. Enjoy!
Internal note: Our lawyers have too little to do. Can we get a lawyer to renegotiate their contract? REALLY?
PLAN
➤ Decide on details (if possible?) during Voip2day 2016
➤ Publish spec on our cool new web site (work in progress) in
December 2016
➤ With your help, put pressure on all vendors
➤ Find out a business model for this work
➤ (free beers doesn’t get work done)
➤ Internal note: Maybe we can sell a lot of those cool t-shirts with our logo
and slogan?

16. “SIP Moving
Forward!
@oej @saghul
SIP
2016
SDSCFFUOS