RFC 3485: The Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Static Dictionary for Signaling Compression (SigComp)
In plain English — editorial summary, not part of the RFC
The Session Initiation Protocol (SIP) is a text-based protocol for initiating and managing communication sessions. The protocol can be compressed by using Signaling Compression (SigComp). Similarly, the Session Description Protocol (SDP) is a text-based protocol intended for describing multimedia sessions for the purposes of session announcement, session invitation, and other forms of multimedia session initiation. This memo defines the SIP/SDP-specific static dictionary that SigComp may use in order to achieve higher efficiency. The dictionary is compression algorithm independent. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3485
- Published
- March 2003
- Authors
- M. Garcia-Martin; C. Bormann; J. Ott; R. Price; A. B. Roach
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 30
- Also known as
- —
- Updated by:
- RFC 4896
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3322Signaling Compression (SigComp) Requirements & AssumptionsCurrent
January 2003
- RFC 2848The PINT Service Protocol: Extensions to SIP and SDP for IP Access to Telephone Call ServicesCurrent
June 2000
- RFC 3321Signaling Compression (SigComp) - Extended OperationsUpdated
January 2003
- RFC 3320Signaling Compression (SigComp)Updated
January 2003
- RFC 3486Compressing the Session Initiation Protocol (SIP)Updated
February 2003
- RFC 3515The Session Initiation Protocol (SIP) Refer MethodUpdated
April 2003
- RFC 3428Session Initiation Protocol (SIP) Extension for Instant MessagingUpdated
December 2002
- RFC 3556Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP) BandwidthCurrent
July 2003
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?