RFC 3486: Compressing the Session Initiation Protocol (SIP)
In plain English — editorial summary, not part of the RFC
This document describes a mechanism to signal that compression is desired for one or more Session Initiation Protocol (SIP) messages. It also states when it is appropriate to send compressed SIP messages to a SIP entity. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3486
- Published
- February 2003
- Authors
- G. Camarillo
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 12
- Also known as
- —
- Updated by:
- RFC 5049
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 3485The Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Static Dictionary for Signaling Compression (SigComp)Updated
March 2003
- RFC 3515The Session Initiation Protocol (SIP) Refer MethodUpdated
April 2003
- RFC 3428Session Initiation Protocol (SIP) Extension for Instant MessagingUpdated
December 2002
- RFC 3398Integrated Services Digital Network (ISDN) User Part (ISUP) to Session Initiation Protocol (SIP) MappingCurrent
December 2002
- RFC 3578Mapping of Integrated Services Digital Network (ISDN) User Part (ISUP) Overlap Signalling to the Session Initiation Protocol (SIP)Current
August 2003
- RFC 3581An Extension to the Session Initiation Protocol (SIP) for Symmetric Response RoutingCurrent
August 2003
- RFC 3608Session Initiation Protocol (SIP) Extension Header Field for Service Route Discovery During RegistrationUpdated
October 2003
- RFC 3361Dynamic Host Configuration Protocol (DHCP-for-IPv4) Option for Session Initiation Protocol (SIP) ServersCurrent
August 2002
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?