RFC 3321: Signaling Compression (SigComp) - Extended Operations
In plain English — editorial summary, not part of the RFC
This document describes how to implement certain mechanisms in SigComp (Signaling Compression), RFC XXX, which can significantly improve the compression efficiency compared to using simple per- message compression. SigComp uses a UDVM (Universal Decompressor Virtual Machine) for decompression, and the mechanisms described in this document are possible to implement using the UDVM instructions defined in RFC XXX.
Document record
- Document ID
- RFC3321
- Published
- January 2003
- Authors
- H. Hannu; J. Christoffersson; S. Forsgren; K.-C. Leung; Z. Liu; R. Price
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 19
- 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 3320Signaling Compression (SigComp)Updated
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 3323A Privacy Mechanism for the Session Initiation Protocol (SIP)Current
December 2002
- RFC 3319Dynamic Host Configuration Protocol (DHCPv6) Options for Session Initiation Protocol (SIP) ServersCurrent
July 2003
- 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?