[hybi] RFC 7692 on Compression Extensions for WebSocket

rfc-editor@rfc-editor.org Tue, 08 December 2015 00:40 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 97DEE1A8989; Mon, 7 Dec 2015 16:40:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id F6AhhVHZKLP5; Mon, 7 Dec 2015 16:40:08 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org []) by ietfa.amsl.com (Postfix) with ESMTP id 46D9F1A898C; Mon, 7 Dec 2015 16:40:08 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id CE186180471; Mon, 7 Dec 2015 16:38:07 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20151208003807.CE186180471@rfc-editor.org>
Date: Mon, 7 Dec 2015 16:38:07 -0800 (PST)
Archived-At: <http://mailarchive.ietf.org/arch/msg/hybi/Tha_bjhlGopaSSlxJ6rwdroASuw>
Cc: drafts-update-ref@iana.org, hybi@ietf.org, rfc-editor@rfc-editor.org
Subject: [hybi] RFC 7692 on Compression Extensions for WebSocket
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hybi/>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Dec 2015 00:40:13 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 7692

        Title:      Compression Extensions for WebSocket 
        Author:     T. Yoshino
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2015
        Mailbox:    tyoshino@google.com
        Pages:      28
        Characters: 62411
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-hybi-permessage-compression-28.txt

        URL:        https://www.rfc-editor.org/info/rfc7692

        DOI:        http://dx.doi.org/10.17487/RFC7692

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.

This document is a product of the BiDirectional or Server-Initiated HTTP Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC