Simpler approach to SIP applications

“Simple SIP Usage Scenario for Applications in the Endpoints” RFC 5638 describes how to exploit processing in the endpoints rather than emulating telephony to simplify the implementation of application and reduce the number of SIP documents that one needs to comply with.

Simple SIP = only the required functions for rendezvous and session setup + security

Goal is to leverage rich internet applications (RIAs) approach rather than trying to be like telephony! RIAs leverage the web browser as the user interface and facilitate the combination (mashups) of various information sources. SIP URIs should be able to be used as flexibly as other URIs in new RIA applications.

Relegates telephony aspects of SIP to something that is done in the gateway to the PSTN and not something that has to be built into every SIP UA.

Slide Notes

H. Sinnreich, A. Johnston, E. Shim, and K. Singh, Simple SIP Usage Scenario for Applications in the Endpoints, RFC Editor, RFC 5638, ISSN 2070-1721, September 2009 http://www.rfc-editor.org/rfc/rfc5638.txt Links to an external site.

Transcript

[slide495] So people have tried to understand Could we make a simpler version of SIP? Could we strip out all of the complex features and now have something that has only the required functions for rendezvous and session setup plus security get rid of everything else. And then we could make a simpler network application And then build so-called rich internet applications. Get all of the other things that you want from these other services, i.e., mashups.