the end of application protocol standardization (?)
DESCRIPTION
The End of Application Protocol Standardization (?). Jonathan Rosenberg Chief Technology Strategist, Skype. Outline. Experiences and Lessons from SIP – the Telecoms Innovation Cycle (Obvious) Industry Trends The Internet Application Innovation Cycle and its Implications for IETF. - PowerPoint PPT PresentationTRANSCRIPT
![Page 1: The End of Application Protocol Standardization (?)](https://reader035.vdocuments.us/reader035/viewer/2022062817/5681692f550346895de077de/html5/thumbnails/1.jpg)
The End of Application Protocol Standardization (?)
Jonathan RosenbergChief Technology Strategist, Skype
![Page 2: The End of Application Protocol Standardization (?)](https://reader035.vdocuments.us/reader035/viewer/2022062817/5681692f550346895de077de/html5/thumbnails/2.jpg)
Outline
• Experiences and Lessons from SIP – the Telecoms Innovation Cycle
• (Obvious) Industry Trends• The Internet Application Innovation Cycle and
its Implications for IETF
![Page 3: The End of Application Protocol Standardization (?)](https://reader035.vdocuments.us/reader035/viewer/2022062817/5681692f550346895de077de/html5/thumbnails/3.jpg)
SIP for Beginners
SIP Serverexample.com
SIP Serverexample.org
SIP
SIP SIP
RTP
![Page 4: The End of Application Protocol Standardization (?)](https://reader035.vdocuments.us/reader035/viewer/2022062817/5681692f550346895de077de/html5/thumbnails/4.jpg)
Example SIP MessageINVITE sip:[email protected] SIP/2.0From: J. Rosenberg <sip:[email protected]> ;tag=76ahSubject: Conference CallTo: John Smith <sip:[email protected]>Via: SIP/2.0/UDP 1.2.3.4;branch=z9hG4bK74bf9Call-ID: [email protected]: application/sdpCSeq: 4711 INVITEContent-Length: 187
v=0o=user1 53655765 2353687637 IN IP4 1.2.3.4s=Salesc=IN IP4 1.2.3.4t=0 0m=audio 3456 RTP/AVP 0
![Page 5: The End of Application Protocol Standardization (?)](https://reader035.vdocuments.us/reader035/viewer/2022062817/5681692f550346895de077de/html5/thumbnails/5.jpg)
SIP Success: Products
Hard Phones Soft Phones
PSTN Gateways
FirewallsSession BorderControllers
![Page 6: The End of Application Protocol Standardization (?)](https://reader035.vdocuments.us/reader035/viewer/2022062817/5681692f550346895de077de/html5/thumbnails/6.jpg)
SIP Success: Service Providers
e2e SIPBackhaul, Peering
Termination
SIP Trunking
![Page 7: The End of Application Protocol Standardization (?)](https://reader035.vdocuments.us/reader035/viewer/2022062817/5681692f550346895de077de/html5/thumbnails/7.jpg)
SIP Success: Industry
![Page 8: The End of Application Protocol Standardization (?)](https://reader035.vdocuments.us/reader035/viewer/2022062817/5681692f550346895de077de/html5/thumbnails/8.jpg)
SIP Failure #1: Same Old Telephony
![Page 9: The End of Application Protocol Standardization (?)](https://reader035.vdocuments.us/reader035/viewer/2022062817/5681692f550346895de077de/html5/thumbnails/9.jpg)
The Telecom Innovation Cycle
Demand
Drive
Develop
Deploy
Sell
Implement
ServiceProviders
EquipmentVendors
SDOs
Time
![Page 10: The End of Application Protocol Standardization (?)](https://reader035.vdocuments.us/reader035/viewer/2022062817/5681692f550346895de077de/html5/thumbnails/10.jpg)
SIP Innovation Failure: Why
• Stuck in the telecom innovation cycle• Adopted by service providers with modest
goals for innovation
![Page 11: The End of Application Protocol Standardization (?)](https://reader035.vdocuments.us/reader035/viewer/2022062817/5681692f550346895de077de/html5/thumbnails/11.jpg)
SIP Failure #2: Interoperability
SIP Server SIP Server
example.com
Inter-Domain
InterServer
Client-Server
![Page 12: The End of Application Protocol Standardization (?)](https://reader035.vdocuments.us/reader035/viewer/2022062817/5681692f550346895de077de/html5/thumbnails/12.jpg)
Interop Report CardSubject Grade CommentsClient to Server D Verbose, yet still missing
basics.Server to Server B Basic calling broadly
interoperable. Not much beyond that.
Interdomain C Still waiting for mass-market inter-domain calling.
![Page 13: The End of Application Protocol Standardization (?)](https://reader035.vdocuments.us/reader035/viewer/2022062817/5681692f550346895de077de/html5/thumbnails/13.jpg)
Too Many Standards
1998 2000 2002 2004 2006 2008 2010 20120
5
10
15
20
25
30
RFC Count
RFC Count
![Page 14: The End of Application Protocol Standardization (?)](https://reader035.vdocuments.us/reader035/viewer/2022062817/5681692f550346895de077de/html5/thumbnails/14.jpg)
SIP Interop Failure: Why
• Too Many Standards• Proprietary Features• Telecom Innovation Cycle (Supply/Demand)
![Page 15: The End of Application Protocol Standardization (?)](https://reader035.vdocuments.us/reader035/viewer/2022062817/5681692f550346895de077de/html5/thumbnails/15.jpg)
Trend #1: “Cloud Apps”
Desktop orMobile
Native App
InternetApplication
Provider
Proprietary overHTTP (aka webservices)
![Page 16: The End of Application Protocol Standardization (?)](https://reader035.vdocuments.us/reader035/viewer/2022062817/5681692f550346895de077de/html5/thumbnails/16.jpg)
Trend #2: Web Apps
Web App(HTML/JS)
InternetApplication
Provider
Proprietary overHTTP (aka webservices)
Browser
![Page 17: The End of Application Protocol Standardization (?)](https://reader035.vdocuments.us/reader035/viewer/2022062817/5681692f550346895de077de/html5/thumbnails/17.jpg)
Trend #3: Inter-domain “REST” APIs
Web App(HTML/JS)
InternetApplication
Provider
Proprietary overHTTP (aka webservices)
Browser
Desktop orMobile
Native App
Open REST API
![Page 18: The End of Application Protocol Standardization (?)](https://reader035.vdocuments.us/reader035/viewer/2022062817/5681692f550346895de077de/html5/thumbnails/18.jpg)
The Internet Software Innovation Cycle
Develop DeployServiceProviders
EquipmentVendors
SDOs
Time
Publish
![Page 19: The End of Application Protocol Standardization (?)](https://reader035.vdocuments.us/reader035/viewer/2022062817/5681692f550346895de077de/html5/thumbnails/19.jpg)
Telecoms vs. Internet Application CyclesCriteria Telecom Cycle Internet Application Cycle
Speed Slow Fast
Dependencies Many None
Primary Service Concern Inter-Provider Intra-Provider
Standards First Last (if Ever)
Hardware Ecosystem Yes No
Scalable to > hundreds of providers
Yes No
Service Offerings Homoegeneous Heterogeneous
![Page 20: The End of Application Protocol Standardization (?)](https://reader035.vdocuments.us/reader035/viewer/2022062817/5681692f550346895de077de/html5/thumbnails/20.jpg)
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