Simple SIP Usage Scenario for Applications in the Endpoints
RFC 5638

Changed author "K. Singh": changed name from "Kundan Singh" to "K. Singh", changed affiliation from "Columbia University Alumni" to "Columbia U. Alumni", cleared country (was "New York, NY, USA"), changed order from "0" to "4"

Changed author "E. Shim": changed name from "Eunsoo Shim" to "E. Shim", cleared country (was "Basking Ridge, NJ 07920 USA"), changed order from "1" to "3"

Changed author "H. Sinnreich": changed name from "Henry Sinnreich" to "H. Sinnreich", changed is_editor from "False" to "True", cleared country (was "San Francisco, CA 94103, USA"), changed order from "3" to "1"

Received changes through RFC Editor sync (changed abstract to 'For Internet-centric usage, the number of SIP-required standards for presence and IM and audio/video communications can be drastically smaller than what has been published by using only the rendezvous and session-initiation capabilities of SIP. The simplification is achieved by avoiding the emulation of telephony and its model of the intelligent network. 'Simple SIP' relies on powerful computing endpoints. Simple SIP desktop applications can be combined with rich Internet applications (RIAs). Significant telephony features may also be implemented in the endpoints.

This approach for SIP reduces the number of SIP standards with which to comply -- from roughly 100 currently, and still growing, to about 11.

References for NAT traversal and for security are also provided. This memo provides information for the Internet community.')