draft-ietf-hybi-permessage-compression-24.txt   draft-ietf-hybi-permessage-compression-25.txt 
HyBi Working Group T. Yoshino HyBi Working Group T. Yoshino
Internet-Draft Google, Inc. Internet-Draft Google, Inc.
Intended status: Standards Track June 24, 2015 Intended status: Standards Track August 6, 2015
Expires: December 26, 2015 Expires: February 7, 2016
Compression Extensions for WebSocket Compression Extensions for WebSocket
draft-ietf-hybi-permessage-compression-24 draft-ietf-hybi-permessage-compression-25
Abstract Abstract
This document defines a framework for creating WebSocket extensions This document defines a framework for creating WebSocket extensions
that add compression functionality to the WebSocket Protocol. An that add compression functionality to the WebSocket Protocol. An
extension based on this framework compresses the payload data portion extension based on this framework compresses the payload data portion
of WebSocket data messages on a per-message basis using parameters of WebSocket data messages on a per-message basis using parameters
negotiated during the opening handshake. This framework provides a negotiated during the opening handshake. This framework provides a
general method for applying a compression algorithm to the contents general method for applying a compression algorithm to the contents
of WebSocket messages. Each compression algorithm has to be defined of WebSocket messages. Each compression algorithm has to be defined
skipping to change at page 1, line 42 skipping to change at page 1, line 42
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current. Drafts is at http://datatracker.ietf.org/drafts/current.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 26, 2015. This Internet-Draft will expire on February 7, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 15, line 18 skipping to change at page 15, line 18
MAY add, change or remove Per-message Compression of proxied messages MAY add, change or remove Per-message Compression of proxied messages
if the intermediary meets all of the following requirements: if the intermediary meets all of the following requirements:
o The intermediary understands the PMCE. o The intermediary understands the PMCE.
o The intermediary can read all data of the proxied WebSocket o The intermediary can read all data of the proxied WebSocket
connection including the opening handshake request, opening connection including the opening handshake request, opening
handshake response, and messages. handshake response, and messages.
o The intermediary can alter the proxied data before forwarding them o The intermediary can alter the proxied data before forwarding them
in accordance with to the constraints of the new combination of in accordance with the constraints of the new combination of
extensions. For example, if Per-message Compression is removed extensions. For example, if Per-message Compression is removed
from messages, the corresponding element in the from messages, the corresponding element in the
"Sec-WebSocket-Extensions" header in the opening handshake "Sec-WebSocket-Extensions" header in the opening handshake
response which enabled the Per-message Compression must also be response which enabled the Per-message Compression must also be
removed. removed.
Otherwise, the intermediary MUST NOT add, change or remove Per- Otherwise, the intermediary MUST NOT add, change or remove Per-
message Compression of proxied messages. message Compression of proxied messages.
8. The permessage-deflate extension 8. The permessage-deflate extension
skipping to change at page 30, line 34 skipping to change at page 30, line 34
The "permessage-deflate" extension name is used in the The "permessage-deflate" extension name is used in the
"Sec-WebSocket-Extensions" header in the WebSocket opening handshake "Sec-WebSocket-Extensions" header in the WebSocket opening handshake
to negotiate use of the permessage-deflate extension. to negotiate use of the permessage-deflate extension.
10.2. Registration of the "Per-message Compressed" WebSocket Framing 10.2. Registration of the "Per-message Compressed" WebSocket Framing
Header Bit Header Bit
This section describes a WebSocket framing header bit registration in This section describes a WebSocket framing header bit registration in
the WebSocket Framing Header Bits Registry [RFC6455]. the WebSocket Framing Header Bits Registry [RFC6455].
Header Bit Value
RSV1 RSV1
Common Name Description
Per-message Compressed
Meaning
The message is compressed or not. RSV1 is set for compressed The message is compressed or not. RSV1 is set for compressed
messages and unset for uncompressed messages. messages and unset for uncompressed messages.
Reference Reference
Section 6 of this document. Section 6 of this document.
The "Per-message Compressed" framing header bit is used on the first The "Per-message Compressed" framing header bit is used on the first
fragment of data messages to indicate whether the payload of the fragment of data messages to indicate whether the payload of the
message is compressed by the PMCE or not. message is compressed by the PMCE or not.
 End of changes. 6 change blocks. 
10 lines changed or deleted 7 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/