RFC 8478: Zstandard Compression and the application/zstd Media Type
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8878.
Current version: RFC 8878 — Zstandard Compression and the 'application/zstd' Media Type
In plain English — editorial summary, not part of the RFC
Zstandard, or "zstd" (pronounced "zee standard"), is a data compression mechanism. This document describes the mechanism and registers a media type and content encoding to be used when transporting zstd-compressed content via Multipurpose Internet Mail Extensions (MIME). Despite use of the word "standard" as part of its name, readers are advised that this document is not an Internet Standards Track specification; it is being published for informational purposes only.
Document record
- Document ID
- RFC8478
- Published
- October 2018
- Authors
- Y. Collet; M. Kucherawy
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 54
- Also known as
- —
- Obsoleted by:
- RFC 8878
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 8724SCHC: Generic Framework for Static Context Header Compression and FragmentationUpdated
April 2020
- RFC 8054Network News Transfer Protocol (NNTP) Extension for CompressionCurrent
January 2017
- RFC 9011Static Context Header Compression and Fragmentation (SCHC) over LoRaWANCurrent
April 2021
- RFC 9204QPACK: Field Compression for HTTP/3Current
June 2022
- RFC 9639Free Lossless Audio Codec (FLAC)Current
December 2024
- RFC 9659Window Sizing for Zstandard Content EncodingCurrent
September 2024
- RFC 4163RObust Header Compression (ROHC): Requirements on TCP/IP Header CompressionCurrent
August 2005
- RFC 3597Handling of Unknown DNS Resource Record (RR) TypesUpdated
September 2003
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?