RFC 7692: Compression Extensions for WebSocket
In plain English — editorial summary, not part of the RFC
This document defines a framework for creating WebSocket extensions that add compression functionality to the WebSocket Protocol. An extension based on this framework compresses the payload data portion of WebSocket data messages on a per-message basis using parameters negotiated during the opening handshake. This framework provides a general method for applying a compression algorithm to the contents of WebSocket messages. Each compression algorithm has to be defined in a document defining the extension by specifying the parameter negotiation and the payload transformation algorithm in detail. This document also specifies one specific compression extension using the DEFLATE algorithm.
Document record
- Document ID
- RFC7692
- Published
- December 2015
- Authors
- T. Yoshino
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 28
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 74006LoWPAN-GHC: Generic Header Compression for IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs)Current
November 2014
- RFC 8054Network News Transfer Protocol (NNTP) Extension for CompressionCurrent
January 2017
- RFC 6713The 'application/zlib' and 'application/gzip' Media TypesCurrent
August 2012
- RFC 7700Preparation, Enforcement, and Comparison of Internationalized Strings Representing NicknamesObsoleted
December 2015
- RFC 7702Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): GroupchatCurrent
December 2015
- RFC 7711PKIX over Secure HTTP (POSH)Current
November 2015
- RFC 7712Domain Name Associations (DNA) in the Extensible Messaging and Presence Protocol (XMPP)Current
November 2015
- RFC 7656A Taxonomy of Semantics and Mechanisms for Real-Time Transport Protocol (RTP) SourcesCurrent
November 2015
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?