Skip to main content

Simple SIP Usage Scenario for Applications in the Endpoints
RFC 5638

Revision differences

Document history

Date By Action
2018-12-20
(System)
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 …
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.')
2015-10-14
(System) Notify list changed from alan@sipstation.com, eunsooshim@gmail.com, henrys@adobe.com, kundan@adobe.com, draft-sinnreich-sip-tools@ietf.org, mary.barnes@nortel.com to mary.barnes@nortel.com, kundan@adobe.com
2009-09-25
Amy Vezza State Changes to RFC Published from RFC Ed Queue by Amy Vezza
2009-09-25
Amy Vezza [Note]: 'RFC 5638' added by Amy Vezza
2009-09-23
(System) RFC published