RFC - 3261
SIP: Session Initiation Protocol
| Original: |
ftp://ftp.isi.edu/in-notes/rfc3261.txt |
| Authors: |
J. Rosenberg [dynamicsoft], H. Schulzrinne [Columbia U.], G. Camarillo [Ericsson], A. Johnston [WorldCom], J. Peterson [Neustar], R. Sparks [dynamicsoft], M. Handley [ICIR], E. Schooler [AT&T]
|
| Date: |
June 2002 |
| Category: |
Proposed Standard |
| Updated by: |
| RFC-4320prop |
Actions Addressing Identified Issues with the Session Initiation Protocol's (SIP) Non-INVITE Transaction |
| RFC-3853prop |
S/MIME Advanced Encryption Standard (AES) Requirement for the Session Initiation Protocol (SIP) |
| RFC-3265prop |
Session Initiation Protocol (SIP)-Specific Event Notification |
| Referred by: |
174 RFC |
| Refers to: |
39 RFC |
Status
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2002). All Rights Reserved.
Abstract
This document describes Session Initiation Protocol (SIP), an
application-layer control (signaling) protocol for creating,
modifying, and terminating sessions with one or more participants.
These sessions include Internet telephone calls, multimedia
distribution, and multimedia conferences.
SIP invitations used to create sessions carry session descriptions
that allow participants to agree on a set of compatible media types.
SIP makes use of elements called proxy servers to help route requests
to the user's current location, authenticate and authorize users for
services, implement provider call-routing policies, and provide
features to users. SIP also provides a registration function that
allows users to upload their current locations for use by proxy
servers. SIP runs on top of several different transport protocols.
