RFC 4077: A Negative Acknowledgement Mechanism for Signaling Compression
In plain English — editorial summary, not part of the RFC
This document describes a mechanism that allows Signaling Compression (SigComp) implementations to report precise error information upon receipt of a message which cannot be decompressed. This negative feedback can be used by the recipient to make fine-grained adjustments to the compressed message before retransmitting it, allowing for rapid and efficient recovery from error situations. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4077
- Published
- May 2005
- Authors
- A.B. Roach
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 16
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3322Signaling Compression (SigComp) Requirements & AssumptionsCurrent
January 2003
- RFC 3321Signaling Compression (SigComp) - Extended OperationsUpdated
January 2003
- RFC 3320Signaling Compression (SigComp)Updated
January 2003
- RFC 3485The Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Static Dictionary for Signaling Compression (SigComp)Updated
March 2003
- RFC 4080Next Steps in Signaling (NSIS): FrameworkCurrent
June 2005
- RFC 4081Security Threats for Next Steps in Signaling (NSIS)Current
June 2005
- RFC 4067Context Transfer Protocol (CXTP)Current
July 2005
- RFC 4066Candidate Access Router Discovery (CARD)Current
July 2005
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?