IMTC Connect 2015, SIP Parity Activity Group Update

SIP Parity Activity Group Update

1

Charles Eckel ([email protected])IMTC SIP Parity AG Chair

IMTC Connect 2015: SIP Parity AG Update

mailto:[email protected]

2

What is the IMTC?• International Multimedia Telecommunications

Consortium• Mission:

Promote and facilitate the development and use of interoperable, real-time, multimedia

telecommunications products and services based on open international standards.


3

Problem Statement

Standards interpreted differently

Solutions are competitive

Interoperability is hard


SIP Parity Activity GroupFocus• Provide video profile for SIP that matches capabilities of H.323• Enable migration from H.323 to SIP

What We Do• Provide forum for members to agree on best practices• Develop and advocate requirements to SDOs• Organize and participate in interoperability testing events

4IMTC Connect 2015: SIP Parity AG Update

Best Practice Documents• SIP Video Profile– Add video (H.264) to SIP based audio telephony

• Role Based Video– Add content sharing to SIP based video conferencing

• SIP Security– Lead adoption of secure signaling (TLS) and media (SRTP)


6

SIP Video Profile• Asymmetric negotiation

– Bandwidth, Video Coding Complexity• Bandwidth Indications - Session level vs. media level• RTP/AVPF profile – SDP offer/answer negotiation• Flow control - SDP vs. RTCP feedback (TMMBR)• Intra frame request - SIP INFO vs. RTCP feedback (PLI/FIR)• H.264 – Recommended set of parameters


7

Recent Developments• IMTC1013 – Published (obsoletes IMTC1012)

– Improves interworking with IMS/3GPP• IMTC1013bis – Draft

– Addresses interworking issue with RTCP feedback parameters• Test Cases

– Updated to fix issue with “m-stream” vs. “mstrm”


SIP Video Profile

http://www.imtc.org/documents/official-documents/

8

Role Based Video Streams• Video - “main” vs. “presentation”• RFC 4796 “content” attribute• Mapping:

– “slides” for H.239 “presentation”– “alt” for H.239 “live”– “main” for the main video stream

• BFCP (Binary Floor Control Protocol)– UDP instead of TCP for transport


9

Recent Developments• IETF BFCPBIS Working Group (Charter)– draft-ietf-bfcpbis-rfc4582bis in RFC editor’s queue– draft-ietf-bfcpbis-rfc4583bis in working group last call

• IMTC best practice to be updated per new RFCs– IMTC Last Call– Publish as IMTC10xx


Role Based Video Streams

http://tools.ietf.org/wg/bfcpbis/charters

http://tools.ietf.org/wg/bfcpbis/draft-ietf-bfcpbis-rfc4582bis/



10

SIP Security Profile


11

Recent Developments• IETF draft– An Opportunistic Approach for Secure Real-time

Transport Protocol (OSRTP), draft-johnston-dispatch-osrtp

• IMTC best practice to be updated per new RFC– IMTC Last Call– Publish as IMTC10xx


SIP Security Profile

https://datatracker.ietf.org/doc/draft-johnston-dispatch-osrtp/




12

SuperOp! 2015 Enhancements • WebRTC/SIP Interworking– Cooperative effort between SIP Parity and WebRTC– Based on SIP Video Profile best practice/test cases

• Lync/SIP Interworking• Network impairments to facilitate testing of video

resiliency and recovery


13

SuperOp! 2015


SIP Video Endpoint

Lync Server

WebRTC Server

SIP Video Endpoint

SIP Proxy / B2BUA /

SBC SIP MCU

SIP / WebRTC Gateway

SIP / Lync Gateway Lync

Endpoint

WebRTC Endpoint

SIP Video Endpoint

14

1. Network Impairments– Bandwidth cap only, not good enough

2. RTCP Feedback interoperability issue discovered– SIP Video Best Practice to be updated to provide

clarifications and guidance3. SIP Video Test Case “m-stream” vs. “mstrm”– Best practice already addresses correctly– Test case fixed to align with best practice

Discoveries


SuperOp! 2015 Results• SIP Video Profile

– 400% increase in number of results reported– 51% Pass (down from 66% in 2014)– 2% Fail (same as in 2014)– 47% Not tested/implemented (up from 31% in 2014)

• Role Based Video– 400% increase in number of results reported– 52% Pass (down from 57% in 2014)– 5 % Fail (up from 4% in 2014)– 43% Not tested/implemented (up from 38% in 2014)

• SIP Security– First time recording detailed results– 38% Pass, 3% Fail, 59% Not tested/implemented– SRTP media achieved in 61% of test combinations


16

1. IPv6 apps2. WebRTC/SIP gateway separate from WebApp

in cloud– Best practice or standard for WebApp to GW

3. UC SDN spec in ONF, interoperability in IMTC

New for SuperOp! 2016 ???


17

Recharter - SIP Interconnect AG• Provides a forum for IMTC member companies to

cooperate and pool resources on issues and extensions to SIP based enterprise communication applications.

• With its best practices documents providing a shared foundation, the group identifies and tackles challenges and opportunities with interoperability, operation, and integration of SIP based applications with emerging communication and networking technologies.


18

SIP Interconnect AG – What We Do• Organize interoperability test efforts (both virtual and face-to-

face). This are done in cooperation and coordination with WebRTC, MANE, SSV, and UC SDN activity groups and with SIPit

• Provide a forum for members to agree on an overall SIP profile for communication applications, particularly where it involves interconnecting with other application and network technologies (e.g. WebRTC, SDN, IPv6)

• Educate members on recent developments in SIP standards and market evolution


19

1. Review, improve, and publish best practices2. Participate in SuperOp! 20163. Champion new work items to address current

needs

Call to Action


20

Questions


IMTC Connect 2015, SIP Parity Activity Group Update

Technology

Transcript of IMTC Connect 2015, SIP Parity Activity Group Update