Simple SIP Usage Scenario for Applications in the Endpoints
RFC 5638
| Document | Type |
RFC - Informational
(September 2009; No errata)
Was draft-sinnreich-sip-tools (individual in rai area)
|
|
|---|---|---|---|
| Authors | Kundan Singh , Eunsoo Shim , Alan Johnston , Henry Sinnreich | ||
| Last updated | 2018-12-20 | ||
| Stream | IETF | ||
| Formats | plain text html pdf htmlized bibtex | ||
| Reviews | |||
| Stream | WG state | (None) | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | RFC 5638 (Informational) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Cullen Jennings | ||
| Send notices to | mary.barnes@nortel.com, kundan@adobe.com | ||
Network Working Group H. Sinnreich, Ed.
Request for Comments: 5638 Adobe
Category: Informational A. Johnston
E. Shim
Avaya
K. Singh
Columbia University Alumni
September 2009
Simple SIP Usage Scenario for Applications in the Endpoints
Abstract
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.
Status of This Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
Sinnreich, et al. Informational [Page 1]
RFC 5638 SIP Usage for Applications in Endpoints September 2009
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the BSD License.
Table of Contents
1. Introduction ....................................................3
2. The Endpoint in the SIP and Web Architectures ...................5
2.1. The Telephony Gateway as a SIP Endpoint ....................6
3. Applicability for Simple SIP in the Endpoints ...................7
3.1. What Simple SIP Can Accomplish .............................7
3.2. Baseline for Simple SIP ....................................7
3.3. What Simple SIP May or May Not Accomplish ..................8
3.4. What Is Out of Scope for Simple SIP ........................8
3.5. Borderline Cases ...........................................9
4. Mandatory SIP References for Internet-Centric Usage .............9
4.1. RFC 3261: "SIP: Session Initiation Protocol" ..............10
4.2. RFC 4566: "SDP: Session Description Protocol" .............10
4.3. RFC 3264: "An Offer/Answer Model with Session
Description Protocol (SDP)" ...............................10
4.4. RFC 3840: "Indicating User Agent Capabilities in
the Session Initiation Protocol (SIP)" ....................10
4.5. RFC 3263: "Session Initiation Protocol (SIP):
Locating SIP Servers" .....................................11
4.6. RFC 3265: "Session Initiation Protocol
(SIP)-Specific Event Notification" ........................11
4.7. RFC 3856: "A Presence Event Package for the
Session Initiation Protocol (SIP)" ........................11
4.8. RFC 3863: "Presence Information Data Format (PIDF)" .......11
4.9. RFC 3428: "Session Initiation Protocol (SIP)
Extension for Instant Messaging" ..........................12
4.10. RFC 4474: "Enhancements for Authenticated
Identity Management in the Session Initiation
Protocol (SIP)" ..........................................12
4.11. RFC 3581: "An Extension to the Session Initiation
Protocol (SIP) for Symmetric Response Routing" ...........12
4.12. Updates to SIP-Related Protocols .........................12
5. SIP Applications in the Endpoints ..............................12
6. NAT Traversal ..................................................14
7. Security Considerations ........................................14
8. Acknowledgements ...............................................15
9. References .....................................................16
Show full document text