1 / 20

Rethinking Application Protocol Standardization: Insights from SIP and Telecom Innovation

This document provides valuable insights into the evolution of application protocol standardization through the lens of Session Initiation Protocol (SIP) and its journey within the telecom innovation cycle. By examining industry trends, interoperability challenges, and lessons learned, we explore the implications for IETF and the broader technology landscape. Key topics include the cycle of innovation in telecom versus internet applications, the impact of proprietary features, and the necessary evolution of standards to keep pace with emerging technologies.

seven
Télécharger la présentation

Rethinking Application Protocol Standardization: Insights from SIP and Telecom Innovation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The End of Application Protocol Standardization (?) Jonathan Rosenberg Chief Technology Strategist, Skype

  2. Outline • Experiences and Lessons from SIP – the Telecoms Innovation Cycle • (Obvious) Industry Trends • The Internet Application Innovation Cycle and its Implications for IETF

  3. SIP for Beginners SIP Serverexample.com SIP Serverexample.org SIP SIP SIP RTP

  4. Example SIP Message INVITE sip:+17327654321@example.com SIP/2.0 From: J. Rosenberg <sip:+14082321122@example.com> ;tag=76ah Subject: Conference Call To: John Smith <sip:+17327654321@example.com> Via: SIP/2.0/UDP 1.2.3.4;branch=z9hG4bK74bf9 Call-ID: 1997234505.56.78@1.2.3.4 Content-type: application/sdp CSeq: 4711 INVITE Content-Length: 187 v=0 o=user1 53655765 2353687637 IN IP4 1.2.3.4 s=Sales c=IN IP4 1.2.3.4 t=0 0 m=audio 3456 RTP/AVP 0

  5. SIP Success: Products Hard Phones Soft Phones PSTN Gateways Session BorderControllers Firewalls

  6. SIP Success: Service Providers Backhaul, Peering e2e SIP Termination SIP Trunking

  7. SIP Success: Industry

  8. SIP Failure #1: Same Old Telephony

  9. The Telecom Innovation Cycle Deploy ServiceProviders Demand Sell Equipment Vendors Drive Implement Develop SDOs Time

  10. SIP Innovation Failure: Why • Stuck in the telecom innovation cycle • Adopted by service providers with modest goals for innovation

  11. SIP Failure #2: Interoperability SIP Server SIP Server Inter-Domain InterServer example.com Client-Server

  12. Interop Report Card

  13. Too Many Standards

  14. SIP Interop Failure: Why • Too Many Standards • Proprietary Features • Telecom Innovation Cycle (Supply/Demand)

  15. Trend #1: “Cloud Apps” InternetApplicationProvider Proprietary overHTTP (aka webservices) Desktop orMobileNative App

  16. Trend #2: Web Apps InternetApplicationProvider Proprietary overHTTP (aka webservices) Web App(HTML/JS) Browser

  17. Trend #3: Inter-domain “REST” APIs InternetApplicationProvider Open REST API Proprietary overHTTP (aka webservices) Web App(HTML/JS) Desktop orMobileNative App Browser

  18. The Internet Software Innovation Cycle Develop Publish Deploy ServiceProviders Equipment Vendors SDOs Time

  19. Telecoms vs. Internet Application Cycles

  20. Implications for the IETF • Standards provide enabling technologies – not application specific • Inter-domain application standardization only when it is following the telecoms paradigm – many small providers • Client/Server application standardization only when software distribution to the client is not possible

More Related