RFC 3320: Signaling Compression (SigComp)
In plain English — editorial summary, not part of the RFC
This document defines SigComp, a solution for compressing messages generated by application protocols such as SIP [RFC-2543] and RTSP [RFC-2326]. The architecture and pre-requisites of SigComp are outlined, along with the format of the SigComp message. Decompression functionality for SigComp is provided by a 'Universal Decompressor Virtual Machine' optimized for the task of running decompression algorithms. The UDVM can be configured to understand the output of many well-known compressors such as DEFLATE [RFC-1951].
Document record
- Document ID
- RFC3320
- Published
- January 2003
- Authors
- R. Price; C. Bormann; J. Christoffersson; H. Hannu; Z. Liu; J. Rosenberg
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 62
- 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 3321Signaling Compression (SigComp) - Extended OperationsUpdated
January 2003
- RFC 3322Signaling Compression (SigComp) Requirements & AssumptionsCurrent
January 2003
- RFC 3485The Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Static Dictionary for Signaling Compression (SigComp)Updated
March 2003
- RFC 2848The PINT Service Protocol: Extensions to SIP and SDP for IP Access to Telephone Call ServicesCurrent
June 2000
- RFC 3319Dynamic Host Configuration Protocol (DHCPv6) Options for Session Initiation Protocol (SIP) ServersCurrent
July 2003
- RFC 3323A Privacy Mechanism for the Session Initiation Protocol (SIP)Current
December 2002
- RFC 3324Short Term Requirements for Network Asserted IdentityCurrent
December 2002
- RFC 3326The Reason Header Field for the Session Initiation Protocol (SIP)Updated
December 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?