RFC 5638: Simple SIP Usage Scenario for Applications in the Endpoints
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC5638
- Published
- September 2009
- Authors
- H. Sinnreich; A. Johnston; E. Shim; K. Singh
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5763Framework for Establishing a Secure Real-time Transport Protocol (SRTP) Security Context Using Datagram Transport Layer Security (DTLS)Updated
May 2010
- RFC 5954Essential Correction for IPv6 ABNF and URI Comparison in RFC 3261Current
August 2010
- RFC 6357Design Considerations for Session Initiation Protocol (SIP) Overload ControlCurrent
August 2011
- RFC 4896Signaling Compression (SigComp) Corrections and ClarificationsCurrent
June 2007
- RFC 4504SIP Telephony Device Requirements and ConfigurationCurrent
May 2006
- RFC 4479A Data Model for PresenceCurrent
July 2006
- RFC 4245High-Level Requirements for Tightly Coupled SIP ConferencingCurrent
November 2005
- RFC 4240Basic Network Media Services with SIPCurrent
December 2005
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?