RFC 5049: Applying Signaling Compression (SigComp) to the Session Initiation Protocol (SIP)
In plain English — editorial summary, not part of the RFC
This document describes some specifics that apply when Signaling Compression (SigComp) is applied to the Session Initiation Protocol (SIP), such as default minimum values of SigComp parameters, compartment and state management, and a few issues on SigComp over TCP. Any implementation of SigComp for use with SIP must conform to this document and SigComp, and in addition, support the SIP and Session Description Protocol (SDP) static dictionary. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5049
- Published
- December 2007
- Authors
- C. Bormann; Z. Liu; R. Price; G. Camarillo
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 21
- Also known as
- —
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 5048Internet Small Computer System Interface (iSCSI) Corrections and ClarificationsObsoleted
October 2007
- RFC 5047DA: Datamover Architecture for the Internet Small Computer System Interface (iSCSI)Updated
October 2007
- RFC 5046Internet Small Computer System Interface (iSCSI) Extensions for Remote Direct Memory Access (RDMA)Obsoleted
October 2007
- RFC 5052Forward Error Correction (FEC) Building BlockCurrent
August 2007
- RFC 5045Applicability of Remote Direct Memory Access Protocol (RDMA) and Direct Data Placement (DDP)Updated
October 2007
- RFC 5053Raptor Forward Error Correction Scheme for Object DeliveryCurrent
October 2007
- RFC 5044Marker PDU Aligned Framing for TCP SpecificationUpdated
October 2007
- RFC 5043Stream Control Transmission Protocol (SCTP) Direct Data Placement (DDP) AdaptationUpdated
October 2007
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?