metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 3261: SIP: Session Initiation Protocol

Still current, but amended. Parts of this document are changed or extended by RFC 3265, RFC 3853, RFC 4320, RFC 4916, RFC 5393, RFC 5621, RFC 5626, RFC 5630, RFC 5922, RFC 5954, RFC 6026, RFC 6141, RFC 6665, RFC 6878, RFC 7462, RFC 7463, RFC 8217, RFC 8591, RFC 8760, RFC 8898, RFC 8996. Read both.

In plain English — editorial summary, not part of the RFC

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. [STANDARDS-TRACK]

Document record

Document ID
RFC3261
Published
July 2002
Authors
J. Rosenberg; H. Schulzrinne; G. Camarillo; A. Johnston; J. Peterson; R. Sparks; M. Handley; E. Schooler
Status
PROPOSED STANDARD
Stream
IETF
Area
rai
Pages
269
Also known as
—
Obsoletes:
RFC 2543
Updated by:
RFC 3265, RFC 3853, RFC 4320, RFC 4916, RFC 5393, RFC 5621, RFC 5626, RFC 5630, RFC 5922, RFC 5954, RFC 6026, RFC 6141, RFC 6665, RFC 6878, RFC 7462, RFC 7463, RFC 8217, RFC 8591, RFC 8760, RFC 8898, RFC 8996

Topics

Standards lineage

This document is one revision in a chain of 7 RFCs, each formally replacing the one before it.

  1. RFC 2543 (1999)
  2. RFC 3261 (2002)
  3. RFC 3262 (2002)
  4. RFC 3263 (2002)
  5. RFC 3264 (2002)
  6. RFC 3265 (2002)
  7. RFC 6665 (2012) ✓

Read the full history of SIP-Specific Event Notification →

Referenced by

21 later RFCs formally update or obsolete part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/3261-sip-session-initiation-protocol