RFC 4465: Signaling Compression (SigComp) Torture Tests
In plain English — editorial summary, not part of the RFC
This document provides a set of "torture tests" for implementers of the Signaling Compression (SigComp) protocol. The torture tests check each of the SigComp Universal Decompressor Virtual Machine instructions in turn, focusing in particular on the boundary and error cases that are not generally encountered when running well-behaved compression algorithms. Tests are also provided for other SigComp entities such as the dispatcher and the state handler. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4465
- Published
- June 2006
- Authors
- A. Surtees; M. West
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 68
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4464Signaling Compression (SigComp) Users' GuideCurrent
May 2006
- RFC 4455Definition of Managed Objects for Small Computer System Interface (SCSI) EntitiesCurrent
April 2006
- RFC 4413TCP/IP Field BehaviorCurrent
March 2006
- RFC 4404Definitions of Managed Objects for Fibre Channel Over TCP/IP (FCIP)Current
February 2006
- RFC 4544Definitions of Managed Objects for Internet Small Computer System Interface (iSCSI)Obsoleted
May 2006
- RFC 4545Definitions of Managed Objects for IP Storage User Identity AuthorizationCurrent
May 2006
- RFC 4369Definitions of Managed Objects for Internet Fibre Channel Protocol (iFCP)Obsoleted
January 2006
- RFC 4362RObust Header Compression (ROHC): A Link-Layer Assisted Profile for IP/UDP/RTPUpdated
January 2006
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?