[hybi] Fwd: publication request: draft-ietf-hybi-permessage-compression-05

[Salvatore Loreto <[e-mail]>]

FYI

I have sent a publication request to the IESG for the 
permessage-compression draft.

cheers
Salvatore

-------- Original Message --------
Subject: 	publication request: draft-ietf-hybi-permessage-compression-05
Date: 	Wed, 20 Feb 2013 11:15:40 +0200
From: 	Salvatore Loreto <[e-mail]>
To: 	Barry Leiba <[e-mail]>, "[e-mail]" 
<[e-mail]>
CC: 	Gabriel Montenegro <[e-mail]>



Dear Barry

I am requesting the publication for the draft:
"WebSocket Per-message Compression"
draft-ietf-hybi-permessage-compression-05

the Writeup is below.
For it I have used the proposed version at:
http://trac.tools.ietf.org/group/iesg/trac/wiki/DraftShepherdWriteupWgAlternate

best regards
Salvatore


Document Writeup
1. Summary

Salvatore Loreto is the document shepherd

Barry Leiba is the responsible Area Director

Abstract
This document specifies a framework for creating WebSocket extensions
that add compression functionality to the WebSocket Protocol.
Extensions based on this framework compress the payload of non-control
WebSocket messages using a specified compression algorithm.
One reserved bit RSV1 in the WebSocket frame header is allocated to
control application of compression for each message. This document
also specifies one specific compression extension using DEFLATE.


2. Review and Consensus


The Compression extension has been discussed extensively within the HyBi
almost since the beginning of the WebSocket standardization process,
however at the time the wg decided, in order to speed up the process and
not increase even more the discussion, not to standardize any extension
in the main WebSocket spec but postpone all of them.
The initial version of the draft was based on per-frame compression, but
then in IETF84 meeting, in Vancouver, the HyBi WG discussed the change
from per-frame to per-message compression
(http://www.ietf.org/mail-archive/web/hybi/current/msg09729.html).
The chairs sensed the WG’s consensus in the room to go ahead with this
change (http://www.ietf.org/mail-archive/web/hybi/current/msg09816.html)

The wg hasn't faced any significant point of difficulty or controversial.

Chrome supports the old perframe deflate draft. However they are going
to update it to the latest one soon.
pywebsocket (http://code.google.com/p/pywebsocket/ ) supports
permessage-compression-04 but needs some changes
on extension parameters parsing to be 05 compliant.

Jetty webserver has supports the permessage-compression draft but an
older version of the draft.



3. Intellectual Property

The author has confirmed conformance with BCPs 78 and 79.


4. Other Points


The draft reference as Informative: RFC1951 "DEFLATE Compressed Data
Format Specification version 1.3"
that appear in the DOWNREF registry.

There is no new IANA registry created by this document.