
From tyoshino@google.com  Fri Oct  4 00:10:06 2013
Return-Path: <tyoshino@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65AC721F9AE2 for <hybi@ietfa.amsl.com>; Fri,  4 Oct 2013 00:10:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7zTYtDR+EuJM for <hybi@ietfa.amsl.com>; Fri,  4 Oct 2013 00:09:58 -0700 (PDT)
Received: from mail-wi0-x233.google.com (mail-wi0-x233.google.com [IPv6:2a00:1450:400c:c05::233]) by ietfa.amsl.com (Postfix) with ESMTP id AC8D121F90CC for <hybi@ietf.org>; Fri,  4 Oct 2013 00:09:13 -0700 (PDT)
Received: by mail-wi0-f179.google.com with SMTP id hm2so1150710wib.6 for <hybi@ietf.org>; Fri, 04 Oct 2013 00:09:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=N2579tqVbM6qoANu+ITmD71s18ydw3O3GLsa1rK2DFA=; b=ZOgGq3Yi0ewweIp6/wAUE5rJJS6fzk8MbqX5iXqZ+u10noNQJrcCKJhve9gPjX4bKN lOxdCjXN6T0O2nuzcax2r9hPucfCaOVCSWcvDLUVGDBjmcOyYjx3TtJ6LIzsb/WvW0At qNMEy/peo9bS2bnRIK+KV5rr6zTazFcpiioA73TiykJMxlkhhFcg2DH2DaKPHGI7jTgp iGjWyszXWU81OX8fo9Af1jvsnRoka/X/ayMzECz0FcUk7E0cqprlLWGRqDSS7sONaYpn qnkYv8Oh1YBO9H1p130FLegW5gGCoDSP4/oIa6XFh6WIQz+yuu20Tf/cvuhEe4eLI4IY 8BIw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-type; bh=N2579tqVbM6qoANu+ITmD71s18ydw3O3GLsa1rK2DFA=; b=FA3qNk4S6DsrnXLNupFFtjFKMs+2Pv1Sc8kwCDwILMA7biTMjEWCvcjv8Fj+J/NpmG lp5YoJmpJ7b6wM9hANK+494FfPvamEU4mvN7Fc1bc4yHrvjQridHOYdsgEvGnwhOj7+2 Kl4EYiMt2eKSSku3NOgI12jDw4okcTSxfEIJRSJYobaujhjZ0TewWINxjePGEMcgZeDG Fa8FGt9x1jZU+yMCHqSjvIlLozu/V4/xaWRQS4Lw+EcC5KwhxnFwHT+iusJmOd9jxjH4 Tht0huXnhucnXUbrW8ZdEypKYIM+ZnsGi7bQFWbpGbW+Y6CLvsizNT1PMbG3s7irdnTP fswA==
X-Gm-Message-State: ALoCoQkfWEODimHLr9+GxbaQ69xXDWn6O4ooaPVTRpHwjzG7BZvs5LQa9AOercf9Tknk9vrP1DKR/UXHMHJsE+TXqp2zZFDqecpu/BkiBbTokILzP4ad5GtiZSLkIVnzHC1yxt7J9w2fwj6tzdZg6ux5yYusPpLQIEaHvcjA0T2lj4WhqSzWDI5uhTJAnR8QnQYMQ0hNpeZ0
X-Received: by 10.180.20.163 with SMTP id o3mr6187112wie.1.1380870552776; Fri, 04 Oct 2013 00:09:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.15.133 with HTTP; Fri, 4 Oct 2013 00:08:52 -0700 (PDT)
From: Takeshi Yoshino <tyoshino@google.com>
Date: Fri, 4 Oct 2013 16:08:52 +0900
Message-ID: <CAH9hSJbwd5qhMJw=3dwk3CDPua5ENRksd9=q2KDcyyma3uKzZg@mail.gmail.com>
To: "hybi@ietf.org" <hybi@ietf.org>, salvatore loreto <salvatore.loreto@ericsson.com>,  Gabriel Montenegro <Gabriel.Montenegro@microsoft.com>
Content-Type: multipart/alternative; boundary=bcaec53f30edc7951a04e7e4fa3f
Subject: [hybi] Restarting IESG review on permessage-deflate
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Fri, 04 Oct 2013 07:10:06 -0000

--bcaec53f30edc7951a04e7e4fa3f
Content-Type: text/plain; charset=ISO-8859-1

Hi HyBi chairs,

After addressing Barry's comments, the spec went through reviews by several
people. It's not receiving any critical issue report recently.

We have two client implementation (Autobahn and Chromium) and three server
implementations (Autobahn, WebSocket++, pywebsocket).

I think we can restart IESG review. What do you think?

--bcaec53f30edc7951a04e7e4fa3f
Content-Type: text/html; charset=ISO-8859-1

<div dir="ltr"><div>Hi HyBi chairs,</div><div><br></div><div>After addressing Barry&#39;s comments, the spec went through reviews by several people. It&#39;s not receiving any critical issue report recently.</div><div><br>

</div><div>We have two client implementation (Autobahn and Chromium) and three server implementations (Autobahn, WebSocket++, pywebsocket).</div><div><br></div><div>I think we can restart IESG review. What do you think?</div>

</div>

--bcaec53f30edc7951a04e7e4fa3f--

From joakim@intalio.com  Fri Oct  4 07:28:02 2013
Return-Path: <joakim@intalio.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC11521F9DA1 for <hybi@ietfa.amsl.com>; Fri,  4 Oct 2013 07:28:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gLqvDDC4FMPQ for <hybi@ietfa.amsl.com>; Fri,  4 Oct 2013 07:27:44 -0700 (PDT)
Received: from mail-ee0-f45.google.com (mail-ee0-f45.google.com [74.125.83.45]) by ietfa.amsl.com (Postfix) with ESMTP id E73AA21F9697 for <hybi@ietf.org>; Fri,  4 Oct 2013 07:24:13 -0700 (PDT)
Received: by mail-ee0-f45.google.com with SMTP id c50so1847133eek.32 for <hybi@ietf.org>; Fri, 04 Oct 2013 07:24:10 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=FXLMVWV1D+TKzcllCP3+5z3wLCCffBF8B/MDtElGy2A=; b=QPB7BWSxPCYSdnqJznjLSQ053ccO6L1HVFmScXZP3hEhW1G6jLe4/Bj4MULk571Il0 xjuO8tzOgtgv95uzpCaichoLIr8Em286XCWwePw9D48wR1K9dD3X5HwlQ1C7rO30j+kM Rg4ZgnRDAZdZKMhcWHuhVoGd0XWIvpxJNbAdO4CpUKksjBlGxgsAmmZaw0DbPoCC7XJJ X5xwlUYxMpUwla03lopLIvBCXnqBltJH0kaaZW1BJzSsNAR7qm9RjSMl99HKgDCTfu6R sqMYR64rBwNl19CWbELJhMG4AqT052QZVtQQvkFQCXLM9gVmq/0ueutiAOw7Ta85BqPl piJg==
X-Gm-Message-State: ALoCoQnRk2TCPpLCKkap3W+JH3ZxJym5k+0SCZI6wacDRmkrpCH7EvbAXLm8MLtuvEplJjBCThFN
MIME-Version: 1.0
X-Received: by 10.14.203.196 with SMTP id f44mr14688eeo.141.1380896650200; Fri, 04 Oct 2013 07:24:10 -0700 (PDT)
Received: by 10.14.134.73 with HTTP; Fri, 4 Oct 2013 07:24:10 -0700 (PDT)
In-Reply-To: <CAH9hSJbwd5qhMJw=3dwk3CDPua5ENRksd9=q2KDcyyma3uKzZg@mail.gmail.com>
References: <CAH9hSJbwd5qhMJw=3dwk3CDPua5ENRksd9=q2KDcyyma3uKzZg@mail.gmail.com>
Date: Fri, 4 Oct 2013 07:24:10 -0700
Message-ID: <CAG4zZZD8eq4w9kyQbX2AJcM1LA8=UyRO7txK7TvmYhSp=YU+9g@mail.gmail.com>
From: Joakim Erdfelt <joakim@intalio.com>
To: Takeshi Yoshino <tyoshino@google.com>
Content-Type: multipart/alternative; boundary=047d7b343ab24eb8f604e7eb0ef3
Cc: "hybi@ietf.org" <hybi@ietf.org>, Gabriel Montenegro <Gabriel.Montenegro@microsoft.com>
Subject: Re: [hybi] Restarting IESG review on permessage-deflate
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Fri, 04 Oct 2013 14:28:03 -0000

--047d7b343ab24eb8f604e7eb0ef3
Content-Type: text/plain; charset=ISO-8859-1

There is also Eclipse Jetty 9.1 (currently in RC releases) support (server
and client)

We cannot support some of the spec, as written.
Our experiences implementing it, and using chromium + pywebsocket for
testing both the server or client implementation.

The following configuration parameters are not supported, nor can/will be.

s2c_no_context_takeover
c2s_no_context_takeover
s2c_max_window_bits
c2s_max_window_bits

This level of control of the deflate algorithm is just not possible in
Java, sorry.
We are not using our own implementation of Deflate, as the one provided by
Java itself is better performant (both in speed and memory use)

We also find the nature of configuration parameters awkward (even if Java
supported these specific ones)
The whole "s2c" and "c2s" prefix noise is unnecessary.

Our requests for this spec:

* eliminate the "s2c" and "c2s" prefixes.
   "c2s" == request, from client, what it wants to do
   "s2c" == response, from server, what it wants to do
   draft-ietf-hybi-permessage-compression-12, doesn't make the case for the
need for these prefixes, they seem superfluous, duplicating configuration
parameters just to add context on which direction they have an effect on.
 something the standard websocket handshake already accomplishes nicely.
so either the stated reason for them in the spec documentation is unclear,
or they truly are irrelevant prefixes.
   imagine a world where we had ...
   POST /upload HTTP/1.1
     Request-Content-Length: 6000
   HTTP/1.1 200 OK
     Response-Content-Length: 50
* define default deflate behavior better.
   http's content encoding and compression has default behavior, for every
flavor of compression scheme.
   even spdy has default behavior (note: while spdy has these kinds of
optional deflate tweaks, in the wild, and in practice, no server currently
honors them)
* move the existing configuration parameters (for no_context_takeover and
max_window_bits) out into optional advanced configuration tweaking.

--047d7b343ab24eb8f604e7eb0ef3
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra">There is also Eclipse Jetty 9.1=
 (currently in RC releases) support (server and client)<div><br></div><div>=
We cannot support some of the spec, as written.</div><div>Our experiences i=
mplementing it, and using chromium + pywebsocket for testing both the serve=
r or client implementation.</div>
<div><br></div><div>The following configuration parameters are not supporte=
d, nor can/will be.</div><div><br></div><div>s2c_no_context_takeover</div><=
div>c2s_no_context_takeover</div><div>s2c_max_window_bits</div><div>c2s_max=
_window_bits</div>
<div><br></div><div>This level of control of the deflate algorithm is just =
not possible in Java, sorry.</div><div>We are not using our own implementat=
ion of Deflate, as the one provided by Java itself is better performant (bo=
th in speed and memory use)</div>
<div><br></div><div>We also find the nature of configuration parameters awk=
ward (even if Java supported these specific ones)</div><div>The whole &quot=
;s2c&quot; and &quot;c2s&quot; prefix noise is unnecessary.</div><div><br>
</div><div>Our requests for this spec:</div><div><br></div><div>* eliminate=
 the &quot;s2c&quot; and &quot;c2s&quot; prefixes.</div><div>=A0 =A0&quot;c=
2s&quot; =3D=3D request, from client, what it wants to do</div><div>=A0 =A0=
&quot;s2c&quot; =3D=3D response, from server, what it wants to do</div>
<div>=A0 =A0draft-ietf-hybi-permessage-compression-12, doesn&#39;t make the=
 case for the need for these prefixes, they seem superfluous, duplicating c=
onfiguration parameters just to add context on which direction they have an=
 effect on. =A0something the standard websocket handshake already accomplis=
hes nicely. =A0 so either the stated reason for them in the spec documentat=
ion is unclear, or they truly are irrelevant prefixes.</div>
<div>=A0 =A0imagine a world where we had ...</div><div>=A0 =A0POST /upload =
HTTP/1.1</div><div>=A0 =A0 =A0Request-Content-Length: 6000</div><div>=A0 =
=A0HTTP/1.1 200 OK</div><div>=A0 =A0 =A0Response-Content-Length: 50</div><d=
iv>* define default deflate behavior better.</div>
<div>=A0 =A0http&#39;s content encoding and compression has default behavio=
r, for every flavor of compression scheme.</div><div>=A0 =A0even spdy has d=
efault behavior (note: while spdy has these kinds of optional deflate tweak=
s, in the wild, and in practice, no server currently honors them)</div>
<div>* move the existing configuration parameters (for no_context_takeover =
and max_window_bits) out into optional advanced configuration tweaking.</di=
v><div><br></div></div></div>

--047d7b343ab24eb8f604e7eb0ef3--

From tobias.oberstein@tavendo.de  Fri Oct  4 08:28:12 2013
Return-Path: <tobias.oberstein@tavendo.de>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3597A21F9B85 for <hybi@ietfa.amsl.com>; Fri,  4 Oct 2013 08:28:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qncVCTRqEUhp for <hybi@ietfa.amsl.com>; Fri,  4 Oct 2013 08:27:58 -0700 (PDT)
Received: from EXHUB020-3.exch020.serverdata.net (exhub020-3.exch020.serverdata.net [206.225.164.30]) by ietfa.amsl.com (Postfix) with ESMTP id 5F5A021F9D46 for <hybi@ietf.org>; Fri,  4 Oct 2013 08:26:32 -0700 (PDT)
Received: from EXVMBX020-12.exch020.serverdata.net ([169.254.3.6]) by EXHUB020-3.exch020.serverdata.net ([206.225.164.30]) with mapi; Fri, 4 Oct 2013 08:26:31 -0700
From: Tobias Oberstein <tobias.oberstein@tavendo.de>
To: Joakim Erdfelt <joakim@intalio.com>, Takeshi Yoshino <tyoshino@google.com>
Date: Fri, 4 Oct 2013 08:26:30 -0700
Thread-Topic: [hybi] Restarting IESG review on permessage-deflate
Thread-Index: Ac7BDfNkC+W3CbxGQT+ic/2r+IsbNwABln0Q
Message-ID: <634914A010D0B943A035D226786325D4446790BF34@EXVMBX020-12.exch020.serverdata.net>
References: <CAH9hSJbwd5qhMJw=3dwk3CDPua5ENRksd9=q2KDcyyma3uKzZg@mail.gmail.com> <CAG4zZZD8eq4w9kyQbX2AJcM1LA8=UyRO7txK7TvmYhSp=YU+9g@mail.gmail.com>
In-Reply-To: <CAG4zZZD8eq4w9kyQbX2AJcM1LA8=UyRO7txK7TvmYhSp=YU+9g@mail.gmail.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "hybi@ietf.org" <hybi@ietf.org>, Gabriel Montenegro <Gabriel.Montenegro@microsoft.com>
Subject: Re: [hybi] Restarting IESG review on permessage-deflate
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Fri, 04 Oct 2013 15:28:12 -0000

> This level of control of the deflate algorithm is just not possible in Ja=
va, sorry.

Well, I'm sorry for the Java community not being able to fix this in 10+ ye=
ars;)

> We are not using our own implementation of Deflate, as the one provided b=
y Java itself is better performant (both in speed and memory use)

I feel your pain, but:

1) Z_SYNC_FLUSH is available in Java now
http://bugs.sun.com/view_bug.do?bug_id=3D4206909

2) FWIW, as a sidenote, here is a pure Java implementation capable of the r=
espective features:
https://github.com/ymnk/jzlib

>We also find the nature of configuration parameters awkward (even if Java =
supported these specific ones)
>The whole "s2c" and "c2s" prefix noise is unnecessary.

No, it's not.

>Our requests for this spec:

I'd vote against changing the spec at this stage:

- it has proved to work
- the parameters and the control offered makes sense
- just because Java is lacking should not impose limitations on everybody e=
lse (C, C++, Python, NodeJS (http://nodejs.org/api/zlib.html#zlib_options),=
 and more all have support for the respective options).

Please: just fix Java.

/Tobias

From derhoermi@gmx.net  Fri Oct  4 08:30:54 2013
Return-Path: <derhoermi@gmx.net>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3373D21F9E77 for <hybi@ietfa.amsl.com>; Fri,  4 Oct 2013 08:30:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.979
X-Spam-Level: 
X-Spam-Status: No, score=-0.979 tagged_above=-999 required=5 tests=[AWL=-0.340, BAYES_00=-2.599, RCVD_IN_BL_SPAMCOP_NET=1.96]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dFAMWi7e0W9R for <hybi@ietfa.amsl.com>; Fri,  4 Oct 2013 08:30:42 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) by ietfa.amsl.com (Postfix) with ESMTP id F34EE21F9B85 for <hybi@ietf.org>; Fri,  4 Oct 2013 08:30:03 -0700 (PDT)
Received: from netb.Speedport_W_700V ([91.35.57.193]) by mail.gmx.com (mrgmx103) with ESMTPA (Nemesis) id 0MBFBB-1Va7fZ0Syj-00AFlB for <hybi@ietf.org>; Fri, 04 Oct 2013 17:30:02 +0200
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Tobias Oberstein <tobias.oberstein@tavendo.de>
Date: Fri, 04 Oct 2013 17:29:57 +0200
Message-ID: <dmnt49hf1bbifiote81fumeamnk76vti1t@hive.bjoern.hoehrmann.de>
References: <CAH9hSJbwd5qhMJw=3dwk3CDPua5ENRksd9=q2KDcyyma3uKzZg@mail.gmail.com> <CAG4zZZD8eq4w9kyQbX2AJcM1LA8=UyRO7txK7TvmYhSp=YU+9g@mail.gmail.com> <634914A010D0B943A035D226786325D4446790BF34@EXVMBX020-12.exch020.serverdata.net>
In-Reply-To: <634914A010D0B943A035D226786325D4446790BF34@EXVMBX020-12.exch020.serverdata.net>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K0:7qthmFA6zQolFIimQAkkwOHjldjL69R2lbMZGgnDmFRn6Ru4uMY 27/hEshNLCtvsMRAHZCp4FUr2PkR+RYmbfUiZHG9xo3Ex4fsy1mtC61UkHpiOtHO00DrUbf umM2XjTjDSivnKAlEfOdRpnEc7oO9B/ZKvyPeWAsjD+sRDwvAU4BfUiMEzBKHfv+f+D94ZI HD6RYkAw3cFmv3oZZJAJA==
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] Restarting IESG review on permessage-deflate
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Fri, 04 Oct 2013 15:30:54 -0000

* Tobias Oberstein wrote:
>>We also find the nature of configuration parameters awkward (even if Java supported these specific ones)
>>The whole "s2c" and "c2s" prefix noise is unnecessary.
>
>No, it's not.

What is your reasoning?
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 

From tobias.oberstein@tavendo.de  Fri Oct  4 09:00:06 2013
Return-Path: <tobias.oberstein@tavendo.de>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7974721F9E94 for <hybi@ietfa.amsl.com>; Fri,  4 Oct 2013 09:00:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uhP3Vlp6z1zS for <hybi@ietfa.amsl.com>; Fri,  4 Oct 2013 08:59:52 -0700 (PDT)
Received: from EXHUB020-5.exch020.serverdata.net (exhub020-5.exch020.serverdata.net [206.225.164.32]) by ietfa.amsl.com (Postfix) with ESMTP id 4DF4421F9E95 for <hybi@ietf.org>; Fri,  4 Oct 2013 08:57:37 -0700 (PDT)
Received: from EXVMBX020-12.exch020.serverdata.net ([169.254.3.6]) by EXHUB020-5.exch020.serverdata.net ([206.225.164.32]) with mapi; Fri, 4 Oct 2013 08:57:27 -0700
From: Tobias Oberstein <tobias.oberstein@tavendo.de>
To: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Fri, 4 Oct 2013 08:57:25 -0700
Thread-Topic: [hybi] Restarting IESG review on permessage-deflate
Thread-Index: Ac7BFpnF1DJHyFkARdid5zktxuHUNQAA4/lQ
Message-ID: <634914A010D0B943A035D226786325D4446790BF87@EXVMBX020-12.exch020.serverdata.net>
References: <CAH9hSJbwd5qhMJw=3dwk3CDPua5ENRksd9=q2KDcyyma3uKzZg@mail.gmail.com> <CAG4zZZD8eq4w9kyQbX2AJcM1LA8=UyRO7txK7TvmYhSp=YU+9g@mail.gmail.com> <634914A010D0B943A035D226786325D4446790BF34@EXVMBX020-12.exch020.serverdata.net> <dmnt49hf1bbifiote81fumeamnk76vti1t@hive.bjoern.hoehrmann.de>
In-Reply-To: <dmnt49hf1bbifiote81fumeamnk76vti1t@hive.bjoern.hoehrmann.de>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] Restarting IESG review on permessage-deflate
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Fri, 04 Oct 2013 16:00:07 -0000

>>>We also find the nature of configuration parameters awkward (even if=20
>>>Java supported these specific ones) The whole "s2c" and "c2s" prefix noi=
se is unnecessary.
>>
>>No, it's not.

>What is your reasoning?

We need to differentiate between parameter offers and parameter accepts, an=
d do that for both directions.

If there is no prefix, both client and server would only be able to use the=
 same parameters for both directions.

/Tobias

From joakim@intalio.com  Fri Oct  4 09:26:05 2013
Return-Path: <joakim@intalio.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50FDA21F9E46 for <hybi@ietfa.amsl.com>; Fri,  4 Oct 2013 09:26:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J9CS8JVKc0zo for <hybi@ietfa.amsl.com>; Fri,  4 Oct 2013 09:26:01 -0700 (PDT)
Received: from mail-ee0-f53.google.com (mail-ee0-f53.google.com [74.125.83.53]) by ietfa.amsl.com (Postfix) with ESMTP id BFEF521F9E3A for <hybi@ietf.org>; Fri,  4 Oct 2013 09:25:57 -0700 (PDT)
Received: by mail-ee0-f53.google.com with SMTP id b15so1958846eek.12 for <hybi@ietf.org>; Fri, 04 Oct 2013 09:25:56 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=KSBYg3P9mxCcmaxPoZQ6hk5OtiUQTboJmsMfqsGmDiE=; b=URXiwz5tf2b1Ogo/EqIJQ/pcef+cYO0BowjcitYZrooONbOnhf5SZO9UcNpN3u+ors VGtppR9sBQh85QJOdlTtzy05w3WQV36zMGD58RudVUlXR+iouQa1d514cnRp2ii+3edQ fB7p8s6dXSPQBPZEL61DCM3rAJPmvn1T9Bp9ZOKtLtANArFZfA7qnrwLYg1sWHm+aghI QGE+QqCbOmw0Gw6X8M3Kst6h5S4UVpnc6fTy+Sg0UFs8aerjmRcaWx/4gbddin5u8k3q MjLMa/HLvh6hai9xzhzMTE/cAMYUCaVzV+AJvydqX18Wktla7KqZdyBCTLEOobSLDqL7 CNoQ==
X-Gm-Message-State: ALoCoQn7fzhPaUAmX8ZTzrsn1MAYnGb75XXKZG16nA8l/JkXDZr9LK8fnxN+iCaxLjY6IF8A6BCz
MIME-Version: 1.0
X-Received: by 10.15.102.71 with SMTP id bq47mr4153494eeb.66.1380903956617; Fri, 04 Oct 2013 09:25:56 -0700 (PDT)
Received: by 10.14.134.73 with HTTP; Fri, 4 Oct 2013 09:25:56 -0700 (PDT)
In-Reply-To: <634914A010D0B943A035D226786325D4446790BF87@EXVMBX020-12.exch020.serverdata.net>
References: <CAH9hSJbwd5qhMJw=3dwk3CDPua5ENRksd9=q2KDcyyma3uKzZg@mail.gmail.com> <CAG4zZZD8eq4w9kyQbX2AJcM1LA8=UyRO7txK7TvmYhSp=YU+9g@mail.gmail.com> <634914A010D0B943A035D226786325D4446790BF34@EXVMBX020-12.exch020.serverdata.net> <dmnt49hf1bbifiote81fumeamnk76vti1t@hive.bjoern.hoehrmann.de> <634914A010D0B943A035D226786325D4446790BF87@EXVMBX020-12.exch020.serverdata.net>
Date: Fri, 4 Oct 2013 09:25:56 -0700
Message-ID: <CAG4zZZDdcC5+cob715KE77uZiPYAo1Oz6M0StLA=vSp5iX_h7A@mail.gmail.com>
From: Joakim Erdfelt <joakim@intalio.com>
To: Tobias Oberstein <tobias.oberstein@tavendo.de>
Content-Type: multipart/alternative; boundary=089e016820f8cdcd3a04e7ecc19e
Cc: "hybi@ietf.org" <hybi@ietf.org>, Bjoern Hoehrmann <derhoermi@gmx.net>
Subject: Re: [hybi] Restarting IESG review on permessage-deflate
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Fri, 04 Oct 2013 16:26:05 -0000

--089e016820f8cdcd3a04e7ecc19e
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Oct 4, 2013 at 8:57 AM, Tobias Oberstein <
tobias.oberstein@tavendo.de> wrote:

> >>>We also find the nature of configuration parameters awkward (even if
> >>>Java supported these specific ones) The whole "s2c" and "c2s" prefix
> noise is unnecessary.
> >>
> >>No, it's not.
>
> >What is your reasoning?
>
> We need to differentiate between parameter offers and parameter accepts,
> and do that for both directions.
>
> If there is no prefix, both client and server would only be able to use
> the same parameters for both directions.
>
>
That's desired actually, and consistent with behavior of other protocols
and extensions (mux for example).
The websocket handshake is always client initiated to server.
The client always says what it desires on the handshake request.  (this is
the spec "c2s")
The server always says what it can do on the handshake response.  (this is
the spec "s2c")
Where does the need for the "s2c" and "c2s" prefixes come from?
Even the justification for them in the permessage-deflate spec is lacking.

To put it another way:

Handshake Request:
"c2s_no_context_takeover"
"c2s_max_window_bits"

Handshake Response:
"s2c_no_context_takeover"
"s2c_max_window_bits"

The spec use of these prefixes is unclear at best, and downright misleading
at worst.
If the spec is trying to say something like this ...

   Hi, I'm the client, I want to talk to you using 1 set of configurations,
and I want you to talk back to me on a different set of configurations.

... then this is not made clear in
http://tools.ietf.org/html/draft-ietf-hybi-permessage-compression-12

And If this is the intention, make it clear, in the spec, that the whole
point of the prefixes is to have different configurations for incoming vs
outgoing frames. (and explain the pros and cons of this)

- Joakim

--089e016820f8cdcd3a04e7ecc19e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Fri, Oct 4, 2013 at 8:57 AM, Tobias Oberstein <span dir=
=3D"ltr">&lt;<a href=3D"mailto:tobias.oberstein@tavendo.de" target=3D"_blan=
k">tobias.oberstein@tavendo.de</a>&gt;</span> wrote:<br><div class=3D"gmail=
_extra">
<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204=
);border-left-style:solid;padding-left:1ex"><div class=3D"im">&gt;&gt;&gt;W=
e also find the nature of configuration parameters awkward (even if<br>

&gt;&gt;&gt;Java supported these specific ones) The whole &quot;s2c&quot; a=
nd &quot;c2s&quot; prefix noise is unnecessary.<br>
&gt;&gt;<br>
&gt;&gt;No, it&#39;s not.<br>
<br>
&gt;What is your reasoning?<br>
<br>
</div>We need to differentiate between parameter offers and parameter accep=
ts, and do that for both directions.<br>
<br>
If there is no prefix, both client and server would only be able to use the=
 same parameters for both directions.<br><span class=3D""><font color=3D"#8=
88888"><br></font></span></blockquote><div><br></div><div>That&#39;s desire=
d actually, and consistent with behavior of other protocols and extensions =
(mux for example).</div>
<div>The websocket handshake is always client initiated to server.</div><di=
v>The client always says what it desires on the handshake request. =A0(this=
 is the spec &quot;c2s&quot;)</div><div>The server always says what it can =
do on the handshake response. =A0(this is the spec &quot;s2c&quot;)</div>
<div>Where does the need for the &quot;s2c&quot; and &quot;c2s&quot; prefix=
es come from?</div><div>Even the justification for them in the permessage-d=
eflate spec is lacking.</div><div><br></div><div>To put it another way:</di=
v>
<div><br></div><div>Handshake Request:</div><div><div class=3D"gmail_extra"=
><div class=3D"gmail_quote"><div>&quot;c2s_no_context_takeover&quot;</div><=
div>&quot;c2s_max_window_bits&quot;<br></div><div><br></div></div></div></d=
iv>
<div>Handshake Response:</div><div>&quot;s2c_no_context_takeover&quot;</div=
><div>&quot;s2c_max_window_bits&quot;</div><div><br></div><div>The spec use=
 of these prefixes is unclear at best, and downright misleading at worst.</=
div>
<div>If the spec is trying to say something like this ...</div><div><br></d=
iv><div>=A0 =A0Hi, I&#39;m the client, I want to talk to you using 1 set of=
 configurations, and I want you to talk back to me on a different set of co=
nfigurations.</div>
<div><br></div><div>... then this is not made clear in=A0<a href=3D"http://=
tools.ietf.org/html/draft-ietf-hybi-permessage-compression-12">http://tools=
.ietf.org/html/draft-ietf-hybi-permessage-compression-12</a>=A0</div><div><=
br>
</div><div>And If this is the intention, make it clear, in the spec, that t=
he whole point of the prefixes is to have different configurations for inco=
ming vs outgoing frames. (and explain the pros and cons of this)</div><div>
<br></div><div>- Joakim</div></div></div></div>

--089e016820f8cdcd3a04e7ecc19e--

From joakim@intalio.com  Fri Oct  4 09:56:01 2013
Return-Path: <joakim@intalio.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 507E521F9D2C for <hybi@ietfa.amsl.com>; Fri,  4 Oct 2013 09:56:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FLcL3nOnd4Fb for <hybi@ietfa.amsl.com>; Fri,  4 Oct 2013 09:55:57 -0700 (PDT)
Received: from mail-ea0-f178.google.com (mail-ea0-f178.google.com [209.85.215.178]) by ietfa.amsl.com (Postfix) with ESMTP id B474421F9D1B for <hybi@ietf.org>; Fri,  4 Oct 2013 09:55:55 -0700 (PDT)
Received: by mail-ea0-f178.google.com with SMTP id a15so1940594eae.9 for <hybi@ietf.org>; Fri, 04 Oct 2013 09:55:54 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=8AsXw4BLLT3pCMYw8gVHb8f0a0ffmej9ChZEdNlzbwY=; b=UDVBB5m5i8v1/v/G0QSYqihhb1r9xeovUL/VrMGJNyBzoFxNuKZXLdFPBRAHurkXmx 64qsVe92/JeYZU4JMiw/qtYand7+lnYHbZhtYW5mxCiE4z/9PW0vtdFh5rGQz4Vv4c9F CjloCLspx/voOjVjCD/NbMoUOYFnM0K/9dlnPLsE3wnRQGj+gmB/r4KqLnLTNdd/erYD 3UJAOm2CDDOUmw/CyA7Lf/+iArbzN5XR5tr+a7e3ymxhTUSTg/EaKgWWBPlt7Emvlzrc myGFFf4hkF+3yjo19PCd6fP800NPc/4vpMxs1CuKFtdpZ9UqcBPlnTB/Ew7SaG2akO2j ErLQ==
X-Gm-Message-State: ALoCoQkwI8XWb+I9mCTtG7gayT8zPv0fLv7S2/bBMXxYMUIMSv8SOiOrdnmI47ELAZMP4NzMBwR3
MIME-Version: 1.0
X-Received: by 10.14.246.11 with SMTP id p11mr23338201eer.9.1380905754789; Fri, 04 Oct 2013 09:55:54 -0700 (PDT)
Received: by 10.14.134.73 with HTTP; Fri, 4 Oct 2013 09:55:54 -0700 (PDT)
In-Reply-To: <634914A010D0B943A035D226786325D4446790BF34@EXVMBX020-12.exch020.serverdata.net>
References: <CAH9hSJbwd5qhMJw=3dwk3CDPua5ENRksd9=q2KDcyyma3uKzZg@mail.gmail.com> <CAG4zZZD8eq4w9kyQbX2AJcM1LA8=UyRO7txK7TvmYhSp=YU+9g@mail.gmail.com> <634914A010D0B943A035D226786325D4446790BF34@EXVMBX020-12.exch020.serverdata.net>
Date: Fri, 4 Oct 2013 09:55:54 -0700
Message-ID: <CAG4zZZDNRZ_kaXBKhx5VkKjpj+Luo53Y7ue0eaGHH_ghoBrdkQ@mail.gmail.com>
From: Joakim Erdfelt <joakim@intalio.com>
To: Tobias Oberstein <tobias.oberstein@tavendo.de>
Content-Type: multipart/alternative; boundary=001a1132ef62fbbb3104e7ed2c3f
Cc: "hybi@ietf.org" <hybi@ietf.org>, Gabriel Montenegro <Gabriel.Montenegro@microsoft.com>
Subject: Re: [hybi] Restarting IESG review on permessage-deflate
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Fri, 04 Oct 2013 16:56:01 -0000

--001a1132ef62fbbb3104e7ed2c3f
Content-Type: text/plain; charset=ISO-8859-1

> Well, I'm sorry for the Java community not being able to fix this in 10+
> years;)
>

Yet, oddly, with web technologies, this hasn't been a problem since our
initial use of Oak in 1995 (yes, Jetty has existed since 1995)
Also, the opposite is true as well.
The capabilities of one set of libraries (c & python) should not be forced
on all environments as well.
The spec should not have these kinds of things mandated or required.
We have no problem with a spec having advanced features and configurables
such as these, but don't force them.



>
> > We are not using our own implementation of Deflate, as the one provided
> by Java itself is better performant (both in speed and memory use)
>
> I feel your pain, but:
>
> 1) Z_SYNC_FLUSH is available in Java now
> http://bugs.sun.com/view_bug.do?bug_id=4206909



This does not operate in the same way as what pywebsocket expects.  However
chromium's behavior is consistent (or resilient, hard to say)



>
>
> 2) FWIW, as a sidenote, here is a pure Java implementation capable of the
> respective features:
> https://github.com/ymnk/jzlib



Again, not performant, and uses too much memory, and is ultimately at odds
with precedents already set with other web technologies.
Remember, websocket is a web technology at its heart.
Imagine the opposite, a theoretical spec mandated something that would mean
you could not use your native implementations of something common, lets say
for argument that you suddenly were forced to, by a spec, to handle
filesystem metadata tags.
Now what?
do you toss out all of your standard file i/o and filesystem libs and start
anew?
do you force the entire environment ecosystem to catch up to
this theoretical spec?
do you introduce another file system library mechanism just to handle this
theoretical spec? having 2 filesystem libraries at the same time?

As you can see, these concepts might have value, for some, but should not
be forced or required.
These are advanced features, optional features.

- Joakim

--001a1132ef62fbbb3104e7ed2c3f
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><div class=3D"gmail_quote">=
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">
Well, I&#39;m sorry for the Java community not being able to fix this in 10=
+ years;)<br></blockquote><div><br></div><div>Yet, oddly, with web technolo=
gies, this hasn&#39;t been a problem since our initial use of Oak in 1995 (=
yes, Jetty has existed since 1995)</div>
<div>Also, the opposite is true as well.</div><div>The capabilities of one =
set of libraries (c &amp; python) should not be forced on all environments =
as well.</div><div>The spec should not have these kinds of things mandated =
or required.</div>
<div>We have no problem with a spec having advanced features and configurab=
les such as these, but don&#39;t force them.</div><div><br></div><div>=A0</=
div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bor=
der-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:sol=
id;padding-left:1ex">

<div class=3D"im"><br>
&gt; We are not using our own implementation of Deflate, as the one provide=
d by Java itself is better performant (both in speed and memory use)<br>
<br>
</div>I feel your pain, but:<br>
<br>
1) Z_SYNC_FLUSH is available in Java now<br>
<a href=3D"http://bugs.sun.com/view_bug.do?bug_id=3D4206909" target=3D"_bla=
nk">http://bugs.sun.com/view_bug.do?bug_id=3D4206909</a></blockquote><div><=
br></div><div><br></div><div>This does not operate in the same way as what =
pywebsocket expects. =A0However chromium&#39;s behavior is consistent (or r=
esilient, hard to say)</div>
<div><br></div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,2=
04);border-left-style:solid;padding-left:1ex"><br>
<br>
2) FWIW, as a sidenote, here is a pure Java implementation capable of the r=
espective features:<br>
<a href=3D"https://github.com/ymnk/jzlib" target=3D"_blank">https://github.=
com/ymnk/jzlib</a></blockquote><div><br></div><div><br></div><div>Again, no=
t performant, and uses too much memory, and is ultimately at odds with prec=
edents already set with other web technologies.</div>
<div>Remember, websocket is a web technology at its heart.</div><div>Imagin=
e the opposite, a theoretical spec mandated something that would mean you c=
ould not use your native implementations of something common, lets say for =
argument that you suddenly were forced to, by a spec, to handle filesystem =
metadata tags.=A0</div>
<div>Now what?=A0</div><div>do you toss out all of your standard file i/o a=
nd filesystem libs and start anew? =A0</div><div>do you force the entire en=
vironment ecosystem to catch up to this=A0theoretical spec? =A0</div><div>d=
o you introduce another file system library mechanism just to handle this t=
heoretical spec? having 2 filesystem libraries at the same time?</div>
<div><br></div><div>As you can see, these concepts might have value, for so=
me, but should not be forced or required.</div><div>These are advanced feat=
ures, optional features.</div><div><br></div><div>- Joakim</div></div></div=
>
</div>

--001a1132ef62fbbb3104e7ed2c3f--

From tobias.oberstein@tavendo.de  Fri Oct  4 09:58:27 2013
Return-Path: <tobias.oberstein@tavendo.de>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54DD321F9C9B for <hybi@ietfa.amsl.com>; Fri,  4 Oct 2013 09:58:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lkbhvTmMp1iW for <hybi@ietfa.amsl.com>; Fri,  4 Oct 2013 09:58:21 -0700 (PDT)
Received: from EXHUB020-5.exch020.serverdata.net (exhub020-5.exch020.serverdata.net [206.225.164.32]) by ietfa.amsl.com (Postfix) with ESMTP id C59F021F9C87 for <hybi@ietf.org>; Fri,  4 Oct 2013 09:58:19 -0700 (PDT)
Received: from EXVMBX020-12.exch020.serverdata.net ([169.254.3.6]) by EXHUB020-5.exch020.serverdata.net ([206.225.164.32]) with mapi; Fri, 4 Oct 2013 09:58:18 -0700
From: Tobias Oberstein <tobias.oberstein@tavendo.de>
To: Joakim Erdfelt <joakim@intalio.com>
Date: Fri, 4 Oct 2013 09:58:16 -0700
Thread-Topic: [hybi] Restarting IESG review on permessage-deflate
Thread-Index: Ac7BHmhkBzAhR0opQqOuBBF9OnMFtgAA+CyQ
Message-ID: <634914A010D0B943A035D226786325D4446790BFE9@EXVMBX020-12.exch020.serverdata.net>
References: <CAH9hSJbwd5qhMJw=3dwk3CDPua5ENRksd9=q2KDcyyma3uKzZg@mail.gmail.com> <CAG4zZZD8eq4w9kyQbX2AJcM1LA8=UyRO7txK7TvmYhSp=YU+9g@mail.gmail.com> <634914A010D0B943A035D226786325D4446790BF34@EXVMBX020-12.exch020.serverdata.net> <dmnt49hf1bbifiote81fumeamnk76vti1t@hive.bjoern.hoehrmann.de> <634914A010D0B943A035D226786325D4446790BF87@EXVMBX020-12.exch020.serverdata.net> <CAG4zZZDdcC5+cob715KE77uZiPYAo1Oz6M0StLA=vSp5iX_h7A@mail.gmail.com>
In-Reply-To: <CAG4zZZDdcC5+cob715KE77uZiPYAo1Oz6M0StLA=vSp5iX_h7A@mail.gmail.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "hybi@ietf.org" <hybi@ietf.org>, Bjoern Hoehrmann <derhoermi@gmx.net>
Subject: Re: [hybi] Restarting IESG review on permessage-deflate
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Fri, 04 Oct 2013 16:58:27 -0000

On Fri, Oct 4, 2013 at 8:57 AM, Tobias Oberstein <tobias.oberstein@tavendo.=
de> wrote:
>>>>>We also find the nature of configuration parameters awkward (even if
>>>>>Java supported these specific ones) The whole "s2c" and "c2s" prefix n=
oise is unnecessary.
>>>>
>>>>No, it's not.

>>>What is your reasoning?
>>We need to differentiate between parameter offers and parameter accepts, =
and do that for both directions.

>>If there is no prefix, both client and server would only be able to use t=
he same parameters for both directions.

>That's desired actually, and consistent with behavior of other protocols a=
nd extensions (mux for example).
...
>Where does the need for the "s2c" and "c2s" prefixes come from?

The need comes from having different parameters for up- vs downstream.

The value of having different parameters up- vs. downstream is being able t=
o optimize for the resource restrictions of both (client & server) independ=
ently.

/Tobias



From tobias.oberstein@tavendo.de  Fri Oct  4 10:11:56 2013
Return-Path: <tobias.oberstein@tavendo.de>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6B7B21F9CC6 for <hybi@ietfa.amsl.com>; Fri,  4 Oct 2013 10:11:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mqQMVypLOMHl for <hybi@ietfa.amsl.com>; Fri,  4 Oct 2013 10:11:53 -0700 (PDT)
Received: from EXHUB020-2.exch020.serverdata.net (exhub020-2.exch020.serverdata.net [206.225.164.29]) by ietfa.amsl.com (Postfix) with ESMTP id B7D7621F9D3E for <hybi@ietf.org>; Fri,  4 Oct 2013 10:11:40 -0700 (PDT)
Received: from EXVMBX020-12.exch020.serverdata.net ([169.254.3.6]) by EXHUB020-2.exch020.serverdata.net ([206.225.164.29]) with mapi; Fri, 4 Oct 2013 10:11:39 -0700
From: Tobias Oberstein <tobias.oberstein@tavendo.de>
To: Joakim Erdfelt <joakim@intalio.com>
Date: Fri, 4 Oct 2013 10:11:37 -0700
Thread-Topic: [hybi] Restarting IESG review on permessage-deflate
Thread-Index: Ac7BIpg9LeVKB/NwQjyc8fiGRzAU9gAALb9g
Message-ID: <634914A010D0B943A035D226786325D4446790BFFC@EXVMBX020-12.exch020.serverdata.net>
References: <CAH9hSJbwd5qhMJw=3dwk3CDPua5ENRksd9=q2KDcyyma3uKzZg@mail.gmail.com> <CAG4zZZD8eq4w9kyQbX2AJcM1LA8=UyRO7txK7TvmYhSp=YU+9g@mail.gmail.com> <634914A010D0B943A035D226786325D4446790BF34@EXVMBX020-12.exch020.serverdata.net> <CAG4zZZDNRZ_kaXBKhx5VkKjpj+Luo53Y7ue0eaGHH_ghoBrdkQ@mail.gmail.com>
In-Reply-To: <CAG4zZZDNRZ_kaXBKhx5VkKjpj+Luo53Y7ue0eaGHH_ghoBrdkQ@mail.gmail.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "hybi@ietf.org" <hybi@ietf.org>, Gabriel Montenegro <Gabriel.Montenegro@microsoft.com>
Subject: Re: [hybi] Restarting IESG review on permessage-deflate
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Fri, 04 Oct 2013 17:11:57 -0000

>>Well, I'm sorry for the Java community not being able to fix this in 10+ =
years;)
>Yet, oddly, with web technologies, this hasn't been a problem since our in=
itial use of Oak in 1995 (yes, Jetty has existed since 1995)

Jetty being around since 1995 is obviously awesome!

As a strange coincidence, zlib has also be around since 1 May 1995 (I haven=
't checked whether the respective options have been in the first version th=
ough).

> The capabilities of one set of libraries (c & python) should not be force=
d on all environments as well.

Lets collect a list: a) stuff that exposes the complete zlib vs b) stuff th=
at does not;)

a) C, C++, Python, NodeJS, Perl, Ruby, PHP, Erlang, Haskell
b) Java

Caveat: I (obviously) have not used all of above myself. Just had a quick g=
lance at their docs.

Pointers:
http://perldoc.perl.org/Compress/Zlib.html#Deflate-Interface
http://www.ruby-doc.org/stdlib-2.0.0/libdoc/zlib/rdoc/Zlib/Deflate.html
http://www.php.net/manual/de/function.gzdeflate.php
http://erlang.org/doc/man/zlib.html
http://hackage.haskell.org/package/zlib-0.5.4.1/docs/Codec-Compression-Zlib=
.html

I stop here;)

/Tobias

From joakim@intalio.com  Fri Oct  4 10:41:13 2013
Return-Path: <joakim@intalio.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32CC421F9DA3 for <hybi@ietfa.amsl.com>; Fri,  4 Oct 2013 10:41:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IpwHb1O3WxvL for <hybi@ietfa.amsl.com>; Fri,  4 Oct 2013 10:41:07 -0700 (PDT)
Received: from mail-ee0-f41.google.com (mail-ee0-f41.google.com [74.125.83.41]) by ietfa.amsl.com (Postfix) with ESMTP id 686F121F9CA6 for <hybi@ietf.org>; Fri,  4 Oct 2013 10:41:02 -0700 (PDT)
Received: by mail-ee0-f41.google.com with SMTP id d17so1966403eek.0 for <hybi@ietf.org>; Fri, 04 Oct 2013 10:41:01 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=Q20A46WZWNR6wBLrpf4aO+rdOvowJu9dLDbqt1r9km0=; b=ByBGhai4osj6SNmme9GGsQ82drjZ/BRXWm6bWjA8pVNRsgLfjxwZyexVTrkMXb35Ma r4UERHdnPQqSHuSHzY+iWc9qGKwHoYDTD4v3pt8l3kmnz5FbJgI1iWvHfiOcY/B0I5jE oPiLOStFWFKTtdz0A78Pd1B4Xq0QGaaFyqmM5INHtJu1UbJQjOeRaXJpotQPbmgIAY8W ZboDNg0lNUn1W+8VeWCq67UvPkfr9v2dXHMbCkR7t2p7KswvjUWdwBaeOjgdwVSvZz0u YlwGdfx6g6JlxfWYNDcPZoC1bUkRb75Omg1o6ZbD4WShVTEFUpEZPXREBQHegZCLcnpV tbGw==
X-Gm-Message-State: ALoCoQkoCoOCrpkJbxsM/sHBvBMtuzMbeyy9x6FbvZp/MMqhcvsFeGHw+qhH7jUeg0RLQhAN0F5r
MIME-Version: 1.0
X-Received: by 10.14.213.68 with SMTP id z44mr4606189eeo.70.1380908461412; Fri, 04 Oct 2013 10:41:01 -0700 (PDT)
Received: by 10.14.134.73 with HTTP; Fri, 4 Oct 2013 10:41:01 -0700 (PDT)
In-Reply-To: <634914A010D0B943A035D226786325D4446790BFFC@EXVMBX020-12.exch020.serverdata.net>
References: <CAH9hSJbwd5qhMJw=3dwk3CDPua5ENRksd9=q2KDcyyma3uKzZg@mail.gmail.com> <CAG4zZZD8eq4w9kyQbX2AJcM1LA8=UyRO7txK7TvmYhSp=YU+9g@mail.gmail.com> <634914A010D0B943A035D226786325D4446790BF34@EXVMBX020-12.exch020.serverdata.net> <CAG4zZZDNRZ_kaXBKhx5VkKjpj+Luo53Y7ue0eaGHH_ghoBrdkQ@mail.gmail.com> <634914A010D0B943A035D226786325D4446790BFFC@EXVMBX020-12.exch020.serverdata.net>
Date: Fri, 4 Oct 2013 10:41:01 -0700
Message-ID: <CAG4zZZC30-d45Ow6pLZkQCYbuqWDwW6U3KW5R43VgafhwrPOEA@mail.gmail.com>
From: Joakim Erdfelt <joakim@intalio.com>
To: Tobias Oberstein <tobias.oberstein@tavendo.de>
Content-Type: multipart/alternative; boundary=047d7b62213a4f8a9b04e7edceaf
Cc: "hybi@ietf.org" <hybi@ietf.org>, Gabriel Montenegro <Gabriel.Montenegro@microsoft.com>
Subject: Re: [hybi] Restarting IESG review on permessage-deflate
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Fri, 04 Oct 2013 17:41:13 -0000

--047d7b62213a4f8a9b04e7edceaf
Content-Type: text/plain; charset=ISO-8859-1

Ok, add to the b) side of the equation:

scala - same classlib and jvm as java
jython - same classlib and jvm as java, no native zlib support here
php - http://www.php.net/manual/en/ref.zlib.php (cannot support
max_window_bits, no_context_takeover might be possible)
c# -
http://msdn.microsoft.com/en-us/library/system.io.compression.deflatestream_methods.aspx
(cannot
support max_window_bits, no_context_takeover might be possible)


--
Joakim Erdfelt <joakim@intalio.com>
webtide.com <http://www.webtide.com/> - intalio.com/jetty
Expert advice, services and support from from the Jetty & CometD experts
eclipse.org/jetty - cometd.org


On Fri, Oct 4, 2013 at 10:11 AM, Tobias Oberstein <
tobias.oberstein@tavendo.de> wrote:

> >>Well, I'm sorry for the Java community not being able to fix this in 10+
> years;)
> >Yet, oddly, with web technologies, this hasn't been a problem since our
> initial use of Oak in 1995 (yes, Jetty has existed since 1995)
>
> Jetty being around since 1995 is obviously awesome!
>
> As a strange coincidence, zlib has also be around since 1 May 1995 (I
> haven't checked whether the respective options have been in the first
> version though).
>
> > The capabilities of one set of libraries (c & python) should not be
> forced on all environments as well.
>
> Lets collect a list: a) stuff that exposes the complete zlib vs b) stuff
> that does not;)
>
> a) C, C++, Python, NodeJS, Perl, Ruby, PHP, Erlang, Haskell
> b) Java
>
> Caveat: I (obviously) have not used all of above myself. Just had a quick
> glance at their docs.
>
> Pointers:
> http://perldoc.perl.org/Compress/Zlib.html#Deflate-Interface
> http://www.ruby-doc.org/stdlib-2.0.0/libdoc/zlib/rdoc/Zlib/Deflate.html
> http://www.php.net/manual/de/function.gzdeflate.php
> http://erlang.org/doc/man/zlib.html
>
> http://hackage.haskell.org/package/zlib-0.5.4.1/docs/Codec-Compression-Zlib.html
>
> I stop here;)
>
> /Tobias
>

--047d7b62213a4f8a9b04e7edceaf
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Ok, add to the b) side of the equation:<div><br></div><div=
>scala - same classlib and jvm as java</div><div>jython - same classlib and=
 jvm as java, no native zlib support here</div><div>php -=A0<a href=3D"http=
://www.php.net/manual/en/ref.zlib.php">http://www.php.net/manual/en/ref.zli=
b.php</a>=A0(cannot support max_window_bits, no_context_takeover might be p=
ossible)</div>
<div>c# -=A0<a href=3D"http://msdn.microsoft.com/en-us/library/system.io.co=
mpression.deflatestream_methods.aspx">http://msdn.microsoft.com/en-us/libra=
ry/system.io.compression.deflatestream_methods.aspx</a>=A0(cannot support m=
ax_window_bits, no_context_takeover might be possible)</div>
<div><br></div></div><div class=3D"gmail_extra"><br clear=3D"all"><div><div=
 dir=3D"ltr"><div>--</div><div>Joakim Erdfelt &lt;<a href=3D"mailto:joakim@=
intalio.com" target=3D"_blank">joakim@intalio.com</a>&gt;</div><div><a href=
=3D"http://www.webtide.com/" target=3D"_blank">webtide.com</a>=A0- <a href=
=3D"http://intalio.com/jetty" target=3D"_blank">intalio.com/jetty</a></div>
<div><span>Expert advice, services and support from=A0</span><span>from the=
 Jetty &amp; CometD experts</span></div><div><a href=3D"http://eclipse.org/=
jetty/" target=3D"_blank">eclipse.org/jetty</a>=A0-=A0<a href=3D"http://com=
etd.org/" target=3D"_blank">cometd.org</a></div>
</div></div>
<br><br><div class=3D"gmail_quote">On Fri, Oct 4, 2013 at 10:11 AM, Tobias =
Oberstein <span dir=3D"ltr">&lt;<a href=3D"mailto:tobias.oberstein@tavendo.=
de" target=3D"_blank">tobias.oberstein@tavendo.de</a>&gt;</span> wrote:<br>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div class=3D"im">&gt;&gt;Well, I&#39;m sorry for the Java community not be=
ing able to fix this in 10+ years;)<br>
&gt;Yet, oddly, with web technologies, this hasn&#39;t been a problem since=
 our initial use of Oak in 1995 (yes, Jetty has existed since 1995)<br>
<br>
</div>Jetty being around since 1995 is obviously awesome!<br>
<br>
As a strange coincidence, zlib has also be around since 1 May 1995 (I haven=
&#39;t checked whether the respective options have been in the first versio=
n though).<br>
<div class=3D"im"><br>
&gt; The capabilities of one set of libraries (c &amp; python) should not b=
e forced on all environments as well.<br>
<br>
</div>Lets collect a list: a) stuff that exposes the complete zlib vs b) st=
uff that does not;)<br>
<br>
a) C, C++, Python, NodeJS, Perl, Ruby, PHP, Erlang, Haskell<br>
b) Java<br>
<br>
Caveat: I (obviously) have not used all of above myself. Just had a quick g=
lance at their docs.<br>
<br>
Pointers:<br>
<a href=3D"http://perldoc.perl.org/Compress/Zlib.html#Deflate-Interface" ta=
rget=3D"_blank">http://perldoc.perl.org/Compress/Zlib.html#Deflate-Interfac=
e</a><br>
<a href=3D"http://www.ruby-doc.org/stdlib-2.0.0/libdoc/zlib/rdoc/Zlib/Defla=
te.html" target=3D"_blank">http://www.ruby-doc.org/stdlib-2.0.0/libdoc/zlib=
/rdoc/Zlib/Deflate.html</a><br>
<a href=3D"http://www.php.net/manual/de/function.gzdeflate.php" target=3D"_=
blank">http://www.php.net/manual/de/function.gzdeflate.php</a><br>
<a href=3D"http://erlang.org/doc/man/zlib.html" target=3D"_blank">http://er=
lang.org/doc/man/zlib.html</a><br>
<a href=3D"http://hackage.haskell.org/package/zlib-0.5.4.1/docs/Codec-Compr=
ession-Zlib.html" target=3D"_blank">http://hackage.haskell.org/package/zlib=
-0.5.4.1/docs/Codec-Compression-Zlib.html</a><br>
<br>
I stop here;)<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
/Tobias<br>
</font></span></blockquote></div><br></div>

--047d7b62213a4f8a9b04e7edceaf--

From derhoermi@gmx.net  Fri Oct  4 10:57:40 2013
Return-Path: <derhoermi@gmx.net>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 399BD21F93DB for <hybi@ietfa.amsl.com>; Fri,  4 Oct 2013 10:57:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.866
X-Spam-Level: 
X-Spam-Status: No, score=-0.866 tagged_above=-999 required=5 tests=[AWL=-0.227, BAYES_00=-2.599, RCVD_IN_BL_SPAMCOP_NET=1.96]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 32y+kKrmGygj for <hybi@ietfa.amsl.com>; Fri,  4 Oct 2013 10:57:36 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) by ietfa.amsl.com (Postfix) with ESMTP id D359421F9D92 for <hybi@ietf.org>; Fri,  4 Oct 2013 10:57:32 -0700 (PDT)
Received: from netb.Speedport_W_700V ([91.35.57.193]) by mail.gmx.com (mrgmx102) with ESMTPA (Nemesis) id 0Lfppu-1WC0782BNC-00pKQJ for <hybi@ietf.org>; Fri, 04 Oct 2013 19:57:26 +0200
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Joakim Erdfelt <joakim@intalio.com>
Date: Fri, 04 Oct 2013 19:57:22 +0200
Message-ID: <6a0u49drlr419pg5goobuf7nos9a4nkpcf@hive.bjoern.hoehrmann.de>
References: <CAH9hSJbwd5qhMJw=3dwk3CDPua5ENRksd9=q2KDcyyma3uKzZg@mail.gmail.com> <CAG4zZZD8eq4w9kyQbX2AJcM1LA8=UyRO7txK7TvmYhSp=YU+9g@mail.gmail.com> <634914A010D0B943A035D226786325D4446790BF34@EXVMBX020-12.exch020.serverdata.net> <dmnt49hf1bbifiote81fumeamnk76vti1t@hive.bjoern.hoehrmann.de> <634914A010D0B943A035D226786325D4446790BF87@EXVMBX020-12.exch020.serverdata.net> <CAG4zZZDdcC5+cob715KE77uZiPYAo1Oz6M0StLA=vSp5iX_h7A@mail.gmail.com>
In-Reply-To: <CAG4zZZDdcC5+cob715KE77uZiPYAo1Oz6M0StLA=vSp5iX_h7A@mail.gmail.com>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K0:hbyId1qh/NxhqDy7/cm/omlMGyJjvuo8XlziGL3wuvSkVETZHPc KInXEwoCbxddoPGHuAKQzlq49sLa+WMIdtPVKXwNJFprBVGHEr8a5dq1HdeQ6auPvPZHWG1 B6qm08iAY73iSCBfm0NpoFL5huQPUswzmEXkh5I1JbOhSX68zx1/N3gDkjZnhA9YvJuYhoI fi/LZgoLMmSVrOSy1RISA==
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] Restarting IESG review on permessage-deflate
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Fri, 04 Oct 2013 17:57:41 -0000

* Joakim Erdfelt wrote:
>If the spec is trying to say something like this ...
>
>   Hi, I'm the client, I want to talk to you using 1 set of configurations,
>and I want you to talk back to me on a different set of configurations.
>
>... then this is not made clear in
>http://tools.ietf.org/html/draft-ietf-hybi-permessage-compression-12
>
>And If this is the intention, make it clear, in the spec, that the whole
>point of the prefixes is to have different configurations for incoming vs
>outgoing frames. (and explain the pros and cons of this)

That seems to be in order.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 

From derhoermi@gmx.net  Fri Oct  4 11:08:48 2013
Return-Path: <derhoermi@gmx.net>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85E6C21F9DAF for <hybi@ietfa.amsl.com>; Fri,  4 Oct 2013 11:08:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.809
X-Spam-Level: 
X-Spam-Status: No, score=-0.809 tagged_above=-999 required=5 tests=[AWL=-0.170, BAYES_00=-2.599, RCVD_IN_BL_SPAMCOP_NET=1.96]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gVFkqediCrLq for <hybi@ietfa.amsl.com>; Fri,  4 Oct 2013 11:08:44 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) by ietfa.amsl.com (Postfix) with ESMTP id 4599321F9DB4 for <hybi@ietf.org>; Fri,  4 Oct 2013 11:08:43 -0700 (PDT)
Received: from netb.Speedport_W_700V ([91.35.57.193]) by mail.gmx.com (mrgmx103) with ESMTPA (Nemesis) id 0Lq9Ma-1W5uTQ0heq-00drxK for <hybi@ietf.org>; Fri, 04 Oct 2013 20:08:41 +0200
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Tobias Oberstein <tobias.oberstein@tavendo.de>
Date: Fri, 04 Oct 2013 20:08:43 +0200
Message-ID: <qb0u491vbecgjihjhkd6d75jo0uoka5al2@hive.bjoern.hoehrmann.de>
References: <CAH9hSJbwd5qhMJw=3dwk3CDPua5ENRksd9=q2KDcyyma3uKzZg@mail.gmail.com> <CAG4zZZD8eq4w9kyQbX2AJcM1LA8=UyRO7txK7TvmYhSp=YU+9g@mail.gmail.com> <634914A010D0B943A035D226786325D4446790BF34@EXVMBX020-12.exch020.serverdata.net> <CAG4zZZDNRZ_kaXBKhx5VkKjpj+Luo53Y7ue0eaGHH_ghoBrdkQ@mail.gmail.com> <634914A010D0B943A035D226786325D4446790BFFC@EXVMBX020-12.exch020.serverdata.net>
In-Reply-To: <634914A010D0B943A035D226786325D4446790BFFC@EXVMBX020-12.exch020.serverdata.net>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K0:TLbeftJWqKsXtImSFaY//owbY0oQ3ZzxT+maA9Mzizlid8fV7Zg Fnx99BL4cTeuXr6mpnu7Gwzmue7j1kboQaTfRogsgNoWjLgLyJ64x2/xeHP/tVXUDCwpi11 E3Ba7h50r65NHUyxAajXhwS9+z8WlUn8O69QDUXXiYLNbZIimzhLQt6ULpyP+Yh3KgL7K0b qOU3UoB6TVmUTY5pFPSPw==
Cc: "hybi@ietf.org" <hybi@ietf.org>, Gabriel Montenegro <Gabriel.Montenegro@microsoft.com>
Subject: Re: [hybi] Restarting IESG review on permessage-deflate
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Fri, 04 Oct 2013 18:08:48 -0000

* Tobias Oberstein wrote:
>Lets collect a list: a) stuff that exposes the complete zlib vs b) stuff that does not;)
>
>a) C, C++, Python, NodeJS, Perl, Ruby, PHP, Erlang, Haskell
>b) Java

If you have an environment to develop application in C then it should be
relatively easy to compile the zlib library and link it to your program,
but the C language and its standard library and the typical extensions
to it do not usually include zlib by themself; and if you write in Java,
there are comparable libraries available where the same holds true, but
the out-of-the-box experience is different. So this does not seem to be
a fair comparison.

A better comparison would be among independent DEFLATE implementations;
that way we could at least tell how zlib-specific the relevant features
are, and if they are very zlib-specific and not commonly implemented in
independent implementations, they might make bad mandatory features. My
http://bjoern.hoehrmann.de/pngwolf/ for instance uses the DEFLATE imple-
mentation in Igor Pavlov's 7-Zip library, which I believe is the best-
compressing free software implementation; that would be a good candiate,
among others.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 

From tobias.oberstein@tavendo.de  Fri Oct  4 11:34:52 2013
Return-Path: <tobias.oberstein@tavendo.de>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02A2B21F9D46 for <hybi@ietfa.amsl.com>; Fri,  4 Oct 2013 11:34:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LJWo11vjngGW for <hybi@ietfa.amsl.com>; Fri,  4 Oct 2013 11:34:48 -0700 (PDT)
Received: from EXHUB020-1.exch020.serverdata.net (exhub020-1.exch020.serverdata.net [206.225.164.28]) by ietfa.amsl.com (Postfix) with ESMTP id DFDC121F9C37 for <hybi@ietf.org>; Fri,  4 Oct 2013 11:34:47 -0700 (PDT)
Received: from EXVMBX020-12.exch020.serverdata.net ([169.254.3.6]) by EXHUB020-1.exch020.serverdata.net ([206.225.164.28]) with mapi; Fri, 4 Oct 2013 11:34:46 -0700
From: Tobias Oberstein <tobias.oberstein@tavendo.de>
To: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Fri, 4 Oct 2013 11:34:44 -0700
Thread-Topic: [hybi] Restarting IESG review on permessage-deflate
Thread-Index: Ac7BLMNXNqQivQfuT2axjmd1+FX0PwAAi9Ug
Message-ID: <634914A010D0B943A035D226786325D4446790C068@EXVMBX020-12.exch020.serverdata.net>
References: <CAH9hSJbwd5qhMJw=3dwk3CDPua5ENRksd9=q2KDcyyma3uKzZg@mail.gmail.com> <CAG4zZZD8eq4w9kyQbX2AJcM1LA8=UyRO7txK7TvmYhSp=YU+9g@mail.gmail.com> <634914A010D0B943A035D226786325D4446790BF34@EXVMBX020-12.exch020.serverdata.net> <CAG4zZZDNRZ_kaXBKhx5VkKjpj+Luo53Y7ue0eaGHH_ghoBrdkQ@mail.gmail.com> <634914A010D0B943A035D226786325D4446790BFFC@EXVMBX020-12.exch020.serverdata.net> <qb0u491vbecgjihjhkd6d75jo0uoka5al2@hive.bjoern.hoehrmann.de>
In-Reply-To: <qb0u491vbecgjihjhkd6d75jo0uoka5al2@hive.bjoern.hoehrmann.de>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "hybi@ietf.org" <hybi@ietf.org>, Gabriel Montenegro <Gabriel.Montenegro@microsoft.com>
Subject: Re: [hybi] Restarting IESG review on permessage-deflate
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Fri, 04 Oct 2013 18:34:52 -0000

>>Lets collect a list: a) stuff that exposes the complete zlib vs b)=20
>>stuff that does not;)
>>
>>a) C, C++, Python, NodeJS, Perl, Ruby, PHP, Erlang, Haskell
>>b) Java

>If you have an environment to develop application in C then it should be r=
elatively easy to compile the zlib library and link it to your program, but=
 the C language and its standard library and the typical extensions to it d=
o not usually include zlib by themself; and if you >write in Java, there ar=
e comparable libraries available where the same holds true, but the out-of-=
the-box experience is different. So this does not seem to be a fair compari=
son.

Of course making up such lists is questionable.

My main point is: should IETF protocols be designed against a least-common =
denominator of todays existing language run-times / implementations / envir=
onments? I don't know if there is a general IETF policy with this. My view:=
 it should not.

>A better comparison would be among independent DEFLATE implementations; th=
at way we could at least tell how zlib-specific the relevant features are, =
and if they are very zlib-specific and not commonly implemented in independ=
ent implementations, they might >make bad mandatory features. My http://bjo=
ern.hoehrmann.de/pngwolf/ for instance uses the DEFLATE imple- mentation in=
 Igor Pavlov's 7-Zip library, which I believe is the best- compressing free=
 software implementation; that would be a good candiate, among >others.

Good point. It's one thing which run-time does expose which feature of one =
and the same Deflate implementation ("zlib"), and another to compare featur=
es of independent Deflate implementations.

Here is another point:

The current spec only refers to the original LZ77 paper under normative-ref=
erences:

http://tools.ietf.org/html/draft-ietf-hybi-permessage-compression-12#page-2=
7

The Deflate RFC

http://tools.ietf.org/html/rfc1951

is only listed under informational.

This is strange, since the "permessage-deflate" extension is not only LZ77,=
 but really Deflate (=3D LZ77 + Huffman Coding + Window Size .. see below).

And the RFC1951 mentions:

" 3.3. Compliance

      A compressor may limit further the ranges of values specified in
      the previous section and still be compliant; for example, it may
      limit the range of backward pointers to some value smaller than
      32K.  Similarly, a compressor may limit the size of blocks so that
      a compressible block fits in memory.
"

Which I read as refering to "window size". But the wording neither has SHOU=
LD nor MUST in it.

Mmh.

/Tobias


From tyoshino@google.com  Fri Oct  4 12:03:45 2013
Return-Path: <tyoshino@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0522121F9E5A for <hybi@ietfa.amsl.com>; Fri,  4 Oct 2013 12:03:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GqzV+G7mBX2e for <hybi@ietfa.amsl.com>; Fri,  4 Oct 2013 12:03:42 -0700 (PDT)
Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) by ietfa.amsl.com (Postfix) with ESMTP id 0199D21F9E3A for <hybi@ietf.org>; Fri,  4 Oct 2013 12:03:26 -0700 (PDT)
Received: by mail-wi0-f169.google.com with SMTP id hj3so2798577wib.2 for <hybi@ietf.org>; Fri, 04 Oct 2013 12:03:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=2C6ovMdWZTvpozh0sC1Sx2Zqi3t0XnRmXtNhOTWKwFs=; b=QqXkzc+XQQEiubq2L3OdpEQsO7XdRYXVOIFu0+AxKbLY3gNv9nMoIS84xqz/7kV27t oJP5TesHk3YtL+MT5EEmElJdhiF1ao1U3YD1xdHVvpEtGB8K6IjR488YRDTs0Lv3xhed ytul61N0Cx8hp4Fh+BsPZOWb2ZawXOt+sURY7B9ZzCoAZjX+LPQs/KR1U93fDrEA6GI4 xH1+V7hJb4EOVTIiWnj5o7wInTwNJmVR2XQ1pBvEeVolcbQa41l+9bn7q+ChIMvawrWv DU3B9D/DiW2Vl694+Ltk2NG/RLvbIrq1s9WPamrk5bHzfwskghuSjRq3PcfuE5b3b1Z5 DVOg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=2C6ovMdWZTvpozh0sC1Sx2Zqi3t0XnRmXtNhOTWKwFs=; b=eqZdRGwScEmnjeho4X2koy5ubdMU5t65V7ItbPF1oXrdtwDlE7eaV8dkUN8j8xCsDi BiaY0MWAuPGG6fzmplAusbvGTDdMYXc+Xq8TwluCeX3sTAn3Op0RFWaNrqjTuqL93FJ6 1X+60KK7n21nRt0AZqCqpjQv8fSMyCVwPdW9Gt2OxZr/raV3wvFDmMiceV6/o6/rPSxv C8eauLmPD0HJ4BfMEWwy3zsspFcO9kaBi68vYJlYxjUAeJJgR4F37+Css9To0RhXsjzD NSaBlCB9b+ErTSoF5Tq96XXQudVSPL90o6Y2jMwvexuPWCNe3SrtIl92XMaRkhvEt0vr vuVw==
X-Gm-Message-State: ALoCoQnQ3Zuv3Ppz+YWkpuFJsshDlmoWwgdS620KI3lJxk2pkJz/xfSFBVSGVtsHDKi0826afMc+Oqf84Ejh0iuwEtwcw8kWy7QtKWMu8Y1OWU9X24Ez3ayZxjO/rrNE7V1hQQSXyqYfKMx2qRkG5jyCkG35I641o6eCY4c75qAzk4EwhAZI/APhDxkGzE/f38GompotODBS
X-Received: by 10.180.185.101 with SMTP id fb5mr8651909wic.11.1380913405020; Fri, 04 Oct 2013 12:03:25 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.15.133 with HTTP; Fri, 4 Oct 2013 12:03:03 -0700 (PDT)
In-Reply-To: <CAG4zZZDdcC5+cob715KE77uZiPYAo1Oz6M0StLA=vSp5iX_h7A@mail.gmail.com>
References: <CAH9hSJbwd5qhMJw=3dwk3CDPua5ENRksd9=q2KDcyyma3uKzZg@mail.gmail.com> <CAG4zZZD8eq4w9kyQbX2AJcM1LA8=UyRO7txK7TvmYhSp=YU+9g@mail.gmail.com> <634914A010D0B943A035D226786325D4446790BF34@EXVMBX020-12.exch020.serverdata.net> <dmnt49hf1bbifiote81fumeamnk76vti1t@hive.bjoern.hoehrmann.de> <634914A010D0B943A035D226786325D4446790BF87@EXVMBX020-12.exch020.serverdata.net> <CAG4zZZDdcC5+cob715KE77uZiPYAo1Oz6M0StLA=vSp5iX_h7A@mail.gmail.com>
From: Takeshi Yoshino <tyoshino@google.com>
Date: Sat, 5 Oct 2013 04:03:03 +0900
Message-ID: <CAH9hSJZS=aQwsc3WqFROstQomAzNL1OemPSK2_eHkPOHMDKzAg@mail.gmail.com>
To: Joakim Erdfelt <joakim@intalio.com>
Content-Type: multipart/alternative; boundary=001a11c2448ef8f29504e7eef4c6
Cc: Bjoern Hoehrmann <derhoermi@gmx.net>, "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] Restarting IESG review on permessage-deflate
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Fri, 04 Oct 2013 19:03:45 -0000

--001a11c2448ef8f29504e7eef4c6
Content-Type: text/plain; charset=ISO-8859-1

Joakim,

I put s2c and c2s prefixes in order to allow response to describe settings
of both direction.

When to allow a client to include multiple permessage-deflate offers, we
need to have some method to have the server to tell the client which offer
has been accepted. I investigated several methods such as adding IDs to
each offer, and then concluded that having the server to send all
parameters (both client -> server and server -> client) is simple and ok.
But to use this method, we need to distinguish parameters for up and down.
So, I introduced these prefixes.

--001a11c2448ef8f29504e7eef4c6
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Joakim,<br><div class=3D"gmail_extra"><br></div><div class=
=3D"gmail_extra">I put s2c and c2s prefixes in order to allow response to d=
escribe settings of both direction.</div><div class=3D"gmail_extra"><br></d=
iv><div class=3D"gmail_extra">

When to allow a client to include multiple permessage-deflate offers, we ne=
ed to have some method to have the server to tell the client which offer ha=
s been accepted. I investigated several methods such as adding IDs to each =
offer, and then concluded that having the server to send all parameters (bo=
th client -&gt; server and server -&gt; client) is simple and ok. But to us=
e this method, we need to distinguish parameters for up and down. So, I int=
roduced these prefixes.</div>

<div class=3D"gmail_extra"><br></div></div>

--001a11c2448ef8f29504e7eef4c6--

From tyoshino@google.com  Fri Oct  4 12:17:50 2013
Return-Path: <tyoshino@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 752D521F9B86 for <hybi@ietfa.amsl.com>; Fri,  4 Oct 2013 12:17:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9zMyvMfPqKhA for <hybi@ietfa.amsl.com>; Fri,  4 Oct 2013 12:17:49 -0700 (PDT)
Received: from mail-wi0-x233.google.com (mail-wi0-x233.google.com [IPv6:2a00:1450:400c:c05::233]) by ietfa.amsl.com (Postfix) with ESMTP id 6AAD321F9A97 for <hybi@ietf.org>; Fri,  4 Oct 2013 12:17:48 -0700 (PDT)
Received: by mail-wi0-f179.google.com with SMTP id hm2so2188513wib.6 for <hybi@ietf.org>; Fri, 04 Oct 2013 12:17:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=4m5Fsj3iI9DOGv8frmuONWU2poNzU9J7wu7serlzgvE=; b=Wr8igcMADLKuD4G93/zAFYvFLDZWbxbU73dEzse+QJTnFc3JPQTYn0YB7G7xAPi6bX kS/BSI35CNzrmLCd5I75aTIhnTUF/0KkIUIr9CJ/aoPfX+ab2PCosXEAa6P0rLZOLnI0 6JpR/y8Lt3onhTfTyAfMlFo7Kyv757l1rLAgATWtXUJ4ynEBnmi/qKdwAimcUjwwFNmU eo8G17HUMbOYThUxB1f2XUPLe5OCE4+uutQuPC3mhD3Ccjyeq+4m6ljqzY1hbwGn/jEW yb9TEGFYFF8QM5PZIxI8N1PlQgn7NVvUnfv4Cm23ItKYpH9RPGp/qAs7UgOJqrX/ekSv DN0A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=4m5Fsj3iI9DOGv8frmuONWU2poNzU9J7wu7serlzgvE=; b=jUybz2twIYZZQwkjsxcemfzajyCAGOQqVsRlePtttTU78ALMllxUTH6tAmhufACSbw PNPU2dAusEYmGmMXamIPoN5UiBGG+TWVlTGPOASnOKV9tt1UpgC/6HGnzM0qRzaz7M+C A8DWTJmFK21FqEjteoqfwuA3hJBsgY2YkYZGpG0g8431dZN2/4U6l6uPXzfI/Jw5M2FH WMaKJr/gQTeEmOBmnMTpyatFrVGFMFHkvjKFVJAaQfb1uK7ttRNXhy9/++WYJdE2p6Lh 1Bx/BGFxZi2OmzNAypNHlJZ2UJbPWFzAU2KljZdqHN7wDoNeDVGCnhjxYRHSHBkqPQoi F9zA==
X-Gm-Message-State: ALoCoQli3F7wkVgbDILe3UXkDSt9DUVDlZJHmvdvFyGMR4om7mTA0z/t3qJ2STcEt8AgtpN1ylDoXdwSPk2fEE9OhmeDF5wzgUKpmm/XlOWFd+zTkn1x11L4SmKsrHwS8PWMdNDCm8HdsDmv22vuJj6Vgabi0Fk/5RiN/YmMsApBKvr98KVEwlQRL/dAC+kHB2xfKFzY0X3e
X-Received: by 10.194.10.193 with SMTP id k1mr3329083wjb.50.1380914267955; Fri, 04 Oct 2013 12:17:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.15.133 with HTTP; Fri, 4 Oct 2013 12:17:26 -0700 (PDT)
In-Reply-To: <CAG4zZZD8eq4w9kyQbX2AJcM1LA8=UyRO7txK7TvmYhSp=YU+9g@mail.gmail.com>
References: <CAH9hSJbwd5qhMJw=3dwk3CDPua5ENRksd9=q2KDcyyma3uKzZg@mail.gmail.com> <CAG4zZZD8eq4w9kyQbX2AJcM1LA8=UyRO7txK7TvmYhSp=YU+9g@mail.gmail.com>
From: Takeshi Yoshino <tyoshino@google.com>
Date: Sat, 5 Oct 2013 04:17:26 +0900
Message-ID: <CAH9hSJY84nbzv62-b3v-rnJf58qc4MWi8uNJSWFGw24kWYyrSw@mail.gmail.com>
To: Joakim Erdfelt <joakim@intalio.com>
Content-Type: multipart/alternative; boundary=047d7b5d4f78684ba204e7ef2845
Cc: "hybi@ietf.org" <hybi@ietf.org>, Gabriel Montenegro <Gabriel.Montenegro@microsoft.com>
Subject: Re: [hybi] Restarting IESG review on permessage-deflate
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Fri, 04 Oct 2013 19:17:50 -0000

--047d7b5d4f78684ba204e7ef2845
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Oct 4, 2013 at 11:24 PM, Joakim Erdfelt <joakim@intalio.com> wrote:

> There is also Eclipse Jetty 9.1 (currently in RC releases) support (server
> and client)
>
> We cannot support some of the spec, as written.
> Our experiences implementing it, and using chromium + pywebsocket for
> testing both the server or client implementation.
>
> The following configuration parameters are not supported, nor can/will be.
>
> s2c_no_context_takeover
> c2s_no_context_takeover
> s2c_max_window_bits
> c2s_max_window_bits
>
>
Sorry, why? s2c_no_context_takeover requests the server to reset context.
The server just need to throw away current deflater, create a new one and
use it.

If the client didn't send s2c_no_context_takeover, you can still do the
same. You don't have to carry over compression context.

The problem is that your server cannot decompress incoming data if the
client carries over compression context. So, you can just reply with
c2s_no_context_takeover. In
http://tools.ietf.org/html/draft-ietf-hybi-permessage-compression-12#section-8.1.1.2,
a client is required to implement c2s_no_context_takeover. I made this
mandatory since it's doable. So, you don't have to worry about clients
coming without c2s_no_context_takeover capability.


> This level of control of the deflate algorithm is just not possible in
> Java, sorry.
>
>
Again, please explain why you can't support no_context_takeover family
parameter.

--047d7b5d4f78684ba204e7ef2845
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra">On Fri, Oct 4, 2013 at 11:24 PM=
, Joakim Erdfelt <span dir=3D"ltr">&lt;<a href=3D"mailto:joakim@intalio.com=
" target=3D"_blank">joakim@intalio.com</a>&gt;</span> wrote:<br><div class=
=3D"gmail_quote">

<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra">There is also =
Eclipse Jetty 9.1 (currently in RC releases) support (server and client)<di=
v>

<br></div><div>We cannot support some of the spec, as written.</div><div>Ou=
r experiences implementing it, and using chromium + pywebsocket for testing=
 both the server or client implementation.</div>
<div><br></div><div>The following configuration parameters are not supporte=
d, nor can/will be.</div><div><br></div><div>s2c_no_context_takeover</div><=
div>c2s_no_context_takeover</div><div>s2c_max_window_bits</div><div>c2s_max=
_window_bits</div>


<div><br></div></div></div></blockquote><div><br></div><div>Sorry, why? s2c=
_no_context_takeover requests the server to reset context. The server just =
need to throw away current deflater, create a new one and use it.</div>

<div><br></div><div>If the client didn&#39;t send s2c_no_context_takeover, =
you can still do the same. You don&#39;t have to carry over compression con=
text.</div><div><br></div><div>The problem is that your server cannot decom=
press incoming data if the client carries over compression context. So, you=
 can just reply with c2s_no_context_takeover. In=A0<a href=3D"http://tools.=
ietf.org/html/draft-ietf-hybi-permessage-compression-12#section-8.1.1.2">ht=
tp://tools.ietf.org/html/draft-ietf-hybi-permessage-compression-12#section-=
8.1.1.2</a>, a client is required to implement c2s_no_context_takeover. I m=
ade this mandatory since it&#39;s doable. So, you don&#39;t have to worry a=
bout clients coming without c2s_no_context_takeover capability.</div>

<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left=
-style:solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra">=
<div>
</div>
<div>This level of control of the deflate algorithm is just not possible in=
 Java, sorry.</div><div><br></div></div></div></blockquote><div><br></div><=
div>Again, please explain why you can&#39;t support no_context_takeover fam=
ily parameter.</div>

<div>=A0</div></div></div></div>

--047d7b5d4f78684ba204e7ef2845--

From webmaster@zaphoyd.com  Fri Oct  4 12:57:01 2013
Return-Path: <webmaster@zaphoyd.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9045E21F8E21 for <hybi@ietfa.amsl.com>; Fri,  4 Oct 2013 12:57:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m6e1ExkxD4LY for <hybi@ietfa.amsl.com>; Fri,  4 Oct 2013 12:56:54 -0700 (PDT)
Received: from sh78.surpasshosting.com (sh78.surpasshosting.com [72.29.64.142]) by ietfa.amsl.com (Postfix) with ESMTP id 2A6A621F9D22 for <hybi@ietf.org>; Fri,  4 Oct 2013 12:56:41 -0700 (PDT)
Received: from ranna.uchicago.edu ([128.135.45.206]:63249) by sh78.surpasshosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80.1) (envelope-from <webmaster@zaphoyd.com>) id 1VSBUK-00066E-Fg for hybi@ietf.org; Fri, 04 Oct 2013 15:56:36 -0400
From: Peter Thorson <webmaster@zaphoyd.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_7AE5B827-4CA7-46A5-8C8E-C734E6EDA6CC"
Message-Id: <F18056D3-5BE0-4064-96FF-F15C709DB51C@zaphoyd.com>
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Date: Fri, 4 Oct 2013 14:56:35 -0500
References: <CAH9hSJbwd5qhMJw=3dwk3CDPua5ENRksd9=q2KDcyyma3uKzZg@mail.gmail.com> <CAG4zZZD8eq4w9kyQbX2AJcM1LA8=UyRO7txK7TvmYhSp=YU+9g@mail.gmail.com> <634914A010D0B943A035D226786325D4446790BF34@EXVMBX020-12.exch020.serverdata.net> <dmnt49hf1bbifiote81fumeamnk76vti1t@hive.bjoern.hoehrmann.de> <634914A010D0B943A035D226786325D4446790BF87@EXVMBX020-12.exch020.serverdata.net> <CAG4zZZDdcC5+cob715KE77uZiPYAo1Oz6M0StLA=vSp5iX_h7A@mail.gmail.com>
To: "hybi@ietf.org" <hybi@ietf.org>
In-Reply-To: <CAG4zZZDdcC5+cob715KE77uZiPYAo1Oz6M0StLA=vSp5iX_h7A@mail.gmail.com>
X-Mailer: Apple Mail (2.1510)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - sh78.surpasshosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - zaphoyd.com
X-Get-Message-Sender-Via: sh78.surpasshosting.com: authenticated_id: webmaster@zaphoyd.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Subject: Re: [hybi] Restarting IESG review on permessage-deflate
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Fri, 04 Oct 2013 19:57:01 -0000

--Apple-Mail=_7AE5B827-4CA7-46A5-8C8E-C734E6EDA6CC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On Oct 4, 2013, at 11:25 , Joakim Erdfelt <joakim@intalio.com> wrote:

> On Fri, Oct 4, 2013 at 8:57 AM, Tobias Oberstein =
<tobias.oberstein@tavendo.de> wrote:
> The spec use of these prefixes is unclear at best, and downright =
misleading at worst.
> If the spec is trying to say something like this ...
>=20
>    Hi, I'm the client, I want to talk to you using 1 set of =
configurations, and I want you to talk back to me on a different set of =
configurations.
>=20
> ... then this is not made clear in =
http://tools.ietf.org/html/draft-ietf-hybi-permessage-compression-12=20
>=20
> And If this is the intention, make it clear, in the spec, that the =
whole point of the prefixes is to have different configurations for =
incoming vs outgoing frames. (and explain the pros and cons of this)

Based on my reading of the draft 12 spec sections for the individual =
method parameters (sec 8.1.1.1-4), it seemed clear to me that the =
intention is specifically to allow asymmetric configuration.

This is useful because the nature of the deflate algorithm and the =
capabilities of endpoints are likely to be asymmetric. Deflate typically =
takes significantly more memory than inflate. Desktop browsers are =
likely to be less memory sensitive than a server processing tens of =
thousands of connections each needing their own sliding window or a =
server running on an embedded device with limited memory. In these cases =
the resource rich endpoint may want to use its extra memory for a better =
outgoing compression ratio while allowing the resource poor endpoint to =
compress less thoroughly to conserve memory.

While I think the present descriptions of each individual parameter =
convey this information, I wouldn't be opposed to clarifying the =
overview part of section 8 to review the asymmetric nature of the =
parameters. A proposal:

=3D=3D=3D=3D=3D=3D=3D Existing =3D=3D=3D=3D=3D=3D=3D

For an offer for this extension, the following 4 extension parameters
are defined.  If needed to distinguish from ones for a response,
these parameters are called with a prefix "client-to-server".

- "s2c_no_context_takeover"
- "c2s_no_context_takeover"
- "s2c_max_window_bits"
- "c2s_max_window_bits"

For a response for this extension, the following 4 extension
parameters are defined.  If needed to distinguish from ones for an
offer, these parameters are called with a prefix "server-to-client".

- "s2c_no_context_takeover"
- "c2s_no_context_takeover"
- "s2c_max_window_bits"
- "c2s_max_window_bits"

=3D=3D=3D=3D=3D=3D=3D Possible clarification =3D=3D=3D=3D=3D=3D=3D

Four extension parameters are defined for permessage-deflate to help=20
endpoints manage per-connection resource usage.

- "s2c_no_context_takeover"
- "c2s_no_context_takeover"
- "s2c_max_window_bits"
- "c2s_max_window_bits"

These represent two methods of constraining memory usage that may be=20
applied independently to either direction of WebSocket traffic. The =
prefixes=20
c2s and s2c are used to indicate the client-to-server channel and the=20
server-to-client channel respectively. All four parameters are defined =
for both=20
a client's offer and a server's response.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

> - Joakim
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi


--Apple-Mail=_7AE5B827-4CA7-46A5-8C8E-C734E6EDA6CC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Diso-8859-1"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Oct 4, 2013, at 11:25 , Joakim Erdfelt &lt;<a =
href=3D"mailto:joakim@intalio.com">joakim@intalio.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div dir=3D"ltr">On Fri, Oct 4, 2013 at 8:57 AM, Tobias =
Oberstein <span dir=3D"ltr">&lt;<a =
href=3D"mailto:tobias.oberstein@tavendo.de" =
target=3D"_blank">tobias.oberstein@tavendo.de</a>&gt;</span> =
wrote:<br><div class=3D"gmail_extra">
<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" =
style=3D"margin:0px 0px 0px =
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left=
-style:solid;padding-left:1ex"><div class=3D"im">The spec use of these =
prefixes is unclear at best, and downright misleading at =
worst.</div></blockquote>
<div>If the spec is trying to say something like this =
...</div><div><br></div><div>&nbsp; &nbsp;Hi, I'm the client, I want to =
talk to you using 1 set of configurations, and I want you to talk back =
to me on a different set of configurations.</div>
<div><br></div><div>... then this is not made clear in&nbsp;<a =
href=3D"http://tools.ietf.org/html/draft-ietf-hybi-permessage-compression-=
12">http://tools.ietf.org/html/draft-ietf-hybi-permessage-compression-12</=
a>&nbsp;</div><div><br>
</div><div>And If this is the intention, make it clear, in the spec, =
that the whole point of the prefixes is to have different configurations =
for incoming vs outgoing frames. (and explain the pros and cons of =
this)</div></div></div></div></blockquote><div><br></div><div>Based on =
my reading of the draft 12 spec sections for the individual method =
parameters (sec 8.1.1.1-4), it seemed clear to me that the intention is =
specifically to allow asymmetric =
configuration.</div><div><br></div><div>This is useful because the =
nature of the deflate algorithm and the capabilities of endpoints are =
likely to be asymmetric.&nbsp;Deflate typically takes significantly more =
memory than inflate.&nbsp;Desktop browsers are likely to be less memory =
sensitive than a server processing tens of thousands of connections each =
needing their own sliding window or a server running on an embedded =
device with limited memory. In these cases the resource rich endpoint =
may want to use its extra memory for a better outgoing compression ratio =
while allowing the resource poor endpoint to compress less thoroughly to =
conserve memory.</div><div><br></div><div>While I think the present =
descriptions of each individual parameter convey this information, I =
wouldn't be opposed to clarifying the overview part of section 8 to =
review the asymmetric nature of the parameters. A =
proposal:</div><div><br></div><div>=3D=3D=3D=3D=3D=3D=3D Existing =
=3D=3D=3D=3D=3D=3D=3D</div><div><div><br></div><div>For an offer for =
this extension, the following 4 extension parameters</div><div>are =
defined. &nbsp;If needed to distinguish from ones for a =
response,</div><div>these parameters are called with a prefix =
"client-to-server".</div><div><br></div><div><div>-&nbsp;"s2c_no_context_t=
akeover"</div><div>-&nbsp;"c2s_no_context_takeover"</div><div>-&nbsp;"s2c_=
max_window_bits"</div><div>-&nbsp;"c2s_max_window_bits"</div></div><div><b=
r></div><div>For a response for this extension, the following 4 =
extension</div><div>parameters are defined. &nbsp;If needed to =
distinguish from ones for an</div><div>offer, these parameters are =
called with a prefix =
"server-to-client".</div><div><br></div><div><div>-&nbsp;"s2c_no_context_t=
akeover"</div><div>-&nbsp;"c2s_no_context_takeover"</div><div>-&nbsp;"s2c_=
max_window_bits"</div><div>-&nbsp;"c2s_max_window_bits"</div></div></div><=
div><br></div><div>=3D=3D=3D=3D=3D=3D=3D&nbsp;Possible =
clarification&nbsp;=3D=3D=3D=3D=3D=3D=3D</div><div><br></div><div>Four =
extension parameters are defined for permessage-deflate to =
help&nbsp;</div><div>endpoints manage per-connection resource =
usage.</div><div><br></div><div>-&nbsp;"s2c_no_context_takeover"</div><div=
>-&nbsp;"c2s_no_context_takeover"</div><div>-&nbsp;"s2c_max_window_bits"</=
div><div>-&nbsp;"c2s_max_window_bits"</div><div><br></div><div>These =
represent two methods of constraining memory usage that may =
be&nbsp;</div><div>applied independently to either direction of =
WebSocket traffic. The&nbsp;prefixes&nbsp;</div><div>c2s and s2c are =
used&nbsp;to indicate the client-to-server channel and =
the&nbsp;</div><div>server-to-client channel respectively. All four =
parameters are defined for both&nbsp;</div><div>a client's offer and a =
server's =
response.</div><div><br></div><div>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D</div><div><br></div><blockquote =
type=3D"cite"><div dir=3D"ltr"><div class=3D"gmail_extra"><div =
class=3D"gmail_quote"><div>- Joakim</div></div></div></div>
_______________________________________________<br>hybi mailing =
list<br><a =
href=3D"mailto:hybi@ietf.org">hybi@ietf.org</a><br>https://www.ietf.org/ma=
ilman/listinfo/hybi<br></blockquote></div><br></body></html>=

--Apple-Mail=_7AE5B827-4CA7-46A5-8C8E-C734E6EDA6CC--

From tyoshino@google.com  Fri Oct  4 18:19:33 2013
Return-Path: <tyoshino@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8365621F9CC0 for <hybi@ietfa.amsl.com>; Fri,  4 Oct 2013 18:19:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n9naaFjLModM for <hybi@ietfa.amsl.com>; Fri,  4 Oct 2013 18:19:33 -0700 (PDT)
Received: from mail-wi0-x22d.google.com (mail-wi0-x22d.google.com [IPv6:2a00:1450:400c:c05::22d]) by ietfa.amsl.com (Postfix) with ESMTP id A053521F9CAF for <hybi@ietf.org>; Fri,  4 Oct 2013 18:19:32 -0700 (PDT)
Received: by mail-wi0-f173.google.com with SMTP id hq15so2459601wib.12 for <hybi@ietf.org>; Fri, 04 Oct 2013 18:19:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=4vxfq3cBB2UaKWXpJfYKUiHOgNf0Y4+eabY9fkxe+SU=; b=Ux5GYecaOVcYfn8v14o9JqEbiXDicv76GUUpK3gwBPQJMM1kbWYm07e+33pY0gf+RA d/16iCZuMFGxC4ui1vAbaE1gr2RkfwPKu9oIXKGwJSDxOmek8djnACpgB3zgfaOaWf2S XuLpptbhZ7kn2W9PrRJ00zqf8p+ReXrsG6eaSKErnghmxR3pkQtVif3gr5q8u2j8OhR+ qoSRunuLHiyuCPtTHG2C6NpUFP/FYxbETvhI/JpUN5yawEsmSsz6VuYluLtMDr+PyttR e8OIVp328aZUHhB1Zdasmt6PQgPyS/Ah1UcNNbhiuOEYe6jH4WAdO2aj1/Oep3tryFOc 7aEw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=4vxfq3cBB2UaKWXpJfYKUiHOgNf0Y4+eabY9fkxe+SU=; b=PIAnzYWAmNGsq/pffi3u2BOuk+Qw2Qp2ZCSzp/1q8rUc8AhAepveoTankSNT0HUSYK 4W4UDPPfv6F+TjaQXG83dRR0fVqy9Ckp/74qq3RErZ+Oq45NRfKh+z5qnIYSkTo01Ttf 6V+Bi+Ia5DiH4pKnbJ1G33Cy1q4OMMci9nzwUQ6rZiQezhCAFqa7f5LJY4V4Xif6YZVW +PNRvVI+0CZR6Gt0qohs6HTHAygsmHpGdphSHeoN6vRnrJ8JZBOvV1Ek5WfOUlhsQ6DG exHyBnvtvPhsuo+uBGSzPZY/ezPpbhx6vWlRctWGpfG1woa7MkskA93YJsdbT05XlDc3 0nKA==
X-Gm-Message-State: ALoCoQkiDUvJ9CjYDF/QQud5FFLowlx/RgudQLkbThswuylVhHnxG791tRzMbjAf9h0fPquk5B8wYYLJXEZELy4Goxey3gV7u5QWgU043/mezcOJusUMdbuTxSWIu22Icg+3xsQ2xAEh/kDtIYw3VgEJLF0SV1diGe+w4724thjt84OorzB7JkEFU46HnU/SKbZGgs7DVyzH
X-Received: by 10.180.99.99 with SMTP id ep3mr9736553wib.11.1380935971440; Fri, 04 Oct 2013 18:19:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.15.133 with HTTP; Fri, 4 Oct 2013 18:19:11 -0700 (PDT)
In-Reply-To: <CAH9hSJY84nbzv62-b3v-rnJf58qc4MWi8uNJSWFGw24kWYyrSw@mail.gmail.com>
References: <CAH9hSJbwd5qhMJw=3dwk3CDPua5ENRksd9=q2KDcyyma3uKzZg@mail.gmail.com> <CAG4zZZD8eq4w9kyQbX2AJcM1LA8=UyRO7txK7TvmYhSp=YU+9g@mail.gmail.com> <CAH9hSJY84nbzv62-b3v-rnJf58qc4MWi8uNJSWFGw24kWYyrSw@mail.gmail.com>
From: Takeshi Yoshino <tyoshino@google.com>
Date: Sat, 5 Oct 2013 10:19:11 +0900
Message-ID: <CAH9hSJYPfMXdcbLnnYn9+Mp4Du9SYMGnPdiXMczg8jEGFjh8-A@mail.gmail.com>
To: Joakim Erdfelt <joakim@intalio.com>
Content-Type: multipart/alternative; boundary=f46d044283c009315f04e7f43624
Cc: "hybi@ietf.org" <hybi@ietf.org>, Gabriel Montenegro <Gabriel.Montenegro@microsoft.com>
Subject: Re: [hybi] Restarting IESG review on permessage-deflate
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Sat, 05 Oct 2013 01:19:33 -0000

--f46d044283c009315f04e7f43624
Content-Type: text/plain; charset=ISO-8859-1

On Sat, Oct 5, 2013 at 4:17 AM, Takeshi Yoshino <tyoshino@google.com> wrote:

>
>  This level of control of the deflate algorithm is just not possible in
>> Java, sorry.
>>
>>
> Again, please explain why you can't support no_context_takeover family
> parameter.
>
>

I tried using java.util.zip.Deflater and Inflater.

For compressing, used deflate() and finish() method. We need to strip a
ZLIB header (CMF and FLG) of 2 bytes at the head and an Adler 32 footer of
4 bytes at the tail from output.

For decompressing, we need to prepend a ZLIB header (CMF of 0x78 and FLG of
0x9c (some FLEVEL, FDICT=0, appropriate FCHECK)). Used inflate() method
until getRemaining() becomes 0. If we want to see Inflater.finished()
returning true to make sure all data is processed, append a block with
BFINAL e.g. 0x01 0x00 0x00 0xFF 0xFF (after appending 0x00 0x00 0xFF 0xFF
as specified in the I-D) and a valid Adler 32 footer (use
java.util.zip.Adler32).

--f46d044283c009315f04e7f43624
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra">On Sat, Oct 5, 2013 at 4:17 AM,=
 Takeshi Yoshino <span dir=3D"ltr">&lt;<a href=3D"mailto:tyoshino@google.co=
m" target=3D"_blank">tyoshino@google.com</a>&gt;</span> wrote:<br><div clas=
s=3D"gmail_quote">

<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"=
im"><br>

</div><div class=3D"gmail_quote"><div class=3D"im"><blockquote class=3D"gma=
il_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-le=
ft-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div di=
r=3D"ltr">

<div class=3D"gmail_extra"><div></div>
<div>This level of control of the deflate algorithm is just not possible in=
 Java, sorry.</div><div><br></div></div></div></blockquote><div><br></div><=
/div><div>Again, please explain why you can&#39;t support no_context_takeov=
er family parameter.</div>


<div>=A0</div></div></div></div>
</blockquote></div><br></div><div class=3D"gmail_extra">I tried using java.=
util.zip.Deflater and Inflater.</div><div class=3D"gmail_extra"><br></div><=
div class=3D"gmail_extra">For compressing, used deflate() and finish() meth=
od. We need to strip a ZLIB header (CMF and FLG) of 2 bytes at the head and=
 an Adler 32 footer of 4 bytes at the tail from output.</div>

<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">For decompr=
essing, we need to prepend a ZLIB header (CMF of 0x78 and FLG of 0x9c (some=
 FLEVEL, FDICT=3D0, appropriate FCHECK)). Used inflate() method until getRe=
maining() becomes 0. If we want to see Inflater.finished() returning true t=
o make sure all data is processed, append a block with BFINAL e.g. 0x01 0x0=
0 0x00 0xFF 0xFF (after appending 0x00 0x00 0xFF 0xFF as specified in the I=
-D) and a valid Adler 32 footer (use java.util.zip.Adler32).=A0</div>

<div class=3D"gmail_extra"><br></div></div>

--f46d044283c009315f04e7f43624--

From tobias.oberstein@tavendo.de  Sat Oct  5 06:41:53 2013
Return-Path: <tobias.oberstein@tavendo.de>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4FF921F8EEA for <hybi@ietfa.amsl.com>; Sat,  5 Oct 2013 06:41:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1RNsjVT+9Z7b for <hybi@ietfa.amsl.com>; Sat,  5 Oct 2013 06:41:49 -0700 (PDT)
Received: from EXHUB020-3.exch020.serverdata.net (exhub020-3.exch020.serverdata.net [206.225.164.30]) by ietfa.amsl.com (Postfix) with ESMTP id A585421F8F32 for <hybi@ietf.org>; Sat,  5 Oct 2013 06:41:46 -0700 (PDT)
Received: from EXVMBX020-12.exch020.serverdata.net ([169.254.3.6]) by EXHUB020-3.exch020.serverdata.net ([206.225.164.30]) with mapi; Sat, 5 Oct 2013 06:41:44 -0700
From: Tobias Oberstein <tobias.oberstein@tavendo.de>
To: Takeshi Yoshino <tyoshino@google.com>, "hybi@ietf.org" <hybi@ietf.org>, salvatore loreto <salvatore.loreto@ericsson.com>, Gabriel Montenegro <Gabriel.Montenegro@microsoft.com>
Date: Sat, 5 Oct 2013 06:41:41 -0700
Thread-Topic: [hybi] Restarting IESG review on permessage-deflate
Thread-Index: Ac7A0MdR1FIr6PlNR/KvrAhAq/CXyAA/t9Ig
Message-ID: <634914A010D0B943A035D226786325D4446790C1EF@EXVMBX020-12.exch020.serverdata.net>
References: <CAH9hSJbwd5qhMJw=3dwk3CDPua5ENRksd9=q2KDcyyma3uKzZg@mail.gmail.com>
In-Reply-To: <CAH9hSJbwd5qhMJw=3dwk3CDPua5ENRksd9=q2KDcyyma3uKzZg@mail.gmail.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: multipart/alternative; boundary="_000_634914A010D0B943A035D226786325D4446790C1EFEXVMBX02012ex_"
MIME-Version: 1.0
Subject: Re: [hybi] Restarting IESG review on permessage-deflate
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Sat, 05 Oct 2013 13:41:54 -0000

--_000_634914A010D0B943A035D226786325D4446790C1EFEXVMBX02012ex_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Takeshi,

thanks for all the work you and others put into the spec!

We'd love to see Chrome (both desktop and Android) ship with permessage-def=
late enabled in production soon. Of course it'll be great if other browsers=
 follow soon.

We have seen significant value / compression ratios (2-15x) for use with JS=
ON-based protocol over WebSocket - great for mobile in particular!

And: we just released AutobahnPython with permessage-deflate support to the=
 Python package repo: https://pypi.python.org/pypi/autobahn

So users can pick this up easily now. For clients and servers. It's ready.

We soon will ship an updated version of AutobahnTestsuite also that include=
s a whole new section for testing permessage-deflate (and our own, unoffici=
al permessage-bzip2 and permessage-snappy).

/Tobias

Von: hybi-bounces@ietf.org [mailto:hybi-bounces@ietf.org] Im Auftrag von Ta=
keshi Yoshino
Gesendet: Freitag, 4. Oktober 2013 09:09
An: hybi@ietf.org; salvatore loreto; Gabriel Montenegro
Betreff: [hybi] Restarting IESG review on permessage-deflate

Hi HyBi chairs,

After addressing Barry's comments, the spec went through reviews by several=
 people. It's not receiving any critical issue report recently.

We have two client implementation (Autobahn and Chromium) and three server =
implementations (Autobahn, WebSocket++, pywebsocket).

I think we can restart IESG review. What do you think?

--_000_634914A010D0B943A035D226786325D4446790C1EFEXVMBX02012ex_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV=3D"Content-Type" CONTENT=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.E-MailFormatvorlage17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DDE link=3D"#0563C1" v=
link=3D"#954F72"><div class=3DWordSection1><p class=3DMsoNormal><span style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-f=
areast-language:EN-US'>Takeshi,<o:p></o:p></span></p><p class=3DMsoNormal><=
span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F=
497D;mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></p><p class=3DMso=
Normal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";c=
olor:#1F497D;mso-fareast-language:EN-US'>thanks for all the work you and ot=
hers put into the spec!<o:p></o:p></span></p><p class=3DMsoNormal><span sty=
le=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso=
-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><=
span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F=
497D;mso-fareast-language:EN-US'>We'd love to see Chrome (both desktop and =
Android) ship with permessage-deflate enabled in production soon. Of course=
 it'll be great if other browsers follow soon.<o:p></o:p></span></p><p clas=
s=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-s=
erif";color:#1F497D;mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri"=
,"sans-serif";color:#1F497D;mso-fareast-language:EN-US'>We have seen signif=
icant value / compression ratios (2-15x) for use with JSON-based protocol o=
ver WebSocket - great for mobile in particular!<o:p></o:p></span></p><p cla=
ss=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-=
serif";color:#1F497D;mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></=
p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri=
","sans-serif";color:#1F497D;mso-fareast-language:EN-US'>And: we just relea=
sed AutobahnPython with permessage-deflate support to the Python package re=
po: <a href=3D"https://pypi.python.org/pypi/autobahn">https://pypi.python.o=
rg/pypi/autobahn</a><o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-f=
areast-language:EN-US'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><sp=
an style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F49=
7D;mso-fareast-language:EN-US'>So users can pick this up easily now. For cl=
ients and servers. It's ready.<o:p></o:p></span></p><p class=3DMsoNormal><s=
pan style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F4=
97D;mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></p><p class=3DMsoN=
ormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";co=
lor:#1F497D;mso-fareast-language:EN-US'>We soon will ship an updated versio=
n of AutobahnTestsuite also that includes a whole new section for testing p=
ermessage-deflate (and our own, unofficial permessage-bzip2 and permessage-=
snappy).<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size=
:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-langua=
ge:EN-US'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareas=
t-language:EN-US'>/Tobias<o:p></o:p></span></p><p class=3DMsoNormal><span s=
tyle=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;m=
so-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal=
><b><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Von=
:</span></b><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-ser=
if"'> hybi-bounces@ietf.org [mailto:hybi-bounces@ietf.org] <b>Im Auftrag vo=
n </b>Takeshi Yoshino<br><b>Gesendet:</b> Freitag, 4. Oktober 2013 09:09<br=
><b>An:</b> hybi@ietf.org; salvatore loreto; Gabriel Montenegro<br><b>Betre=
ff:</b> [hybi] Restarting IESG review on permessage-deflate<o:p></o:p></spa=
n></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><p class=3DMsoNor=
mal>Hi HyBi chairs,<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbs=
p;</o:p></p></div><div><p class=3DMsoNormal>After addressing Barry's commen=
ts, the spec went through reviews by several people. It's not receiving any=
 critical issue report recently.<o:p></o:p></p></div><div><p class=3DMsoNor=
mal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>We have two client=
 implementation (Autobahn and Chromium) and three server implementations (A=
utobahn, WebSocket++, pywebsocket).<o:p></o:p></p></div><div><p class=3DMso=
Normal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>I think we can =
restart IESG review. What do you think?<o:p></o:p></p></div></div></div></b=
ody></html>=

--_000_634914A010D0B943A035D226786325D4446790C1EFEXVMBX02012ex_--

From ricea@google.com  Sun Oct  6 19:37:32 2013
Return-Path: <ricea@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A033521E8129 for <hybi@ietfa.amsl.com>; Sun,  6 Oct 2013 19:37:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OE8pDurWIOJb for <hybi@ietfa.amsl.com>; Sun,  6 Oct 2013 19:37:31 -0700 (PDT)
Received: from mail-vb0-x22f.google.com (mail-vb0-x22f.google.com [IPv6:2607:f8b0:400c:c02::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 30D5F21E811F for <hybi@ietf.org>; Sun,  6 Oct 2013 19:37:30 -0700 (PDT)
Received: by mail-vb0-f47.google.com with SMTP id h10so3132695vbh.20 for <hybi@ietf.org>; Sun, 06 Oct 2013 19:37:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=DdHACco4jnQsidwZJ01fLiZosIG2q2AS82q++i0VgUU=; b=ONY2iO3CMAIiOvnjSFu1fO6Xts5yUudi3elrbJUME51MbakwYb7LYx2DQmGTs8c5wH GNhSOsCZm5LevsGZu0YfFvIonkhNHN28UWoE1lPihxCL6vBzQ82WiI+Ks/s02A7b7Fmk VuYfNFOEmxdTx4RGkniNGnabsJnLRXxcFX2BL/z1ZFVXyTNohrHrF2abx8qAyMcqb34O 9kVIiFNaMs6gzFm+87A56o4w0B65aQBV1/n2kEK3+QCbpyP3tUfzL+eCvV+U8ZsZ0p6g rUCYDpvlh23GUGTeQm/fOv7kBYP8TB00mnh8AdPqgbxuRBng3L0AJfD/89zp14bNuDw7 UtFQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=DdHACco4jnQsidwZJ01fLiZosIG2q2AS82q++i0VgUU=; b=ddrlAiveagZ0QQ6Z30QQVr/HS6hOL6B/Xp6vB+XPrHoqEKRe9ktCLLxFMjCcIBDu9I c+UL4k6mF0I0mrdjx8zDT+d2ez5IpnVlGPQ0nEfoIC+JH1kcTGlvXH3kPnZRyKHO72KM n20wztUAWl/bZ0TeOpcC59/ilFP1YC2aeuktAFgXUuycrVAHLvIItt9AHbI0+B/5wW2/ f1BU+3RqNQTciNfGrIQmXi9xlf0sN7F/mCdyuVTmf7HziKF8FjJfsgui0Iw+HVrjrjH0 3NMkeVdx78kqBdyEfvfasfMHP5f6j9lL8pKh/NdaAGvDx4aR/edwIf/DrYRtWnS+Exn0 EhkA==
X-Gm-Message-State: ALoCoQknw1MxGid801nTstxTDYAT8PFW4lUKSumK5GZThSY9wpAoKu+KVIX4OcNIYYcCZJjRz7h53+7b0NVaWyrtN8GRR3d10PnelcVCFHi3QEo7iWkgHSPe40eN8UmoXPY+Ret41vaSHR/gJSuhvIA7Bl8QH9GuROhLy+i8QoIKgIbusUOix+3CafEWucZQdBi1gKgMeeZc
MIME-Version: 1.0
X-Received: by 10.52.52.137 with SMTP id t9mr1211677vdo.22.1381113450310; Sun, 06 Oct 2013 19:37:30 -0700 (PDT)
Received: by 10.52.167.163 with HTTP; Sun, 6 Oct 2013 19:37:30 -0700 (PDT)
In-Reply-To: <CAG4zZZC30-d45Ow6pLZkQCYbuqWDwW6U3KW5R43VgafhwrPOEA@mail.gmail.com>
References: <CAH9hSJbwd5qhMJw=3dwk3CDPua5ENRksd9=q2KDcyyma3uKzZg@mail.gmail.com> <CAG4zZZD8eq4w9kyQbX2AJcM1LA8=UyRO7txK7TvmYhSp=YU+9g@mail.gmail.com> <634914A010D0B943A035D226786325D4446790BF34@EXVMBX020-12.exch020.serverdata.net> <CAG4zZZDNRZ_kaXBKhx5VkKjpj+Luo53Y7ue0eaGHH_ghoBrdkQ@mail.gmail.com> <634914A010D0B943A035D226786325D4446790BFFC@EXVMBX020-12.exch020.serverdata.net> <CAG4zZZC30-d45Ow6pLZkQCYbuqWDwW6U3KW5R43VgafhwrPOEA@mail.gmail.com>
Date: Mon, 7 Oct 2013 11:37:30 +0900
Message-ID: <CAHixhFr1WRoRoLbw0eMTAfog3uLAyueYKMi_QKMkTHSeiiLhPw@mail.gmail.com>
From: Adam Rice <ricea@google.com>
To: "hybi@ietf.org" <hybi@ietf.org>
Content-Type: multipart/alternative; boundary=089e0122f65e99d61104e81d882d
Subject: Re: [hybi] Restarting IESG review on permessage-deflate
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Mon, 07 Oct 2013 02:37:32 -0000

--089e0122f65e99d61104e81d882d
Content-Type: text/plain; charset=ISO-8859-1

For PHP, soywiz has worked out that the "$encoding" parameter allows you to
set the number of window bits--see the comment at
http://www.php.net/manual/en/function.zlib-encode.php

Interestingly, the problem with PHP seems to be not supporting
no_context_takeover, but supporting the default context_takeover behaviour.
zlib_decode() creates a new zlib context every time.

There might be a way to abuse the gz* functions to do it, I have not
explored them in depth.

It is always possible to support no_context_takeover in any language by
creating a new compression context for each message.


On 5 October 2013 02:41, Joakim Erdfelt <joakim@intalio.com> wrote:

> Ok, add to the b) side of the equation:
>
> scala - same classlib and jvm as java
> jython - same classlib and jvm as java, no native zlib support here
> php - http://www.php.net/manual/en/ref.zlib.php (cannot support
> max_window_bits, no_context_takeover might be possible)
> c# -
> http://msdn.microsoft.com/en-us/library/system.io.compression.deflatestream_methods.aspx (cannot
> support max_window_bits, no_context_takeover might be possible)
>
>
> --
> Joakim Erdfelt <joakim@intalio.com>
> webtide.com <http://www.webtide.com/> - intalio.com/jetty
> Expert advice, services and support from from the Jetty & CometD experts
> eclipse.org/jetty - cometd.org
>
>
> On Fri, Oct 4, 2013 at 10:11 AM, Tobias Oberstein <
> tobias.oberstein@tavendo.de> wrote:
>
>> >>Well, I'm sorry for the Java community not being able to fix this in
>> 10+ years;)
>> >Yet, oddly, with web technologies, this hasn't been a problem since our
>> initial use of Oak in 1995 (yes, Jetty has existed since 1995)
>>
>> Jetty being around since 1995 is obviously awesome!
>>
>> As a strange coincidence, zlib has also be around since 1 May 1995 (I
>> haven't checked whether the respective options have been in the first
>> version though).
>>
>> > The capabilities of one set of libraries (c & python) should not be
>> forced on all environments as well.
>>
>> Lets collect a list: a) stuff that exposes the complete zlib vs b) stuff
>> that does not;)
>>
>> a) C, C++, Python, NodeJS, Perl, Ruby, PHP, Erlang, Haskell
>> b) Java
>>
>> Caveat: I (obviously) have not used all of above myself. Just had a quick
>> glance at their docs.
>>
>> Pointers:
>> http://perldoc.perl.org/Compress/Zlib.html#Deflate-Interface
>> http://www.ruby-doc.org/stdlib-2.0.0/libdoc/zlib/rdoc/Zlib/Deflate.html
>> http://www.php.net/manual/de/function.gzdeflate.php
>> http://erlang.org/doc/man/zlib.html
>>
>> http://hackage.haskell.org/package/zlib-0.5.4.1/docs/Codec-Compression-Zlib.html
>>
>> I stop here;)
>>
>> /Tobias
>>
>
>
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi
>
>

--089e0122f65e99d61104e81d882d
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><span style=3D"font-family:arial,sans-serif;font-size:12.7=
27272033691406px">For PHP, soywiz has worked out that the &quot;$encoding&q=
uot; parameter allows you to set the number of window bits--see the comment=
 at=A0</span><a href=3D"http://www.php.net/manual/en/function.zlib-encode.p=
hp" target=3D"_blank" class=3D"cremed" style=3D"font-family:arial,sans-seri=
f;font-size:12.727272033691406px">http://www.php.net/manual/en/function.zli=
b-encode.php</a><div style=3D"font-family:arial,sans-serif;font-size:12.727=
272033691406px">
<br></div><div style=3D"font-family:arial,sans-serif;font-size:12.727272033=
691406px">Interestingly, the problem with PHP seems to be not supporting no=
_context_takeover, but supporting the default context_takeover behaviour. z=
lib_decode() creates a new zlib context every time.</div>
<div style=3D"font-family:arial,sans-serif;font-size:12.727272033691406px">=
<br></div><div style=3D"font-family:arial,sans-serif;font-size:12.727272033=
691406px">There might be a way to abuse the gz* functions to do it, I have =
not explored them in depth.</div>
<div style=3D"font-family:arial,sans-serif;font-size:12.727272033691406px">=
<br></div><div style=3D"font-family:arial,sans-serif;font-size:12.727272033=
691406px">It is always possible to support no_context_takeover in any langu=
age by creating a new compression context for each message.</div>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On 5 Oc=
tober 2013 02:41, Joakim Erdfelt <span dir=3D"ltr">&lt;<a href=3D"mailto:jo=
akim@intalio.com" target=3D"_blank">joakim@intalio.com</a>&gt;</span> wrote=
:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex">
<div dir=3D"ltr">Ok, add to the b) side of the equation:<div><br></div><div=
>scala - same classlib and jvm as java</div><div>jython - same classlib and=
 jvm as java, no native zlib support here</div><div>php -=A0<a href=3D"http=
://www.php.net/manual/en/ref.zlib.php" target=3D"_blank">http://www.php.net=
/manual/en/ref.zlib.php</a>=A0(cannot support max_window_bits, no_context_t=
akeover might be possible)</div>

<div>c# -=A0<a href=3D"http://msdn.microsoft.com/en-us/library/system.io.co=
mpression.deflatestream_methods.aspx" target=3D"_blank">http://msdn.microso=
ft.com/en-us/library/system.io.compression.deflatestream_methods.aspx</a>=
=A0(cannot support max_window_bits, no_context_takeover might be possible)<=
/div>

<div><br></div></div><div class=3D"gmail_extra"><br clear=3D"all"><div><div=
 dir=3D"ltr"><div>--</div><div>Joakim Erdfelt &lt;<a href=3D"mailto:joakim@=
intalio.com" target=3D"_blank">joakim@intalio.com</a>&gt;</div><div><a href=
=3D"http://www.webtide.com/" target=3D"_blank">webtide.com</a>=A0- <a href=
=3D"http://intalio.com/jetty" target=3D"_blank">intalio.com/jetty</a></div>

<div><span>Expert advice, services and support from=A0</span><span>from the=
 Jetty &amp; CometD experts</span></div><div><a href=3D"http://eclipse.org/=
jetty/" target=3D"_blank">eclipse.org/jetty</a>=A0-=A0<a href=3D"http://com=
etd.org/" target=3D"_blank">cometd.org</a></div>

</div></div><div><div class=3D"h5">
<br><br><div class=3D"gmail_quote">On Fri, Oct 4, 2013 at 10:11 AM, Tobias =
Oberstein <span dir=3D"ltr">&lt;<a href=3D"mailto:tobias.oberstein@tavendo.=
de" target=3D"_blank">tobias.oberstein@tavendo.de</a>&gt;</span> wrote:<br>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">

<div>&gt;&gt;Well, I&#39;m sorry for the Java community not being able to f=
ix this in 10+ years;)<br>
&gt;Yet, oddly, with web technologies, this hasn&#39;t been a problem since=
 our initial use of Oak in 1995 (yes, Jetty has existed since 1995)<br>
<br>
</div>Jetty being around since 1995 is obviously awesome!<br>
<br>
As a strange coincidence, zlib has also be around since 1 May 1995 (I haven=
&#39;t checked whether the respective options have been in the first versio=
n though).<br>
<div><br>
&gt; The capabilities of one set of libraries (c &amp; python) should not b=
e forced on all environments as well.<br>
<br>
</div>Lets collect a list: a) stuff that exposes the complete zlib vs b) st=
uff that does not;)<br>
<br>
a) C, C++, Python, NodeJS, Perl, Ruby, PHP, Erlang, Haskell<br>
b) Java<br>
<br>
Caveat: I (obviously) have not used all of above myself. Just had a quick g=
lance at their docs.<br>
<br>
Pointers:<br>
<a href=3D"http://perldoc.perl.org/Compress/Zlib.html#Deflate-Interface" ta=
rget=3D"_blank">http://perldoc.perl.org/Compress/Zlib.html#Deflate-Interfac=
e</a><br>
<a href=3D"http://www.ruby-doc.org/stdlib-2.0.0/libdoc/zlib/rdoc/Zlib/Defla=
te.html" target=3D"_blank">http://www.ruby-doc.org/stdlib-2.0.0/libdoc/zlib=
/rdoc/Zlib/Deflate.html</a><br>
<a href=3D"http://www.php.net/manual/de/function.gzdeflate.php" target=3D"_=
blank">http://www.php.net/manual/de/function.gzdeflate.php</a><br>
<a href=3D"http://erlang.org/doc/man/zlib.html" target=3D"_blank">http://er=
lang.org/doc/man/zlib.html</a><br>
<a href=3D"http://hackage.haskell.org/package/zlib-0.5.4.1/docs/Codec-Compr=
ession-Zlib.html" target=3D"_blank">http://hackage.haskell.org/package/zlib=
-0.5.4.1/docs/Codec-Compression-Zlib.html</a><br>
<br>
I stop here;)<br>
<span><font color=3D"#888888"><br>
/Tobias<br>
</font></span></blockquote></div><br></div></div></div>
<br>_______________________________________________<br>
hybi mailing list<br>
<a href=3D"mailto:hybi@ietf.org">hybi@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/hybi" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/hybi</a><br>
<br></blockquote></div><br></div>

--089e0122f65e99d61104e81d882d--

From tyoshino@google.com  Mon Oct  7 19:46:05 2013
Return-Path: <tyoshino@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17C0311E817B for <hybi@ietfa.amsl.com>; Mon,  7 Oct 2013 19:46:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X2RzlfK3SdzH for <hybi@ietfa.amsl.com>; Mon,  7 Oct 2013 19:46:04 -0700 (PDT)
Received: from mail-wi0-x231.google.com (mail-wi0-x231.google.com [IPv6:2a00:1450:400c:c05::231]) by ietfa.amsl.com (Postfix) with ESMTP id 157EA11E8113 for <hybi@ietf.org>; Mon,  7 Oct 2013 19:46:03 -0700 (PDT)
Received: by mail-wi0-f177.google.com with SMTP id hq15so4709wib.4 for <hybi@ietf.org>; Mon, 07 Oct 2013 19:46:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=P1u93jHYlT7ofJTVVt5TeF7NTyh/5NR3hU/Pp9fbSSY=; b=XAKgu7WOvEs43ZEVsTKEPlM3npXBt+K6FRSNX1+LvGZ2/+swxcTT7aUqOmWhnDvM7l AsotRZEwX/GZNIpNbh0lRdKknf8nFNExP+CW4e3Yavt59Tv58+nFUMlEzX373nhv5HzH N6TpKKRuaQJQYW6TDplmywGaLLkdIVrxq6iN46JfIsh+jvvbQ5VDGDcIon4J3NVuj9rh s32zWvwLj/fBzMuQ7Z0efpWlfaYHxTarLrdW/cMgHXfK8XkiElG1gYlIiyZWoN5TTHAh N/uifmuVlMkpTDNY/R3gUzy9NIzKp7WmKRTMYNFbDs+Ywxv4AnI8pkJ3Adfektht5glE j8xA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=P1u93jHYlT7ofJTVVt5TeF7NTyh/5NR3hU/Pp9fbSSY=; b=CZceybtDsFZSawdZ6D6qOjkrLkKchtGsIflTj8Ytc9o8t1kdt4qbFbvoabdscma7s6 nrkX14uYNEeLIkOcobSiuRDXZU6UgyzowmmfzEHOFEazzEULSzxHjG2NRsxyWgK1a8EJ W4RlZIlfh+5WJ/UN7Nd3ERFhM1neOS29WA6hv84/cnrGSdy971YxHDAsBLPxSjhLNCQh N0NTd8vXFYm4jMu7oIzCdVQnsSnBRJWmpM5RKFoeo7bBDJKkUi0d+vbrbHpVJE6ne1y0 Yt7WUbCpll4JHShkdcmBHUNyq3ZDlabEu0yIbjbPvoNfOsyQQnFy3OomyBFMkTfWmJQ8 ETkQ==
X-Gm-Message-State: ALoCoQmHXPGlNOQq2LVa0VcDiZjOirzx0/NCO9MNVhU8U6A+0ZvJIf3aPdCvTXrdlReObB6MnEtyRDW4Ds/Hp4ksYZHLGXq8MQbpAe3wIXt3/3s4FPi7xOxfUuew+SfsV7v9APm13zruZak/g8YAt54GHhqMzRl9uP2ymmFp1wwBPp2QmMescxlsR0bPa7RtUQZRDs/+4hdQ
X-Received: by 10.194.11.38 with SMTP id n6mr27863245wjb.25.1381200362416; Mon, 07 Oct 2013 19:46:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.15.133 with HTTP; Mon, 7 Oct 2013 19:45:41 -0700 (PDT)
In-Reply-To: <634914A010D0B943A035D226786325D4446790C1EF@EXVMBX020-12.exch020.serverdata.net>
References: <CAH9hSJbwd5qhMJw=3dwk3CDPua5ENRksd9=q2KDcyyma3uKzZg@mail.gmail.com> <634914A010D0B943A035D226786325D4446790C1EF@EXVMBX020-12.exch020.serverdata.net>
From: Takeshi Yoshino <tyoshino@google.com>
Date: Tue, 8 Oct 2013 11:45:41 +0900
Message-ID: <CAH9hSJZ_BhpTi=Ncm9D4B8vvaGfkO3OezeXywf3JAqak2Ltz5A@mail.gmail.com>
To: Tobias Oberstein <tobias.oberstein@tavendo.de>
Content-Type: multipart/alternative; boundary=047d7b5d5710f74c9904e831c455
Cc: "hybi@ietf.org" <hybi@ietf.org>, Gabriel Montenegro <Gabriel.Montenegro@microsoft.com>
Subject: Re: [hybi] Restarting IESG review on permessage-deflate
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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 Oct 2013 02:46:05 -0000

--047d7b5d5710f74c9904e831c455
Content-Type: text/plain; charset=ISO-8859-1

On Sat, Oct 5, 2013 at 10:41 PM, Tobias Oberstein <
tobias.oberstein@tavendo.de> wrote:

> We have seen significant value / compression ratios (2-15x) for use with
> JSON-based protocol over WebSocket - great for mobile in particular!
>
> ** **
>
> And: we just released AutobahnPython with permessage-deflate support to
> the Python package repo: https://pypi.python.org/pypi/autobahn****
>
> ** **
>
>
Great!


> So users can pick this up easily now. For clients and servers. It's ready.
> ****
>
> ** **
>
> We soon will ship an updated version of AutobahnTestsuite also that
> includes a whole new section for testing permessage-deflate (and our own,
> unofficial permessage-bzip2 and permessage-snappy).
>

Thanks as usual. We'll check it out.

--047d7b5d5710f74c9904e831c455
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Sat, Oct 5, 2013 at 10:41 PM, Tobias Oberstein <span di=
r=3D"ltr">&lt;<a href=3D"mailto:tobias.oberstein@tavendo.de" target=3D"_bla=
nk">tobias.oberstein@tavendo.de</a>&gt;</span> wrote:<br><div class=3D"gmai=
l_extra">

<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang=3D"DE" =
link=3D"#0563C1" vlink=3D"#954F72"><p class=3D"MsoNormal"><span style=3D"co=
lor:rgb(31,73,125);font-family:Calibri,sans-serif;font-size:11pt">We have s=
een significant value / compression ratios (2-15x) for use with JSON-based =
protocol over WebSocket - great for mobile in particular!</span><br>

</p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></sp=
an></p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&=
quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">And: we just relea=
sed AutobahnPython with permessage-deflate support to the Python package re=
po: <a href=3D"https://pypi.python.org/pypi/autobahn" target=3D"_blank">htt=
ps://pypi.python.org/pypi/autobahn</a><u></u><u></u></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"></span></p>

</div></blockquote><div><br></div><div>Great!</div><div>=A0</div><blockquot=
e class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc sol=
id;padding-left:1ex"><div lang=3D"DE" link=3D"#0563C1" vlink=3D"#954F72"><p=
 class=3D"MsoNormal">

<span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:#1f497d">So users can pick this up easily now. For client=
s and servers. It&#39;s ready.<u></u><u></u></span></p><p class=3D"MsoNorma=
l">

<span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:#1f497d"><u></u>=A0<u></u></span></p><p class=3D"MsoNorma=
l"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1f497d">We soon will ship an updated version of Autob=
ahnTestsuite also that includes a whole new section for testing permessage-=
deflate (and our own, unofficial permessage-bzip2 and permessage-snappy).</=
span></p>

</div></blockquote><div><br></div><div>Thanks as usual. We&#39;ll check it =
out.</div><div>=A0</div></div></div></div>

--047d7b5d5710f74c9904e831c455--

From internet-drafts@ietf.org  Mon Oct  7 20:43:49 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE11A21E81B7; Mon,  7 Oct 2013 20:43:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.564
X-Spam-Level: 
X-Spam-Status: No, score=-102.564 tagged_above=-999 required=5 tests=[AWL=0.036, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UFKTiLjvR8xF; Mon,  7 Oct 2013 20:43:48 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 63EC521E81D6; Mon,  7 Oct 2013 20:43:44 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131008034344.3492.4171.idtracker@ietfa.amsl.com>
Date: Mon, 07 Oct 2013 20:43:44 -0700
Cc: hybi@ietf.org
Subject: [hybi] I-D Action: draft-ietf-hybi-permessage-compression-13.txt
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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 Oct 2013 03:43:50 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the BiDirectional or Server-Initiated HTTP Wo=
rking Group of the IETF.

	Title           : Compression Extensions for WebSocket
	Author(s)       : Takeshi Yoshino
	Filename        : draft-ietf-hybi-permessage-compression-13.txt
	Pages           : 29
	Date            : 2013-10-07

Abstract:
   This document specifies 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 non-control WebSocket messages on a per-message basis using
   parameters negotiated during the opening handshake.  This framework
   provides a general method to apply a compression algorithm to the
   contents of WebSocket messages.  For each compression algorithm, an
   extension is defined by specifying parameter negotiation and
   compression algorithm in detail.  This document also specifies one
   specific compression extension using the DEFLATE algorithm.

   Please send feedback to the hybi@ietf.org mailing list.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-hybi-permessage-compression

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-hybi-permessage-compression-13

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-hybi-permessage-compression-13


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From tyoshino@google.com  Mon Oct  7 20:47:57 2013
Return-Path: <tyoshino@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C18621E813C for <hybi@ietfa.amsl.com>; Mon,  7 Oct 2013 20:47:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.331
X-Spam-Level: 
X-Spam-Status: No, score=-1.331 tagged_above=-999 required=5 tests=[AWL=-0.646, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MISSING_HEADERS=1.292, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RE7QKm0BP7co for <hybi@ietfa.amsl.com>; Mon,  7 Oct 2013 20:47:56 -0700 (PDT)
Received: from mail-wg0-x234.google.com (mail-wg0-x234.google.com [IPv6:2a00:1450:400c:c00::234]) by ietfa.amsl.com (Postfix) with ESMTP id 220DE21E8138 for <hybi@ietf.org>; Mon,  7 Oct 2013 20:47:55 -0700 (PDT)
Received: by mail-wg0-f52.google.com with SMTP id m15so8248613wgh.7 for <hybi@ietf.org>; Mon, 07 Oct 2013 20:47:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:cc :content-type; bh=vTF4ePAWVcIY6mPiNYVQKEzD3Ic7dAxJK6P4Fcf1OYA=; b=ft14hnzkAr34g1c6USDHfXJ/pk+dBN8S1b9HWFXCSQXEZDmTILTOIUczMfBy2HZ+P0 OPVGHGKqkIYW12llrcmX7idcuPSfga2gwoEqCXThQh7HAuYkmwFZ8+FQ3Vxe40u/lS6Z OhuIHCDPE+nhSAxzS+m14rGL8bGdVjuwET3eTek843SIYJzGvLaryqit1CrEi3GK3WtE 1M1oxZO7hl0kYL8j6PuQUm6/j1CBuyHkMOwoaLlt22QBWlslSSyp2Ipy1LLo41R2tOr+ cU0LPKidtxh2XRkaKQrEGdj41ihVXcnKkkWH/MjkcLrvUoe0ERZabKK18xVbQNdTJ0oZ +kBA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:cc:content-type; bh=vTF4ePAWVcIY6mPiNYVQKEzD3Ic7dAxJK6P4Fcf1OYA=; b=JliSGiMovjRJtsWfjNyLBG06uDY1eV5qDGo/Ind8nGMkNC4+xC91tgWyMm98XeoXFO YX/rKoAPGAIVVQwqXKdd6FLuvS0vec3XcIQ9ioBOIdjycXZpJDhN1sPx3RL6t+pqZqeU pvl/1CgC30oJzVy8TcNRxmEzsG2phYzNv8nJgXyIS16kPOLkVYmwKwQNxAC8iCK2Mjsg EDEbHPGgmNSI7Dtsx+4hvcj8j8Lvh2/JgI1PSkHjvsb3Me7qX3M3iaJkYV3uXqXjvjvX 4wXdYn24prgnJCIjbqd50ZrZSm1VB7AIzAS7B2QWk49ruGEXNeqS+R7oOPJ/E/AT9IO5 L96g==
X-Gm-Message-State: ALoCoQlDbrx8jTX5T9vF/V9whEqxWloJdFJqQb+6jJNwQjL2Hne1y6MwW0UM4+/FJ9h1Mk99me0hM9cdVmTeWlbBK/P8xoV5FTh38f2TF6YG5xMr7pGwhMAuFBFqlOFXg38pgLdvmBURT5MyOqiiN1bLZ8cxfhXfIjRrZHQC8Ryp8stDwy7sQtBAIv84XFsSk2EtKna06axB
X-Received: by 10.180.210.231 with SMTP id mx7mr22347612wic.5.1381204075170; Mon, 07 Oct 2013 20:47:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.15.133 with HTTP; Mon, 7 Oct 2013 20:47:35 -0700 (PDT)
In-Reply-To: <20131008034344.3492.4171.idtracker@ietfa.amsl.com>
References: <20131008034344.3492.4171.idtracker@ietfa.amsl.com>
From: Takeshi Yoshino <tyoshino@google.com>
Date: Tue, 8 Oct 2013 12:47:35 +0900
Message-ID: <CAH9hSJZKwBhmMg5jAa1U93g+Q1Hfv0nRDx=m_ZAbj-oi=_Ba7g@mail.gmail.com>
Cc: "hybi@ietf.org" <hybi@ietf.org>
Content-Type: multipart/alternative; boundary=001a11c25d32437bdd04e832a22c
Subject: Re: [hybi] I-D Action: draft-ietf-hybi-permessage-compression-13.txt
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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 Oct 2013 03:47:57 -0000

--001a11c25d32437bdd04e832a22c
Content-Type: text/plain; charset=ISO-8859-1

- explained why prefixes like s2c_ and c2s_ are needed
- added short note about adjusting ZLIB/Adler-32 field


On Tue, Oct 8, 2013 at 12:43 PM, <internet-drafts@ietf.org> wrote:

>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>  This draft is a work item of the BiDirectional or Server-Initiated HTTP
> Working Group of the IETF.
>
>         Title           : Compression Extensions for WebSocket
>         Author(s)       : Takeshi Yoshino
>         Filename        : draft-ietf-hybi-permessage-compression-13.txt
>         Pages           : 29
>         Date            : 2013-10-07
>
> Abstract:
>    This document specifies 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 non-control WebSocket messages on a per-message basis using
>    parameters negotiated during the opening handshake.  This framework
>    provides a general method to apply a compression algorithm to the
>    contents of WebSocket messages.  For each compression algorithm, an
>    extension is defined by specifying parameter negotiation and
>    compression algorithm in detail.  This document also specifies one
>    specific compression extension using the DEFLATE algorithm.
>
>    Please send feedback to the hybi@ietf.org mailing list.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-hybi-permessage-compression
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-hybi-permessage-compression-13
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-hybi-permessage-compression-13
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi
>

--001a11c25d32437bdd04e832a22c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>- explained why prefixes like s2c_ and c2s_ are neede=
d<br></div><div>- added short note about adjusting ZLIB/Adler-32 field<br><=
div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra"><br><div cla=
ss=3D"gmail_quote">


On Tue, Oct 8, 2013 at 12:43 PM,  <span dir=3D"ltr">&lt;<a href=3D"mailto:i=
nternet-drafts@ietf.org" target=3D"_blank">internet-drafts@ietf.org</a>&gt;=
</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex">


<br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
=A0This draft is a work item of the BiDirectional or Server-Initiated HTTP =
Working Group of the IETF.<br>
<br>
=A0 =A0 =A0 =A0 Title =A0 =A0 =A0 =A0 =A0 : Compression Extensions for WebS=
ocket<br>
=A0 =A0 =A0 =A0 Author(s) =A0 =A0 =A0 : Takeshi Yoshino<br>
=A0 =A0 =A0 =A0 Filename =A0 =A0 =A0 =A0: draft-ietf-hybi-permessage-compre=
ssion-13.txt<br>
=A0 =A0 =A0 =A0 Pages =A0 =A0 =A0 =A0 =A0 : 29<br>
=A0 =A0 =A0 =A0 Date =A0 =A0 =A0 =A0 =A0 =A0: 2013-10-07<br>
<br>
Abstract:<br>
=A0 =A0This document specifies a framework for creating WebSocket extension=
s<br>
=A0 =A0that add compression functionality to the WebSocket Protocol. =A0An<=
br>
=A0 =A0extension based on this framework compresses the payload data portio=
n<br>
=A0 =A0of non-control WebSocket messages on a per-message basis using<br>
=A0 =A0parameters negotiated during the opening handshake. =A0This framewor=
k<br>
=A0 =A0provides a general method to apply a compression algorithm to the<br=
>
=A0 =A0contents of WebSocket messages. =A0For each compression algorithm, a=
n<br>
=A0 =A0extension is defined by specifying parameter negotiation and<br>
=A0 =A0compression algorithm in detail. =A0This document also specifies one=
<br>
=A0 =A0specific compression extension using the DEFLATE algorithm.<br>
<br>
=A0 =A0Please send feedback to the <a href=3D"mailto:hybi@ietf.org" target=
=3D"_blank">hybi@ietf.org</a> mailing list.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-hybi-permessage-comp=
ression" target=3D"_blank">https://datatracker.ietf.org/doc/draft-ietf-hybi=
-permessage-compression</a><br>
<br>
There&#39;s also a htmlized version available at:<br>
<a href=3D"http://tools.ietf.org/html/draft-ietf-hybi-permessage-compressio=
n-13" target=3D"_blank">http://tools.ietf.org/html/draft-ietf-hybi-permessa=
ge-compression-13</a><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-hybi-permessage-co=
mpression-13" target=3D"_blank">http://www.ietf.org/rfcdiff?url2=3Ddraft-ie=
tf-hybi-permessage-compression-13</a><br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" target=3D"_blank">ftp://ftp=
.ietf.org/internet-drafts/</a><br>
<br>
_______________________________________________<br>
hybi mailing list<br>
<a href=3D"mailto:hybi@ietf.org" target=3D"_blank">hybi@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/hybi" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/hybi</a><br>
</blockquote></div><br></div></div></div>

--001a11c25d32437bdd04e832a22c--

From tyoshino@google.com  Mon Oct  7 20:50:47 2013
Return-Path: <tyoshino@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D979C21E81B7 for <hybi@ietfa.amsl.com>; Mon,  7 Oct 2013 20:50:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.869
X-Spam-Level: 
X-Spam-Status: No, score=-1.869 tagged_above=-999 required=5 tests=[AWL=0.108,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LjRYvjSHHHs5 for <hybi@ietfa.amsl.com>; Mon,  7 Oct 2013 20:50:46 -0700 (PDT)
Received: from mail-we0-x234.google.com (mail-we0-x234.google.com [IPv6:2a00:1450:400c:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id CA12321E8136 for <hybi@ietf.org>; Mon,  7 Oct 2013 20:50:43 -0700 (PDT)
Received: by mail-we0-f180.google.com with SMTP id q59so7948143wes.11 for <hybi@ietf.org>; Mon, 07 Oct 2013 20:50:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=x0KwxB8DPYPk13pdirXMtZzORYnyvxRLSXab9EUG4KU=; b=KZ+yoXInXEO6OKZtweqK3et8tCGcaNE236318R3QvpBCPZQMX47VMeVNW3O2tM1PxS ZoFtzXc7i+AqRTMfaJQZPj95+MSqiodQbGhLIUuLJyNMNjxtji7Q9qrqgAbcidAFvBuF mWQFDVz3/nF7MmjLIlATzaG6IQHMlFfB17tGYCy8iaRahEprdcegjBrNtfe5uz76LBXD zqZhbqsTjcbZ0cZT6AZ3z+nZl3z7kf1KSLMaxGVsHknYqo/o7mszrCZ60IUEp5vGOpr9 sDdZ6eL1pyFW/m2kZIk7PzTtM/GLJBcSz0578egMVaVzyHNT0pww9YFcOpSP2lkFLRMO L9dw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=x0KwxB8DPYPk13pdirXMtZzORYnyvxRLSXab9EUG4KU=; b=kjIVkmC+/VJUn67//5W+lh5bDF5ChFcbSXivu7rzGH7nqVV8Mny3FOofES4WJtE53i U7rvE0jF68i3l5mCW0BO1J3LKxkLw0ydtL50y6JiOFHYCaFdYr8sGa9Zn9fJsOlf/X7C JRj5RP99XHLKIUWa99A+C4DKnkGc2G5ZaAYznmvHv+g6lUFRx5OLStytX4140NqzLTuD AqIwaB/sn071hUSN+smnDjSNOolR8lBzDLEyZCYzNg1NnYVfOlAJKfgWAAGKY39g9SeT ksiimJYBf2rrDncVtPGDhdmpOqW43vJFmwL9aD3mXLZERzGK61PJsSV1wyPdVF4wG6gq OZSw==
X-Gm-Message-State: ALoCoQmdTgUYJhYYkNyfiP0+XVTY+4FHi03QRJfh/4BlfSkkBv/mGGNS60kcRYa1RGFh1DVUc1vdUuUhP4fY7T8kbQg5eulZV6sWzmQ+mxqK+81h+LFePbv4CO34gbEufmVzhO4ZOHB3qw4WOV9uA3ZMQoKSJBGPos8fCFv6wQPiLFIGf5XGYR1tQd1xnuKFIxo2aiYDnswO
X-Received: by 10.180.89.98 with SMTP id bn2mr22238381wib.42.1381204242770; Mon, 07 Oct 2013 20:50:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.15.133 with HTTP; Mon, 7 Oct 2013 20:50:21 -0700 (PDT)
In-Reply-To: <CAH9hSJZ_BhpTi=Ncm9D4B8vvaGfkO3OezeXywf3JAqak2Ltz5A@mail.gmail.com>
References: <CAH9hSJbwd5qhMJw=3dwk3CDPua5ENRksd9=q2KDcyyma3uKzZg@mail.gmail.com> <634914A010D0B943A035D226786325D4446790C1EF@EXVMBX020-12.exch020.serverdata.net> <CAH9hSJZ_BhpTi=Ncm9D4B8vvaGfkO3OezeXywf3JAqak2Ltz5A@mail.gmail.com>
From: Takeshi Yoshino <tyoshino@google.com>
Date: Tue, 8 Oct 2013 12:50:21 +0900
Message-ID: <CAH9hSJZ99Me1f4-4xjdkiEas71zftfy6oGPaHChAP4+0gg1sVw@mail.gmail.com>
To: "hybi@ietf.org" <hybi@ietf.org>, Joakim Erdfelt <joakim@intalio.com>
Content-Type: multipart/alternative; boundary=f46d04447fbb40cdd004e832ac6b
Cc: Gabriel Montenegro <Gabriel.Montenegro@microsoft.com>
Subject: Re: [hybi] Restarting IESG review on permessage-deflate
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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 Oct 2013 03:50:48 -0000

--f46d04447fbb40cdd004e832ac6b
Content-Type: text/plain; charset=ISO-8859-1

Published a new version -13. Tried to address Joakim's comments. Please
check it out.

--f46d04447fbb40cdd004e832ac6b
Content-Type: text/html; charset=ISO-8859-1

<div dir="ltr">Published a new version -13. Tried to address Joakim&#39;s comments. Please check it out.</div>

--f46d04447fbb40cdd004e832ac6b--

From joakim@intalio.com  Tue Oct  8 20:14:28 2013
Return-Path: <joakim@intalio.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D93411E8127 for <hybi@ietfa.amsl.com>; Tue,  8 Oct 2013 20:14:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BDDEn2AHXzVQ for <hybi@ietfa.amsl.com>; Tue,  8 Oct 2013 20:14:24 -0700 (PDT)
Received: from mail-ee0-f51.google.com (mail-ee0-f51.google.com [74.125.83.51]) by ietfa.amsl.com (Postfix) with ESMTP id C2BB611E8126 for <hybi@ietf.org>; Tue,  8 Oct 2013 20:14:23 -0700 (PDT)
Received: by mail-ee0-f51.google.com with SMTP id c1so74164eek.38 for <hybi@ietf.org>; Tue, 08 Oct 2013 20:14:22 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=t9rrofMuLcFqh2T6y8jK2Gg9L3ylQg6wc71TXRBIKZ0=; b=fQFLG2FTlsSaBIAYXLZYf/OydyOmoLcwmScR+0bX4N9ZZ1Zm46xIypGrCEZPdY7Ixu vPm6ewAL6fmLeWW+lmeqpEbS2nOemBs5bjDNgXxmt5TsVeUsISAMTXUGbmxOaSdZmJxS PEU1Zw3jANJ4NfmcpJd1eoU2hi55q/95SR9AgHLj+b4ayBNgsn526uXis5J0DFocNcvp iHvjg7VBzmxsZUNCBg7LaYcydjh8eLIiHyXhUaYy3NKhpvASAy86ETrIGshH/S7wJAJU fV0zr0EJksAAgvZsQrtlpv89Elav3dhoYyKcNij0lBU1tW3/4BrploqifvR0v9rw5G2h vDOQ==
X-Gm-Message-State: ALoCoQlGvZ2Oe6OzDSWy9uXM+w9jn+6t8lcWTo0BNeLWEmPdsn7ZshKHekFWXAacsatmaKIHIDWT
MIME-Version: 1.0
X-Received: by 10.15.107.135 with SMTP id cb7mr76414eeb.60.1381288462433; Tue, 08 Oct 2013 20:14:22 -0700 (PDT)
Received: by 10.14.134.73 with HTTP; Tue, 8 Oct 2013 20:14:22 -0700 (PDT)
In-Reply-To: <CAH9hSJZKwBhmMg5jAa1U93g+Q1Hfv0nRDx=m_ZAbj-oi=_Ba7g@mail.gmail.com>
References: <20131008034344.3492.4171.idtracker@ietfa.amsl.com> <CAH9hSJZKwBhmMg5jAa1U93g+Q1Hfv0nRDx=m_ZAbj-oi=_Ba7g@mail.gmail.com>
Date: Tue, 8 Oct 2013 20:14:22 -0700
Message-ID: <CAG4zZZC2umzmq2vXPJGmR5+hZuRiRO7BN+9via8dBK7Og4XhBg@mail.gmail.com>
From: Joakim Erdfelt <joakim@intalio.com>
To: Takeshi Yoshino <tyoshino@google.com>
Content-Type: multipart/alternative; boundary=089e01634c7c22d38804e846488c
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] I-D Action: draft-ietf-hybi-permessage-compression-13.txt
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 09 Oct 2013 03:14:28 -0000

--089e01634c7c22d38804e846488c
Content-Type: text/plain; charset=ISO-8859-1

Jetty's Commentary on draft-ietf-hybi-permessage-compression-13.txt

----------------------

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3

 > good
 > +1 for the removal of the PPP text

   2.  Conformance Requirements and Terminology . . . . . . . . . . .  4

 > standard language, good

   3.  Complementary Terminology  . . . . . . . . . . . . . . . . . .  5

 > sufficient, would providing links to RFC6455 sections be worthwhile?
 > example:

 - Non-control message means a message consists of non-control frames.
 + Non-control message means a message that consists of non-control
   frames (e.g., data frames) as defined in [Section 5.6] of [RFC6455]

 - Message payload (or payload of a message) means concatenation of the
 - payload data portion of all frames consisting the message.
 + Message payload (or payload of a message) means concatenation of the
 + payload data portion of all data frames consisting of a single
 + message, as defined in [Section 6] of [RFC6455]

 > no commentary on section for the paragraphs about Extension behavior
 > as the reference to [Section 9] of [RFC6455] is handled in the next
 > section of this doc

   4.  WebSocket Per-message Compression Extension  . . . . . . . . .  6

 > good

   5.  Extension Negotiation  . . . . . . . . . . . . . . . . . . . .  7

 > the section on "Agreed parameters" is confusing

   "Agreed parameters" MUST represent all parameters that can determine
   behavior of both the server and the client so that it's unnecessary
   to identify which offer has been accepted.

 > what is this trying to say?
 > starts out by saying that a new key phrase "agreed parameters" is
 > a mandatory representation of all parameters that can determine
 > the behavior of incoming vs outgoing frames.  Then it adds on the
 > confusing part about about the parameters being unnessary to use
 > to identify which offer has been accepted.  That's counter to
 > how this extension works later in the same document, even the
 > example in same paragraph.

   For example, if a client
   sends an offer with a parameter "enable_compression" and another
   without the parameter, the server accepts the former by sending back
   an element including a parameter that acknowledges
   "enable_compression".  The name of the acknowledging parameter
   doesn't need to be the same as the offer.

 > to put this another way, like the example hints at.
 > the client makes an offer, identifying 2 sets of parameters.
 > how it wants to talk to server, and how it wants the server to
 > talk to it.
 > the server will use the stated client side configuration/behavior,
 > if it can, (otherwise it doesn't negotiate the extension), and
 > then make a determination of its own configuration/behavior,
 > based on hints provided in the client request extension /
 > negotiation, and respond to the extension negotiation with
 > how it is expecting the client communications and how it
 > will communicate to the client.  If the client doesn't like
 > it, then the client closes with close code 1010.

 > The server is ultimately in control of its own
 > communications and configuration (this is normal behavior for
 > web communications, even http)
 > in http land, for example, the client can POST with compression
 > and state that it accepts compression, but the server does not
 > have to honor that, as ultimately the server, the server developer,
 > the server operations folks, and the networking folks will
 > want to change behavior of the server communications to suit
 > the demands that they have for the server.

 > the rest of this is not very strict about this, but this section on
 > "Agreed parameters" appears to makes this strict, and counter to existing
 > behavior for web technologies.

 > We see the new language for s2c_ and c2s_, but still think these are
 > awful choices, and will point out why this language just adds to the
 > confusion later in the spec.

 > The added language about the directionality is useful.

 > Since all websocket communications are initiated by client to server
 > these should just be s/s2c_/server_/g and s/c2s_/client_/g

 > This is one of the first extension specs, and will likely be used
 > as an example for other extension specs, don't propagate bad behavior
 > this early in the process.  Be clear and easy to follow.

   If a server gives an invalid response, such as accepting a PMCE that
   the client did not offer, the client MUST _Fail the WebSocket
   Connection_.

 > should we mention close code 1010 here?

     5.1.  Negotiation Examples . . . . . . . . . . . . . . . . . . .  8

   o  Offer the permessage-foo with a parameter use_y which enables a
      feature y as first choice, and the permessage-foo without the
      use_y parameter as a fallback plan.

          permessage-foo; use_y, permessage-foo

 > suggest eliminating this entirely.
 > we believe this to be an improper interpretation of the extension
 > rules in RFC6455.
 > Basically, Extensions should not be aware of each other, but rather
 > have some rules that apply equally to all extensions in a consistent
 > behavior.
 > If we have extensions that need to be aware of each other in order
 > to know if they can run or not, then you put the burden of all
 > future extensions to be aware of all other extensions.
 > In the above example, this would be invalid an invalid offer.
 > as both tokens are using RSV1 bit, causing the server to either
 > not use the extension or fail the connection as there are 2
 > extensions both requesting RSV1 bit.

 > An interpretation of the rules outlined in RFC6455:
 >  - extension might use a RSV bit (extension spec declares which one)
 >  - extension might need to refragment the frames
 >  - extension will only work if frame boundaries are preserved
 >  - extension might use extension data section

 > With this knowledge, the base RFC6455 extension negotiation can
 > determine what is possible, and what is in conflict on the
 > extension offer line.

 > Lets say, for example, we have 3 fictious extensions along with
 > permessage-deflate
 >   a) The metadata extension
 >      - uses RSV1
 >      - uses extension-data
 >      - doesn't care about frame boundaries
 >      this tacks on some arbitrary metadata about the message on each
frame
 >   b) The gpgsig extension
 >      - uses RSV2
 >      - does not use extension-data
 >      - doesn't care about frame boundaries
 >      this does a gpg cryptographic signature of each the frame
 >   c) The interleaving extension
 >      - uses RSV3
 >      - uses extension data
 >      - doesn't care about frame boundaries on input
 >      - will adjust fragmentation to suit its needs
 >      this interleaves multiple messages at the same time
 >   d) The permessage-deflate
 >      - uses RSV1
 >      - does not use extension-data
 >      - doesn't care about frame boundaries on input
 >      - will adjust fragmentation to suit its needs
 >      this does what this spec is all about

 > If an offer arrives with all of these ..
 >   Sec-WebSocket-Extension: interleaving, metadata, gpgsig,
permessage-deflate
 >
 > What should the base RFC6455 do to negotiate this?
 >   1) one path would be to not respond with metadata or permessage-deflate
 >      as both declare RSV1 bit use, and that's a conflict.  This is the
 >      behavior outlined in RFC6455, but the reasons for conflict are lost
 >      as theres no mechanism to communicate this conflict.
 >   2) another path would be to fail the handshake with an HTTP response
code 400
 >      with details about the conflict.
 >   3) a first-to-file approach could also be used, and if there is a RSV1
 >      conflict, the first one in the offer to declare it is the one that
 >      will be used, and all subsequent RSV1 declarations will not be used.
 >   4) extension spec specific fallback behavior (as outlined in the
 >      current permessage-deflate spec)
 >      This is a variation to the first-to-file approach, but instead of
 >      first to file, its first to negotiate successfully, causing all
 >      downstream conflicting extensions to never be negotiated.
 >
 > You might be leaning towards #3 or #4, but wait!  Mux changes the rules
again.
 > If during mux you see an offer like this ...
 >   Sec-WebSocket-Extension: metadata, mux, permessage-deflate
 > Then the physical connection will be using metadata, and the
 > all of the virtual connection (channels) will be using
permessage-deflate.

 > Now, to go back to the example in the spec documentation.
 >    permessage-foo; use_y, permessage-foo

   6.  Framing  . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

 > good

     6.1.  Compression  . . . . . . . . . . . . . . . . . . . . . . . 10

   2.  If this PMCE is the last extension to process outgoing messages,
       build frame(s) by using the compressed data instead of the
       original data for the message payload, and setting the

 > The condition "if this PCME is the last extension to process
 > outgoing messages" is meaningless, here and further down in this
 > section.  The process is the same for all PMCEs regardless if it is
 > the first, middle, or last extension.
 >
 > Also, with the current spec, we would argue that it is impossible
 > to have multiple active PMCEs anyway (due to the RSV1 bit requirement)

     6.2.  Decompression  . . . . . . . . . . . . . . . . . . . . . . 11

 > Again, same commentary about the "PCME is the last extension"
 > condition being irrelevant

   7.  Intermediaries . . . . . . . . . . . . . . . . . . . . . . . . 13

 > good, but could use some commentary that if the intermediaries are
 > not aware of the opening handshake, then they should make no
 > modifications to the frames.  See [Section 5.4] of [RFC6455]
 > 3rd paragraph for similar text.

   8.  permessage-deflate extension . . . . . . . . . . . . . . . . . 14

 > OK, some suggestions on how to clean this section up.
 >
 > Introduce the 4 extension parameters first.
 >
 >   Use the language found elsewhere in the spec now about the asymmetric
 >   nature of the extension parameter configuration.
 >
 >   The following 2 extension parameters control the behavior of the
 >   deflate configuration for Client-to-Server messages:
 >   (We took this notation from the title of [Section 5.3] of [RFC-6455],
 >    including the capitalization)
 >
 >     o  "c2s_no_context_takeover"
 >     o  "c2s_max_window_bits"
 >
 >   The following 2 extension parameters control the behavior of the
 >   deflate configuration for Server-to-Client messages:
 >
 >     o  "s2c_no_context_takeover"
 >     o  "s2c_max_window_bits"
 >
 > Then describe how the Offer works. (essentially the language you
 > have now in the doc, with careful attention to not mix your intro
 > and then bullets)
 >    Request: desired client behavior + desired server behavior
 >    Response: acknowledge client behavior + server chosen behavior
 >
 > Example of confusing language:

   For an offer for this extension, the following 4 extension parameters
   are defined.  If needed to distinguish from ones for a response,
   these parameters are called with a prefix "client-to-server".

   o  "s2c_no_context_takeover"

   o  "c2s_no_context_takeover"

   o  "s2c_max_window_bits"

   o  "c2s_max_window_bits"

 > This section introduces you to "client-to-server", then lists
 > s2c_*, why?  Same for the next section, but in reverse.
 > Don't mix the introduction of the extension parameters and
 > the behavior of the request and response together.
 >
 > Finally, go into the MUST rules for Client and Server like you
 > currently have in the spec documentation.
 >
 > Include wording for Client MUST pointing back to close code
 > 1010 from [RC6455] as a recommended behavior for dealing with
 > bad extension negotiation.
 > Even for things like a server saying s2c_max_window_bits=1024

     8.1.  Method Parameters  . . . . . . . . . . . . . . . . . . . . 15
       8.1.1.  Context Takeover Control . . . . . . . . . . . . . . . 15

 > Include explicit language indicating default behavior for
 > context takeover.

 > When documenting one side, for example "s2c_", do not make references
 > to the opposite direction.  Its confusing, noisy, and adds no value.
 >
 > For example, Section 8.1.2.2. c2s_max_window_bits, start out talking
 > about the c2s_max_window_bits, then has suddenly talks about
 > "server-to-client parameter", mentioning behavior and server limits.
 > This is confusing.
 > Fix this, clarify it, eliminate the noise, or simplify it.
 >
 > Eg of simplification:
 >
 >  See [Section 8.1.2.1.] "s2c_max_window_bits" for server side
 >  equivalent
 >
 > We suspect that the use of "c2s" and "client-to-server" to
 > interchangably refer to either the "extension parameter token" itself
 > or the phase of the extension negotiation (request or response) is
 > the cause of the confusion.
 >
 > Either choose new terminology for the extension parameter token, or
 > choose new terminology for the phase of the extension negotiation
 > (request side or response side)
 >

       8.1.2.  Limiting the LZ77 sliding window size  . . . . . . . . 16

 > Include explicit language indicating default size for
 > LZ77 sliding window size.
 > RFC1979 seems to indicate 32KB as the maximum value, but no obvious
 > word on what is the default behavior, assuming no window size is
 > specifically declared.
 >
 > The ABNF for the c2s_max_window_bits indicates that a digit is required,
 > but the text indicates that no value is possible.
 > What does no-value mean?

       8.1.3.  Example  . . . . . . . . . . . . . . . . . . . . . . . 18

 > See earlier commentary about no value c2s_max_window_bits extension
 > parameter token.
 > See earlier commentary about extension negotiation for example #3
 > (fallback behavior written into this spec)

     8.2.  Message Payload Transformation . . . . . . . . . . . . . . 19

 > good
 > (one note, the BFINAL logic needs to be validated in current
 > implementations.  as BFINAL does not behave the same in pywebsocket,
 > autobahn, chrome, and safari).  We had to hack BFINAL to always be
 > 0 for outgoing frames from our server in order for existing
 > client implementations to work.

       8.2.1.  Compression  . . . . . . . . . . . . . . . . . . . . . 19

 > good

       8.2.2.  Decompression  . . . . . . . . . . . . . . . . . . . . 20

 > good

       8.2.3.  Examples . . . . . . . . . . . . . . . . . . . . . . . 21

 > Include example of multiple message behavior with no_context_takeover
 > configured.

     8.3.  Implementation Notes . . . . . . . . . . . . . . . . . . . 24

 > This section's updates are good.
 > The LZ77 sliding window size recommendation is ok, but where's the
 > default LZ77 sliding window size?

     8.4.  Intermediaries . . . . . . . . . . . . . . . . . . . . . . 24

 > Isn't this section identical to [Section 7] in this same spec?

 > We have no comments for the remaining sections

   9.  Security Considerations  . . . . . . . . . . . . . . . . . . . 25
   10. IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 26
     10.1. Registration of the "permessage-deflate" WebSocket
           Extension Name . . . . . . . . . . . . . . . . . . . . . . 26
     10.2. Registration of the "Per-message Compressed" WebSocket
           Framing Header Bit . . . . . . . . . . . . . . . . . . . . 26
   11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 27
   12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 28
     12.1. Normative References . . . . . . . . . . . . . . . . . . . 28
     12.2. Informative References . . . . . . . . . . . . . . . . . . 28
   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 29

--
Joakim Erdfelt <joakim@intalio.com>
webtide.com <http://www.webtide.com/> - intalio.com/jetty
Expert advice, services and support from from the Jetty & CometD experts
eclipse.org/jetty - cometd.org


On Mon, Oct 7, 2013 at 8:47 PM, Takeshi Yoshino <tyoshino@google.com> wrote:

> - explained why prefixes like s2c_ and c2s_ are needed
> - added short note about adjusting ZLIB/Adler-32 field
>
>
>
> On Tue, Oct 8, 2013 at 12:43 PM, <internet-drafts@ietf.org> wrote:
>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>>  This draft is a work item of the BiDirectional or Server-Initiated HTTP
>> Working Group of the IETF.
>>
>>         Title           : Compression Extensions for WebSocket
>>         Author(s)       : Takeshi Yoshino
>>         Filename        : draft-ietf-hybi-permessage-compression-13.txt
>>         Pages           : 29
>>         Date            : 2013-10-07
>>
>> Abstract:
>>    This document specifies 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 non-control WebSocket messages on a per-message basis using
>>    parameters negotiated during the opening handshake.  This framework
>>    provides a general method to apply a compression algorithm to the
>>    contents of WebSocket messages.  For each compression algorithm, an
>>    extension is defined by specifying parameter negotiation and
>>    compression algorithm in detail.  This document also specifies one
>>    specific compression extension using the DEFLATE algorithm.
>>
>>    Please send feedback to the hybi@ietf.org mailing list.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-hybi-permessage-compression
>>
>> There's also a htmlized version available at:
>> http://tools.ietf.org/html/draft-ietf-hybi-permessage-compression-13
>>
>> A diff from the previous version is available at:
>> http://www.ietf.org/rfcdiff?url2=draft-ietf-hybi-permessage-compression-13
>>
>>
>> Please note that it may take a couple of minutes from the time of
>> submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> _______________________________________________
>> hybi mailing list
>> hybi@ietf.org
>> https://www.ietf.org/mailman/listinfo/hybi
>>
>
>
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi
>
>

--089e01634c7c22d38804e846488c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Jetty&#39;s Commentary on=A0draft-ietf-hybi-permessage-com=
pression-13.txt<div><br></div><div>----------------------</div><div><div><b=
r></div><div>=A0 =A01. =A0Introduction . . . . . . . . . . . . . . . . . . =
. . . . . . . =A03</div>
<div>=A0 =A0</div><div>=A0&gt; good</div><div>=A0&gt; +1 for the removal of=
 the PPP text</div><div>=A0 =A0</div><div>=A0 =A02. =A0Conformance Requirem=
ents and Terminology . . . . . . . . . . . =A04</div><div>=A0 =A0</div><div=
>=A0&gt; standard language, good</div>
<div>=A0 =A0</div><div>=A0 =A03. =A0Complementary Terminology =A0. . . . . =
. . . . . . . . . . . . . =A05</div><div>=A0 =A0</div><div>=A0&gt; sufficie=
nt, would providing links to RFC6455 sections be worthwhile?</div><div>=A0&=
gt; example:</div>
<div>=A0</div><div>=A0- Non-control message means a message consists of non=
-control frames.</div><div>=A0+ Non-control message means a message that co=
nsists of non-control</div><div>=A0 =A0frames (e.g., data frames) as define=
d in [Section 5.6] of [RFC6455]</div>
<div>=A0 =A0</div><div>=A0- Message payload (or payload of a message) means=
 concatenation of the</div><div>=A0- payload data portion of all frames con=
sisting the message.</div><div>=A0+ Message payload (or payload of a messag=
e) means concatenation of the</div>
<div>=A0+ payload data portion of all data frames consisting of a single</d=
iv><div>=A0+ message, as defined in [Section 6] of [RFC6455]</div><div>=A0<=
/div><div>=A0&gt; no commentary on section for the paragraphs about Extensi=
on behavior</div>
<div>=A0&gt; as the reference to [Section 9] of [RFC6455] is handled in the=
 next</div><div>=A0&gt; section of this doc</div><div>=A0 =A0</div><div>=A0=
 =A04. =A0WebSocket Per-message Compression Extension =A0. . . . . . . . . =
=A06</div><div>
=A0</div><div>=A0&gt; good</div><div>=A0 =A0</div><div>=A0 =A05. =A0Extensi=
on Negotiation =A0. . . . . . . . . . . . . . . . . . . . =A07</div><div>=
=A0 =A0</div><div>=A0&gt; the section on &quot;Agreed parameters&quot; is c=
onfusing</div><div>=A0</div>
<div>=A0 =A0&quot;Agreed parameters&quot; MUST represent all parameters tha=
t can determine</div><div>=A0 =A0behavior of both the server and the client=
 so that it&#39;s unnecessary</div><div>=A0 =A0to identify which offer has =
been accepted.</div>
<div>=A0</div><div>=A0&gt; what is this trying to say?</div><div>=A0&gt; st=
arts out by saying that a new key phrase &quot;agreed parameters&quot; is</=
div><div>=A0&gt; a mandatory representation of all parameters that can dete=
rmine</div>
<div>=A0&gt; the behavior of incoming vs outgoing frames. =A0Then it adds o=
n the</div><div>=A0&gt; confusing part about about the parameters being unn=
essary to use</div><div>=A0&gt; to identify which offer has been accepted. =
=A0That&#39;s counter to</div>
<div>=A0&gt; how this extension works later in the same document, even the<=
/div><div>=A0&gt; example in same paragraph.</div><div>=A0</div><div>=A0 =
=A0For example, if a client</div><div>=A0 =A0sends an offer with a paramete=
r &quot;enable_compression&quot; and another</div>
<div>=A0 =A0without the parameter, the server accepts the former by sending=
 back</div><div>=A0 =A0an element including a parameter that acknowledges</=
div><div>=A0 =A0&quot;enable_compression&quot;. =A0The name of the acknowle=
dging parameter</div>
<div>=A0 =A0doesn&#39;t need to be the same as the offer.</div><div>=A0</di=
v><div>=A0&gt; to put this another way, like the example hints at.</div><di=
v>=A0&gt; the client makes an offer, identifying 2 sets of parameters.</div=
><div>
=A0&gt; how it wants to talk to server, and how it wants the server to</div=
><div>=A0&gt; talk to it.</div><div>=A0&gt; the server will use the stated =
client side configuration/behavior,</div><div>=A0&gt; if it can, (otherwise=
 it doesn&#39;t negotiate the extension), and</div>
<div>=A0&gt; then make a determination of its own configuration/behavior,</=
div><div>=A0&gt; based on hints provided in the client request extension /<=
/div><div>=A0&gt; negotiation, and respond to the extension negotiation wit=
h</div>
<div>=A0&gt; how it is expecting the client communications and how it</div>=
<div>=A0&gt; will communicate to the client. =A0If the client doesn&#39;t l=
ike</div><div>=A0&gt; it, then the client closes with close code 1010.</div=
><div>
=A0</div><div>=A0&gt; The server is ultimately in control of its own</div><=
div>=A0&gt; communications and configuration (this is normal behavior for</=
div><div>=A0&gt; web communications, even http)</div><div>=A0&gt; in http l=
and, for example, the client can POST with compression</div>
<div>=A0&gt; and state that it accepts compression, but the server does not=
</div><div>=A0&gt; have to honor that, as ultimately the server, the server=
 developer,</div><div>=A0&gt; the server operations folks, and the networki=
ng folks will</div>
<div>=A0&gt; want to change behavior of the server communications to suit</=
div><div>=A0&gt; the demands that they have for the server.</div><div>=A0</=
div><div>=A0&gt; the rest of this is not very strict about this, but this s=
ection on</div>
<div>=A0&gt; &quot;Agreed parameters&quot; appears to makes this strict, an=
d counter to existing</div><div>=A0&gt; behavior for web technologies.</div=
><div>=A0=A0</div><div>=A0&gt; We see the new language for s2c_ and c2s_, b=
ut still think these are</div>
<div>=A0&gt; awful choices, and will point out why this language just adds =
to the</div><div>=A0&gt; confusion later in the spec.</div><div>=A0</div><d=
iv>=A0&gt; The added language about the directionality is useful.</div><div=
>=A0</div>
<div>=A0&gt; Since all websocket communications are initiated by client to =
server</div><div>=A0&gt; these should just be s/s2c_/server_/g and s/c2s_/c=
lient_/g</div><div>=A0</div><div>=A0&gt; This is one of the first extension=
 specs, and will likely be used</div>
<div>=A0&gt; as an example for other extension specs, don&#39;t propagate b=
ad behavior</div><div>=A0&gt; this early in the process. =A0Be clear and ea=
sy to follow.</div><div>=A0</div><div>=A0 =A0If a server gives an invalid r=
esponse, such as accepting a PMCE that</div>
<div>=A0 =A0the client did not offer, the client MUST _Fail the WebSocket</=
div><div>=A0 =A0Connection_.</div><div>=A0 =A0</div><div>=A0&gt; should we =
mention close code 1010 here?</div><div>=A0 =A0</div><div>=A0 =A0 =A05.1. =
=A0Negotiation Examples . . . . . . . . . . . . . . . . . . . =A08</div>
<div>=A0 =A0 =A0</div><div>=A0 =A0o =A0Offer the permessage-foo with a para=
meter use_y which enables a</div><div>=A0 =A0 =A0 feature y as first choice=
, and the permessage-foo without the</div><div>=A0 =A0 =A0 use_y parameter =
as a fallback plan.</div>
<div><br></div><div>=A0 =A0 =A0 =A0 =A0 permessage-foo; use_y, permessage-f=
oo</div><div>=A0 =A0 =A0 =A0 =A0=A0</div><div>=A0&gt; suggest eliminating t=
his entirely.</div><div>=A0&gt; we believe this to be an improper interpret=
ation of the extension</div>
<div>=A0&gt; rules in RFC6455.</div><div>=A0&gt; Basically, Extensions shou=
ld not be aware of each other, but rather</div><div>=A0&gt; have some rules=
 that apply equally to all extensions in a consistent</div><div>=A0&gt; beh=
avior.</div>
<div>=A0&gt; If we have extensions that need to be aware of each other in o=
rder</div><div>=A0&gt; to know if they can run or not, then you put the bur=
den of all</div><div>=A0&gt; future extensions to be aware of all other ext=
ensions.</div>
<div>=A0&gt; In the above example, this would be invalid an invalid offer.<=
/div><div>=A0&gt; as both tokens are using RSV1 bit, causing the server to =
either=A0</div><div>=A0&gt; not use the extension or fail the connection as=
 there are 2</div>
<div>=A0&gt; extensions both requesting RSV1 bit.</div><div>=A0</div><div>=
=A0&gt; An interpretation of the rules outlined in RFC6455:</div><div>=A0&g=
t; =A0- extension might use a RSV bit (extension spec declares which one)</=
div><div>
=A0&gt; =A0- extension might need to refragment the frames</div><div>=A0&gt=
; =A0- extension will only work if frame boundaries are preserved</div><div=
>=A0&gt; =A0- extension might use extension data section</div><div>=A0</div=
><div>=A0&gt; With this knowledge, the base RFC6455 extension negotiation c=
an</div>
<div>=A0&gt; determine what is possible, and what is in conflict on the=A0<=
/div><div>=A0&gt; extension offer line.</div><div><br></div><div>=A0&gt; Le=
ts say, for example, we have 3 fictious extensions along with</div><div>=A0=
&gt; permessage-deflate</div>
<div>=A0&gt; =A0 a) The metadata extension</div><div>=A0&gt; =A0 =A0 =A0- u=
ses RSV1</div><div>=A0&gt; =A0 =A0 =A0- uses extension-data</div><div>=A0&g=
t; =A0 =A0 =A0- doesn&#39;t care about frame boundaries</div><div>=A0&gt; =
=A0 =A0 =A0this tacks on some arbitrary metadata about the message on each =
frame</div>
<div>=A0&gt; =A0 b) The gpgsig extension</div><div>=A0&gt; =A0 =A0 =A0- use=
s RSV2</div><div>=A0&gt; =A0 =A0 =A0- does not use extension-data</div><div=
>=A0&gt; =A0 =A0 =A0- doesn&#39;t care about frame boundaries</div><div>=A0=
&gt; =A0 =A0 =A0this does a gpg cryptographic signature of each the frame</=
div>
<div>=A0&gt; =A0 c) The interleaving extension</div><div>=A0&gt; =A0 =A0 =
=A0- uses RSV3</div><div>=A0&gt; =A0 =A0 =A0- uses extension data</div><div=
>=A0&gt; =A0 =A0 =A0- doesn&#39;t care about frame boundaries on input</div=
><div>=A0&gt; =A0 =A0 =A0- will adjust fragmentation to suit its needs</div=
>
<div>=A0&gt; =A0 =A0 =A0this interleaves multiple messages at the same time=
</div><div>=A0&gt; =A0 d) The permessage-deflate</div><div>=A0&gt; =A0 =A0 =
=A0- uses RSV1</div><div>=A0&gt; =A0 =A0 =A0- does not use extension-data</=
div><div>=A0&gt; =A0 =A0 =A0- doesn&#39;t care about frame boundaries on in=
put</div>
<div>=A0&gt; =A0 =A0 =A0- will adjust fragmentation to suit its needs</div>=
<div>=A0&gt; =A0 =A0 =A0this does what this spec is all about</div><div>=A0=
</div><div>=A0&gt; If an offer arrives with all of these ..</div><div>=A0&g=
t; =A0 Sec-WebSocket-Extension: interleaving, metadata, gpgsig, permessage-=
deflate</div>
<div>=A0&gt;</div><div>=A0&gt; What should the base RFC6455 do to negotiate=
 this?</div><div>=A0&gt; =A0 1) one path would be to not respond with metad=
ata or permessage-deflate</div><div>=A0&gt; =A0 =A0 =A0as both declare RSV1=
 bit use, and that&#39;s a conflict. =A0This is the</div>
<div>=A0&gt; =A0 =A0 =A0behavior outlined in RFC6455, but the reasons for c=
onflict are lost</div><div>=A0&gt; =A0 =A0 =A0as theres no mechanism to com=
municate this conflict.</div><div>=A0&gt; =A0 2) another path would be to f=
ail the handshake with an HTTP response code 400</div>
<div>=A0&gt; =A0 =A0 =A0with details about the conflict.</div><div>=A0&gt; =
=A0 3) a first-to-file approach could also be used, and if there is a RSV1<=
/div><div>=A0&gt; =A0 =A0 =A0conflict, the first one in the offer to declar=
e it is the one that</div>
<div>=A0&gt; =A0 =A0 =A0will be used, and all subsequent RSV1 declarations =
will not be used.</div><div>=A0&gt; =A0 4) extension spec specific fallback=
 behavior (as outlined in the=A0</div><div>=A0&gt; =A0 =A0 =A0current perme=
ssage-deflate spec)</div>
<div>=A0&gt; =A0 =A0 =A0This is a variation to the first-to-file approach, =
but instead of</div><div>=A0&gt; =A0 =A0 =A0first to file, its first to neg=
otiate successfully, causing all</div><div>=A0&gt; =A0 =A0 =A0downstream co=
nflicting extensions to never be negotiated.</div>
<div>=A0&gt; =A0 =A0 =A0</div><div>=A0&gt; You might be leaning towards #3 =
or #4, but wait! =A0Mux changes the rules again.</div><div>=A0&gt; If durin=
g mux you see an offer like this ...</div><div>=A0&gt; =A0 Sec-WebSocket-Ex=
tension: metadata, mux, permessage-deflate</div>
<div>=A0&gt; Then the physical connection will be using metadata, and the</=
div><div>=A0&gt; all of the virtual connection (channels) will be using per=
message-deflate.</div><div><br></div><div>=A0&gt; Now, to go back to the ex=
ample in the spec documentation.</div>
<div>=A0&gt; =A0 =A0permessage-foo; use_y, permessage-foo</div><div>=A0 =A0=
 =A0</div><div>=A0 =A06. =A0Framing =A0. . . . . . . . . . . . . . . . . . =
. . . . . . . . . 10</div><div>=A0 =A0</div><div>=A0&gt; good</div><div>=A0=
</div><div>=A0 =A0 =A06.1. =A0Compression =A0. . . . . . . . . . . . . . . =
. . . . . . . . 10</div>
<div>=A0 =A0 =A0</div><div>=A0 =A02. =A0If this PMCE is the last extension =
to process outgoing messages,</div><div>=A0 =A0 =A0 =A0build frame(s) by us=
ing the compressed data instead of the</div><div>=A0 =A0 =A0 =A0original da=
ta for the message payload, and setting the</div>
<div><br></div><div>=A0&gt; The condition &quot;if this PCME is the last ex=
tension to process</div><div>=A0&gt; outgoing messages&quot; is meaningless=
, here and further down in this=A0</div><div>=A0&gt; section. =A0The proces=
s is the same for all PMCEs regardless if it is</div>
<div>=A0&gt; the first, middle, or last extension.</div><div>=A0&gt;</div><=
div>=A0&gt; Also, with the current spec, we would argue that it is impossib=
le</div><div>=A0&gt; to have multiple active PMCEs anyway (due to the RSV1 =
bit requirement)</div>
<div>=A0</div><div>=A0 =A0 =A06.2. =A0Decompression =A0. . . . . . . . . . =
. . . . . . . . . . . . 11</div><div>=A0 =A0 =A0</div><div>=A0&gt; Again, s=
ame commentary about the &quot;PCME is the last extension&quot;</div><div>=
=A0&gt; condition being irrelevant</div>
<div>=A0 =A0 =A0</div><div>=A0 =A07. =A0Intermediaries . . . . . . . . . . =
. . . . . . . . . . . . . . 13</div><div>=A0 =A0</div><div>=A0&gt; good, bu=
t could use some commentary that if the intermediaries are</div><div>=A0&gt=
; not aware of the opening handshake, then they should make no</div>
<div>=A0&gt; modifications to the frames. =A0See [Section 5.4] of [RFC6455]=
</div><div>=A0&gt; 3rd paragraph for similar text.</div><div>=A0 =A0</div><=
div>=A0 =A08. =A0permessage-deflate extension . . . . . . . . . . . . . . .=
 . . 14</div>
<div>=A0 =A0</div><div>=A0&gt; OK, some suggestions on how to clean this se=
ction up.</div><div>=A0&gt;</div><div>=A0&gt; Introduce the 4 extension par=
ameters first.</div><div>=A0&gt;</div><div>=A0&gt; =A0 Use the language fou=
nd elsewhere in the spec now about the asymmetric=A0</div>
<div>=A0&gt; =A0 nature of the extension parameter configuration.</div><div=
>=A0&gt; =A0=A0</div><div>=A0&gt; =A0 The following 2 extension parameters =
control the behavior of the</div><div>=A0&gt; =A0 deflate configuration for=
 Client-to-Server messages:</div>
<div>=A0&gt; =A0 (We took this notation from the title of [Section 5.3] of =
[RFC-6455],</div><div>=A0&gt; =A0 =A0including the capitalization)</div><di=
v>=A0&gt;</div><div>=A0&gt; =A0 =A0 o =A0&quot;c2s_no_context_takeover&quot=
;</div><div>=A0&gt; =A0 =A0 o =A0&quot;c2s_max_window_bits&quot;</div>
<div>=A0&gt;</div><div>=A0&gt; =A0 The following 2 extension parameters con=
trol the behavior of the</div><div>=A0&gt; =A0 deflate configuration for Se=
rver-to-Client messages:</div><div>=A0&gt;</div><div>=A0&gt; =A0 =A0 o =A0&=
quot;s2c_no_context_takeover&quot;</div>
<div>=A0&gt; =A0 =A0 o =A0&quot;s2c_max_window_bits&quot;</div><div>=A0&gt;=
</div><div>=A0&gt; Then describe how the Offer works. (essentially the lang=
uage you</div><div>=A0&gt; have now in the doc, with careful attention to n=
ot mix your intro</div>
<div>=A0&gt; and then bullets)</div><div>=A0&gt; =A0 =A0Request: desired cl=
ient behavior + desired server behavior</div><div>=A0&gt; =A0 =A0Response: =
acknowledge client behavior + server chosen behavior</div><div>=A0&gt;</div=
><div>=A0&gt; Example of confusing language:</div>
<div>=A0</div><div>=A0 =A0For an offer for this extension, the following 4 =
extension parameters</div><div>=A0 =A0are defined. =A0If needed to distingu=
ish from ones for a response,</div><div>=A0 =A0these parameters are called =
with a prefix &quot;client-to-server&quot;.</div>
<div><br></div><div>=A0 =A0o =A0&quot;s2c_no_context_takeover&quot;</div><d=
iv><br></div><div>=A0 =A0o =A0&quot;c2s_no_context_takeover&quot;</div><div=
><br></div><div>=A0 =A0o =A0&quot;s2c_max_window_bits&quot;</div><div><br><=
/div><div>=A0 =A0o =A0&quot;c2s_max_window_bits&quot;</div>
<div>=A0 =A0</div><div>=A0&gt; This section introduces you to &quot;client-=
to-server&quot;, then lists</div><div>=A0&gt; s2c_*, why? =A0Same for the n=
ext section, but in reverse.</div><div>=A0&gt; Don&#39;t mix the introducti=
on of the extension parameters and</div>
<div>=A0&gt; the behavior of the request and response together.</div><div>=
=A0&gt;</div><div>=A0&gt; Finally, go into the MUST rules for Client and Se=
rver like you</div><div>=A0&gt; currently have in the spec documentation.</=
div><div>
=A0&gt;</div><div>=A0&gt; Include wording for Client MUST pointing back to =
close code</div><div>=A0&gt; 1010 from [RC6455] as a recommended behavior f=
or dealing with</div><div>=A0&gt; bad extension negotiation.</div><div>=A0&=
gt; Even for things like a server saying s2c_max_window_bits=3D1024</div>
<div>=A0 =A0</div><div>=A0 =A0 =A08.1. =A0Method Parameters =A0. . . . . . =
. . . . . . . . . . . . . . 15</div><div>=A0 =A0 =A0 =A08.1.1. =A0Context T=
akeover Control . . . . . . . . . . . . . . . 15</div><div>=A0 =A0 =A0 =A0<=
/div><div>=A0&gt; Include explicit language indicating default behavior for=
</div>
<div>=A0&gt; context takeover.</div><div>=A0</div><div>=A0&gt; When documen=
ting one side, for example &quot;s2c_&quot;, do not make references</div><d=
iv>=A0&gt; to the opposite direction. =A0Its confusing, noisy, and adds no =
value.</div>
<div>=A0&gt;</div><div>=A0&gt; For example, Section 8.1.2.2. c2s_max_window=
_bits, start out talking</div><div>=A0&gt; about the c2s_max_window_bits, t=
hen has suddenly talks about=A0</div><div>=A0&gt; &quot;server-to-client pa=
rameter&quot;, mentioning behavior and server limits.</div>
<div>=A0&gt; This is confusing.</div><div>=A0&gt; Fix this, clarify it, eli=
minate the noise, or simplify it.</div><div>=A0&gt;</div><div>=A0&gt; Eg of=
 simplification:</div><div>=A0&gt;</div><div>=A0&gt; =A0See [Section 8.1.2.=
1.] &quot;s2c_max_window_bits&quot; for server side</div>
<div>=A0&gt; =A0equivalent</div><div>=A0&gt;</div><div>=A0&gt; We suspect t=
hat the use of &quot;c2s&quot; and &quot;client-to-server&quot; to=A0</div>=
<div>=A0&gt; interchangably refer to either the &quot;extension parameter t=
oken&quot; itself=A0</div>
<div>=A0&gt; or the phase of the extension negotiation (request or response=
) is</div><div>=A0&gt; the cause of the confusion.</div><div>=A0&gt;=A0</di=
v><div>=A0&gt; Either choose new terminology for the extension parameter to=
ken, or=A0</div>
<div>=A0&gt; choose new terminology for the phase of the extension negotiat=
ion</div><div>=A0&gt; (request side or response side)</div><div>=A0&gt;</di=
v><div>=A0 =A0 =A0 =A0</div><div>=A0 =A0 =A0 =A08.1.2. =A0Limiting the LZ77=
 sliding window size =A0. . . . . . . . 16</div>
<div>=A0 =A0 =A0 =A0</div><div>=A0&gt; Include explicit language indicating=
 default size for</div><div>=A0&gt; LZ77 sliding window size.</div><div>=A0=
&gt; RFC1979 seems to indicate 32KB as the maximum value, but no obvious</d=
iv><div>=A0&gt; word on what is the default behavior, assuming no window si=
ze is</div>
<div>=A0&gt; specifically declared.</div><div>=A0&gt;</div><div>=A0&gt; The=
 ABNF for the c2s_max_window_bits indicates that a digit is required,</div>=
<div>=A0&gt; but the text indicates that no value is possible.</div><div>=
=A0&gt; What does no-value mean?</div>
<div>=A0 =A0 =A0 =A0</div><div>=A0 =A0 =A0 =A08.1.3. =A0Example =A0. . . . =
. . . . . . . . . . . . . . . . . . . 18</div><div>=A0 =A0 =A0 =A0</div><di=
v>=A0&gt; See earlier commentary about no value c2s_max_window_bits extensi=
on</div><div>=A0&gt; parameter token.</div>
<div>=A0&gt; See earlier commentary about extension negotiation for example=
 #3=A0</div><div>=A0&gt; (fallback behavior written into this spec)</div><d=
iv>=A0 =A0 =A0 =A0</div><div>=A0 =A0 =A08.2. =A0Message Payload Transformat=
ion . . . . . . . . . . . . . . 19</div>
<div>=A0 =A0 =A0</div><div>=A0&gt; good=A0</div><div>=A0&gt; (one note, the=
 BFINAL logic needs to be validated in current</div><div>=A0&gt; implementa=
tions. =A0as BFINAL does not behave the same in pywebsocket,</div><div>=A0&=
gt; autobahn, chrome, and safari). =A0We had to hack BFINAL to always be</d=
iv>
<div>=A0&gt; 0 for outgoing frames from our server in order for existing</d=
iv><div>=A0&gt; client implementations to work.</div><div>=A0 =A0 =A0</div>=
<div>=A0 =A0 =A0 =A08.2.1. =A0Compression =A0. . . . . . . . . . . . . . . =
. . . . . . 19</div>
<div><br></div><div>=A0&gt; good</div><div><br></div><div>=A0 =A0 =A0 =A08.=
2.2. =A0Decompression =A0. . . . . . . . . . . . . . . . . . . . 20</div><d=
iv><br></div><div>=A0&gt; good</div><div><br></div><div>=A0 =A0 =A0 =A08.2.=
3. =A0Examples . . . . . . . . . . . . . . . . . . . . . . . 21</div>
<div>=A0 =A0 =A0 =A0</div><div>=A0&gt; Include example of multiple message =
behavior with no_context_takeover</div><div>=A0&gt; configured.</div><div>=
=A0 =A0 =A0 =A0</div><div>=A0 =A0 =A08.3. =A0Implementation Notes . . . . .=
 . . . . . . . . . . . . . . 24</div>
<div>=A0 =A0 =A0</div><div>=A0&gt; This section&#39;s updates are good.</di=
v><div>=A0&gt; The LZ77 sliding window size recommendation is ok, but where=
&#39;s the</div><div>=A0&gt; default LZ77 sliding window size?</div><div>=
=A0 =A0 =A0</div>
<div>=A0 =A0 =A08.4. =A0Intermediaries . . . . . . . . . . . . . . . . . . =
. . . . 24</div><div>=A0 =A0 =A0</div><div>=A0&gt; Isn&#39;t this section i=
dentical to [Section 7] in this same spec?</div><div><br></div><div>=A0&gt;=
 We have no comments for the remaining sections</div>
<div>=A0 =A0 =A0</div><div>=A0 =A09. =A0Security Considerations =A0. . . . =
. . . . . . . . . . . . . . . 25</div><div>=A0 =A010. IANA Considerations =
=A0. . . . . . . . . . . . . . . . . . . . . 26</div><div>=A0 =A0 =A010.1. =
Registration of the &quot;permessage-deflate&quot; WebSocket</div>
<div>=A0 =A0 =A0 =A0 =A0 =A0Extension Name . . . . . . . . . . . . . . . . =
. . . . . . 26</div><div>=A0 =A0 =A010.2. Registration of the &quot;Per-mes=
sage Compressed&quot; WebSocket</div><div>=A0 =A0 =A0 =A0 =A0 =A0Framing He=
ader Bit . . . . . . . . . . . . . . . . . . . . 26</div>
<div>=A0 =A011. Acknowledgements . . . . . . . . . . . . . . . . . . . . . =
. . 27</div><div>=A0 =A012. References . . . . . . . . . . . . . . . . . . =
. . . . . . . . 28</div><div>=A0 =A0 =A012.1. Normative References . . . . =
. . . . . . . . . . . . . . . 28</div>
<div>=A0 =A0 =A012.2. Informative References . . . . . . . . . . . . . . . =
. . . 28</div><div>=A0 =A0Author&#39;s Address . . . . . . . . . . . . . . =
. . . . . . . . . . . 29</div></div></div><div class=3D"gmail_extra"><br cl=
ear=3D"all">
<div><div dir=3D"ltr"><div>--</div><div>Joakim Erdfelt &lt;<a href=3D"mailt=
o:joakim@intalio.com" target=3D"_blank">joakim@intalio.com</a>&gt;</div><di=
v><a href=3D"http://www.webtide.com/" target=3D"_blank">webtide.com</a>=A0-=
 <a href=3D"http://intalio.com/jetty" target=3D"_blank">intalio.com/jetty</=
a></div>
<div><span>Expert advice, services and support from=A0</span><span>from the=
 Jetty &amp; CometD experts</span></div><div><a href=3D"http://eclipse.org/=
jetty/" target=3D"_blank">eclipse.org/jetty</a>=A0-=A0<a href=3D"http://com=
etd.org/" target=3D"_blank">cometd.org</a></div>
</div></div>
<br><br><div class=3D"gmail_quote">On Mon, Oct 7, 2013 at 8:47 PM, Takeshi =
Yoshino <span dir=3D"ltr">&lt;<a href=3D"mailto:tyoshino@google.com" target=
=3D"_blank">tyoshino@google.com</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">
<div dir=3D"ltr"><div>- explained why prefixes like s2c_ and c2s_ are neede=
d<br></div><div>- added short note about adjusting ZLIB/Adler-32 field<div>=
<div class=3D"h5"><br><div class=3D"gmail_extra"><br></div><div class=3D"gm=
ail_extra">
<br><div class=3D"gmail_quote">


On Tue, Oct 8, 2013 at 12:43 PM,  <span dir=3D"ltr">&lt;<a href=3D"mailto:i=
nternet-drafts@ietf.org" target=3D"_blank">internet-drafts@ietf.org</a>&gt;=
</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex">



<br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
=A0This draft is a work item of the BiDirectional or Server-Initiated HTTP =
Working Group of the IETF.<br>
<br>
=A0 =A0 =A0 =A0 Title =A0 =A0 =A0 =A0 =A0 : Compression Extensions for WebS=
ocket<br>
=A0 =A0 =A0 =A0 Author(s) =A0 =A0 =A0 : Takeshi Yoshino<br>
=A0 =A0 =A0 =A0 Filename =A0 =A0 =A0 =A0: draft-ietf-hybi-permessage-compre=
ssion-13.txt<br>
=A0 =A0 =A0 =A0 Pages =A0 =A0 =A0 =A0 =A0 : 29<br>
=A0 =A0 =A0 =A0 Date =A0 =A0 =A0 =A0 =A0 =A0: 2013-10-07<br>
<br>
Abstract:<br>
=A0 =A0This document specifies a framework for creating WebSocket extension=
s<br>
=A0 =A0that add compression functionality to the WebSocket Protocol. =A0An<=
br>
=A0 =A0extension based on this framework compresses the payload data portio=
n<br>
=A0 =A0of non-control WebSocket messages on a per-message basis using<br>
=A0 =A0parameters negotiated during the opening handshake. =A0This framewor=
k<br>
=A0 =A0provides a general method to apply a compression algorithm to the<br=
>
=A0 =A0contents of WebSocket messages. =A0For each compression algorithm, a=
n<br>
=A0 =A0extension is defined by specifying parameter negotiation and<br>
=A0 =A0compression algorithm in detail. =A0This document also specifies one=
<br>
=A0 =A0specific compression extension using the DEFLATE algorithm.<br>
<br>
=A0 =A0Please send feedback to the <a href=3D"mailto:hybi@ietf.org" target=
=3D"_blank">hybi@ietf.org</a> mailing list.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-hybi-permessage-comp=
ression" target=3D"_blank">https://datatracker.ietf.org/doc/draft-ietf-hybi=
-permessage-compression</a><br>
<br>
There&#39;s also a htmlized version available at:<br>
<a href=3D"http://tools.ietf.org/html/draft-ietf-hybi-permessage-compressio=
n-13" target=3D"_blank">http://tools.ietf.org/html/draft-ietf-hybi-permessa=
ge-compression-13</a><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-hybi-permessage-co=
mpression-13" target=3D"_blank">http://www.ietf.org/rfcdiff?url2=3Ddraft-ie=
tf-hybi-permessage-compression-13</a><br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" target=3D"_blank">ftp://ftp=
.ietf.org/internet-drafts/</a><br>
<br>
_______________________________________________<br>
hybi mailing list<br>
<a href=3D"mailto:hybi@ietf.org" target=3D"_blank">hybi@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/hybi" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/hybi</a><br>
</blockquote></div><br></div></div></div></div></div>
<br>_______________________________________________<br>
hybi mailing list<br>
<a href=3D"mailto:hybi@ietf.org">hybi@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/hybi" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/hybi</a><br>
<br></blockquote></div><br></div>

--089e01634c7c22d38804e846488c--

From tyoshino@google.com  Wed Oct  9 00:41:06 2013
Return-Path: <tyoshino@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A39E21F843F for <hybi@ietfa.amsl.com>; Wed,  9 Oct 2013 00:41:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.885
X-Spam-Level: 
X-Spam-Status: No, score=-1.885 tagged_above=-999 required=5 tests=[AWL=0.092,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hglvmiRLLdg6 for <hybi@ietfa.amsl.com>; Wed,  9 Oct 2013 00:41:05 -0700 (PDT)
Received: from mail-wi0-x22b.google.com (mail-wi0-x22b.google.com [IPv6:2a00:1450:400c:c05::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 5C0BD21E80E2 for <hybi@ietf.org>; Wed,  9 Oct 2013 00:40:52 -0700 (PDT)
Received: by mail-wi0-f171.google.com with SMTP id hm2so7865508wib.16 for <hybi@ietf.org>; Wed, 09 Oct 2013 00:40:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=9Cj3Qe+TM7sOcUtIs+057Fw1JhBdNLXpdE6DojG3WGI=; b=pjJKHhoithdWuAti8Rqzza1u56IyjeMVUDcgQlN6aWrIFaqNFflCOCu2vf7Vu9j39n hIS3D7NVnGpKMFMSRvZ4tofGWlq9SA14oO9mRiUdcnLcx0M6eFnUKaroL9ZSwXoxLBGs gU1g4+YOeVB6vMIXY3wxzgkIrGDkgcdkzqX6efOu+BlfbYQ5VihZ0w3vtWKFYCaqt4sP GrH2yhveIQmt6nJSPoIZVBdRRYinnliMJ+Y+AD6GeicW19FIEMzX05VtpAlTrDpH+cil 61265jXfDrUpJ7H3rfBwCyoaxCvWd7rWXoIx/iu/Qezmx60Pu7G6b8whxCN884G3LMma Dy+w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=9Cj3Qe+TM7sOcUtIs+057Fw1JhBdNLXpdE6DojG3WGI=; b=VNHa2+dcs7AmXXXIJt1Vw9UZv1WlBrkVyE3NjAIs6Vk0P9zh8WuCf7VZTKnWKtICuU QN5Iny/gNHiYt10SyFBnXj134FMXUY6VCd5/H5MeEDxRCpzCjbxW6YQxn/82bHxCdpff h5uU13alfjX0MtLw+DNYlHk9C7aOQZSca9B7WSgUaj5iYW9JERWZXagVIZLhGD4dqYWs htBYDYuhn1prIUcS1nivwb0aiSL88B/fIP89zAypBOaiYxvet0e+6pLyThMajUvWgVJA gqcU7ZgtTHeadzOPZBmhfa8S6V0h9wqVoG5jkDeNKMlf8U2Wlx2ngWiSYwrTtDUwMYTO SNMw==
X-Gm-Message-State: ALoCoQk0FZQYK/2TSBOF5cPl1tUd52MyVhMhviIlRmNFWGSB9K/p0A6gQxkqDCKlGu4YXK4NBCgn69f149XDUgcwEVMTQ7ICxnVBeux7E90b+afR+892EuNsw47no1Hn7EgSjwn+dUN8pvu9CdwqBp5lpSsN0jEyZm+VSQbb+XboNj768Nsj+m6mVnPqHqlGhRTPp25s3M+g
X-Received: by 10.180.89.98 with SMTP id bn2mr1441147wib.42.1381304450389; Wed, 09 Oct 2013 00:40:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.15.133 with HTTP; Wed, 9 Oct 2013 00:40:30 -0700 (PDT)
In-Reply-To: <CAG4zZZC2umzmq2vXPJGmR5+hZuRiRO7BN+9via8dBK7Og4XhBg@mail.gmail.com>
References: <20131008034344.3492.4171.idtracker@ietfa.amsl.com> <CAH9hSJZKwBhmMg5jAa1U93g+Q1Hfv0nRDx=m_ZAbj-oi=_Ba7g@mail.gmail.com> <CAG4zZZC2umzmq2vXPJGmR5+hZuRiRO7BN+9via8dBK7Og4XhBg@mail.gmail.com>
From: Takeshi Yoshino <tyoshino@google.com>
Date: Wed, 9 Oct 2013 16:40:30 +0900
Message-ID: <CAH9hSJaC6cK_cDypjiOGOG1Nf6Pm6qng=Qz=59KaT8vyvfo-fA@mail.gmail.com>
To: Joakim Erdfelt <joakim@intalio.com>
Content-Type: multipart/alternative; boundary=f46d04447fbb17b6a904e84a018f
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] I-D Action: draft-ietf-hybi-permessage-compression-13.txt
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 09 Oct 2013 07:41:06 -0000

--f46d04447fbb17b6a904e84a018f
Content-Type: text/plain; charset=ISO-8859-1

Thank you for careful review. I'll address them.

Some questions.


On Wed, Oct 9, 2013 at 12:14 PM, Joakim Erdfelt <joakim@intalio.com> wrote:

>  > what is this trying to say?
>  > starts out by saying that a new key phrase "agreed parameters" is
>  > a mandatory representation of all parameters that can determine
>  > the behavior of incoming vs outgoing frames.  Then it adds on the
>  > confusing part about about the parameters being unnessary to use
>  > to identify which offer has been accepted.  That's counter to
>  > how this extension works later in the same document, even the
>  > example in same paragraph.
>

How about

"Agreed parameters" MUST represent how the requests and hints in the
client's offer have been handled in addition to the server's requests and
hints on the client's behavior, so that the client can configure its
behavior without identifying which PMCE offer has been accepted.


>
>    For example, if a client
>    sends an offer with a parameter "enable_compression" and another
>    without the parameter, the server accepts the former by sending back
>    an element including a parameter that acknowledges
>    "enable_compression".  The name of the acknowledging parameter
>    doesn't need to be the same as the offer.
>
>  > to put this another way, like the example hints at.
>  > the client makes an offer, identifying 2 sets of parameters.
>  > how it wants to talk to server, and how it wants the server to
>  > talk to it.
>  > the server will use the stated client side configuration/behavior,
>  > if it can, (otherwise it doesn't negotiate the extension), and
>  > then make a determination of its own configuration/behavior,
>  > based on hints provided in the client request extension /
>  > negotiation, and respond to the extension negotiation with
>  > how it is expecting the client communications and how it
>  > will communicate to the client.  If the client doesn't like
>  > it, then the client closes with close code 1010.
>

Thanks for the suggestion. Made some rephrasing. Please take a look:

----

Though how to handle parameters in detail will be specified in the
specifications for each PMCEs, general negotiation flow will be like this:

A client makes an offer including parameters identifying the followings:
- Hints about how the client is planning to compress data
- Requests about how the server compresses data
- Limitation of the client's compression functionality

The peer server uses these parameters, makes a determination of its
behavior based on them if it can and wants to proceed with this PMCE
enabled, and responds to the client with parameters identifying the
followings:
- Requests about how the client compresses data
- How the server will compress data

The client uses these parameters from the server make a determination of
its behavior based on them if it can and wants to proceed.
Otherwise, the client starts closing handshake with close code 1010.

----


>  > We see the new language for s2c_ and c2s_, but still think these are
>  > awful choices, and will point out why this language just adds to the
>  > confusion later in the spec.
>
>  > The added language about the directionality is useful.
>
>  > Since all websocket communications are initiated by client to server
>  > these should just be s/s2c_/server_/g and s/c2s_/client_/g
>

Initially, I thought like this: Each client does both compression and
decompression. Their compression parameters can differ. So, it'd be better
prefixing them with explicit words about direction (or together with words
like _trasmitted or _outgoing. I.e. server_transmitted, client_transmitted,
server_outgoing, server_incoming).

But looking at them again, I see that it's not so unclear that they're
about compressing operation.

I'm fine with that renaming.


>           permessage-foo; use_y, permessage-foo
>
>  > suggest eliminating this entirely.
>  > we believe this to be an improper interpretation of the extension
>  > rules in RFC6455.
>  > Basically, Extensions should not be aware of each other, but rather
>  > have some rules that apply equally to all extensions in a consistent
>  > behavior.
>

Are you suggesting that we drop the feature of multiple configuration
offering?


>   > If we have extensions that need to be aware of each other in order
>  > to know if they can run or not, then you put the burden of all
>  > future extensions to be aware of all other extensions.
>

I agree that without some O(n)-like rule, it's very hard to resolve
conflict of extensions. In pywebsocket, we experienced that, yes.


>   > If an offer arrives with all of these ..
>  >   Sec-WebSocket-Extension: interleaving, metadata, gpgsig,
> permessage-deflate
>  >
>  > What should the base RFC6455 do to negotiate this?
>  >   1) one path would be to not respond with metadata or
> permessage-deflate
>  >      as both declare RSV1 bit use, and that's a conflict.  This is the
>  >      behavior outlined in RFC6455, but the reasons for conflict are lost
>  >      as theres no mechanism to communicate this conflict.
>  >   2) another path would be to fail the handshake with an HTTP response
> code 400
>  >      with details about the conflict.
>  >   3) a first-to-file approach could also be used, and if there is a RSV1
>  >      conflict, the first one in the offer to declare it is the one that
>  >      will be used, and all subsequent RSV1 declarations will not be
> used.
>  >   4) extension spec specific fallback behavior (as outlined in the
>  >      current permessage-deflate spec)
>  >      This is a variation to the first-to-file approach, but instead of
>  >      first to file, its first to negotiate successfully, causing all
>  >      downstream conflicting extensions to never be negotiated.
>  >
>  > You might be leaning towards #3 or #4, but wait!  Mux changes the rules
> again.
>  > If during mux you see an offer like this ...
>  >   Sec-WebSocket-Extension: metadata, mux, permessage-deflate
>  > Then the physical connection will be using metadata, and the
>  > all of the virtual connection (channels) will be using
> permessage-deflate.
>

Yes, handling of mux is complex...

I thought that it's not realistic to have generalize rule but get consensus
on how to handle special extensions such as mux e.g. mux needs to be
resolved first.

Except for such special things, basically resolution should happen based on
combination of (3) and (4) ((4) only inside subgroup like a set of PMCEs
listed in sequence) and the client should be aware of that to decide the
order of offers properly.


>
>  > Now, to go back to the example in the spec documentation.
>  >    permessage-foo; use_y, permessage-foo
>

As far as PMCEs are grouped together, it should be easy to resolve between
them and choose one.

--f46d04447fbb17b6a904e84a018f
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra">Thank you for careful review. I=
&#39;ll address them.</div><div class=3D"gmail_extra"><br></div><div class=
=3D"gmail_extra">Some questions.</div><div class=3D"gmail_extra"><br><br><d=
iv class=3D"gmail_quote">

On Wed, Oct 9, 2013 at 12:14 PM, Joakim Erdfelt <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:joakim@intalio.com" target=3D"_blank">joakim@intalio.com</a>&g=
t;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0=
px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);borde=
r-left-style:solid;padding-left:1ex">

<div dir=3D"ltr"><div><div>=A0&gt; what is this trying to say?</div><div>=
=A0&gt; starts out by saying that a new key phrase &quot;agreed parameters&=
quot; is</div><div>=A0&gt; a mandatory representation of all parameters tha=
t can determine</div>


<div>=A0&gt; the behavior of incoming vs outgoing frames. =A0Then it adds o=
n the</div><div>=A0&gt; confusing part about about the parameters being unn=
essary to use</div><div>=A0&gt; to identify which offer has been accepted. =
=A0That&#39;s counter to</div>


<div>=A0&gt; how this extension works later in the same document, even the<=
/div><div>=A0&gt; example in same paragraph.</div><div></div></div></div></=
blockquote><div><br></div><div>How about</div><div><br></div><div>&quot;Agr=
eed parameters&quot; MUST represent how the requests and hints in the clien=
t&#39;s offer have been handled in addition to the server&#39;s requests an=
d hints on the client&#39;s behavior, so that the client can configure its =
behavior without identifying which PMCE offer has been accepted.</div>

<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left=
-style:solid;padding-left:1ex"><div dir=3D"ltr"><div><div>=A0</div><div>=A0=
 =A0For example, if a client</div>

<div>=A0 =A0sends an offer with a parameter &quot;enable_compression&quot; =
and another</div>
<div>=A0 =A0without the parameter, the server accepts the former by sending=
 back</div><div>=A0 =A0an element including a parameter that acknowledges</=
div><div>=A0 =A0&quot;enable_compression&quot;. =A0The name of the acknowle=
dging parameter</div>


<div>=A0 =A0doesn&#39;t need to be the same as the offer.</div><div>=A0</di=
v><div>=A0&gt; to put this another way, like the example hints at.</div><di=
v>=A0&gt; the client makes an offer, identifying 2 sets of parameters.</div=
><div>


=A0&gt; how it wants to talk to server, and how it wants the server to</div=
><div>=A0&gt; talk to it.</div><div>=A0&gt; the server will use the stated =
client side configuration/behavior,</div><div>=A0&gt; if it can, (otherwise=
 it doesn&#39;t negotiate the extension), and</div>


<div>=A0&gt; then make a determination of its own configuration/behavior,</=
div><div>=A0&gt; based on hints provided in the client request extension /<=
/div><div>=A0&gt; negotiation, and respond to the extension negotiation wit=
h</div>


<div>=A0&gt; how it is expecting the client communications and how it</div>=
<div>=A0&gt; will communicate to the client. =A0If the client doesn&#39;t l=
ike</div><div>=A0&gt; it, then the client closes with close code 1010.</div=
><div>


</div></div></div></blockquote><div><br></div><div>Thanks for the suggestio=
n. Made some rephrasing. Please take a look:</div><div><br></div><div>----<=
/div><div><br></div><div>Though how to handle parameters in detail will be =
specified in the specifications for each PMCEs, general negotiation flow wi=
ll be like this:</div>

<div><br></div><div>A client makes an offer including parameters identifyin=
g the followings:<br></div><div>- Hints about how the client is planning to=
 compress data</div><div>- Requests about how the server compresses data</d=
iv>

<div>- Limitation of the client&#39;s compression functionality</div><div><=
br></div><div>The peer server uses these parameters, makes a determination =
of its behavior based on them if it can and wants to proceed with this PMCE=
 enabled, and responds to the client with parameters identifying the follow=
ings:</div>

<div>- Requests about how the client compresses data</div><div>- How the se=
rver will compress data</div><div><br></div><div>The client uses these para=
meters from the server make a determination of its behavior based on them i=
f it can and wants to proceed.</div>

<div>Otherwise, the client starts closing handshake with close code 1010.</=
div><div><br></div><div>----</div><div>=A0</div><blockquote class=3D"gmail_=
quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-=
color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">

<div dir=3D"ltr"><div>=A0&gt; We see the new language for s2c_ and c2s_, bu=
t still think these are</div>
<div>=A0&gt; awful choices, and will point out why this language just adds =
to the</div><div>=A0&gt; confusion later in the spec.</div><div>=A0</div><d=
iv>=A0&gt; The added language about the directionality is useful.</div><div=
>=A0</div>


<div>=A0&gt; Since all websocket communications are initiated by client to =
server</div><div>=A0&gt; these should just be s/s2c_/server_/g and s/c2s_/c=
lient_/g=A0</div></div></blockquote><div><br></div><div>Initially, I though=
t like this: Each client does both compression and decompression. Their com=
pression parameters can differ. So, it&#39;d be better prefixing them with =
explicit words about direction (or together with words like _trasmitted or =
_outgoing. I.e. server_transmitted, client_transmitted, server_outgoing, se=
rver_incoming).</div>

<div><br></div><div>But looking at them again, I see that it&#39;s not so u=
nclear that they&#39;re about compressing operation.</div><div><br></div><d=
iv>I&#39;m fine with that renaming.</div><div>=A0</div><blockquote class=3D=
"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;borde=
r-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">

<div dir=3D"ltr"><div>=A0 =A0 =A0 =A0 =A0 permessage-foo; use_y, permessage=
-foo<br></div><div>=A0 =A0 =A0 =A0 =A0=A0</div><div>=A0&gt; suggest elimina=
ting this entirely.</div><div>=A0&gt; we believe this to be an improper int=
erpretation of the extension</div>


<div>=A0&gt; rules in RFC6455.</div><div>=A0&gt; Basically, Extensions shou=
ld not be aware of each other, but rather</div><div>=A0&gt; have some rules=
 that apply equally to all extensions in a consistent</div><div>=A0&gt; beh=
avior.</div>

</div></blockquote><div><br></div><div>Are you suggesting that we drop the =
feature of multiple configuration offering?</div><div>=A0</div><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1=
px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:=
1ex">

<div dir=3D"ltr">
<div>=A0&gt; If we have extensions that need to be aware of each other in o=
rder</div><div>=A0&gt; to know if they can run or not, then you put the bur=
den of all</div><div>=A0&gt; future extensions to be aware of all other ext=
ensions.</div>

</div></blockquote><div><br></div><div>I agree that without some O(n)-like =
rule, it&#39;s very hard to resolve conflict of extensions. In pywebsocket,=
 we experienced that, yes.</div><div>=A0</div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-co=
lor:rgb(204,204,204);border-left-style:solid;padding-left:1ex">

<div dir=3D"ltr">
<div>=A0&gt; If an offer arrives with all of these ..<br></div><div>=A0&gt;=
 =A0 Sec-WebSocket-Extension: interleaving, metadata, gpgsig, permessage-de=
flate</div>
<div>=A0&gt;</div><div>=A0&gt; What should the base RFC6455 do to negotiate=
 this?</div><div>=A0&gt; =A0 1) one path would be to not respond with metad=
ata or permessage-deflate</div><div>=A0&gt; =A0 =A0 =A0as both declare RSV1=
 bit use, and that&#39;s a conflict. =A0This is the</div>


<div>=A0&gt; =A0 =A0 =A0behavior outlined in RFC6455, but the reasons for c=
onflict are lost</div><div>=A0&gt; =A0 =A0 =A0as theres no mechanism to com=
municate this conflict.</div><div>=A0&gt; =A0 2) another path would be to f=
ail the handshake with an HTTP response code 400</div>


<div>=A0&gt; =A0 =A0 =A0with details about the conflict.</div><div>=A0&gt; =
=A0 3) a first-to-file approach could also be used, and if there is a RSV1<=
/div><div>=A0&gt; =A0 =A0 =A0conflict, the first one in the offer to declar=
e it is the one that</div>


<div>=A0&gt; =A0 =A0 =A0will be used, and all subsequent RSV1 declarations =
will not be used.</div><div>=A0&gt; =A0 4) extension spec specific fallback=
 behavior (as outlined in the=A0</div><div>=A0&gt; =A0 =A0 =A0current perme=
ssage-deflate spec)</div>


<div>=A0&gt; =A0 =A0 =A0This is a variation to the first-to-file approach, =
but instead of</div><div>=A0&gt; =A0 =A0 =A0first to file, its first to neg=
otiate successfully, causing all</div><div>=A0&gt; =A0 =A0 =A0downstream co=
nflicting extensions to never be negotiated.</div>


<div>=A0&gt; =A0 =A0 =A0</div><div>=A0&gt; You might be leaning towards #3 =
or #4, but wait! =A0Mux changes the rules again.</div><div>=A0&gt; If durin=
g mux you see an offer like this ...</div><div>=A0&gt; =A0 Sec-WebSocket-Ex=
tension: metadata, mux, permessage-deflate</div>


<div>=A0&gt; Then the physical connection will be using metadata, and the</=
div><div>=A0&gt; all of the virtual connection (channels) will be using per=
message-deflate.</div></div></blockquote><div><br></div><div>Yes, handling =
of mux is complex...</div>

<div><br></div><div>I thought that it&#39;s not realistic to have generaliz=
e rule but get consensus on how to handle special extensions such as mux e.=
g. mux needs to be resolved first.</div><div><br></div><div>Except for such=
 special things, basically resolution should happen based on combination of=
 (3) and (4) ((4) only inside subgroup like a set of PMCEs listed in sequen=
ce) and the client should be aware of that to decide the order of offers pr=
operly.</div>

<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left=
-style:solid;padding-left:1ex"><div dir=3D"ltr"><div><br></div><div>=A0&gt;=
 Now, to go back to the example in the spec documentation.</div>


<div>=A0&gt; =A0 =A0permessage-foo; use_y, permessage-foo</div></div></bloc=
kquote><div><br></div><div>As far as PMCEs are grouped together, it should =
be easy to resolve between them and choose one.</div><div>=A0</div></div></=
div>

</div>

--f46d04447fbb17b6a904e84a018f--

From tyoshino@google.com  Wed Oct  9 01:07:01 2013
Return-Path: <tyoshino@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BEBE321E80F5 for <hybi@ietfa.amsl.com>; Wed,  9 Oct 2013 01:07:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level: 
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[AWL=0.081,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UnU+gxh2g3RW for <hybi@ietfa.amsl.com>; Wed,  9 Oct 2013 01:07:01 -0700 (PDT)
Received: from mail-wg0-x22b.google.com (mail-wg0-x22b.google.com [IPv6:2a00:1450:400c:c00::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 0EB8321E80E2 for <hybi@ietf.org>; Wed,  9 Oct 2013 01:06:55 -0700 (PDT)
Received: by mail-wg0-f43.google.com with SMTP id y10so467331wgg.10 for <hybi@ietf.org>; Wed, 09 Oct 2013 01:06:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=v9YYl6NnTI/7ROeNM4r9lHguN2LbWHGHRYSwFRhpJiE=; b=bpNTJeAUr8pt0f16UO126nkIkc6L8yyJHPiRKptRzLsE56ptsBoZsNsd0kvUKVk4FQ mFRkDFlbLFFspvqIhdhtEZfZtUwrvLYVCh7A8PTfR3SlOtYl6C5FPXDmqXeBIHZk16H8 ON5dh66vCKGyeMovX3ciPo96wamfYKO/TlN0jBk8AeNn/zsOIK8qH7zB2BhQ45HFrt/z IXbMucbNirstZMFLkS8jghnfK4VNNOkpTEN1PNHp+33dj5W2ltu1+Kk+IWlWILWlhMyK SPApNW5+FeivcC1SJvwGFT06mWQgd7RuvgJXTAx3nqEKvnqiOmtyGlR/3B9ywF6/zf/+ XEPg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-type; bh=v9YYl6NnTI/7ROeNM4r9lHguN2LbWHGHRYSwFRhpJiE=; b=MdZqtMCUSVFS38Bs39dW3zSrIKCdTjITLOGW0T1SXluALuVfiNqZntB2uqsFxfwJkH Kr+/nCZLO7ostIuxWzoO1bZHPPvxa74MW4yMg7qeZnQNmK9puTs0aurpVxwBlJUTBR7i 1FJABcjJv7o/PW7Kq9rz1Q523xE4l6Bwpgcd9F/fbwRNUUjkuQKSGTa/gR8vg118VQby 39yKSdQrNW4aW79Dbi1npEMA0A/SBcX7jeNNXYf30p41SYtwHJL8y+p8+v8kId0LVxTK VCo8rFXT/w0/EgAhjzwsUFG8+BT1a+kD2U+qNyVd08/CrB9nNn9MNk5flvkBpDpl12x/ gSmQ==
X-Gm-Message-State: ALoCoQmNGHqMi4Amq4tqUijpUNGJurg0baUOSlbzKpJ+UiN9BPfygL3ZZGAvbC2/9ul6Vg6dwhmlfXzoB8fvDLwPOk6QsTqqPFd/MGeOGvsgfuKai5flNSMpDrYg4HsYryu14l0a8dLq/JCROeJ2vXEjMnVT3KR5Bl39VnCdI/HcR2gbDKzm2r4lUp0GWa+FsUyDDLoYCnct
X-Received: by 10.180.89.98 with SMTP id bn2mr1535717wib.42.1381306015089; Wed, 09 Oct 2013 01:06:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.15.133 with HTTP; Wed, 9 Oct 2013 01:06:35 -0700 (PDT)
From: Takeshi Yoshino <tyoshino@google.com>
Date: Wed, 9 Oct 2013 17:06:35 +0900
Message-ID: <CAH9hSJant3VBw0FBM69V9wPvi3WmJLikZdX4ySELy+CShgoOKA@mail.gmail.com>
To: "hybi@ietf.org" <hybi@ietf.org>
Content-Type: multipart/alternative; boundary=f46d04447fbb5b23df04e84a5edb
Subject: [hybi] [permessage-deflate] Renaming s2c_ and c2s_ prefix to server_ and client_
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 09 Oct 2013 08:07:02 -0000

--f46d04447fbb5b23df04e84a5edb
Content-Type: text/plain; charset=ISO-8859-1

(Splitting into an independent thread)

Joakim suggested that we should rename them.
http://www.ietf.org/mail-archive/web/hybi/current/msg10201.html
 > Since all websocket communications are initiated by client to server
 > these should just be s/s2c_/server_/g and s/c2s_/client_/g

Initially, I chose these prefixes to make it easy to understand that
they're attributes for each direction by including source and destination
explicitly. But server_ and client_ are not so confusing, too. As these
parameters are request about the peer's output, everyone should understand
X_no_context_takeover and X_max_window_bits as parameters instructing
compressor of X.

If we do this, we should do this right now. I don't have strong opinion
about this change. If there's no objection, I'll take it.

--f46d04447fbb5b23df04e84a5edb
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>(Splitting into an independent thread)</div><div><br>=
</div>Joakim suggested that we should rename them.
<div><a href=3D"http://www.ietf.org/mail-archive/web/hybi/current/msg10201.=
html">http://www.ietf.org/mail-archive/web/hybi/current/msg10201.html</a><b=
r></div><div><div><div>=A0&gt; Since all websocket communications are initi=
ated by client to server</div>

<div>=A0&gt; these should just be s/s2c_/server_/g and s/c2s_/client_/g</di=
v></div></div><div><br></div><div><div>Initially, I chose these prefixes to=
 make it easy to understand that they&#39;re attributes for each direction =
by including source and destination explicitly. But server_ and client_ are=
 not so confusing, too. As these parameters are request about the peer&#39;=
s output, everyone should understand X_no_context_takeover and X_max_window=
_bits as parameters instructing compressor of X.</div>

</div><div><br></div><div>If we do this, we should do this right now. I don=
&#39;t have strong opinion about this change. If there&#39;s no objection, =
I&#39;ll take it.</div><div><br></div></div>

--f46d04447fbb5b23df04e84a5edb--

From tobias.oberstein@tavendo.de  Wed Oct  9 01:14:43 2013
Return-Path: <tobias.oberstein@tavendo.de>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6A8721F9E80 for <hybi@ietfa.amsl.com>; Wed,  9 Oct 2013 01:14:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1OY19WtxMst3 for <hybi@ietfa.amsl.com>; Wed,  9 Oct 2013 01:14:38 -0700 (PDT)
Received: from EXHUB020-4.exch020.serverdata.net (exhub020-4.exch020.serverdata.net [206.225.164.31]) by ietfa.amsl.com (Postfix) with ESMTP id 4BE0211E814E for <hybi@ietf.org>; Wed,  9 Oct 2013 01:14:32 -0700 (PDT)
Received: from EXVMBX020-12.exch020.serverdata.net ([169.254.3.210]) by EXHUB020-4.exch020.serverdata.net ([206.225.164.31]) with mapi; Wed, 9 Oct 2013 01:14:31 -0700
From: Tobias Oberstein <tobias.oberstein@tavendo.de>
To: Takeshi Yoshino <tyoshino@google.com>, "hybi@ietf.org" <hybi@ietf.org>
Date: Wed, 9 Oct 2013 01:14:25 -0700
Thread-Topic: [hybi] [permessage-deflate] Renaming s2c_ and c2s_ prefix to server_ and client_
Thread-Index: Ac7ExozKXxqJ7NJtQb614Lr8H94wRgAAHUMw
Message-ID: <634914A010D0B943A035D226786325D44468A0021B@EXVMBX020-12.exch020.serverdata.net>
References: <CAH9hSJant3VBw0FBM69V9wPvi3WmJLikZdX4ySELy+CShgoOKA@mail.gmail.com>
In-Reply-To: <CAH9hSJant3VBw0FBM69V9wPvi3WmJLikZdX4ySELy+CShgoOKA@mail.gmail.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: multipart/alternative; boundary="_000_634914A010D0B943A035D226786325D44468A0021BEXVMBX02012ex_"
MIME-Version: 1.0
Subject: Re: [hybi] [permessage-deflate] Renaming s2c_ and c2s_ prefix to	server_ and client_
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 09 Oct 2013 08:14:43 -0000

--_000_634914A010D0B943A035D226786325D44468A0021BEXVMBX02012ex_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I have no strong opinion either. But if we change, then now (before Chrome =
gets shipped with compression enabled ..)

/Tobias

Von: hybi-bounces@ietf.org [mailto:hybi-bounces@ietf.org] Im Auftrag von Ta=
keshi Yoshino
Gesendet: Mittwoch, 9. Oktober 2013 10:07
An: hybi@ietf.org
Betreff: [hybi] [permessage-deflate] Renaming s2c_ and c2s_ prefix to serve=
r_ and client_

(Splitting into an independent thread)

Joakim suggested that we should rename them.
http://www.ietf.org/mail-archive/web/hybi/current/msg10201.html
 > Since all websocket communications are initiated by client to server
 > these should just be s/s2c_/server_/g and s/c2s_/client_/g

Initially, I chose these prefixes to make it easy to understand that they'r=
e attributes for each direction by including source and destination explici=
tly. But server_ and client_ are not so confusing, too. As these parameters=
 are request about the peer's output, everyone should understand X_no_conte=
xt_takeover and X_max_window_bits as parameters instructing compressor of X=
.

If we do this, we should do this right now. I don't have strong opinion abo=
ut this change. If there's no objection, I'll take it.


--_000_634914A010D0B943A035D226786325D44468A0021BEXVMBX02012ex_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV=3D"Content-Type" CONTENT=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.E-MailFormatvorlage17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DDE link=3Dblue vlink=
=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'fon=
t-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-=
language:EN-US'>I have no strong opinion either. But if we change, then now=
 (before Chrome gets shipped with compression enabled ..)<o:p></o:p></span>=
</p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calib=
ri","sans-serif";color:#1F497D;mso-fareast-language:EN-US'><o:p>&nbsp;</o:p=
></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-famil=
y:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US'>/Tobias<=
o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;f=
ont-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US'=
><o:p>&nbsp;</o:p></span></p><div style=3D'border:none;border-left:solid bl=
ue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div style=3D'border:none;border-t=
op:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><=
span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Von:</sp=
an></b><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>=
 hybi-bounces@ietf.org [mailto:hybi-bounces@ietf.org] <b>Im Auftrag von </b=
>Takeshi Yoshino<br><b>Gesendet:</b> Mittwoch, 9. Oktober 2013 10:07<br><b>=
An:</b> hybi@ietf.org<br><b>Betreff:</b> [hybi] [permessage-deflate] Renami=
ng s2c_ and c2s_ prefix to server_ and client_<o:p></o:p></span></p></div><=
/div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><p class=3DMsoNorm=
al>(Splitting into an independent thread)<o:p></o:p></p></div><div><p class=
=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal>Joakim suggest=
ed that we should rename them. <o:p></o:p></p><div><p class=3DMsoNormal><a =
href=3D"http://www.ietf.org/mail-archive/web/hybi/current/msg10201.html">ht=
tp://www.ietf.org/mail-archive/web/hybi/current/msg10201.html</a><o:p></o:p=
></p></div><div><div><div><p class=3DMsoNormal>&nbsp;&gt; Since all websock=
et communications are initiated by client to server<o:p></o:p></p></div><di=
v><p class=3DMsoNormal>&nbsp;&gt; these should just be s/s2c_/server_/g and=
 s/c2s_/client_/g<o:p></o:p></p></div></div></div><div><p class=3DMsoNormal=
><o:p>&nbsp;</o:p></p></div><div><div><p class=3DMsoNormal>Initially, I cho=
se these prefixes to make it easy to understand that they're attributes for=
 each direction by including source and destination explicitly. But server_=
 and client_ are not so confusing, too. As these parameters are request abo=
ut the peer's output, everyone should understand X_no_context_takeover and =
X_max_window_bits as parameters instructing compressor of X.<o:p></o:p></p>=
</div></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p cl=
ass=3DMsoNormal>If we do this, we should do this right now. I don't have st=
rong opinion about this change. If there's no objection, I'll take it.<o:p>=
</o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div>=
</div></div></body></html>=

--_000_634914A010D0B943A035D226786325D44468A0021BEXVMBX02012ex_--

From webmaster@zaphoyd.com  Wed Oct  9 07:16:38 2013
Return-Path: <webmaster@zaphoyd.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E3A521E8090 for <hybi@ietfa.amsl.com>; Wed,  9 Oct 2013 07:16:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.595
X-Spam-Level: 
X-Spam-Status: No, score=-0.595 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, TRACKER_ID=2.003]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Iuea9a-X5BAF for <hybi@ietfa.amsl.com>; Wed,  9 Oct 2013 07:16:33 -0700 (PDT)
Received: from authsmtp00.uchicago.edu (authsmtp00.uchicago.edu [128.135.12.120]) by ietfa.amsl.com (Postfix) with ESMTP id 9B7AC11E816E for <hybi@ietf.org>; Wed,  9 Oct 2013 07:16:33 -0700 (PDT)
Received: from [10.0.1.88] (c-68-51-76-178.hsd1.il.comcast.net [68.51.76.178]) (Authenticated sender: zaphoyd) by authsmtp00.uchicago.edu (Postfix) with ESMTP id 3ACC54980B0; Wed,  9 Oct 2013 09:16:24 -0500 (CDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_2A90F4C5-DF38-45A3-89EC-0C082273ECAC"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Peter Thorson <webmaster@zaphoyd.com>
In-Reply-To: <CAH9hSJant3VBw0FBM69V9wPvi3WmJLikZdX4ySELy+CShgoOKA@mail.gmail.com>
Date: Wed, 9 Oct 2013 09:16:22 -0500
Message-Id: <5BEA69BA-D0D4-4F4A-8CFB-741A433EAAA6@zaphoyd.com>
References: <CAH9hSJant3VBw0FBM69V9wPvi3WmJLikZdX4ySELy+CShgoOKA@mail.gmail.com>
To: Takeshi Yoshino <tyoshino@google.com>
X-Mailer: Apple Mail (2.1510)
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] [permessage-deflate] Renaming s2c_ and c2s_ prefix to server_ and client_
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 09 Oct 2013 14:16:38 -0000

--Apple-Mail=_2A90F4C5-DF38-45A3-89EC-0C082273ECAC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Mostly neutral here with a slight preference for s2c/c2s vs =
server_/client_ for the following reason:

server_no_context_takeover

If I am a server receiving a message does this parameter apply to me? =
well it says server.. but in fact it doesn't.
If I am a client receiving a message does this parameter apply to me? =
well it says server.. but in fact it does.

s2c_no_context_takeover

If I am a server receiving a message does this parameter apply to me? In =
the prefix, server is not in the receiving position, does not apply.
If I am a client receiving a message does this parameter apply to me? In =
the prefix, client is in the receiving position, does apply.

The original relies on the spec to encode the fact that the s and c in =
s2c are "server" and "client". The proposal relies on the spec to encode =
the fact that server_ implies server to client. I found the explicit =
mention of both ends in the parameter helpful for quickly working out =
whether a particular parameter applied to a particular piece of code =
without referencing the spec.

Whether that outweighs the initial cryptic-ness of "s2c/c2s" I don't =
have a strong opinion on. I'd prefer server_no_context_takeover to =
server_to_client_no_context_takeover. In the grand scheme of things the =
difference is minor and I'll be fine with updating WebSocket++ either =
way.

Peter

On Oct 9, 2013, at 3:06 , Takeshi Yoshino <tyoshino@google.com> wrote:

> (Splitting into an independent thread)
>=20
> Joakim suggested that we should rename them.
> http://www.ietf.org/mail-archive/web/hybi/current/msg10201.html
>  > Since all websocket communications are initiated by client to =
server
>  > these should just be s/s2c_/server_/g and s/c2s_/client_/g
>=20
> Initially, I chose these prefixes to make it easy to understand that =
they're attributes for each direction by including source and =
destination explicitly. But server_ and client_ are not so confusing, =
too. As these parameters are request about the peer's output, everyone =
should understand X_no_context_takeover and X_max_window_bits as =
parameters instructing compressor of X.
>=20
> If we do this, we should do this right now. I don't have strong =
opinion about this change. If there's no objection, I'll take it.
>=20
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi


--Apple-Mail=_2A90F4C5-DF38-45A3-89EC-0C082273ECAC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Diso-8859-1"><meta http-equiv=3D"Content-Type" =
content=3D"text/html charset=3Diso-8859-1"></head><body =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div>Mostly neutral here with a =
slight preference for s2c/c2s vs server_/client_ for the following =
reason:</div><div><br></div><div>server_no_context_takeover</div><div><br>=
</div><div>If I am a server receiving a message does this parameter =
apply to me? well it says server.. but in fact it doesn't.</div><div>If =
I am a client receiving a message does this parameter apply to me? well =
it says server.. but in fact it =
does.</div><div><br></div><div>s2c_no_context_takeover</div><div><br></div=
><div>If I am a server receiving a message does this parameter apply to =
me? In the prefix, server is not in the receiving position, does not =
apply.</div><div>If I am a client receiving a message does this =
parameter apply to me? In the prefix, client is in the receiving =
position, does apply.</div><div><br></div><div>The original relies on =
the spec to encode the fact that the s and c in s2c are "server" and =
"client". The proposal relies on the spec to encode the fact that =
server_ implies server to client. I found the explicit mention of both =
ends in the parameter helpful for quickly working out whether a =
particular parameter applied to a particular piece of code without =
referencing the spec.</div><div><br></div><div>Whether that outweighs =
the initial cryptic-ness of "s2c/c2s" I don't have a strong opinion on. =
I'd prefer server_no_context_takeover to =
server_to_client_no_context_takeover. In the grand scheme of things the =
difference is minor and I'll be fine with updating WebSocket++ either =
way.</div><div><br></div><div>Peter</div><div><br></div><div><div><div>On =
Oct 9, 2013, at 3:06 , Takeshi Yoshino &lt;<a =
href=3D"mailto:tyoshino@google.com">tyoshino@google.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div dir=3D"ltr"><div>(Splitting into an independent =
thread)</div><div><br></div>Joakim suggested that we should rename them.
<div><a =
href=3D"http://www.ietf.org/mail-archive/web/hybi/current/msg10201.html">h=
ttp://www.ietf.org/mail-archive/web/hybi/current/msg10201.html</a><br></di=
v><div><div>&nbsp;&gt; Since all websocket communications are initiated =
by client to server</div>

<div>&nbsp;&gt; these should just be s/s2c_/server_/g and =
s/c2s_/client_/g</div></div><div><br></div><div><div>Initially, I chose =
these prefixes to make it easy to understand that they're attributes for =
each direction by including source and destination explicitly. But =
server_ and client_ are not so confusing, too. As these parameters are =
request about the peer's output, everyone should understand =
X_no_context_takeover and X_max_window_bits as parameters instructing =
compressor of X.</div>

</div><div><br></div><div>If we do this, we should do this right now. I =
don't have strong opinion about this change. If there's no objection, =
I'll take it.</div><div><br></div></div>
_______________________________________________<br>hybi mailing =
list<br><a href=3D"mailto:hybi@ietf.org">hybi@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/hybi">https://www.ietf.org/m=
ailman/listinfo/hybi</a><br></blockquote></div><br></div></body></html>=

--Apple-Mail=_2A90F4C5-DF38-45A3-89EC-0C082273ECAC--

From joakim@intalio.com  Wed Oct  9 11:48:24 2013
Return-Path: <joakim@intalio.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C9CB21E817F for <hybi@ietfa.amsl.com>; Wed,  9 Oct 2013 11:48:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 01T7R+f7jvPY for <hybi@ietfa.amsl.com>; Wed,  9 Oct 2013 11:48:20 -0700 (PDT)
Received: from mail-ea0-f175.google.com (mail-ea0-f175.google.com [209.85.215.175]) by ietfa.amsl.com (Postfix) with ESMTP id 9DA2721E8183 for <hybi@ietf.org>; Wed,  9 Oct 2013 11:48:13 -0700 (PDT)
Received: by mail-ea0-f175.google.com with SMTP id m14so634475eaj.34 for <hybi@ietf.org>; Wed, 09 Oct 2013 11:48:12 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=zK9z3Q8UlESrZqV4dqF7yatvNxhDuJckz9D+/zxWDcY=; b=hO3F/6TdHEPM1hact0fYBHLsev2pWxcqZnXNEbkjiL/KsJF/xGjZXg8nPij0o0dQHI 2IG4BNq23QyzSyxSIlJSwiUXHBIEl6L9T6D9VuiUTZArubu3VhBYQuT3PVI9sWd/WdUG K923UBKbtEnQYYoGUAip87f5zog694moVAHEWRgsBCIbJtdKi5UgiLwTd1VtAz6j1FtZ qew8yEAglVMeD+1ZY3lCGQy9IWsdj9S5Lf5OdyGegmkyy3Hjxvq+3VYtqXiDDlvqTS7n URiUlITKsdSyfbBby7/6urfyeFBICdnKH3epNxBmZYPQG0nHi6vi5hC/UdS+AFmJTw0H vIqw==
X-Gm-Message-State: ALoCoQnafWr5/SEux+4F6BZByOYS9E4bUaT9RCsg7wVrdjeLrQZLQcwtC3RcMQ3n2RDM3Xfx2esa
MIME-Version: 1.0
X-Received: by 10.15.100.198 with SMTP id bn46mr13433891eeb.11.1381344492388;  Wed, 09 Oct 2013 11:48:12 -0700 (PDT)
Received: by 10.14.134.73 with HTTP; Wed, 9 Oct 2013 11:48:12 -0700 (PDT)
Date: Wed, 9 Oct 2013 11:48:12 -0700
Message-ID: <CAG4zZZAqGcVP=4P9qfo2Gm3fbPHKntwZ5aF=hDePccfKnD4kWQ@mail.gmail.com>
From: Joakim Erdfelt <joakim@intalio.com>
To: "hybi@ietf.org" <hybi@ietf.org>
Content-Type: multipart/alternative; boundary=089e0163549ec8129d04e8535380
Subject: [hybi] permessage-deflate and missing asymmetric configurations
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 09 Oct 2013 18:48:24 -0000

--089e0163549ec8129d04e8535380
Content-Type: text/plain; charset=ISO-8859-1

One important aspect missing from the asymmetric configurations for
permessage-deflate is the lack of disabling the compression.

It would be ideal to allow an asymmetric connection where, for example the
client is talking compressed, but the server is not. (or vice versa)

Why is this feature not present in the spec?


--
Joakim Erdfelt <joakim@intalio.com>
webtide.com <http://www.webtide.com/> - intalio.com/jetty
Expert advice, services and support from from the Jetty & CometD experts
eclipse.org/jetty - cometd.org

--089e0163549ec8129d04e8535380
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>One important aspect missing from the asymmetric conf=
igurations for permessage-deflate is the lack of disabling the compression.=
</div><div><br></div><div>It would be ideal to allow an asymmetric connecti=
on where, for example the client is talking compressed, but the server is n=
ot. (or vice versa)</div>
<div><br></div><div>Why is this feature not present in the spec?</div><div>=
<br></div><br clear=3D"all"><div><div dir=3D"ltr"><div>--</div><div>Joakim =
Erdfelt &lt;<a href=3D"mailto:joakim@intalio.com" target=3D"_blank">joakim@=
intalio.com</a>&gt;</div>
<div><a href=3D"http://www.webtide.com/" target=3D"_blank">webtide.com</a>=
=A0- <a href=3D"http://intalio.com/jetty" target=3D"_blank">intalio.com/jet=
ty</a></div><div><span>Expert advice, services and support from=A0</span><s=
pan>from the Jetty &amp; CometD experts</span></div>
<div><a href=3D"http://eclipse.org/jetty/" target=3D"_blank">eclipse.org/je=
tty</a>=A0-=A0<a href=3D"http://cometd.org/" target=3D"_blank">cometd.org</=
a></div></div></div>
</div>

--089e0163549ec8129d04e8535380--

From webmaster@zaphoyd.com  Wed Oct  9 12:34:21 2013
Return-Path: <webmaster@zaphoyd.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32F7C21E819F for <hybi@ietfa.amsl.com>; Wed,  9 Oct 2013 12:34:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BC6RKhtM-dwW for <hybi@ietfa.amsl.com>; Wed,  9 Oct 2013 12:34:17 -0700 (PDT)
Received: from sh78.surpasshosting.com (sh78.surpasshosting.com [72.29.64.142]) by ietfa.amsl.com (Postfix) with ESMTP id B745121E8194 for <hybi@ietf.org>; Wed,  9 Oct 2013 12:34:16 -0700 (PDT)
Received: from ranna.uchicago.edu ([128.135.45.206]:50366) by sh78.surpasshosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80.1) (envelope-from <webmaster@zaphoyd.com>) id 1VTzWR-0003LO-3h for hybi@ietf.org; Wed, 09 Oct 2013 15:34:15 -0400
From: Peter Thorson <webmaster@zaphoyd.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_AC9DD293-D990-4FB5-97F9-1749E5E61378"
Message-Id: <02030518-6F55-4E50-9AB8-06C7540C8AE1@zaphoyd.com>
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Date: Wed, 9 Oct 2013 14:34:14 -0500
References: <CAG4zZZAqGcVP=4P9qfo2Gm3fbPHKntwZ5aF=hDePccfKnD4kWQ@mail.gmail.com>
To: "hybi@ietf.org" <hybi@ietf.org>
In-Reply-To: <CAG4zZZAqGcVP=4P9qfo2Gm3fbPHKntwZ5aF=hDePccfKnD4kWQ@mail.gmail.com>
X-Mailer: Apple Mail (2.1510)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - sh78.surpasshosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - zaphoyd.com
X-Get-Message-Sender-Via: sh78.surpasshosting.com: authenticated_id: webmaster@zaphoyd.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Subject: Re: [hybi] permessage-deflate and missing asymmetric configurations
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 09 Oct 2013 19:34:21 -0000

--Apple-Mail=_AC9DD293-D990-4FB5-97F9-1749E5E61378
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

The spec allows disabling compression on a per message basis. To do what =
you describe a server could simply negotiate compression per the =
client's request then not send any compressed frames or create any =
compression contexts for itself.

There may be some additional resource savings possible if an endpoint =
knows it will never receive a compressed message. That should be =
considered at least.

On Oct 9, 2013, at 13:48 , Joakim Erdfelt <joakim@intalio.com> wrote:

> One important aspect missing from the asymmetric configurations for =
permessage-deflate is the lack of disabling the compression.
>=20
> It would be ideal to allow an asymmetric connection where, for example =
the client is talking compressed, but the server is not. (or vice versa)
>=20
> Why is this feature not present in the spec?
>=20
>=20
> --
> Joakim Erdfelt <joakim@intalio.com>
> webtide.com - intalio.com/jetty
> Expert advice, services and support from from the Jetty & CometD =
experts
> eclipse.org/jetty - cometd.org
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi


--Apple-Mail=_AC9DD293-D990-4FB5-97F9-1749E5E61378
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Diso-8859-1"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">The =
spec allows disabling compression on a per message basis. To do what you =
describe a server could simply negotiate compression per the client's =
request then not send any compressed frames or create any compression =
contexts for itself.<div><br></div><div>There may be some additional =
resource savings possible if an endpoint knows it will never receive a =
compressed message. That should be considered at =
least.</div><div><br></div><div><div>On Oct 9, 2013, at 13:48 , Joakim =
Erdfelt &lt;<a =
href=3D"mailto:joakim@intalio.com">joakim@intalio.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div dir=3D"ltr"><div>One important aspect missing from =
the asymmetric configurations for permessage-deflate is the lack of =
disabling the compression.</div><div><br></div><div>It would be ideal to =
allow an asymmetric connection where, for example the client is talking =
compressed, but the server is not. (or vice versa)</div>
<div><br></div><div>Why is this feature not present in the =
spec?</div><div><br></div><br clear=3D"all"><div><div =
dir=3D"ltr"><div>--</div><div>Joakim Erdfelt &lt;<a =
href=3D"mailto:joakim@intalio.com" =
target=3D"_blank">joakim@intalio.com</a>&gt;</div>
<div><a href=3D"http://www.webtide.com/" =
target=3D"_blank">webtide.com</a>&nbsp;- <a =
href=3D"http://intalio.com/jetty" =
target=3D"_blank">intalio.com/jetty</a></div><div><span>Expert advice, =
services and support from&nbsp;</span><span>from the Jetty &amp; CometD =
experts</span></div>
<div><a href=3D"http://eclipse.org/jetty/" =
target=3D"_blank">eclipse.org/jetty</a>&nbsp;-&nbsp;<a =
href=3D"http://cometd.org/" =
target=3D"_blank">cometd.org</a></div></div></div>
</div>
_______________________________________________<br>hybi mailing =
list<br><a =
href=3D"mailto:hybi@ietf.org">hybi@ietf.org</a><br>https://www.ietf.org/ma=
ilman/listinfo/hybi<br></blockquote></div><br></body></html>=

--Apple-Mail=_AC9DD293-D990-4FB5-97F9-1749E5E61378--

From joakim@intalio.com  Wed Oct  9 12:45:40 2013
Return-Path: <joakim@intalio.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D07F21E819A for <hybi@ietfa.amsl.com>; Wed,  9 Oct 2013 12:45:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8UueeJBSLPkU for <hybi@ietfa.amsl.com>; Wed,  9 Oct 2013 12:45:36 -0700 (PDT)
Received: from mail-ea0-f175.google.com (mail-ea0-f175.google.com [209.85.215.175]) by ietfa.amsl.com (Postfix) with ESMTP id 315B021E8195 for <hybi@ietf.org>; Wed,  9 Oct 2013 12:45:32 -0700 (PDT)
Received: by mail-ea0-f175.google.com with SMTP id m14so666157eaj.34 for <hybi@ietf.org>; Wed, 09 Oct 2013 12:45:32 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=nS+y/gDWY0B++1+khyLR5KwIEpeMthhrvdG/oM5kPoo=; b=k+OS3MoZOaA3MVMrflBH+Z5x7q/UxbASDHlA8kotYCjPTiFoBktheCSI19aTK2Gl7m 7vcEfNmk0/1A8sW2hEH02jvV4fa7tcu3TiPloHulTwp6oBmkEVbKci0pzrTjZ0iQ3Bzz aEQKPxHWmkzDpd74EEQYK48jCDWiMpW74QO/FbBhQ/3ykq43QDWS/Hsfbx8mh5JpDbNP ys32JaGoD2ycq9KgsqJJwMGgFHeVZOVxdGfDIvS1pMtHyHgvUXO6Fu5OocV29VhB1XhE xcS4XI8RNWYk5BPzKvv0iwfUut9HGuIiZFa97h7O9IoB7ID3V+heRmlPLcRhhNycCRMb oH7g==
X-Gm-Message-State: ALoCoQkxrx7VFvdB9Y/oDbbCKDwZseAkoA0QZqNHO7SU0sBndr1EY5aiF/8NbsqugYrjqVHG/6sp
MIME-Version: 1.0
X-Received: by 10.14.198.197 with SMTP id v45mr6391583een.52.1381347932078; Wed, 09 Oct 2013 12:45:32 -0700 (PDT)
Received: by 10.14.134.73 with HTTP; Wed, 9 Oct 2013 12:45:31 -0700 (PDT)
In-Reply-To: <02030518-6F55-4E50-9AB8-06C7540C8AE1@zaphoyd.com>
References: <CAG4zZZAqGcVP=4P9qfo2Gm3fbPHKntwZ5aF=hDePccfKnD4kWQ@mail.gmail.com> <02030518-6F55-4E50-9AB8-06C7540C8AE1@zaphoyd.com>
Date: Wed, 9 Oct 2013 12:45:31 -0700
Message-ID: <CAG4zZZCYkuQx40zn-wUBoeSecJ-NTDku-nD5-gkSSy-A1vhxNQ@mail.gmail.com>
From: Joakim Erdfelt <joakim@intalio.com>
To: Peter Thorson <webmaster@zaphoyd.com>
Content-Type: multipart/alternative; boundary=047d7b3a7fcacd96e604e854201b
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] permessage-deflate and missing asymmetric configurations
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 09 Oct 2013 19:45:40 -0000

--047d7b3a7fcacd96e604e854201b
Content-Type: text/plain; charset=ISO-8859-1

Was the idea of having compression level as a configurable ever on the
table?
Then we could simply state a compression level of 0, which would still
create the deflate blocks, but do no real work or effort to compress.

As for having the endpoint code control behavior inside of an extension,
that seems difficult to control or expose.
For example: do we even have the ability, in javascript on the browser, to
control the extensions that are offered? or interrogate the open connection
to know what extensions have been negotiated?


--
Joakim Erdfelt <joakim@intalio.com>
webtide.com <http://www.webtide.com/> - intalio.com/jetty
Expert advice, services and support from from the Jetty & CometD experts
eclipse.org/jetty - cometd.org


On Wed, Oct 9, 2013 at 12:34 PM, Peter Thorson <webmaster@zaphoyd.com>wrote:

> The spec allows disabling compression on a per message basis. To do what
> you describe a server could simply negotiate compression per the client's
> request then not send any compressed frames or create any compression
> contexts for itself.
>
> There may be some additional resource savings possible if an endpoint
> knows it will never receive a compressed message. That should be considered
> at least.
>
> On Oct 9, 2013, at 13:48 , Joakim Erdfelt <joakim@intalio.com> wrote:
>
> One important aspect missing from the asymmetric configurations for
> permessage-deflate is the lack of disabling the compression.
>
> It would be ideal to allow an asymmetric connection where, for example the
> client is talking compressed, but the server is not. (or vice versa)
>
> Why is this feature not present in the spec?
>
>
> --
> Joakim Erdfelt <joakim@intalio.com>
> webtide.com <http://www.webtide.com/> - intalio.com/jetty
> Expert advice, services and support from from the Jetty & CometD experts
> eclipse.org/jetty - cometd.org
>  _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi
>
>
>
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi
>
>

--047d7b3a7fcacd96e604e854201b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Was the idea of having compression level as a configurable=
 ever on the table?<div>Then we could simply state a compression level of 0=
, which would still create the deflate blocks, but do no real work or effor=
t to compress.</div>
<div><br></div><div>As for having the endpoint code control behavior inside=
 of an extension, that seems difficult to control or expose.</div><div>For =
example: do we even have the ability, in javascript on the browser, to cont=
rol the extensions that are offered? or interrogate the open connection to =
know what extensions have been negotiated?</div>
<div><br></div></div><div class=3D"gmail_extra"><br clear=3D"all"><div><div=
 dir=3D"ltr"><div>--</div><div>Joakim Erdfelt &lt;<a href=3D"mailto:joakim@=
intalio.com" target=3D"_blank">joakim@intalio.com</a>&gt;</div><div><a href=
=3D"http://www.webtide.com/" target=3D"_blank">webtide.com</a>=A0- <a href=
=3D"http://intalio.com/jetty" target=3D"_blank">intalio.com/jetty</a></div>
<div><span>Expert advice, services and support from=A0</span><span>from the=
 Jetty &amp; CometD experts</span></div><div><a href=3D"http://eclipse.org/=
jetty/" target=3D"_blank">eclipse.org/jetty</a>=A0-=A0<a href=3D"http://com=
etd.org/" target=3D"_blank">cometd.org</a></div>
</div></div>
<br><br><div class=3D"gmail_quote">On Wed, Oct 9, 2013 at 12:34 PM, Peter T=
horson <span dir=3D"ltr">&lt;<a href=3D"mailto:webmaster@zaphoyd.com" targe=
t=3D"_blank">webmaster@zaphoyd.com</a>&gt;</span> wrote:<br><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa=
dding-left:1ex">
<div style=3D"word-wrap:break-word"><div class=3D"im">The spec allows disab=
ling compression on a per message basis. To do what you describe a server c=
ould simply negotiate compression per the client&#39;s request then not sen=
d any compressed frames or create any compression contexts for itself.<div>
<br></div><div>There may be some additional resource savings possible if an=
 endpoint knows it will never receive a compressed message. That should be =
considered at least.</div><div><br></div></div><div><div class=3D"im"><div>
On Oct 9, 2013, at 13:48 , Joakim Erdfelt &lt;<a href=3D"mailto:joakim@inta=
lio.com" target=3D"_blank">joakim@intalio.com</a>&gt; wrote:</div><br></div=
><blockquote type=3D"cite"><div><div class=3D"h5"><div dir=3D"ltr"><div>One=
 important aspect missing from the asymmetric configurations for permessage=
-deflate is the lack of disabling the compression.</div>
<div><br></div><div>It would be ideal to allow an asymmetric connection whe=
re, for example the client is talking compressed, but the server is not. (o=
r vice versa)</div>
<div><br></div><div>Why is this feature not present in the spec?</div><div>=
<br></div><br clear=3D"all"><div><div dir=3D"ltr"><div>--</div><div>Joakim =
Erdfelt &lt;<a href=3D"mailto:joakim@intalio.com" target=3D"_blank">joakim@=
intalio.com</a>&gt;</div>

<div><a href=3D"http://www.webtide.com/" target=3D"_blank">webtide.com</a>=
=A0- <a href=3D"http://intalio.com/jetty" target=3D"_blank">intalio.com/jet=
ty</a></div><div><span>Expert advice, services and support from=A0</span><s=
pan>from the Jetty &amp; CometD experts</span></div>

<div><a href=3D"http://eclipse.org/jetty/" target=3D"_blank">eclipse.org/je=
tty</a>=A0-=A0<a href=3D"http://cometd.org/" target=3D"_blank">cometd.org</=
a></div></div></div>
</div></div></div><div class=3D"im">
_______________________________________________<br>hybi mailing list<br><a =
href=3D"mailto:hybi@ietf.org" target=3D"_blank">hybi@ietf.org</a><br><a hre=
f=3D"https://www.ietf.org/mailman/listinfo/hybi" target=3D"_blank">https://=
www.ietf.org/mailman/listinfo/hybi</a><br>
</div></blockquote></div><br></div><br>____________________________________=
___________<br>
hybi mailing list<br>
<a href=3D"mailto:hybi@ietf.org">hybi@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/hybi" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/hybi</a><br>
<br></blockquote></div><br></div>

--047d7b3a7fcacd96e604e854201b--

From tyoshino@google.com  Wed Oct  9 13:24:46 2013
Return-Path: <tyoshino@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22CA721E8156 for <hybi@ietfa.amsl.com>; Wed,  9 Oct 2013 13:24:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.905
X-Spam-Level: 
X-Spam-Status: No, score=-1.905 tagged_above=-999 required=5 tests=[AWL=0.072,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XwBhczfdGmIs for <hybi@ietfa.amsl.com>; Wed,  9 Oct 2013 13:24:45 -0700 (PDT)
Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) by ietfa.amsl.com (Postfix) with ESMTP id 3DE5F21E8178 for <hybi@ietf.org>; Wed,  9 Oct 2013 13:24:44 -0700 (PDT)
Received: by mail-wi0-f169.google.com with SMTP id cb5so1253979wib.2 for <hybi@ietf.org>; Wed, 09 Oct 2013 13:24:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=s+Kbqp2ykvDPy8XdoDRflg+ppHN594JKosggjJ+SwN0=; b=nhlqfiWTbQ0nI7RRAmuOM41IUsEcRIT2nnoDhdl8P6MoO3XvoDRCPpaT2WCw1/aXCy 843dftLhy5zoKC6ns/5rJKIj81OH3IK6zUIiuhMGQCjq5tyt0nLV2lNQ3hdePvAqsqHX MwBzA1fY/4bVyE2tzJVuHrQphgaFw8brB17KvJnBX053GdEM5ZuMvh35cErGG7QtNc7p 2Fty+vFFRiaGqyoqnt3IKG/QAyORXmgz+otntFlRAlTLWw0I1u61Ll75sOeUm+Byj9QQ 1W4qlEVkWNlY1t+6CEaTcReSHNH3+MYH3+C3wvXyWiQfUpxFpGqcF5Vlnd27sYZQsrve IRUg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=s+Kbqp2ykvDPy8XdoDRflg+ppHN594JKosggjJ+SwN0=; b=PsJmlXdPzbsttLFK0oGY4yPpqdCsAqoncrHhuy26pKd9nRSCOZcpaOgv31YupuBIGg ikU9YHED4N645OkJUsgqpvQHzvHt02deCJ4VRliKkq5arH3bop8vN2D8bGew6a1HAgBZ bNu2XTj4tIP2E6nG1G0G5UXtYbg7Ur9BclCHUMY40Dj9RIMzeonwDWMgC4i0VSP9ubvl FCv0us59sRyyNnjVLDI43mZlKBPwj4HJbGA8SWSs+CLG3yF9SuPExkclWqIX4LhApbwp uOGJHcMyffkTHZX7yThiaMnusA1hZNwkzuWrZuy5LfMACD7jT59BOXOaGBlnwgoVQakn zK/Q==
X-Gm-Message-State: ALoCoQlFQ0bA7kiKcGnFnhyPSWBLXZTfOuhvnZfL3TzNs7s05BLYVUneGUx/MOIzw4T9Fuc9T7lBpaWgz6DNMo9XB2rj9IJLYoUW5PcCehHxm37QI+utgU/j9EGtosVrmpfeVGORSTmsuMyBa3UZz5akxevZZ2f8AesNqTBml/VANUtV33h34gE8poScXwcS4v87Mt5V83JO
X-Received: by 10.180.89.98 with SMTP id bn2mr4360086wib.42.1381350284043; Wed, 09 Oct 2013 13:24:44 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.15.133 with HTTP; Wed, 9 Oct 2013 13:24:23 -0700 (PDT)
In-Reply-To: <CAG4zZZCYkuQx40zn-wUBoeSecJ-NTDku-nD5-gkSSy-A1vhxNQ@mail.gmail.com>
References: <CAG4zZZAqGcVP=4P9qfo2Gm3fbPHKntwZ5aF=hDePccfKnD4kWQ@mail.gmail.com> <02030518-6F55-4E50-9AB8-06C7540C8AE1@zaphoyd.com> <CAG4zZZCYkuQx40zn-wUBoeSecJ-NTDku-nD5-gkSSy-A1vhxNQ@mail.gmail.com>
From: Takeshi Yoshino <tyoshino@google.com>
Date: Thu, 10 Oct 2013 05:24:23 +0900
Message-ID: <CAH9hSJZugsZjJ7j7EoGseT9QauQ2bApK7OcWAtirCZ6b0SHwvA@mail.gmail.com>
To: Joakim Erdfelt <joakim@intalio.com>
Content-Type: multipart/alternative; boundary=f46d04447fbbfdceb404e854ac72
Cc: "hybi@ietf.org" <hybi@ietf.org>, Peter Thorson <webmaster@zaphoyd.com>
Subject: Re: [hybi] permessage-deflate and missing asymmetric configurations
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 09 Oct 2013 20:24:46 -0000

--f46d04447fbbfdceb404e854ac72
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Oct 10, 2013 at 4:45 AM, Joakim Erdfelt <joakim@intalio.com> wrote:

> Was the idea of having compression level as a configurable ever on the
> table?
>

Since each endpoint can choose any compression level as long as wbits and
context mode are negotiated, I didn't include compression level negotiation.


> Then we could simply state a compression level of 0, which would still
> create the deflate blocks, but do no real work or effort to compress.
>

IIRC, with only a few people but we reached consensus that we'll start
experimenting heuristics to choose compression on/off in UAs and also
updating API spec to allow webapps to turn on/off compression for each
message.

Adding extension parameters to turn on/off compression allows for disabling
client-to-server compression while enabling server-to-client compression
but it's per-connection level configuration. I was not sure if it's so
worthwhile to include such a halfway feature.


> As for having the endpoint code control behavior inside of an extension,
> that seems difficult to control or expose.
> For example: do we even have the ability, in javascript on the browser, to
> control the extensions that are offered? or interrogate the open connection
> to know what extensions have been negotiated?
>

Using the extensions attribute, we can know what extensions are negotiated.

Rough plan was adding some attribute or method or overloading send() method
of WebSocket to allow webapps to flip compression on/off.

--f46d04447fbbfdceb404e854ac72
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>On Thu, Oct 10, 2013 at 4:45 AM, Joakim Erdfelt <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:joakim@intalio.com" target=3D"_blank">jo=
akim@intalio.com</a>&gt;</span> wrote:<br></div><div class=3D"gmail_extra">=
<div class=3D"gmail_quote">

<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div dir=3D"ltr">Was the idea of having compression level =
as a configurable ever on the table?</div>

</blockquote><div><br></div><div>Since each endpoint can choose any compres=
sion level as long as wbits and context mode are negotiated, I didn&#39;t i=
nclude compression level negotiation.</div><div>=A0</div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;bo=
rder-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">

<div dir=3D"ltr"><div>Then we could simply state a compression level of 0, =
which would still create the deflate blocks, but do no real work or effort =
to compress.</div></div></blockquote><div><br></div><div>IIRC, with only a =
few people but we reached consensus that we&#39;ll start experimenting heur=
istics to choose compression on/off in UAs and also updating API spec to al=
low webapps to turn on/off compression for each message.</div>

<div><br></div><div>Adding extension parameters to turn on/off compression =
allows for disabling client-to-server compression while enabling server-to-=
client compression but it&#39;s per-connection level configuration. I was n=
ot sure if it&#39;s so worthwhile to include such a halfway feature.</div>

<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left=
-style:solid;padding-left:1ex"><div dir=3D"ltr"><div></div><div>As for havi=
ng the endpoint code control behavior inside of an extension, that seems di=
fficult to control or expose.</div>

<div>For example: do we even have the ability, in javascript on the browser=
, to control the extensions that are offered? or interrogate the open conne=
ction to know what extensions have been negotiated?</div></div></blockquote=
>

<div><br></div><div>Using the extensions attribute, we can know what extens=
ions are negotiated.</div><div><br></div><div>Rough plan was adding some at=
tribute or method or overloading send() method of WebSocket to allow webapp=
s to flip compression on/off.</div>

<div>=A0</div></div></div></div>

--f46d04447fbbfdceb404e854ac72--

From tyoshino@google.com  Wed Oct  9 13:35:50 2013
Return-Path: <tyoshino@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF43021E81A1 for <hybi@ietfa.amsl.com>; Wed,  9 Oct 2013 13:35:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level: 
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[AWL=0.065,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oCmaikpbQeJr for <hybi@ietfa.amsl.com>; Wed,  9 Oct 2013 13:35:50 -0700 (PDT)
Received: from mail-we0-x229.google.com (mail-we0-x229.google.com [IPv6:2a00:1450:400c:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id D96A611E80FC for <hybi@ietf.org>; Wed,  9 Oct 2013 13:35:49 -0700 (PDT)
Received: by mail-we0-f169.google.com with SMTP id q58so1500618wes.14 for <hybi@ietf.org>; Wed, 09 Oct 2013 13:35:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=q9N1U3SEUtyba9T1vnpH7A2CVuFztZolcGz6xWLssQo=; b=fPMTH+d9Se+DfywxTGE0/JQ95qwoCmcxObNgarhyeQLys88mfunxRXN6eiRVOBb6Ft sYHTyPILlbJ3J8fKhgl38I6bLlMWBqyzp/tnswAf+5m7gnJ1N6cN46VF+UkhW6Orwm7j 65rN6mJOT8+5jjOYH9Xdk+mrIlu2xYcvGsU4M0vIn7JGe4m5PKUGkXqNvakpDgxZC4Ii pO1bwAz+hV0UpDntCScWiC2kCn55uYDpPRg0RRa+YpPpHAhLDsrG26z5oCz+ZzP2B32B ivPj3JO4a48woQgMJXZmz6N7NCtZBRC7cQ0FKQr6X5qfZYZHtaEXySTobUDU/sSS8xIg l13w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=q9N1U3SEUtyba9T1vnpH7A2CVuFztZolcGz6xWLssQo=; b=ASTBP8AruVbIznPIiQ/mloX33tEHQuxRS4DbsnqRWf+NRwoEjMluNVYskbRgWM5zF3 MTtvUcuAAfREnLYqH65OjViJMROA0yOBosq++q6CwyLzh+OgL8+HM88s7busfLlZ1j5Q 1qywnxLFyVptrfyZw/zDFTTgE72aURiD+J3uFYNtBzw8XJPYKBRwE3Zzm806TLL7+pgC d5W14jV2E4CFc3CMULvbeSr4d+0QXthQp+gqYR1jCEDKfbuP7J5KcByio5ZJX9XIY1Ji CvtjPJGCmSEbTkKGPv5QQ3R4TPEzrcxP+bQThxxsAasatcmCKRDp+cvqXY7DhcnfpHQj E74Q==
X-Gm-Message-State: ALoCoQnCxf2uB0/EqqZDyzS0S22+enTB39N+wt/DQoWwqadknqDbuIB+U/vxko+jePLLNK3OYOWSsmz5j2mBXnpoRMgKCGiiq65w+rBzsGPCGvdUMKyV9NnQAGhhYfHpYlbiM80R3+0BXZLhCZ6lyeprvpzNhXYGX5/1eRr9oczhH9F9sI1GslR69zUKRvSXYtqGQ3sxXzuL
X-Received: by 10.180.211.71 with SMTP id na7mr3828477wic.5.1381350948979; Wed, 09 Oct 2013 13:35:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.15.133 with HTTP; Wed, 9 Oct 2013 13:35:28 -0700 (PDT)
In-Reply-To: <02030518-6F55-4E50-9AB8-06C7540C8AE1@zaphoyd.com>
References: <CAG4zZZAqGcVP=4P9qfo2Gm3fbPHKntwZ5aF=hDePccfKnD4kWQ@mail.gmail.com> <02030518-6F55-4E50-9AB8-06C7540C8AE1@zaphoyd.com>
From: Takeshi Yoshino <tyoshino@google.com>
Date: Thu, 10 Oct 2013 05:35:28 +0900
Message-ID: <CAH9hSJZdY83xRg0a-AUtmrV9Y3He8AKNb1fV5Utq=gEoDuEGWA@mail.gmail.com>
To: Peter Thorson <webmaster@zaphoyd.com>
Content-Type: multipart/alternative; boundary=001a11c347e09fed1d04e854d4d1
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] permessage-deflate and missing asymmetric configurations
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 09 Oct 2013 20:35:51 -0000

--001a11c347e09fed1d04e854d4d1
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Oct 10, 2013 at 4:34 AM, Peter Thorson <webmaster@zaphoyd.com>wrote:

> There may be some additional resource savings possible if an endpoint
> knows it will never receive a compressed message. That should be considered
> at least.
>

In terms of software without very tight memory limitation, it can be
accomplished just by delaying initialization of inflater until it sees a
compressed message?

--001a11c347e09fed1d04e854d4d1
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Thu, Oct 10, 2013 at 4:34 AM, Peter Thorson <span dir=
=3D"ltr">&lt;<a href=3D"mailto:webmaster@zaphoyd.com" target=3D"_blank">web=
master@zaphoyd.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div=
 class=3D"gmail_quote">

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-word"><div>The=
re may be some additional resource savings possible if an endpoint knows it=
 will never receive a compressed message. That should be considered at leas=
t.</div>

</div></blockquote><div><br></div><div>In terms of software without very ti=
ght memory limitation, it can be accomplished just by delaying initializati=
on of inflater until it sees a compressed message?</div><div>=A0</div></div=
>

</div></div>

--001a11c347e09fed1d04e854d4d1--

From tyoshino@google.com  Wed Oct  9 13:59:47 2013
Return-Path: <tyoshino@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32EC611E80D9 for <hybi@ietfa.amsl.com>; Wed,  9 Oct 2013 13:59:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.918
X-Spam-Level: 
X-Spam-Status: No, score=-1.918 tagged_above=-999 required=5 tests=[AWL=0.059,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O+6E-0-7BctF for <hybi@ietfa.amsl.com>; Wed,  9 Oct 2013 13:59:46 -0700 (PDT)
Received: from mail-we0-x22d.google.com (mail-we0-x22d.google.com [IPv6:2a00:1450:400c:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 49DB921E8160 for <hybi@ietf.org>; Wed,  9 Oct 2013 13:59:46 -0700 (PDT)
Received: by mail-we0-f173.google.com with SMTP id u57so1492999wes.4 for <hybi@ietf.org>; Wed, 09 Oct 2013 13:59:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=YPLFx7hN+RkwPsDnDOGrOGe4HsbXSoB2UxnI1UHDJ+Y=; b=NzSetcj2apQJYxPigKMttJBq3EzSf23LPLi7Aw76oh0pnErLynvwnFLYVqT+rQzkOK jwnjHs6AYgM/PJfh5EmJrs6ZL8WECT48GMyDS6hQl2CWchifcZJ3ZB5KTQAMAioM+WoB lzHEmHxzYAjijvxMy+Cy3Q2ALDmT8zKsss3TSMYCumyaVn2U+g6iG1+EaTi3P9UhhQ09 kkqm/izCzOiMQf8oykq/mRrVBq1wwUWFq6I99wEm3bqkkdl/eYZq9ikLd55Yqdqn6Wb1 j6QsHujDxZ7LBAGQFHWn+YWTffWeBI+lmhkAV3SOIkIG5wOCs+ROmZa7WoWjoe7mzYg3 d47w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=YPLFx7hN+RkwPsDnDOGrOGe4HsbXSoB2UxnI1UHDJ+Y=; b=Q0AueOcB0TsL4bj8viWZADLGn/3xXdKXp3hc0ofR8ACVKNAwdk8zWz8VCr/cl64+8x 5h3+W0/XzPzVQdDRpdJN8gxOFD7i6CE8mO+dxcELNwfNad5zS4pxqYG+O8NIKhcKQfnh o28A5+YzrkhQuv64ow00PavWf2SgJzHQJ0qBRJvN+ynlilWQXjTrJW26iQGouzPOhzri Bv0QoFXSm4vOd+hWnWr91r2gRWrlnaGMZkm/HQux01RXUz/OxpCCcdGL35uOTQbiHKql tD4BULGwYWfkVnqnkGZR5CDbNhQuQe+VKMV+5f4zVZ9jTQMM8hOBGRhDB8AVCUe27q/y Pziw==
X-Gm-Message-State: ALoCoQkWArkJ2lRMlygelhuWVnZwzoSa+Q7NhqDZuk75C8oTwZcOXG306ummzzlak6HYr2k5Vyh80o3D33Sm6fw1Zi+z/vm68zodIUquXBZq4Lc53BXn7KOFWxnfq30eVX0X0wYlGZB4lC1xqOvgZaa05k5yMBl6m5+TTN/c3DuvJ37cuyP27XtzaXP2GwdtMRGqgKnOWc0g
X-Received: by 10.195.13.45 with SMTP id ev13mr8617724wjd.20.1381352378287; Wed, 09 Oct 2013 13:59:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.15.133 with HTTP; Wed, 9 Oct 2013 13:59:18 -0700 (PDT)
In-Reply-To: <CAH9hSJZugsZjJ7j7EoGseT9QauQ2bApK7OcWAtirCZ6b0SHwvA@mail.gmail.com>
References: <CAG4zZZAqGcVP=4P9qfo2Gm3fbPHKntwZ5aF=hDePccfKnD4kWQ@mail.gmail.com> <02030518-6F55-4E50-9AB8-06C7540C8AE1@zaphoyd.com> <CAG4zZZCYkuQx40zn-wUBoeSecJ-NTDku-nD5-gkSSy-A1vhxNQ@mail.gmail.com> <CAH9hSJZugsZjJ7j7EoGseT9QauQ2bApK7OcWAtirCZ6b0SHwvA@mail.gmail.com>
From: Takeshi Yoshino <tyoshino@google.com>
Date: Thu, 10 Oct 2013 05:59:18 +0900
Message-ID: <CAH9hSJZVAjUPu=6b1CsVVnCRchSGY5hN+ongpkrkVUPJVDmFgQ@mail.gmail.com>
To: Joakim Erdfelt <joakim@intalio.com>
Content-Type: multipart/alternative; boundary=047d7bfced1ed16e7004e855291a
Cc: "hybi@ietf.org" <hybi@ietf.org>, Peter Thorson <webmaster@zaphoyd.com>
Subject: Re: [hybi] permessage-deflate and missing asymmetric configurations
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 09 Oct 2013 20:59:47 -0000

--047d7bfced1ed16e7004e855291a
Content-Type: text/plain; charset=ISO-8859-1

If we introduce the feature it'll be like this. We add new parameters, say,
server_no_compress and client_no_compress.

- client MAY request server_no_compress
- client MAY send a hint client_no_compress
- server MAY respond with client_no_compress
- server MUST respond with server_no_compress if received it from client

- client MUST NOT include server_no_compress together with other server_
parameters
- server MUST NOT include server_no_compress together with other server_
parameters
- server MUST NOT include client_no_compress together with other client_
parameters

--047d7bfced1ed16e7004e855291a
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">If we introduce the feature it&#39;ll be like this. We add=
 new parameters, say, server_no_compress and client_no_compress.<div><br></=
div><div>- client MAY request server_no_compress</div><div>- client MAY sen=
d a hint client_no_compress</div>

<div>- server MAY respond with client_no_compress</div><div>- server MUST r=
espond with server_no_compress if received it from client</div><div><br></d=
iv><div>- client MUST NOT include server_no_compress together with other se=
rver_ parameters</div>

<div>- server MUST NOT include server_no_compress together with other serve=
r_ parameters</div><div>- server MUST NOT include client_no_compress togeth=
er with other client_ parameters=A0</div></div>

--047d7bfced1ed16e7004e855291a--

From tobias.oberstein@tavendo.de  Sun Oct 13 01:13:32 2013
Return-Path: <tobias.oberstein@tavendo.de>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A95A11E8127 for <hybi@ietfa.amsl.com>; Sun, 13 Oct 2013 01:13:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E6Mz-039ak1W for <hybi@ietfa.amsl.com>; Sun, 13 Oct 2013 01:13:27 -0700 (PDT)
Received: from EXHUB020-1.exch020.serverdata.net (exhub020-1.exch020.serverdata.net [206.225.164.28]) by ietfa.amsl.com (Postfix) with ESMTP id 2733B21E80B7 for <hybi@ietf.org>; Sun, 13 Oct 2013 01:13:23 -0700 (PDT)
Received: from EXVMBX020-12.exch020.serverdata.net ([169.254.3.240]) by EXHUB020-1.exch020.serverdata.net ([206.225.164.28]) with mapi; Sun, 13 Oct 2013 01:13:21 -0700
From: Tobias Oberstein <tobias.oberstein@tavendo.de>
To: Takeshi Yoshino <tyoshino@google.com>, Joakim Erdfelt <joakim@intalio.com>
Date: Sun, 13 Oct 2013 01:13:18 -0700
Thread-Topic: [hybi] permessage-deflate and missing asymmetric configurations
Thread-Index: Ac7FLZw7V4dA7qr2RN66+5XssbA6agCvaqAA
Message-ID: <634914A010D0B943A035D226786325D44469B06661@EXVMBX020-12.exch020.serverdata.net>
References: <CAG4zZZAqGcVP=4P9qfo2Gm3fbPHKntwZ5aF=hDePccfKnD4kWQ@mail.gmail.com> <02030518-6F55-4E50-9AB8-06C7540C8AE1@zaphoyd.com> <CAG4zZZCYkuQx40zn-wUBoeSecJ-NTDku-nD5-gkSSy-A1vhxNQ@mail.gmail.com> <CAH9hSJZugsZjJ7j7EoGseT9QauQ2bApK7OcWAtirCZ6b0SHwvA@mail.gmail.com>
In-Reply-To: <CAH9hSJZugsZjJ7j7EoGseT9QauQ2bApK7OcWAtirCZ6b0SHwvA@mail.gmail.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "hybi@ietf.org" <hybi@ietf.org>, Peter Thorson <webmaster@zaphoyd.com>
Subject: Re: [hybi] permessage-deflate and missing asymmetric configurations
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Sun, 13 Oct 2013 08:13:32 -0000

>>Was the idea of having compression level as a configurable ever on the ta=
ble?
>Since each endpoint can choose any compression level as long as wbits and =
context mode are negotiated, I didn't include compression level negotiation=
.
=A0
Exactly.

We only need to negotiate parameters that must be agreed upon make the comm=
unication compatible - not every knob that is available at the compressor/d=
ecompressor within each endpoint.

Compression level is a useful knob .. but doesn't need to be negotiated.

>Rough plan was adding some attribute or method or overloading send() metho=
d of WebSocket to allow webapps to flip compression on/off.

Exposing an API for apps to control compression yes/no on a _per message_ b=
asis is definitely worth: the app might have knowledge whether a given payl=
oad is compressible at all. E.g. when the app has encrypted the payload (fo=
r end-to-end privacy), it makes no sense to compress at WS level. Payload n=
eeds to be compressed before encryption.

/Tobias
=A0

From tobias.oberstein@tavendo.de  Sun Oct 13 01:18:52 2013
Return-Path: <tobias.oberstein@tavendo.de>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1EFE21F9A97 for <hybi@ietfa.amsl.com>; Sun, 13 Oct 2013 01:18:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zeSfKOJHXZqI for <hybi@ietfa.amsl.com>; Sun, 13 Oct 2013 01:18:46 -0700 (PDT)
Received: from EXHUB020-1.exch020.serverdata.net (exhub020-1.exch020.serverdata.net [206.225.164.28]) by ietfa.amsl.com (Postfix) with ESMTP id DF1B921F8E3D for <hybi@ietf.org>; Sun, 13 Oct 2013 01:18:42 -0700 (PDT)
Received: from EXVMBX020-12.exch020.serverdata.net ([169.254.3.240]) by EXHUB020-1.exch020.serverdata.net ([206.225.164.28]) with mapi; Sun, 13 Oct 2013 01:18:41 -0700
From: Tobias Oberstein <tobias.oberstein@tavendo.de>
To: Takeshi Yoshino <tyoshino@google.com>, Joakim Erdfelt <joakim@intalio.com>
Date: Sun, 13 Oct 2013 01:18:40 -0700
Thread-Topic: [hybi] permessage-deflate and missing asymmetric configurations
Thread-Index: Ac7FMoDlKEBnqcHQRW6LFMPigXhxzQCuaxMA
Message-ID: <634914A010D0B943A035D226786325D44469B06662@EXVMBX020-12.exch020.serverdata.net>
References: <CAG4zZZAqGcVP=4P9qfo2Gm3fbPHKntwZ5aF=hDePccfKnD4kWQ@mail.gmail.com> <02030518-6F55-4E50-9AB8-06C7540C8AE1@zaphoyd.com> <CAG4zZZCYkuQx40zn-wUBoeSecJ-NTDku-nD5-gkSSy-A1vhxNQ@mail.gmail.com> <CAH9hSJZugsZjJ7j7EoGseT9QauQ2bApK7OcWAtirCZ6b0SHwvA@mail.gmail.com> <CAH9hSJZVAjUPu=6b1CsVVnCRchSGY5hN+ongpkrkVUPJVDmFgQ@mail.gmail.com>
In-Reply-To: <CAH9hSJZVAjUPu=6b1CsVVnCRchSGY5hN+ongpkrkVUPJVDmFgQ@mail.gmail.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: multipart/alternative; boundary="_000_634914A010D0B943A035D226786325D44469B06662EXVMBX02012ex_"
MIME-Version: 1.0
Cc: "hybi@ietf.org" <hybi@ietf.org>, Peter Thorson <webmaster@zaphoyd.com>
Subject: Re: [hybi] permessage-deflate and missing asymmetric configurations
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Sun, 13 Oct 2013 08:18:52 -0000

--_000_634914A010D0B943A035D226786325D44469B06662EXVMBX02012ex_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

my vote: -1 for those new parameters.

IMHO they are not needed: an endpoint can choose to not compress (an indivi=
dual or all) messages anyway without any negotiation needed - it can also d=
iscard context even when context takeover was negotiated and choose less wi=
ndow bits than negotiated.

In essence, the negotiation only needs to establish _upper bounds_ on resou=
rce consumption (memory) within endpoints. Hence, context takeover and wind=
ow bits.

/Tobias

Von: hybi-bounces@ietf.org [mailto:hybi-bounces@ietf.org] Im Auftrag von Ta=
keshi Yoshino
Gesendet: Mittwoch, 9. Oktober 2013 22:59
An: Joakim Erdfelt
Cc: hybi@ietf.org; Peter Thorson
Betreff: Re: [hybi] permessage-deflate and missing asymmetric configuration=
s

If we introduce the feature it'll be like this. We add new parameters, say,=
 server_no_compress and client_no_compress.

- client MAY request server_no_compress
- client MAY send a hint client_no_compress
- server MAY respond with client_no_compress
- server MUST respond with server_no_compress if received it from client

- client MUST NOT include server_no_compress together with other server_ pa=
rameters
- server MUST NOT include server_no_compress together with other server_ pa=
rameters
- server MUST NOT include client_no_compress together with other client_ pa=
rameters

--_000_634914A010D0B943A035D226786325D44469B06662EXVMBX02012ex_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV=3D"Content-Type" CONTENT=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.E-MailFormatvorlage17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DDE link=3D"#0563C1" v=
link=3D"#954F72"><div class=3DWordSection1><p class=3DMsoNormal><span style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-f=
areast-language:EN-US'>my vote: -1 for those new parameters.<o:p></o:p></sp=
an></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Ca=
libri","sans-serif";color:#1F497D;mso-fareast-language:EN-US'><o:p>&nbsp;</=
o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-fa=
mily:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US'>IMHO =
they are not needed: an endpoint can choose to not compress (an individual =
or all) messages anyway without any negotiation needed - it can also discar=
d context even when context takeover was negotiated and choose less window =
bits than negotiated.<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-f=
areast-language:EN-US'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><sp=
an style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F49=
7D;mso-fareast-language:EN-US'>In essence, the negotiation only needs to es=
tablish _upper bounds_ on resource consumption (memory) within endpoints. H=
ence, context takeover and window bits. <o:p></o:p></span></p><p class=3DMs=
oNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";=
color:#1F497D;mso-fareast-language:EN-US'><o:p>&nbsp;</o:p></span></p><p cl=
ass=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans=
-serif";color:#1F497D;mso-fareast-language:EN-US'>/Tobias<o:p></o:p></span>=
</p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calib=
ri","sans-serif";color:#1F497D;mso-fareast-language:EN-US'><o:p>&nbsp;</o:p=
></span></p><div style=3D'border:none;border-left:solid blue 1.5pt;padding:=
0cm 0cm 0cm 4.0pt'><div><div style=3D'border:none;border-top:solid #E1E1E1 =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span style=3D'fon=
t-size:11.0pt;font-family:"Calibri","sans-serif"'>Von:</span></b><span styl=
e=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'> hybi-bounces@iet=
f.org [mailto:hybi-bounces@ietf.org] <b>Im Auftrag von </b>Takeshi Yoshino<=
br><b>Gesendet:</b> Mittwoch, 9. Oktober 2013 22:59<br><b>An:</b> Joakim Er=
dfelt<br><b>Cc:</b> hybi@ietf.org; Peter Thorson<br><b>Betreff:</b> Re: [hy=
bi] permessage-deflate and missing asymmetric configurations<o:p></o:p></sp=
an></p></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=
=3DMsoNormal>If we introduce the feature it'll be like this. We add new par=
ameters, say, server_no_compress and client_no_compress.<o:p></o:p></p><div=
><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>=
- client MAY request server_no_compress<o:p></o:p></p></div><div><p class=
=3DMsoNormal>- client MAY send a hint client_no_compress<o:p></o:p></p></di=
v><div><p class=3DMsoNormal>- server MAY respond with client_no_compress<o:=
p></o:p></p></div><div><p class=3DMsoNormal>- server MUST respond with serv=
er_no_compress if received it from client<o:p></o:p></p></div><div><p class=
=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>- client =
MUST NOT include server_no_compress together with other server_ parameters<=
o:p></o:p></p></div><div><p class=3DMsoNormal>- server MUST NOT include ser=
ver_no_compress together with other server_ parameters<o:p></o:p></p></div>=
<div><p class=3DMsoNormal>- server MUST NOT include client_no_compress toge=
ther with other client_ parameters&nbsp;<o:p></o:p></p></div></div></div></=
div></body></html>=

--_000_634914A010D0B943A035D226786325D44469B06662EXVMBX02012ex_--

From tobias.oberstein@tavendo.de  Sun Oct 13 10:33:42 2013
Return-Path: <tobias.oberstein@tavendo.de>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B3B121E80EE for <hybi@ietfa.amsl.com>; Sun, 13 Oct 2013 10:33:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 86Cob+fw7NOu for <hybi@ietfa.amsl.com>; Sun, 13 Oct 2013 10:33:37 -0700 (PDT)
Received: from EXHUB020-5.exch020.serverdata.net (exhub020-5.exch020.serverdata.net [206.225.164.32]) by ietfa.amsl.com (Postfix) with ESMTP id 5FD9421E80B3 for <hybi@ietf.org>; Sun, 13 Oct 2013 10:33:36 -0700 (PDT)
Received: from EXVMBX020-12.exch020.serverdata.net ([169.254.3.240]) by EXHUB020-5.exch020.serverdata.net ([206.225.164.32]) with mapi; Sun, 13 Oct 2013 10:33:30 -0700
From: Tobias Oberstein <tobias.oberstein@tavendo.de>
To: "hybi@ietf.org" <hybi@ietf.org>
Date: Sun, 13 Oct 2013 10:33:28 -0700
Thread-Topic: AutobahnTestsuite 0.5.6
Thread-Index: Ac7IOkyQONVkEOnKTg69wkOHwNV2rQ==
Message-ID: <634914A010D0B943A035D226786325D44469B06671@EXVMBX020-12.exch020.serverdata.net>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [hybi] AutobahnTestsuite 0.5.6
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Sun, 13 Oct 2013 17:33:42 -0000

Hi,

Just released a new AutobahnTestsuite version .. includes WebSocket compres=
sion ("permessage-deflate") testing.

For details and links to reports, pls see announcement here: https://groups=
.google.com/forum/#!topic/autobahnws/_WIk5Z_xJ4U

/Tobias

From internet-drafts@ietf.org  Tue Oct 15 07:00:26 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A143411E817B; Tue, 15 Oct 2013 07:00:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.588
X-Spam-Level: 
X-Spam-Status: No, score=-102.588 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XUWBTTy7MzMr; Tue, 15 Oct 2013 07:00:26 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D888B21E80BB; Tue, 15 Oct 2013 07:00:16 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131015140016.2154.93984.idtracker@ietfa.amsl.com>
Date: Tue, 15 Oct 2013 07:00:16 -0700
Cc: hybi@ietf.org
Subject: [hybi] I-D Action: draft-ietf-hybi-permessage-compression-14.txt
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 15 Oct 2013 14:00:26 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the BiDirectional or Server-Initiated HTTP Wo=
rking Group of the IETF.

	Title           : Compression Extensions for WebSocket
	Author(s)       : Takeshi Yoshino
	Filename        : draft-ietf-hybi-permessage-compression-14.txt
	Pages           : 30
	Date            : 2013-10-15

Abstract:
   This document specifies 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 non-control WebSocket messages on a per-message basis using
   parameters negotiated during the opening handshake.  This framework
   provides a general method to apply a compression algorithm to the
   contents of WebSocket messages.  For each compression algorithm, an
   extension is defined by specifying parameter negotiation and
   compression algorithm in detail.  This document also specifies one
   specific compression extension using the DEFLATE algorithm.

   Please send feedback to the hybi@ietf.org mailing list.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-hybi-permessage-compression

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-hybi-permessage-compression-14

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-hybi-permessage-compression-14


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From tyoshino@google.com  Tue Oct 15 07:01:06 2013
Return-Path: <tyoshino@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3EE121E815C for <hybi@ietfa.amsl.com>; Tue, 15 Oct 2013 07:01:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.923
X-Spam-Level: 
X-Spam-Status: No, score=-1.923 tagged_above=-999 required=5 tests=[AWL=0.054,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fSheOzj2MCqm for <hybi@ietfa.amsl.com>; Tue, 15 Oct 2013 07:01:05 -0700 (PDT)
Received: from mail-ee0-x230.google.com (mail-ee0-x230.google.com [IPv6:2a00:1450:4013:c00::230]) by ietfa.amsl.com (Postfix) with ESMTP id 68C4111E8138 for <hybi@ietf.org>; Tue, 15 Oct 2013 07:00:55 -0700 (PDT)
Received: by mail-ee0-f48.google.com with SMTP id l10so4007510eei.21 for <hybi@ietf.org>; Tue, 15 Oct 2013 07:00:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=UzmL09KCqbVdGsEdw82io6nWF9Xm2rFCkr/U3UOJE84=; b=B5C7m6RRs9j5jBomKLIark2uvLubS8BP6Hu7fe8S45tIBys0Q5IgXklkYp+g+cnGCY zR1O5+AtaMtX2UjG+bfovmTUNk4O6Kk37+ui4Lu+SxnpnG+jYwYruUQkjCDVQOvOe858 VTgvzsRCggdq4X/K9jMsaA3BbuGr0Ay8WpZWB1p6PC31ZaDpsLoEa1RisZ4ib7X94qZV t2+JEZln278qYqx6Sq52jbx4Y0dC2A3mlBvaymRx682bDH3CA+SDIKGB+iQFjHyS+R+B 5B9btBQAH9aYdhtXi1zZUrxZyd/K972acH6n5ZHJbq7kTS+DJDdCQ2Q+CXj5ECIpC364 H6rA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=UzmL09KCqbVdGsEdw82io6nWF9Xm2rFCkr/U3UOJE84=; b=elmYFMLRa5lflgHrpVlxMnSC1wQeVexarq5pSvHi97utf9rDoKokPTE7lMvTxWexwF /vnNQa7mVANol6lWARNAzlTheG0BWwdr0YMEL+Z+nYKrdDe+ub8RBci++61lL3o0gb/D XopgDk0qyJMKPMOESyIEFRVUJBiRw6fg62Mihg0MYZBUzz6pffi88X/jssLkys4OMctB 2Xuwv7N4OAeJuMa7uKsQ2bpCLsmGzSTUrYk701ZeDgjqoX+uNw70GPtyg78i1MUAPy/t 0waVVbPA/sqcRwgH2RYm+wJF3mk0XZY128YD2BfOoG9bxcDcGWnzrpWhoAwbcvFNDbqf E+FQ==
X-Gm-Message-State: ALoCoQlAQo/RwG645lSKrMZLy4hI+y/QijUDcJ8QSGzIvNvfXSJxA6V/X5JTf8lwOFzFLaX479Gj0cT6+2UgTZCnoSZoaE+VJuF1uZGyDyKUzIAMi2Wx7m7nXlY9iL2YhHc5Tjmz+Lp9YQwcWwZpwFMNUjppiQZHJ32YL2ofbq+N7fBNVMQbgya34Yu1tZHrf5UgudRa47ui
X-Received: by 10.14.108.9 with SMTP id p9mr960259eeg.8.1381845654494; Tue, 15 Oct 2013 07:00:54 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.49.140 with HTTP; Tue, 15 Oct 2013 07:00:33 -0700 (PDT)
In-Reply-To: <CAG4zZZC2umzmq2vXPJGmR5+hZuRiRO7BN+9via8dBK7Og4XhBg@mail.gmail.com>
References: <20131008034344.3492.4171.idtracker@ietfa.amsl.com> <CAH9hSJZKwBhmMg5jAa1U93g+Q1Hfv0nRDx=m_ZAbj-oi=_Ba7g@mail.gmail.com> <CAG4zZZC2umzmq2vXPJGmR5+hZuRiRO7BN+9via8dBK7Og4XhBg@mail.gmail.com>
From: Takeshi Yoshino <tyoshino@google.com>
Date: Tue, 15 Oct 2013 23:00:33 +0900
Message-ID: <CAH9hSJYjwnJQLAaeVQvmEX2+_b8q_gzE_+zuq_6XW=-_u-4R8g@mail.gmail.com>
To: Joakim Erdfelt <joakim@intalio.com>
Content-Type: multipart/alternative; boundary=001a11c28d345efd1404e8c8032c
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] I-D Action: draft-ietf-hybi-permessage-compression-13.txt
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 15 Oct 2013 14:01:06 -0000

--001a11c28d345efd1404e8c8032c
Content-Type: text/plain; charset=ISO-8859-1

Some addressed in -14. The rest will be addressed in -15.

On Wed, Oct 9, 2013 at 12:14 PM, Joakim Erdfelt <joakim@intalio.com> wrote:

>    1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
>
>  > good
>  > +1 for the removal of the PPP text
>

Yes. It was broken after rendering HTML.


>    3.  Complementary Terminology  . . . . . . . . . . . . . . . . . .  5
>
>  > sufficient, would providing links to RFC6455 sections be worthwhile?
>  > example:
>
>  - Non-control message means a message consists of non-control frames.
>  + Non-control message means a message that consists of non-control
>    frames (e.g., data frames) as defined in [Section 5.6] of [RFC6455]
>
done


>
>  - Message payload (or payload of a message) means concatenation of the
>  - payload data portion of all frames consisting the message.
>  + Message payload (or payload of a message) means concatenation of the
>  + payload data portion of all data frames consisting of a single
>  + message, as defined in [Section 6] of [RFC6455]
>

s/consisting of/representing/ ?

done


>
>  > no commentary on section for the paragraphs about Extension behavior
>  > as the reference to [Section 9] of [RFC6455] is handled in the next
>  > section of this doc
>
>
>    5.  Extension Negotiation  . . . . . . . . . . . . . . . . . . . .  7
>

Used texts I showed in my last reply.


>
>    If a server gives an invalid response, such as accepting a PMCE that
>    the client did not offer, the client MUST _Fail the WebSocket
>    Connection_.
>
>  > should we mention close code 1010 here?
>

I'm not sure if 1010 is for this kind of failure. The text in RFC 6455
sounds like it's used to reject an opening handshake response that doesn't
include extension(s) the client considered to be mandatory.

There isn't any extension with concept of mandatory introduced yet.
permessage-deflate is not mandatory extension. We just want to tell the
server that it sent back an invalid extension response.


>
>
>      6.1.  Compression  . . . . . . . . . . . . . . . . . . . . . . . 10
>
>    2.  If this PMCE is the last extension to process outgoing messages,
>        build frame(s) by using the compressed data instead of the
>        original data for the message payload, and setting the
>
>  > The condition "if this PCME is the last extension to process
>  > outgoing messages" is meaningless, here and further down in this
>  > section.  The process is the same for all PMCEs regardless if it is
>  > the first, middle, or last extension.
>  >
>  > Also, with the current spec, we would argue that it is impossible
>  > to have multiple active PMCEs anyway (due to the RSV1 bit requirement)
>
>

[TBA]


>      6.2.  Decompression  . . . . . . . . . . . . . . . . . . . . . . 11
>
>  > Again, same commentary about the "PCME is the last extension"
>  > condition being irrelevant
>
>

[TBA]


>    7.  Intermediaries . . . . . . . . . . . . . . . . . . . . . . . . 13
>
>  > good, but could use some commentary that if the intermediaries are
>  > not aware of the opening handshake, then they should make no
>  > modifications to the frames.  See [Section 5.4] of [RFC6455]
>  > 3rd paragraph for similar text.
>
>

[TBA]


>    8.  permessage-deflate extension . . . . . . . . . . . . . . . . . 14
>
>  > OK, some suggestions on how to clean this section up.
>  >
>  > Introduce the 4 extension parameters first.
>  >
>  >   Use the language found elsewhere in the spec now about the asymmetric
>  >   nature of the extension parameter configuration.
>  >
>  >   The following 2 extension parameters control the behavior of the
>  >   deflate configuration for Client-to-Server messages:
>  >   (We took this notation from the title of [Section 5.3] of [RFC-6455],
>  >    including the capitalization)
>  >
>  >     o  "c2s_no_context_takeover"
>  >     o  "c2s_max_window_bits"
>  >
>  >   The following 2 extension parameters control the behavior of the
>  >   deflate configuration for Server-to-Client messages:
>  >
>  >     o  "s2c_no_context_takeover"
>  >     o  "s2c_max_window_bits"
>  >
>  > Then describe how the Offer works. (essentially the language you
>  > have now in the doc, with careful attention to not mix your intro
>  > and then bullets)
>  >    Request: desired client behavior + desired server behavior
>  >    Response: acknowledge client behavior + server chosen behavior
>  >
>  > Example of confusing language:
>
>    For an offer for this extension, the following 4 extension parameters
>    are defined.  If needed to distinguish from ones for a response,
>    these parameters are called with a prefix "client-to-server".
>
>    o  "s2c_no_context_takeover"
>
>    o  "c2s_no_context_takeover"
>
>    o  "s2c_max_window_bits"
>
>    o  "c2s_max_window_bits"
>
>  > This section introduces you to "client-to-server", then lists
>  > s2c_*, why?  Same for the next section, but in reverse.
>  > Don't mix the introduction of the extension parameters and
>  > the behavior of the request and response together.
>  >
>  > Finally, go into the MUST rules for Client and Server like you
>  > currently have in the spec documentation.
>   >
>  > Include wording for Client MUST pointing back to close code
>  > 1010 from [RC6455] as a recommended behavior for dealing with
>  > bad extension negotiation.
>  > Even for things like a server saying s2c_max_window_bits=1024
>
>

[TBA]


>      8.1.  Method Parameters  . . . . . . . . . . . . . . . . . . . . 15
>        8.1.1.  Context Takeover Control . . . . . . . . . . . . . . . 15
>
>  > Include explicit language indicating default behavior for
>  > context takeover.
>
>  > When documenting one side, for example "s2c_", do not make references
>  > to the opposite direction.  Its confusing, noisy, and adds no value.
>  >
>  > For example, Section 8.1.2.2. c2s_max_window_bits, start out talking
>  > about the c2s_max_window_bits, then has suddenly talks about
>  > "server-to-client parameter", mentioning behavior and server limits.
>  > This is confusing.
>  > Fix this, clarify it, eliminate the noise, or simplify it.
>  >
>  > Eg of simplification:
>  >
>  >  See [Section 8.1.2.1.] "s2c_max_window_bits" for server side
>  >  equivalent
>  >
>  > We suspect that the use of "c2s" and "client-to-server" to
>  > interchangably refer to either the "extension parameter token" itself
>  > or the phase of the extension negotiation (request or response) is
>  > the cause of the confusion.
>  >
>  > Either choose new terminology for the extension parameter token, or
>  > choose new terminology for the phase of the extension negotiation
>  > (request side or response side)
>  >
>

[TBA]


>
>        8.1.2.  Limiting the LZ77 sliding window size  . . . . . . . . 16
>
>  > Include explicit language indicating default size for
>  > LZ77 sliding window size.
>

Added texts.


>  > RFC1979 seems to indicate 32KB as the maximum value, but no obvious
>  > word on what is the default behavior, assuming no window size is
>  > specifically declared.
>  >
>  > The ABNF for the c2s_max_window_bits indicates that a digit is required,
>  > but the text indicates that no value is possible.
>  > What does no-value mean?
>

It means that only capability is announced with no hint.

Added texts.


>
>        8.1.3.  Example  . . . . . . . . . . . . . . . . . . . . . . . 18
>
>  > See earlier commentary about no value c2s_max_window_bits extension
>  > parameter token.
>  > See earlier commentary about extension negotiation for example #3
>  > (fallback behavior written into this spec)
>
>      8.2.  Message Payload Transformation . . . . . . . . . . . . . . 19
>
>  > good
>  > (one note, the BFINAL logic needs to be validated in current
>  > implementations.  as BFINAL does not behave the same in pywebsocket,
>  > autobahn, chrome, and safari).  We had to hack BFINAL to always be
>  > 0 for outgoing frames from our server in order for existing
>  > client implementations to work.
>

Sorry. Could you please elaborate this?


>
>        8.2.3.  Examples . . . . . . . . . . . . . . . . . . . . . . . 21
>
>  > Include example of multiple message behavior with no_context_takeover
>  > configured.
>

In "Sharing LZ77 Sliding Window" section, the second example is identical
to the first one. This is the example of multiple message behavior with
no_context_takeover.

>   This is the payload of the first message the client has sent.  If the
>   "agreed parameters" contain the "c2s_no_context_takeover" extension
>   parameter, the client compresses the payload of the next message into
>   the same bytes (if the client uses the same "BTYPE" value and
>   "BFINAL" value).  So, the payload of the second message will be:
>
>       0xf2 0x48 0xcd 0xc9 0xc9 0x07 0x00

Added concatenated examples.


>
>      8.3.  Implementation Notes . . . . . . . . . . . . . . . . . . . 24
>
>  > This section's updates are good.
>  > The LZ77 sliding window size recommendation is ok, but where's the
>  > default LZ77 sliding window size?
>

This sentence in "Compression" section

> An endpoint MUST NOT use an LZ77 sliding window longer than 32,768 bytes
to compress messages to send.

and these sentences in "Decompression" section are intended to define
default LZ77 sliding window size.

> Otherwise, the client MUST use a 32,768 byte LZ77 sliding window to
decompress received messages.

> Otherwise, the server MUST use a 32,768 byte LZ77 sliding window to
decompress received messages.


>
>      8.4.  Intermediaries . . . . . . . . . . . . . . . . . . . . . . 24
>
>  > Isn't this section identical to [Section 7] in this same spec?
>

Yes. Section 7 is talking about interaction with intermediaries in general,
and this section is saying almost the same thing but using
permessage-deflate specific language for example.

--001a11c28d345efd1404e8c8032c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Some addressed in -14. The rest will be addressed in =
-15.</div><div><br></div>On Wed, Oct 9, 2013 at 12:14 PM, Joakim Erdfelt <s=
pan dir=3D"ltr">&lt;<a href=3D"mailto:joakim@intalio.com" target=3D"_blank"=
>joakim@intalio.com</a>&gt;</span> wrote:<br>


<div class=3D"gmail_extra"><div class=3D"gmail_quote"><blockquote class=3D"=
gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border=
-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div=
 dir=3D"ltr">


<div><div>=A0 =A01. =A0Introduction . . . . . . . . . . . . . . . . . . . .=
 . . . . . =A03</div>
<div>=A0 =A0</div><div>=A0&gt; good</div><div>=A0&gt; +1 for the removal of=
 the PPP text</div><div></div></div></div></blockquote><div>=A0</div><div>Y=
es. It was broken after rendering HTML.</div><div><br></div><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;=
border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex=
">


<div dir=3D"ltr"><div><div>=A0 =A0</div><div>=A0 =A03. =A0Complementary Ter=
minology =A0. . . . . . . . . . . . . . . . . . =A05</div><div>=A0 =A0</div=
><div>=A0&gt; sufficient, would providing links to RFC6455 sections be wort=
hwhile?</div><div>


=A0&gt; example:</div>
<div>=A0</div><div>=A0- Non-control message means a message consists of non=
-control frames.</div><div>=A0+ Non-control message means a message that co=
nsists of non-control</div><div>=A0 =A0frames (e.g., data frames) as define=
d in [Section 5.6] of [RFC6455]</div>



<div></div></div></div></blockquote><div>done</div><div>=A0</div><blockquot=
e class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width=
:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-lef=
t:1ex">


<div dir=3D"ltr"><div><div>=A0 =A0</div><div>=A0- Message payload (or paylo=
ad of a message) means concatenation of the</div><div>=A0- payload data por=
tion of all frames consisting the message.</div><div>=A0+ Message payload (=
or payload of a message) means concatenation of the</div>



<div>=A0+ payload data portion of all data frames consisting of a single</d=
iv><div>=A0+ message, as defined in [Section 6] of [RFC6455]</div></div></d=
iv></blockquote><div><br></div><div>s/consisting of/representing/ ?</div><d=
iv>


<br></div><div>done</div><div>=A0</div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb=
(204,204,204);border-left-style:solid;padding-left:1ex"><div dir=3D"ltr"><d=
iv>

=A0</div>
<div>=A0&gt; no commentary on section for the paragraphs about Extension be=
havior</div>
<div>=A0&gt; as the reference to [Section 9] of [RFC6455] is handled in the=
 next</div><div>=A0&gt; section of this doc</div><div>=A0 =A0</div><div>=A0=
 =A0=A0</div><div>=A0 =A05. =A0Extension Negotiation =A0. . . . . . . . . .=
 . . . . . . . . . . =A07</div>


<div></div></div></blockquote><div><br></div><div>Used texts I showed in my=
 last reply.</div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,20=
4,204);border-left-style:solid;padding-left:1ex">


<div dir=3D"ltr"><div>=A0 =A0</div><div>=A0 =A0If a server gives an invalid=
 response, such as accepting a PMCE that<br></div>
<div>=A0 =A0the client did not offer, the client MUST _Fail the WebSocket</=
div><div>=A0 =A0Connection_.</div><div>=A0 =A0</div><div>=A0&gt; should we =
mention close code 1010 here?</div></div></blockquote><div><br></div><div>I=
&#39;m not sure if 1010 is for this kind of failure. The text in RFC 6455 s=
ounds like it&#39;s used to reject an opening handshake response that doesn=
&#39;t include extension(s) the client considered to be mandatory.</div>


<div><br></div><div>There isn&#39;t any extension with concept of mandatory=
 introduced yet. permessage-deflate is not mandatory extension. We just wan=
t to tell the server that it sent back an invalid extension response.</div>


<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left=
-style:solid;padding-left:1ex"><div dir=3D"ltr"><div>=A0=A0</div><div><br><=
/div></div>


</blockquote><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px =
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-=
style:solid;padding-left:1ex"><div dir=3D"ltr"><div>=A0 =A0 =A06.1. =A0Comp=
ression =A0. . . . . . . . . . . . . . . . . . . . . . . 10</div>



<div>=A0 =A0 =A0</div><div>=A0 =A02. =A0If this PMCE is the last extension =
to process outgoing messages,</div><div>=A0 =A0 =A0 =A0build frame(s) by us=
ing the compressed data instead of the</div><div>=A0 =A0 =A0 =A0original da=
ta for the message payload, and setting the</div>



<div><br></div><div>=A0&gt; The condition &quot;if this PCME is the last ex=
tension to process</div><div>=A0&gt; outgoing messages&quot; is meaningless=
, here and further down in this=A0</div><div>=A0&gt; section. =A0The proces=
s is the same for all PMCEs regardless if it is</div>



<div>=A0&gt; the first, middle, or last extension.</div><div>=A0&gt;</div><=
div>=A0&gt; Also, with the current spec, we would argue that it is impossib=
le</div><div>=A0&gt; to have multiple active PMCEs anyway (due to the RSV1 =
bit requirement)</div>



<div>=A0</div></div></blockquote><div><br></div><div>[TBA]</div><div>=A0</d=
iv><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bord=
er-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:soli=
d;padding-left:1ex">


<div dir=3D"ltr"><div>=A0 =A0 =A06.2. =A0Decompression =A0. . . . . . . . .=
 . . . . . . . . . . . . . 11</div><div>=A0 =A0 =A0</div><div>=A0&gt; Again=
, same commentary about the &quot;PCME is the last extension&quot;</div><di=
v>=A0&gt; condition being irrelevant</div>



<div>=A0 =A0 =A0</div></div></blockquote><div><br></div><div>[TBA]</div><di=
v>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.=
8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-st=
yle:solid;padding-left:1ex">


<div dir=3D"ltr"><div>=A0 =A07. =A0Intermediaries . . . . . . . . . . . . .=
 . . . . . . . . . . . 13</div><div>=A0 =A0</div><div>=A0&gt; good, but cou=
ld use some commentary that if the intermediaries are</div><div>=A0&gt; not=
 aware of the opening handshake, then they should make no</div>



<div>=A0&gt; modifications to the frames. =A0See [Section 5.4] of [RFC6455]=
</div><div>=A0&gt; 3rd paragraph for similar text.</div><div>=A0 =A0</div><=
/div></blockquote><div><br></div><div>[TBA]</div><div>=A0</div><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1=
px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:=
1ex">


<div dir=3D"ltr"><div>=A0 =A08. =A0permessage-deflate extension . . . . . .=
 . . . . . . . . . . . 14</div>
<div>=A0 =A0</div><div>=A0&gt; OK, some suggestions on how to clean this se=
ction up.</div><div>=A0&gt;</div><div>=A0&gt; Introduce the 4 extension par=
ameters first.</div><div>=A0&gt;</div><div>=A0&gt; =A0 Use the language fou=
nd elsewhere in the spec now about the asymmetric=A0</div>



<div>=A0&gt; =A0 nature of the extension parameter configuration.</div><div=
>=A0&gt; =A0=A0</div><div>=A0&gt; =A0 The following 2 extension parameters =
control the behavior of the</div><div>=A0&gt; =A0 deflate configuration for=
 Client-to-Server messages:</div>



<div>=A0&gt; =A0 (We took this notation from the title of [Section 5.3] of =
[RFC-6455],</div><div>=A0&gt; =A0 =A0including the capitalization)</div><di=
v>=A0&gt;</div><div>=A0&gt; =A0 =A0 o =A0&quot;c2s_no_context_takeover&quot=
;</div><div>=A0&gt; =A0 =A0 o =A0&quot;c2s_max_window_bits&quot;</div>



<div>=A0&gt;</div><div>=A0&gt; =A0 The following 2 extension parameters con=
trol the behavior of the</div><div>=A0&gt; =A0 deflate configuration for Se=
rver-to-Client messages:</div><div>=A0&gt;</div><div>=A0&gt; =A0 =A0 o =A0&=
quot;s2c_no_context_takeover&quot;</div>



<div>=A0&gt; =A0 =A0 o =A0&quot;s2c_max_window_bits&quot;</div><div>=A0&gt;=
</div><div>=A0&gt; Then describe how the Offer works. (essentially the lang=
uage you</div><div>=A0&gt; have now in the doc, with careful attention to n=
ot mix your intro</div>



<div>=A0&gt; and then bullets)</div><div>=A0&gt; =A0 =A0Request: desired cl=
ient behavior + desired server behavior</div><div>=A0&gt; =A0 =A0Response: =
acknowledge client behavior + server chosen behavior</div><div>=A0&gt;</div=
><div>=A0&gt; Example of confusing language:</div>



<div>=A0</div><div>=A0 =A0For an offer for this extension, the following 4 =
extension parameters</div><div>=A0 =A0are defined. =A0If needed to distingu=
ish from ones for a response,</div><div>=A0 =A0these parameters are called =
with a prefix &quot;client-to-server&quot;.</div>



<div><br></div><div>=A0 =A0o =A0&quot;s2c_no_context_takeover&quot;</div><d=
iv><br></div><div>=A0 =A0o =A0&quot;c2s_no_context_takeover&quot;</div><div=
><br></div><div>=A0 =A0o =A0&quot;s2c_max_window_bits&quot;</div><div><br><=
/div><div>=A0 =A0o =A0&quot;c2s_max_window_bits&quot;</div>



<div>=A0 =A0</div><div>=A0&gt; This section introduces you to &quot;client-=
to-server&quot;, then lists</div><div>=A0&gt; s2c_*, why? =A0Same for the n=
ext section, but in reverse.</div><div>=A0&gt; Don&#39;t mix the introducti=
on of the extension parameters and</div>



<div>=A0&gt; the behavior of the request and response together.</div><div>=
=A0&gt;</div><div>=A0&gt; Finally, go into the MUST rules for Client and Se=
rver like you</div><div>=A0&gt; currently have in the spec documentation.</=
div>


<div>
=A0&gt;</div><div>=A0&gt; Include wording for Client MUST pointing back to =
close code</div><div>=A0&gt; 1010 from [RC6455] as a recommended behavior f=
or dealing with</div><div>=A0&gt; bad extension negotiation.</div><div>=A0&=
gt; Even for things like a server saying s2c_max_window_bits=3D1024</div>



<div>=A0 =A0</div></div></blockquote><div><br></div><div>[TBA]</div><div>=
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8e=
x;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-styl=
e:solid;padding-left:1ex">


<div dir=3D"ltr"><div>=A0 =A0 =A08.1. =A0Method Parameters =A0. . . . . . .=
 . . . . . . . . . . . . . 15</div><div>=A0 =A0 =A0 =A08.1.1. =A0Context Ta=
keover Control . . . . . . . . . . . . . . . 15</div><div>=A0 =A0 =A0 =A0</=
div><div>=A0&gt; Include explicit language indicating default behavior for<=
/div>



<div>=A0&gt; context takeover.</div><div>=A0</div><div>=A0&gt; When documen=
ting one side, for example &quot;s2c_&quot;, do not make references</div><d=
iv>=A0&gt; to the opposite direction. =A0Its confusing, noisy, and adds no =
value.</div>



<div>=A0&gt;</div><div>=A0&gt; For example, Section 8.1.2.2. c2s_max_window=
_bits, start out talking</div><div>=A0&gt; about the c2s_max_window_bits, t=
hen has suddenly talks about=A0</div><div>=A0&gt; &quot;server-to-client pa=
rameter&quot;, mentioning behavior and server limits.</div>



<div>=A0&gt; This is confusing.</div><div>=A0&gt; Fix this, clarify it, eli=
minate the noise, or simplify it.</div><div>=A0&gt;</div><div>=A0&gt; Eg of=
 simplification:</div><div>=A0&gt;</div><div>=A0&gt; =A0See [Section 8.1.2.=
1.] &quot;s2c_max_window_bits&quot; for server side</div>



<div>=A0&gt; =A0equivalent</div><div>=A0&gt;</div><div>=A0&gt; We suspect t=
hat the use of &quot;c2s&quot; and &quot;client-to-server&quot; to=A0</div>=
<div>=A0&gt; interchangably refer to either the &quot;extension parameter t=
oken&quot; itself=A0</div>



<div>=A0&gt; or the phase of the extension negotiation (request or response=
) is</div><div>=A0&gt; the cause of the confusion.</div><div>=A0&gt;=A0</di=
v><div>=A0&gt; Either choose new terminology for the extension parameter to=
ken, or=A0</div>



<div>=A0&gt; choose new terminology for the phase of the extension negotiat=
ion</div><div>=A0&gt; (request side or response side)</div><div>=A0&gt;</di=
v></div></blockquote><div><br></div><div>[TBA]</div><div>=A0</div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-widt=
h:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-le=
ft:1ex">


<div dir=3D"ltr"><div>=A0 =A0 =A0 =A0</div><div>=A0 =A0 =A0 =A08.1.2. =A0Li=
miting the LZ77 sliding window size =A0. . . . . . . . 16</div>
<div>=A0 =A0 =A0 =A0</div><div>=A0&gt; Include explicit language indicating=
 default size for</div><div>=A0&gt; LZ77 sliding window size.</div></div></=
blockquote><div><br></div><div>Added texts.</div><div>=A0</div><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1=
px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:=
1ex">


<div dir=3D"ltr"><div>=A0&gt; RFC1979 seems to indicate 32KB as the maximum=
 value, but no obvious</div><div>=A0&gt; word on what is the default behavi=
or, assuming no window size is</div>
<div>=A0&gt; specifically declared.</div><div>=A0&gt;</div><div>=A0&gt; The=
 ABNF for the c2s_max_window_bits indicates that a digit is required,</div>=
<div>=A0&gt; but the text indicates that no value is possible.</div><div>=
=A0&gt; What does no-value mean?</div>



<div></div></div></blockquote><div><br></div><div>It means that only capabi=
lity is announced with no hint.</div><div><br></div><div>Added texts.</div>=
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left=
-style:solid;padding-left:1ex">


<div dir=3D"ltr"><div>=A0 =A0 =A0 =A0</div><div>=A0 =A0 =A0 =A08.1.3. =A0Ex=
ample =A0. . . . . . . . . . . . . . . . . . . . . . . 18</div><div>=A0 =A0=
 =A0 =A0</div><div>=A0&gt; See earlier commentary about no value c2s_max_wi=
ndow_bits extension</div><div>


=A0&gt; parameter token.</div>
<div>=A0&gt; See earlier commentary about extension negotiation for example=
 #3=A0</div><div>=A0&gt; (fallback behavior written into this spec)</div><d=
iv>=A0 =A0 =A0 =A0</div><div>=A0 =A0 =A08.2. =A0Message Payload Transformat=
ion . . . . . . . . . . . . . . 19</div>



<div>=A0 =A0 =A0</div><div>=A0&gt; good=A0</div><div>=A0&gt; (one note, the=
 BFINAL logic needs to be validated in current</div><div>=A0&gt; implementa=
tions. =A0as BFINAL does not behave the same in pywebsocket,</div><div>=A0&=
gt; autobahn, chrome, and safari). =A0We had to hack BFINAL to always be</d=
iv>



<div>=A0&gt; 0 for outgoing frames from our server in order for existing</d=
iv><div>=A0&gt; client implementations to work.</div></div></blockquote><di=
v><br></div><div>Sorry. Could you please elaborate this?</div><div>=A0</div=
>


<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div dir=3D"ltr"><div>=A0 =A0 =A0</div><div>=A0 =A0 =A0 =
=A08.2.3. =A0Examples . . . . . . . . . . . . . . . . . . . . . . . 21<br>


</div>
<div>=A0 =A0 =A0 =A0</div><div>=A0&gt; Include example of multiple message =
behavior with no_context_takeover</div><div>=A0&gt; configured.</div></div>=
</blockquote><div><br></div><div>In &quot;Sharing LZ77 Sliding Window&quot;=
 section, the second example is identical to the first one. This is the exa=
mple of multiple message behavior with no_context_takeover.<br>


</div><div><br></div><div><div>&gt; =A0 This is the payload of the first me=
ssage the client has sent. =A0If the</div><div>&gt; =A0 &quot;agreed parame=
ters&quot; contain the &quot;c2s_no_context_takeover&quot; extension</div><=
div>


&gt; =A0 parameter, the client compresses the payload of the next message i=
nto</div><div>&gt; =A0 the same bytes (if the client uses the same &quot;BT=
YPE&quot; value and</div><div>&gt; =A0 &quot;BFINAL&quot; value). =A0So, th=
e payload of the second message will be:</div>


<div>&gt;</div><div>&gt; =A0 =A0 =A0 0xf2 0x48 0xcd 0xc9 0xc9 0x07 0x00</di=
v></div><div><br></div><div>Added concatenated examples.</div><div>=A0</div=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;=
padding-left:1ex">


<div dir=3D"ltr"><div>=A0 =A0 =A0 =A0</div><div>=A0 =A0 =A08.3. =A0Implemen=
tation Notes . . . . . . . . . . . . . . . . . . . 24</div>
<div>=A0 =A0 =A0</div><div>=A0&gt; This section&#39;s updates are good.</di=
v><div>=A0&gt; The LZ77 sliding window size recommendation is ok, but where=
&#39;s the</div><div>=A0&gt; default LZ77 sliding window size?</div></div><=
/blockquote>


<div><br></div><div>This sentence in &quot;Compression&quot; section</div><=
div><br></div><div>&gt; An endpoint MUST NOT use an LZ77 sliding window lon=
ger than 32,768 bytes to compress messages to send.</div><div><br></div>


<div>and these sentences in &quot;Decompression&quot; section are intended =
to define default LZ77 sliding window size.</div><div><br></div><div>&gt; O=
therwise, the client MUST use a 32,768 byte LZ77 sliding window to decompre=
ss received messages.<br>


</div><div><br></div><div>&gt; Otherwise, the server MUST use a 32,768 byte=
 LZ77 sliding window to decompress received messages.<br></div><div>=A0</di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid=
;padding-left:1ex">


<div dir=3D"ltr"><div>=A0 =A0 =A0</div>
<div>=A0 =A0 =A08.4. =A0Intermediaries . . . . . . . . . . . . . . . . . . =
. . . . 24</div><div>=A0 =A0 =A0</div><div>=A0&gt; Isn&#39;t this section i=
dentical to [Section 7] in this same spec?</div></div></blockquote><div><br=
></div><div>


Yes. Section 7 is talking about interaction with intermediaries in general,=
 and this section is saying almost the same thing but using permessage-defl=
ate specific language for example.</div><div>=A0</div></div></div></div>


--001a11c28d345efd1404e8c8032c--

From tyoshino@google.com  Tue Oct 15 07:01:25 2013
Return-Path: <tyoshino@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C831C21E80BF for <hybi@ietfa.amsl.com>; Tue, 15 Oct 2013 07:01:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.927
X-Spam-Level: 
X-Spam-Status: No, score=-1.927 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DLsrmZy-CytD for <hybi@ietfa.amsl.com>; Tue, 15 Oct 2013 07:01:25 -0700 (PDT)
Received: from mail-ee0-x22f.google.com (mail-ee0-x22f.google.com [IPv6:2a00:1450:4013:c00::22f]) by ietfa.amsl.com (Postfix) with ESMTP id CCA4221E815B for <hybi@ietf.org>; Tue, 15 Oct 2013 07:01:13 -0700 (PDT)
Received: by mail-ee0-f47.google.com with SMTP id d49so4034793eek.34 for <hybi@ietf.org>; Tue, 15 Oct 2013 07:01:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=rmQZ9MYqoBUtnnvZ/Gkr7aKh25nwBZs4KjApdn0XCYg=; b=SK8COuezmzcoPPsuRyQuwyHrPsC6mjQFS7YUTh3wJtNkAbQtjyrM25MK1k7iuELWFQ UjyJUlDSCDiOuVhk9DpW6ub0fKZt+mBO3s1CFq6FiAWmhlelY01H/te8KBN6rIRjGhlL AfT6iNNkDSf5wZB2zwMxJlSzi3U231PgS1aGZ5qMFAqQce5/vEmOdd6MlL73Hu/8TY6w lEZnIi3QMcSeoagV2A7IHO+NtQ50Fy+HOFuo5JQFL7jJjNiQExpPEercU0masf4poPX1 ziLUw7LahHrcY2cLBjQg2mJ8sHPI6/Tga+yDljRm62BFWaI6LCYEia1hj2/8AEVqheTM 6RpQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=rmQZ9MYqoBUtnnvZ/Gkr7aKh25nwBZs4KjApdn0XCYg=; b=MOovK3+Lt8zgCOqGwzYosABer/3d8FACfE3RHKiOVxtTGf6eLRZR438oMgD3Q90Hpe ZkVUzD8nFsKYaOb6H8aQZP6tmR24EmNfz/ke0KAMrrgIpcZII7ASoRC3BCpLZxLga7CV shASLQO3Le8khUzBrxuzf8NQJVS51ja40loykpHJC/HYorcCaNz6tpvFrtlwSSAun7Rw q4+rzdnvDsWcSSirDs2Oqakb5B878IsO65gxCWzYe9ylDh0RgZi2eeq0zuIbrX5GGzrJ /62rE3hZbY+0lBKDbCb4zgHDfUvOCeGuQCXAWIipcT2jljBxtv+McEyCDCMh5kExs7Fz AXvg==
X-Gm-Message-State: ALoCoQlsz/wg0f7j/LgFGj/X0AWidGCAkx+D9soXG+kHC8NrtoMN/y93fu6eH3IeSU6pMG/Zx3yIxZ7JLL3ed6T5vyWsXmeAUVb+BfPDfLmmNyWvMvI+n5yyJA6c5jcrOlvgMI1bEilDqDqFXYz32J8klt7ULsGLsLRQn6x0ngKvqZzxYHWFTje0WyKHcSqEHpFdWFm2H2e1
X-Received: by 10.14.113.137 with SMTP id a9mr945486eeh.3.1381845672957; Tue, 15 Oct 2013 07:01:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.49.140 with HTTP; Tue, 15 Oct 2013 07:00:52 -0700 (PDT)
In-Reply-To: <634914A010D0B943A035D226786325D4446790C068@EXVMBX020-12.exch020.serverdata.net>
References: <CAH9hSJbwd5qhMJw=3dwk3CDPua5ENRksd9=q2KDcyyma3uKzZg@mail.gmail.com> <CAG4zZZD8eq4w9kyQbX2AJcM1LA8=UyRO7txK7TvmYhSp=YU+9g@mail.gmail.com> <634914A010D0B943A035D226786325D4446790BF34@EXVMBX020-12.exch020.serverdata.net> <CAG4zZZDNRZ_kaXBKhx5VkKjpj+Luo53Y7ue0eaGHH_ghoBrdkQ@mail.gmail.com> <634914A010D0B943A035D226786325D4446790BFFC@EXVMBX020-12.exch020.serverdata.net> <qb0u491vbecgjihjhkd6d75jo0uoka5al2@hive.bjoern.hoehrmann.de> <634914A010D0B943A035D226786325D4446790C068@EXVMBX020-12.exch020.serverdata.net>
From: Takeshi Yoshino <tyoshino@google.com>
Date: Tue, 15 Oct 2013 23:00:52 +0900
Message-ID: <CAH9hSJamrgEUCdMcaoj2DeEr9k6D-x6zPSqX08SWo3_Hvi0S=Q@mail.gmail.com>
To: Tobias Oberstein <tobias.oberstein@tavendo.de>
Content-Type: multipart/alternative; boundary=001a1133a71878b28104e8c804b4
Cc: "hybi@ietf.org" <hybi@ietf.org>, Bjoern Hoehrmann <derhoermi@gmx.net>, Gabriel Montenegro <Gabriel.Montenegro@microsoft.com>
Subject: Re: [hybi] Restarting IESG review on permessage-deflate
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 15 Oct 2013 14:01:26 -0000

--001a1133a71878b28104e8c804b4
Content-Type: text/plain; charset=ISO-8859-1

On Sat, Oct 5, 2013 at 3:34 AM, Tobias Oberstein <
tobias.oberstein@tavendo.de> wrote:

> The Deflate RFC
>
> http://tools.ietf.org/html/rfc1951
>
> is only listed under informational.
>
> This is strange, since the "permessage-deflate" extension is not only
> LZ77, but really Deflate (= LZ77 + Huffman Coding + Window Size .. see
> below).
>

Fixed in -14.

--001a1133a71878b28104e8c804b4
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra">On Sat, Oct 5, 2013 at 3:34 AM,=
 Tobias Oberstein <span dir=3D"ltr">&lt;<a href=3D"mailto:tobias.oberstein@=
tavendo.de" target=3D"_blank">tobias.oberstein@tavendo.de</a>&gt;</span> wr=
ote:<br>


<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><span style=
=3D"color:rgb(34,34,34)">The Deflate RFC</span><br></div>
<br>
<a href=3D"http://tools.ietf.org/html/rfc1951" target=3D"_blank">http://too=
ls.ietf.org/html/rfc1951</a><br>
<br>
is only listed under informational.<br>
<br>
This is strange, since the &quot;permessage-deflate&quot; extension is not =
only LZ77, but really Deflate (=3D LZ77 + Huffman Coding + Window Size .. s=
ee below).<br></blockquote><div><br></div><div>Fixed in -14.</div><div>=A0<=
/div>


</div></div></div>

--001a1133a71878b28104e8c804b4--

From tyoshino@google.com  Tue Oct 15 07:01:42 2013
Return-Path: <tyoshino@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B41ED21E815A for <hybi@ietfa.amsl.com>; Tue, 15 Oct 2013 07:01:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.931
X-Spam-Level: 
X-Spam-Status: No, score=-1.931 tagged_above=-999 required=5 tests=[AWL=0.046,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ocPsobfAAJsl for <hybi@ietfa.amsl.com>; Tue, 15 Oct 2013 07:01:41 -0700 (PDT)
Received: from mail-ea0-x22a.google.com (mail-ea0-x22a.google.com [IPv6:2a00:1450:4013:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 6661221E8123 for <hybi@ietf.org>; Tue, 15 Oct 2013 07:01:25 -0700 (PDT)
Received: by mail-ea0-f170.google.com with SMTP id h14so4018272eak.15 for <hybi@ietf.org>; Tue, 15 Oct 2013 07:01:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=LUplJLmBIbr/eSjgSo/C/H+e/i7zkukcjd7miMjCzpc=; b=ZJMrRltu43E6KblwCUNFWlhTYfE19JrOLqgw70t58UStOoD59n3DQ/fdXtCSiVqer9 V39jeGBFMpIqciZDYhLuXuFSpPQ9w/QFEBQ/SdGDILtVa+B5utOfhnu+w9NMVx7Ob3/C 3AwlysVRFYcFA8MHPMaLVEdD7ohwu5KckGB2ClJwnWYfX3gnooWPMcr87GWO7O8T/mdr r9amZcEhy+BcoMgKFLt6bM9QKNfMqhRGzqr0wHqOfG+opyMk34Uqcm9HpQJWJMftAzPm vjCw4/3qh+WdyK7B+lmJPOREGCCfoUuOb/oWrwgiZ38WdJR3Yi6TrI4MKZIg4rOu8Gkp PNzg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=LUplJLmBIbr/eSjgSo/C/H+e/i7zkukcjd7miMjCzpc=; b=cq8QJgv5t3z2tZBv9Dp3iMcQbk9q3YoVpqRTXdOwsM0t+Qckavm3kZx3rTb4plr2q2 G7l55gCQPmKhzPKVMOmKHEtKtV2QTrrBbfnBKVfwEc+M80k1rHi4veRVns18RJiePtBQ NsZkLvuyOuUyqJda9e75F8O2jfIVuLZG5JB8IFwSlhklFx+heZloORZ/BZYz+Qkon6nk 1Np/Xoywz8wzTcwrkkeiyPYFJ+STl3ADfSWnz3NY5m0lRh5Xd3uU4KttpY3b/fXgZipU yd8Cxoonn2jQBPFu+LbanaGlW/1Lrxu17+J81JDY1bB3YJuqz8+cAdY4t7Nwd5zg69s2 wsfA==
X-Gm-Message-State: ALoCoQnwedHDuSbOR90k05x2fxVonNSwJjuNoXODfIAHsLVmeUkXJZ0IlboJTw6eVv1wtqONXjftGBnm8NtLIlf+iqlW8uOPB5pcmL28kv7Fnn3Rxe0L48M0DEU+omJU6MXxPihvmKYN9eQ3bcFZU0qzbXccxhueQk4U6D7iyNpZ/ccWKxgYpSjVw2A52TS88aXiIzuNKa+p
X-Received: by 10.14.251.76 with SMTP id a52mr907068ees.76.1381845684555; Tue, 15 Oct 2013 07:01:24 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.49.140 with HTTP; Tue, 15 Oct 2013 07:01:04 -0700 (PDT)
In-Reply-To: <F18056D3-5BE0-4064-96FF-F15C709DB51C@zaphoyd.com>
References: <CAH9hSJbwd5qhMJw=3dwk3CDPua5ENRksd9=q2KDcyyma3uKzZg@mail.gmail.com> <CAG4zZZD8eq4w9kyQbX2AJcM1LA8=UyRO7txK7TvmYhSp=YU+9g@mail.gmail.com> <634914A010D0B943A035D226786325D4446790BF34@EXVMBX020-12.exch020.serverdata.net> <dmnt49hf1bbifiote81fumeamnk76vti1t@hive.bjoern.hoehrmann.de> <634914A010D0B943A035D226786325D4446790BF87@EXVMBX020-12.exch020.serverdata.net> <CAG4zZZDdcC5+cob715KE77uZiPYAo1Oz6M0StLA=vSp5iX_h7A@mail.gmail.com> <F18056D3-5BE0-4064-96FF-F15C709DB51C@zaphoyd.com>
From: Takeshi Yoshino <tyoshino@google.com>
Date: Tue, 15 Oct 2013 23:01:04 +0900
Message-ID: <CAH9hSJZsW8nPLeSH2OE33e5ESzz2oMpeQSqNNmaVCcb=2eoACg@mail.gmail.com>
To: Peter Thorson <webmaster@zaphoyd.com>
Content-Type: multipart/alternative; boundary=001a1132f39e29ad7004e8c80591
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] Restarting IESG review on permessage-deflate
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 15 Oct 2013 14:01:42 -0000

--001a1132f39e29ad7004e8c80591
Content-Type: text/plain; charset=ISO-8859-1

Thanks, Peter. I replaced mine with your text in -14.


On Sat, Oct 5, 2013 at 4:56 AM, Peter Thorson <webmaster@zaphoyd.com> wrote:

> ======= Possible clarification =======
>
> Four extension parameters are defined for permessage-deflate to help
> endpoints manage per-connection resource usage.
>
> - "s2c_no_context_takeover"
> - "c2s_no_context_takeover"
> - "s2c_max_window_bits"
> - "c2s_max_window_bits"
>
> These represent two methods of constraining memory usage that may be
> applied independently to either direction of WebSocket traffic.
> The prefixes
> c2s and s2c are used to indicate the client-to-server channel and the
> server-to-client channel respectively. All four parameters are defined for
> both
> a client's offer and a server's response.
>
> =====================
>

--001a1132f39e29ad7004e8c80591
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Thanks, Peter. I replaced mine with your text in -14.=
</div><div><br></div><div><br></div>On Sat, Oct 5, 2013 at 4:56 AM, Peter T=
horson <span dir=3D"ltr">&lt;<a href=3D"mailto:webmaster@zaphoyd.com" targe=
t=3D"_blank">webmaster@zaphoyd.com</a>&gt;</span> wrote:<br>


<div class=3D"gmail_extra"><div class=3D"gmail_quote"><blockquote class=3D"=
gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-=
left:1ex"><div style=3D"word-wrap:break-word"><div><div><div><span style=3D=
"color:rgb(34,34,34)">=3D=3D=3D=3D=3D=3D=3D=A0Possible clarification=A0=3D=
=3D=3D=3D=3D=3D=3D</span><br>


</div></div><div><br></div><div>Four extension parameters are defined for p=
ermessage-deflate to help=A0</div><div>endpoints manage per-connection reso=
urce usage.</div><div><br></div><div>-=A0&quot;s2c_no_context_takeover&quot=
;</div>


<div>-=A0&quot;c2s_no_context_takeover&quot;</div><div>-=A0&quot;s2c_max_wi=
ndow_bits&quot;</div><div>-=A0&quot;c2s_max_window_bits&quot;</div><div><br=
></div><div>These represent two methods of constraining memory usage that m=
ay be=A0</div>


<div>applied independently to either direction of WebSocket traffic. The=A0=
prefixes=A0</div><div>c2s and s2c are used=A0to indicate the client-to-serv=
er channel and the=A0</div><div>server-to-client channel respectively. All =
four parameters are defined for both=A0</div>


<div>a client&#39;s offer and a server&#39;s response.</div><div><br></div>=
<div>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</div><=
/div></div></blockquote><div>=A0</div></div></div></div>

--001a1132f39e29ad7004e8c80591--

From tyoshino@google.com  Tue Oct 15 07:03:11 2013
Return-Path: <tyoshino@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0397211E817B for <hybi@ietfa.amsl.com>; Tue, 15 Oct 2013 07:03:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.288
X-Spam-Level: 
X-Spam-Status: No, score=-1.288 tagged_above=-999 required=5 tests=[AWL=-0.603, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MISSING_HEADERS=1.292, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8ehaAmcOejB6 for <hybi@ietfa.amsl.com>; Tue, 15 Oct 2013 07:03:10 -0700 (PDT)
Received: from mail-ee0-x22f.google.com (mail-ee0-x22f.google.com [IPv6:2a00:1450:4013:c00::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 5655121E80CC for <hybi@ietf.org>; Tue, 15 Oct 2013 07:03:02 -0700 (PDT)
Received: by mail-ee0-f47.google.com with SMTP id d49so3956914eek.20 for <hybi@ietf.org>; Tue, 15 Oct 2013 07:03:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:cc :content-type; bh=Tc7es+j1zDQOqusHBN6BOtRY3mRBHGYuuRlvd0njvpI=; b=SUSnOL0vyOLrF2fXBoj1MdC/Z5qORYz9OVDAId9T+jjap4/pWDjhVP+wSqPpw2akFm tKFZMojFcrtDGR+Dsj6gQeWqEoHvk28fGXJ3yjngvNG5YZfw2l5SUULi5se32kTgomsj ayKNR5CUkwRYZtO/J/RTrtzAfloMp2IO5MjmzjoO+8VSVbFez0UdeVQSsAkCn+6x6WTR nHah2i+AZwrM2ZMlgq5v1cJYm00ORsqKTZ3m9kqtUONKgXcuTsl0dSf0nKys4P2WaBj8 YRxc6e1TN0cczt9FLAGVWvZzFfaNhc699nVmka7I1Pb9aGcxzaaXbz6HOmtgnD/SwVZN BYUA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:cc:content-type; bh=Tc7es+j1zDQOqusHBN6BOtRY3mRBHGYuuRlvd0njvpI=; b=S80relcwiMmX+3QVb8hryo7VcrcYXtdYOao6UjV+maXR1Kqk5TQwTiR46ASLTAQfCU suhgF5B1PXkVLWkq88MoYmfp+ugyCf/BOwG8Md/TsZJMDAonkfTZA44dJ3O6m8RzEdx1 v2i2e+cb2CPjwb36bbf0ST+Ibo1sK/qmiHV2iZ/OMhUXJw8MDxZ1NBw5bBVJE+DUMC91 hArB0kRZsZkSr5Q/XSRY/A3sX/w7XTf7IgisEERksJrmvCML8uRggbIoyYoaAAe89T2D spXoWI/yABtycCJjQ3zFVw6PUYLIIME+RXfBo/Q1lEEC18xvQiRJwyQpMQtI7zoUkWhy ZG7g==
X-Gm-Message-State: ALoCoQlA9ZmNWAboXojGI/8fME9950i67PZ6h73w9X8NF64wwcF1z142H28hWMVjr2dpijjSoDZcIdxvDenfTWrxH5nC4+U9L4WxbH3CpJZOzJvIGvJLpq1fLnPxxmnXWksdInGBXR1NIv/qfr7D3fHCa0Bvp4x4/y9mM6En5SjrTp6rIGYbdk79Ct50WxtHLlSkQamJ489Q
X-Received: by 10.14.214.136 with SMTP id c8mr956183eep.6.1381845781502; Tue, 15 Oct 2013 07:03:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.49.140 with HTTP; Tue, 15 Oct 2013 07:02:41 -0700 (PDT)
In-Reply-To: <20131015140016.2154.93984.idtracker@ietfa.amsl.com>
References: <20131015140016.2154.93984.idtracker@ietfa.amsl.com>
From: Takeshi Yoshino <tyoshino@google.com>
Date: Tue, 15 Oct 2013 23:02:41 +0900
Message-ID: <CAH9hSJZg7Z9RNJuHbbwnpe_79uzF0Ebd60JR5MO9zUUD6rSr5A@mail.gmail.com>
Cc: "hybi@ietf.org" <hybi@ietf.org>
Content-Type: multipart/alternative; boundary=047d7b624320f0fbb204e8c80a4f
Subject: Re: [hybi] I-D Action: draft-ietf-hybi-permessage-compression-14.txt
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 15 Oct 2013 14:03:11 -0000

--047d7b624320f0fbb204e8c80a4f
Content-Type: text/plain; charset=ISO-8859-1

Addressed Tobias and Peter's comments, and half of Jetty's commentary from
Joakim.

Takeshi


On Tue, Oct 15, 2013 at 11:00 PM, <internet-drafts@ietf.org> wrote:

>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>  This draft is a work item of the BiDirectional or Server-Initiated HTTP
> Working Group of the IETF.
>
>         Title           : Compression Extensions for WebSocket
>         Author(s)       : Takeshi Yoshino
>         Filename        : draft-ietf-hybi-permessage-compression-14.txt
>         Pages           : 30
>         Date            : 2013-10-15
>
> Abstract:
>    This document specifies 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 non-control WebSocket messages on a per-message basis using
>    parameters negotiated during the opening handshake.  This framework
>    provides a general method to apply a compression algorithm to the
>    contents of WebSocket messages.  For each compression algorithm, an
>    extension is defined by specifying parameter negotiation and
>    compression algorithm in detail.  This document also specifies one
>    specific compression extension using the DEFLATE algorithm.
>
>    Please send feedback to the hybi@ietf.org mailing list.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-hybi-permessage-compression
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-hybi-permessage-compression-14
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-hybi-permessage-compression-14
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi
>

--047d7b624320f0fbb204e8c80a4f
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Addressed Tobias and Peter&#39;s comments, and half of Jet=
ty&#39;s commentary from Joakim.</div><div class=3D"gmail_extra"><br clear=
=3D"all"><div>Takeshi</div>
<br><br><div class=3D"gmail_quote">On Tue, Oct 15, 2013 at 11:00 PM,  <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:internet-drafts@ietf.org" target=3D"_bla=
nk">internet-drafts@ietf.org</a>&gt;</span> wrote:<br><blockquote class=3D"=
gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-=
left:1ex">

<br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
=A0This draft is a work item of the BiDirectional or Server-Initiated HTTP =
Working Group of the IETF.<br>
<br>
=A0 =A0 =A0 =A0 Title =A0 =A0 =A0 =A0 =A0 : Compression Extensions for WebS=
ocket<br>
=A0 =A0 =A0 =A0 Author(s) =A0 =A0 =A0 : Takeshi Yoshino<br>
=A0 =A0 =A0 =A0 Filename =A0 =A0 =A0 =A0: draft-ietf-hybi-permessage-compre=
ssion-14.txt<br>
=A0 =A0 =A0 =A0 Pages =A0 =A0 =A0 =A0 =A0 : 30<br>
=A0 =A0 =A0 =A0 Date =A0 =A0 =A0 =A0 =A0 =A0: 2013-10-15<br>
<br>
Abstract:<br>
=A0 =A0This document specifies a framework for creating WebSocket extension=
s<br>
=A0 =A0that add compression functionality to the WebSocket Protocol. =A0An<=
br>
=A0 =A0extension based on this framework compresses the payload data portio=
n<br>
=A0 =A0of non-control WebSocket messages on a per-message basis using<br>
=A0 =A0parameters negotiated during the opening handshake. =A0This framewor=
k<br>
=A0 =A0provides a general method to apply a compression algorithm to the<br=
>
=A0 =A0contents of WebSocket messages. =A0For each compression algorithm, a=
n<br>
=A0 =A0extension is defined by specifying parameter negotiation and<br>
=A0 =A0compression algorithm in detail. =A0This document also specifies one=
<br>
=A0 =A0specific compression extension using the DEFLATE algorithm.<br>
<br>
=A0 =A0Please send feedback to the <a href=3D"mailto:hybi@ietf.org">hybi@ie=
tf.org</a> mailing list.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-hybi-permessage-comp=
ression" target=3D"_blank">https://datatracker.ietf.org/doc/draft-ietf-hybi=
-permessage-compression</a><br>
<br>
There&#39;s also a htmlized version available at:<br>
<a href=3D"http://tools.ietf.org/html/draft-ietf-hybi-permessage-compressio=
n-14" target=3D"_blank">http://tools.ietf.org/html/draft-ietf-hybi-permessa=
ge-compression-14</a><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-hybi-permessage-co=
mpression-14" target=3D"_blank">http://www.ietf.org/rfcdiff?url2=3Ddraft-ie=
tf-hybi-permessage-compression-14</a><br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" target=3D"_blank">ftp://ftp=
.ietf.org/internet-drafts/</a><br>
<br>
_______________________________________________<br>
hybi mailing list<br>
<a href=3D"mailto:hybi@ietf.org">hybi@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/hybi" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/hybi</a><br>
</blockquote></div><br></div>

--047d7b624320f0fbb204e8c80a4f--

From tyoshino@google.com  Tue Oct 15 07:09:11 2013
Return-Path: <tyoshino@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8666021F9E1A for <hybi@ietfa.amsl.com>; Tue, 15 Oct 2013 07:09:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level: 
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[AWL=0.081,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ar0anqJs5bTJ for <hybi@ietfa.amsl.com>; Tue, 15 Oct 2013 07:09:11 -0700 (PDT)
Received: from mail-ea0-x232.google.com (mail-ea0-x232.google.com [IPv6:2a00:1450:4013:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id E621621F8C7C for <hybi@ietf.org>; Tue, 15 Oct 2013 07:09:10 -0700 (PDT)
Received: by mail-ea0-f178.google.com with SMTP id a15so4014272eae.37 for <hybi@ietf.org>; Tue, 15 Oct 2013 07:09:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=ei/2ioI6wEd3FHB0L9bDMPyOv8xFMrLBO9+ricvdTtk=; b=Fr4L6hw1sE/u1cJVGTfqWQh2olp9GBLDZwKF8JiXyvXqvGVyLTDblLHUM2ars/sB0w t+nr9yex7jK0X4NFu4hxdWbk9CFE5Tf/JvLU59fHWDb3nvnfa2hduIElbrXaIWJrukcP oplJ8GbRigEr9Sn8j43oxsJZZX0y4Kz1+YIyBEm04hC0EcFl9cpeaxiv+l9LYA2kWnry OxpNxL1qcaa/FdmlFA0cFzrWsXGbD2+ehfBbHrkr6BGmSLzAwyD7kvgSAE2twxPGjUsU gh8DhiGWnEYCzD09To2snVfX5aVrvri5Nb6DaChZgZa9bHe4sppk/ubb/u5npy8v3CR+ V1Dg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=ei/2ioI6wEd3FHB0L9bDMPyOv8xFMrLBO9+ricvdTtk=; b=FnEBOdsymJrB1ah7MiIlgCQLHMyJJzS/jw/q+FsXQ0Yw79p+ctGIXCcpYxxCgjVbT8 5K3zHQtjCOXQgP6mUInw+vLwxTKLTnK0do8t01WGCSlAOIsN/GUbAEyMcYs0J+JPlAQ/ D8hvcYc9rBw68Aje1Muc5oQcf8AFtTiQnFodzXi2RjjXb4Add2izgCQ5U8AGegEZzyB4 PzJ1ZqEjXZ3pRkVz+WapLgmNRNJJ5dCpTX3ypU/urg7sdBJasn0+ZSe/fw8nqKIsqh6U h392ZUilakweAoope+JHu1N1zxFaSCwGD5zpVrfLXpXTgySdHf0kctYy6hhRvgZ1LgE/ Mq1A==
X-Gm-Message-State: ALoCoQlJORYniQkTmP0pWgni8CdP+PmkuuWiogE5c5K0ZKCVCnDEUSuFS9xhaIDnFD/ekk4f5kU8714euFUUwILY0wp15lc9X1Ru3N3uXKYZgl54Smj2a3pmi+MuVZ7owDylhquboO3KSd338s4xO0IPNxKiFmdBcfUtk/XCFUUIZldysJJEbzvvk5azUraoTKRn6IqNX3CF
X-Received: by 10.14.109.66 with SMTP id r42mr987869eeg.43.1381846150052; Tue, 15 Oct 2013 07:09:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.49.140 with HTTP; Tue, 15 Oct 2013 07:08:49 -0700 (PDT)
In-Reply-To: <5BEA69BA-D0D4-4F4A-8CFB-741A433EAAA6@zaphoyd.com>
References: <CAH9hSJant3VBw0FBM69V9wPvi3WmJLikZdX4ySELy+CShgoOKA@mail.gmail.com> <5BEA69BA-D0D4-4F4A-8CFB-741A433EAAA6@zaphoyd.com>
From: Takeshi Yoshino <tyoshino@google.com>
Date: Tue, 15 Oct 2013 23:08:49 +0900
Message-ID: <CAH9hSJYNrBkf=2=2DHdipvXwN4XEKDe2BOc4g1eZr38U7m7jdw@mail.gmail.com>
To: Peter Thorson <webmaster@zaphoyd.com>, Joakim Erdfelt <joakim@intalio.com>
Content-Type: multipart/alternative; boundary=001a11c1ac12e8960e04e8c820ba
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] [permessage-deflate] Renaming s2c_ and c2s_ prefix to server_ and client_
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 15 Oct 2013 14:09:11 -0000

--001a11c1ac12e8960e04e8c820ba
Content-Type: text/plain; charset=ISO-8859-1

Thanks, all.

Joakim, please show Jetty's opinion again. Then, I'll make decision to move
forward.

Tobias: neutral
Peter: neutral slight preference for s2c_
Takeshi: neutral slight preference for s2c_
Joakim: preference for server_

--001a11c1ac12e8960e04e8c820ba
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thanks, all.<div><br></div><div>Joakim, please show Jetty&=
#39;s opinion again. Then, I&#39;ll make decision to move forward.</div><di=
v><br></div><div>Tobias: neutral</div><div>Peter: neutral slight preference=
 for s2c_</div>


<div>Takeshi: neutral slight preference for s2c_</div><div>Joakim: preferen=
ce for server_</div><div>=A0</div></div>

--001a11c1ac12e8960e04e8c820ba--

From joakim@intalio.com  Tue Oct 15 08:13:36 2013
Return-Path: <joakim@intalio.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21FEA11E81E0 for <hybi@ietfa.amsl.com>; Tue, 15 Oct 2013 08:13:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QA4RI4nuBNgZ for <hybi@ietfa.amsl.com>; Tue, 15 Oct 2013 08:13:32 -0700 (PDT)
Received: from mail-ea0-f175.google.com (mail-ea0-f175.google.com [209.85.215.175]) by ietfa.amsl.com (Postfix) with ESMTP id 8382F11E8192 for <hybi@ietf.org>; Tue, 15 Oct 2013 08:13:25 -0700 (PDT)
Received: by mail-ea0-f175.google.com with SMTP id m14so4002451eaj.6 for <hybi@ietf.org>; Tue, 15 Oct 2013 08:13:24 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=e68Wm8XsblGgK6KYQsqZclph3mlwYHr4Jq7V1vqrYQo=; b=SThz8S/3e+XmbpGq3g59iwJlWG/M6PJTg7oGqPHhz+LwTg08cBO+tv67IvWMwJsWUs 56GwI19MaLrY1OI6dBp6gmuvM3TBCkRYLbRybSfFbx8QYpgWmyCAwGkcr3g3+fT/3HrF 1YEUbu2qbDAjsrURidwEUqK7PpAB69fMSCAmkWbpmFO2jmPkcHHkPOpwo41rYoG76onX AHrIjbAAWQ8pM4aXif1uDfvrGNAp5C22nSPmjNbMLSaELg7r+BV8QQz/4YoroUO0n3ZF Jn44bzwOpqyQpmnLbxR0pBev9rVo98SgKcY4WEgBDPR0xtZzET6iuxTwHpvGP097Te8p g1Jw==
X-Gm-Message-State: ALoCoQmlQtsF0ld5aPEirkvFDnOFJqZ0I8jRqTO7EcSHZWm5u6SS1shMDINOx5zLkxVYjSmpnXJP
MIME-Version: 1.0
X-Received: by 10.14.203.70 with SMTP id e46mr1412911eeo.33.1381850004497; Tue, 15 Oct 2013 08:13:24 -0700 (PDT)
Received: by 10.14.133.74 with HTTP; Tue, 15 Oct 2013 08:13:24 -0700 (PDT)
In-Reply-To: <CAH9hSJYNrBkf=2=2DHdipvXwN4XEKDe2BOc4g1eZr38U7m7jdw@mail.gmail.com>
References: <CAH9hSJant3VBw0FBM69V9wPvi3WmJLikZdX4ySELy+CShgoOKA@mail.gmail.com> <5BEA69BA-D0D4-4F4A-8CFB-741A433EAAA6@zaphoyd.com> <CAH9hSJYNrBkf=2=2DHdipvXwN4XEKDe2BOc4g1eZr38U7m7jdw@mail.gmail.com>
Date: Tue, 15 Oct 2013 08:13:24 -0700
Message-ID: <CAG4zZZDtUEnvgPmcKWsE9mFockUYA0PDFUE1SxNr+ubN0v9=xg@mail.gmail.com>
From: Joakim Erdfelt <joakim@intalio.com>
To: Takeshi Yoshino <tyoshino@google.com>
Content-Type: multipart/alternative; boundary=047d7b3440f4a6b5ef04e8c906b6
Cc: "hybi@ietf.org" <hybi@ietf.org>, Peter Thorson <webmaster@zaphoyd.com>
Subject: Re: [hybi] [permessage-deflate] Renaming s2c_ and c2s_ prefix to server_ and client_
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 15 Oct 2013 15:13:36 -0000

--047d7b3440f4a6b5ef04e8c906b6
Content-Type: text/plain; charset=ISO-8859-1

The problem is the language choices in the spec already.

Take this for example: (from Section
8.1.2.2<http://tools.ietf.org/html/draft-ietf-hybi-permessage-compression-13#section-8.1.2.2>of
draft-ietf-hybi-permessage-compression-13)

8.1.2.2.  c2s_max_window_bits

   A client MAY include the "c2s_max_window_bits" extension parameter in
   an offer.  This parameter has no value or a decimal integer value
   without leading zeroes between 8 to 15 inclusive indicating the
   base-2 logarithm of the LZ77 sliding window size.  Using this
   parameter, a client tells the peer server that the client supports
   the server-to-client "c2s_max_window_bits" extension parameter.  If
   the parameter has a value, the parameter also tells the peer server a
   hint that even if the server sends the "c2s_max_window_bits"
   extension parameter with a bigger value or doesn't send it at all,
   the client is not going to use LZ77 sliding window size greater than
   the size specified by the value to compress messages.

   If a received offer has the "c2s_max_window_bits" extension
   parameter, the server MAY include the "c2s_max_window_bits" extension
   parameter in the response to the offer.  If the "c2s_max_window_bits"
   extension parameter in the received offer has a value, the server may
   either ignore this value or use this value to avoid allocating an
   unnecessarily big LZ77 sliding window by specifying
   "c2s_max_window_bits" extension parameter with a value equal to or
   smaller than the received value in the response.  This server-to-
   client parameter has a decimal integer value without leading zeroes
   between 8 to 15 inclusive indicating the base-2 logarithm of the LZ77
   sliding window size.

       c2s_max_window_bits = 1*DIGIT

   Using this server-to-client parameter, a server limits the LZ77
   sliding window size that the client uses to compress messages.  This
   reduces the amount of memory that the server has to reserve for the
   connection, in the same way the "s2c_max_window_bits" extension
   parameter does for the client.

   If a received offer doesn't have the "c2s_max_window_bits" extension
   parameter, the server MUST NOT include the "c2s_max_window_bits"
   extension parameter in the response to the offer.


We start by talking of "c2s_" then half way through the first paragraph we
start talking about "server-to-client" and even point out the "c2s_"
parameter as an example of the "server-to-client".

The spec mixes the use of "c2s" and "client-to-server" in various places,
in what we can only assume is sometimes it refers the parameter, sometimes
it refers to the direction of the conversation, sometimes it refers to the
extension negotiation step, sometimes it refers to the extension
negotiation phase.

Months have been spent trying to decipher this spec by multiple people with
years of experience on ietf specs, both as consumers and participants.  the
spec should be able to sit on its own, with as clear of definition as
possible at the time, reducing as much of the "interpretation" and question
asking that will arise from the spec.

The "2s" and "2c" portions are irrelevant, and actually cause confusion as
you use the same language elsewhere.

proposal:

"c2s_" used in extension-param tokens should be "client_" to refer to
"client produced compression"
"s2c_" used in extension-param tokens should be "server_" to refer to
"server produced compression"

"client-to-server", and "server-to-client" use within spec should be
clarified, and never be left without a clarification.
   when referring to the extension negotiation request phase.
      consider "extension negotiation request" or "extension negotiation
offer" for current "client-to-server" use
      consider "extension negotiation response" or "extension negotiation
accept" for current "server-to-client" use.
   when referring to the flow of frames on a connected websocket.
      this is where the existing "Client-to-Server" terminology is
consistent with RFC6455 (see Section
5.3<http://tools.ietf.org/html/rfc6455#section-5.3>
).
      so feel free to start using for "Server-to-Client" here as well, but
not in the above.

another choice is to never leave "Client-to-Server" alone with no
clarification, always follow it with consistent verbiage, like RFC6455 does.

Its never "Client-to-Server" just to refer to a directionality, its a
compound concept, such as "Client-to-Server Masking" or "Client-to-Server
message".

Suspicions/Theories:

The language choices of this spec probably come from the overall attempt at
being neutral to what side (client or server) the spec is documenting from.
If you look at the overall language of RFC6455, you see that it is
presented from the point of view of the Client, with the Server roles and
responsibilities being explained only when needed to.  Otherwise, both
sides are assumed to be the same in behavior.
If RFC6455 used the same techniques as the permessage-deflate spec, then
you'd have 2 sections: Client, fully documented with barely a mention of
server, then Server, fully documented we barely a mention of client.

Permessage-deflate could have been documented the same way as RFC6455, but
it isn't, so now you have extra work to be careful in your language
choices, eliminate ambiguity, make things more clear.


Our the final translation of the permessage-deflate extension spec, as
written:

Simplified Neutral Language:
Incoming frames/messages are compressed when RSV1 is set
Outgoing frames/messages can be compressed, but set RSV1 if you do.
Configuration of Incoming frames/messages compression is controlled by
Extension Parameters for the opposite side of yourself.
Configuration of Outgoing frames/messages compression is controlled by
Extension Parameters for your side.

Side Specific Language:
client_* Extension Parameters are for controlling frames/messages
compression produced by client
server_* Extension Parameters are for controlling frames/messages
compression produced by server

Here's the example of same Section 8.1.2.2 with the proposed change: (quick
edit)

8.1.2.2.  client_max_window_bits

   A client MAY include the "client_max_window_bits" extension parameter in
   an extension negotiation offer.  This parameter MAY have no value or a
decimal integer value
   without leading zeroes between 8 to 15 inclusive indicating the
   base-2 logarithm of the LZ77 sliding window size.  The use of this
   parameter in a extension negotiation offer informs the peer server that
   the client supports the "client_max_window_bits" extension parameter.
   If the parameter has a value, the parameter also tells the peer server a
   hint that even if the server sends the "client_max_window_bits"
   extension parameter on the extension negotiation response with a bigger
value,
   or doesn't send it at all, the client is not going to use LZ77 sliding
window
   size greater than the size specified by the value to compress messages.

   If a received extension negotiation offer has the
"client_max_window_bits" extension
   parameter, the server MAY include the "client_max_window_bits" extension
   parameter in the extension negotiation response.  If the
"client_max_window_bits"
   extension parameter in the received extension negotiation offer has a
value, the server may
   either ignore this value or use this value to avoid allocating an
   unnecessarily big LZ77 sliding window by specifying
   "client_max_window_bits" extension parameter with a value equal to or
   smaller than the received value in the response.
   The extension negotiation accept parameter value MUST have a decimal
   integer value without leading zeroes between 8 to 15 inclusive
   indicating the base-2 logarithm of the LZ77 sliding window size.

       client_max_window_bits = 1*DIGIT

   The use of the extension negotiation response parameter allows a server
to limit the LZ77
   sliding window size that the client uses to compress messages.  This
   reduces the amount of memory that the server has to reserve for the
   connection, in the same way the "server_max_window_bits" extension
   parameter does for the client.

   If a received extension negotiation offer doesn't have the
"client_max_window_bits" extension
   parameter, the server MUST NOT include the "client_max_window_bits"
   extension parameter in the extension negotiation response to the offer.

Hope this helps explain where we are coming from.


--
Joakim Erdfelt <joakim@intalio.com>
webtide.com <http://www.webtide.com/> - intalio.com/jetty
Expert advice, services and support from from the Jetty & CometD experts
eclipse.org/jetty - cometd.org


On Tue, Oct 15, 2013 at 7:08 AM, Takeshi Yoshino <tyoshino@google.com>wrote:

> Thanks, all.
>
> Joakim, please show Jetty's opinion again. Then, I'll make decision to
> move forward.
>
> Tobias: neutral
> Peter: neutral slight preference for s2c_
> Takeshi: neutral slight preference for s2c_
> Joakim: preference for server_
>
>

--047d7b3440f4a6b5ef04e8c906b6
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>The problem is the language choices in the spec alrea=
dy.<br></div><div><br></div><div>Take this for example: (from <a href=3D"ht=
tp://tools.ietf.org/html/draft-ietf-hybi-permessage-compression-13#section-=
8.1.2.2">Section 8.1.2.2</a> of draft-ietf-hybi-permessage-compression-13)<=
/div>
<div><br></div><div><div><font face=3D"courier new, monospace">8.1.2.2. =A0=
c2s_max_window_bits</font></div><div><font face=3D"courier new, monospace">=
<br></font></div><div><font face=3D"courier new, monospace">=A0 =A0A client=
 MAY include the &quot;c2s_max_window_bits&quot; extension parameter in</fo=
nt></div>
<div><font face=3D"courier new, monospace">=A0 =A0an offer. =A0This paramet=
er has no value or a decimal integer value</font></div><div><font face=3D"c=
ourier new, monospace">=A0 =A0without leading zeroes between 8 to 15 inclus=
ive indicating the</font></div>
<div><font face=3D"courier new, monospace">=A0 =A0base-2 logarithm of the L=
Z77 sliding window size. =A0Using this</font></div><div><font face=3D"couri=
er new, monospace">=A0 =A0parameter, a client tells the peer server that th=
e client supports</font></div>
<div><font face=3D"courier new, monospace">=A0 =A0the server-to-client &quo=
t;c2s_max_window_bits&quot; extension parameter. =A0If</font></div><div><fo=
nt face=3D"courier new, monospace">=A0 =A0the parameter has a value, the pa=
rameter also tells the peer server a</font></div>
<div><font face=3D"courier new, monospace">=A0 =A0hint that even if the ser=
ver sends the &quot;c2s_max_window_bits&quot;</font></div><div><font face=
=3D"courier new, monospace">=A0 =A0extension parameter with a bigger value =
or doesn&#39;t send it at all,</font></div>
<div><font face=3D"courier new, monospace">=A0 =A0the client is not going t=
o use LZ77 sliding window size greater than</font></div><div><font face=3D"=
courier new, monospace">=A0 =A0the size specified by the value to compress =
messages.</font></div>
<div><font face=3D"courier new, monospace"><br></font></div><div><font face=
=3D"courier new, monospace">=A0 =A0If a received offer has the &quot;c2s_ma=
x_window_bits&quot; extension</font></div><div><font face=3D"courier new, m=
onospace">=A0 =A0parameter, the server MAY include the &quot;c2s_max_window=
_bits&quot; extension</font></div>
<div><font face=3D"courier new, monospace">=A0 =A0parameter in the response=
 to the offer. =A0If the &quot;c2s_max_window_bits&quot;</font></div><div><=
font face=3D"courier new, monospace">=A0 =A0extension parameter in the rece=
ived offer has a value, the server may</font></div>
<div><font face=3D"courier new, monospace">=A0 =A0either ignore this value =
or use this value to avoid allocating an</font></div><div><font face=3D"cou=
rier new, monospace">=A0 =A0unnecessarily big LZ77 sliding window by specif=
ying</font></div>
<div><font face=3D"courier new, monospace">=A0 =A0&quot;c2s_max_window_bits=
&quot; extension parameter with a value equal to or</font></div><div><font =
face=3D"courier new, monospace">=A0 =A0smaller than the received value in t=
he response. =A0This server-to-</font></div>
<div><font face=3D"courier new, monospace">=A0 =A0client parameter has a de=
cimal integer value without leading zeroes</font></div><div><font face=3D"c=
ourier new, monospace">=A0 =A0between 8 to 15 inclusive indicating the base=
-2 logarithm of the LZ77</font></div>
<div><font face=3D"courier new, monospace">=A0 =A0sliding window size.</fon=
t></div><div><font face=3D"courier new, monospace"><br></font></div><div><f=
ont face=3D"courier new, monospace">=A0 =A0 =A0 =A0c2s_max_window_bits =3D =
1*DIGIT</font></div>
<div><font face=3D"courier new, monospace"><br></font></div><div><font face=
=3D"courier new, monospace">=A0 =A0Using this server-to-client parameter, a=
 server limits the LZ77</font></div><div><font face=3D"courier new, monospa=
ce">=A0 =A0sliding window size that the client uses to compress messages. =
=A0This</font></div>
<div><font face=3D"courier new, monospace">=A0 =A0reduces the amount of mem=
ory that the server has to reserve for the</font></div><div><font face=3D"c=
ourier new, monospace">=A0 =A0connection, in the same way the &quot;s2c_max=
_window_bits&quot; extension</font></div>
<div><font face=3D"courier new, monospace">=A0 =A0parameter does for the cl=
ient.</font></div><div><font face=3D"courier new, monospace"><br></font></d=
iv><div><font face=3D"courier new, monospace">=A0 =A0If a received offer do=
esn&#39;t have the &quot;c2s_max_window_bits&quot; extension</font></div>
<div><font face=3D"courier new, monospace">=A0 =A0parameter, the server MUS=
T NOT include the &quot;c2s_max_window_bits&quot;</font></div><div><font fa=
ce=3D"courier new, monospace">=A0 =A0extension parameter in the response to=
 the offer.</font></div>
</div><div><br></div><div><br></div><div>We start by talking of &quot;c2s_&=
quot; then half way through the first paragraph we start talking about &quo=
t;server-to-client&quot; and even point out the &quot;c2s_&quot; parameter =
as an example of the &quot;server-to-client&quot;.</div>
<div><br></div><div>The spec mixes the use of &quot;c2s&quot; and &quot;cli=
ent-to-server&quot; in various places, in what we can only assume is someti=
mes it refers the parameter, sometimes it refers to the direction of the co=
nversation, sometimes it refers to the extension negotiation step, sometime=
s it refers to the extension negotiation phase.</div>
<div><br></div><div>Months have been spent trying to decipher this spec by =
multiple people with years of experience on ietf specs, both as consumers a=
nd participants. =A0the spec should be able to sit on its own, with as clea=
r of definition as possible at the time, reducing as much of the &quot;inte=
rpretation&quot; and question asking that will arise from the spec.<br>
</div><div><br></div><div>The &quot;2s&quot; and &quot;2c&quot; portions ar=
e irrelevant, and actually cause confusion as you use the same language els=
ewhere.</div><div><br></div><div>proposal:</div><div><br></div><div>&quot;c=
2s_&quot; used in extension-param tokens should be &quot;client_&quot; to r=
efer to &quot;client produced compression&quot;</div>
<div>&quot;s2c_&quot; used in extension-param tokens should be &quot;server=
_&quot; to refer to &quot;server produced compression&quot;</div><div><br><=
/div><div>&quot;client-to-server&quot;, and &quot;server-to-client&quot; us=
e within spec should be clarified, and never be left without a clarificatio=
n.</div>
<div>=A0 =A0when referring to the extension negotiation request phase.</div=
><div>=A0 =A0 =A0 consider &quot;extension negotiation request&quot; or &qu=
ot;extension negotiation offer&quot; for current &quot;client-to-server&quo=
t; use</div>
<div>=A0 =A0 =A0 consider &quot;extension negotiation response&quot; or &qu=
ot;extension negotiation accept&quot; for current &quot;server-to-client&qu=
ot; use.</div><div>=A0 =A0when referring to the flow of frames on a connect=
ed websocket.</div>
<div>=A0 =A0 =A0 this is where the existing &quot;Client-to-Server&quot; te=
rminology is consistent with RFC6455 (see <a href=3D"http://tools.ietf.org/=
html/rfc6455#section-5.3">Section 5.3</a>).</div><div>=A0 =A0 =A0 so feel f=
ree to start using for &quot;Server-to-Client&quot; here as well, but not i=
n the above.</div>
<div><br></div><div>another choice is to never leave &quot;Client-to-Server=
&quot; alone with no clarification, always follow it with consistent verbia=
ge, like RFC6455 does.</div><div><br></div><div>Its never &quot;Client-to-S=
erver&quot; just to refer to a directionality, its a compound concept, such=
 as &quot;Client-to-Server Masking&quot; or &quot;Client-to-Server message&=
quot;.</div>
<div><br></div><div>Suspicions/Theories:</div><blockquote style=3D"margin:0=
 0 0 40px;border:none;padding:0px"><div>The language choices of this spec p=
robably come from the overall attempt at being neutral to what side (client=
 or server) the spec is documenting from.</div>
<div>If you look at the overall language of RFC6455, you see that it is pre=
sented from the point of view of the Client, with the Server roles and resp=
onsibilities being explained only when needed to. =A0Otherwise, both sides =
are assumed to be the same in behavior.=A0</div>
<div>If RFC6455 used the same techniques as the permessage-deflate spec, th=
en you&#39;d have 2 sections: Client, fully documented with barely a mentio=
n of server, then Server, fully documented we barely a mention of client.</=
div>
<div><br></div><div>Permessage-deflate could have been documented the same =
way as RFC6455, but it isn&#39;t, so now you have extra work to be careful =
in your language choices, eliminate ambiguity, make things more clear.</div=
>
</blockquote><div><br></div><div>Our the final translation of the permessag=
e-deflate extension spec, as written:</div><div><br></div><div>Simplified N=
eutral Language:</div><div>Incoming=A0frames/messages=A0are compressed when=
 RSV1 is set</div>
<div>Outgoing=A0frames/messages=A0can be compressed, but set RSV1 if you do=
.</div><div>Configuration of Incoming=A0frames/messages=A0compression is co=
ntrolled by Extension Parameters for the opposite side of yourself.</div><d=
iv>Configuration of Outgoing=A0frames/messages=A0compression is controlled =
by Extension Parameters for your side.</div>
<div><br></div><div>Side Specific Language:</div><div>client_* Extension Pa=
rameters are for controlling frames/messages compression produced by client=
</div><div>server_* Extension Parameters are for controlling frames/message=
s compression produced by server</div>
<div><br></div><div>Here&#39;s the example of same Section 8.1.2.2 with the=
 proposed change: (quick edit)</div><div><br></div><div><div><font face=3D"=
courier new, monospace">8.1.2.2. =A0client_max_window_bits</font></div><div=
>
<font face=3D"courier new, monospace"><br></font></div><div><font face=3D"c=
ourier new, monospace">=A0 =A0A client MAY include the &quot;client_max_win=
dow_bits&quot; extension parameter in</font></div><div><font face=3D"courie=
r new, monospace">=A0 =A0an extension negotiation offer. =A0This parameter =
MAY have no value or a decimal integer value</font></div>
<div><font face=3D"courier new, monospace">=A0 =A0without leading zeroes be=
tween 8 to 15 inclusive indicating the</font></div><div><font face=3D"couri=
er new, monospace">=A0 =A0base-2 logarithm of the LZ77 sliding window size.=
 =A0The use of this</font></div>
<div><font face=3D"courier new, monospace">=A0 =A0parameter in a extension =
negotiation offer informs the peer server that</font></div><div><font face=
=3D"courier new, monospace">=A0 =A0the client supports the=A0</font><span s=
tyle=3D"font-family:&#39;courier new&#39;,monospace">&quot;client_max_windo=
w_bits&quot; extension parameter. =A0</span></div>
<div><span style=3D"font-family:&#39;courier new&#39;,monospace">=A0 =A0If=
=A0</span><span style=3D"font-family:&#39;courier new&#39;,monospace">the p=
arameter has a value, the parameter also tells the peer server a</span></di=
v><div>
<font face=3D"courier new, monospace">=A0 =A0hint that even if the server s=
ends the &quot;client_max_window_bits&quot;</font></div><div><font face=3D"=
courier new, monospace">=A0 =A0extension parameter on the extension negotia=
tion response with a bigger value,=A0</font></div>
<div><font face=3D"courier new, monospace">=A0 =A0or doesn&#39;t send it at=
 all,=A0</font><span style=3D"font-family:&#39;courier new&#39;,monospace">=
the client is not going to use LZ77 sliding window</span></div><div><span s=
tyle=3D"font-family:&#39;courier new&#39;,monospace">=A0 =A0size greater th=
an</span><span style=3D"font-family:&#39;courier new&#39;,monospace">=A0the=
 size specified by the value to compress messages.</span></div>
<div><font face=3D"courier new, monospace"><br></font></div><div><font face=
=3D"courier new, monospace">=A0 =A0If a received extension negotiation offe=
r has the &quot;client_max_window_bits&quot; extension</font></div><div><fo=
nt face=3D"courier new, monospace">=A0 =A0parameter, the server MAY include=
 the &quot;client_max_window_bits&quot; extension</font></div>
<div><font face=3D"courier new, monospace">=A0 =A0parameter in the extensio=
n negotiation response. =A0If the &quot;client_max_window_bits&quot;</font>=
</div><div><font face=3D"courier new, monospace">=A0 =A0extension parameter=
 in the received extension negotiation offer has a value, the server may</f=
ont></div>
<div><font face=3D"courier new, monospace">=A0 =A0either ignore this value =
or use this value to avoid allocating an</font></div><div><font face=3D"cou=
rier new, monospace">=A0 =A0unnecessarily big LZ77 sliding window by specif=
ying</font></div>
<div><font face=3D"courier new, monospace">=A0 =A0&quot;client_max_window_b=
its&quot; extension parameter with a value equal to or</font></div></div><d=
iv><div><font face=3D"courier new, monospace">=A0 =A0smaller than the recei=
ved value in the response. =A0</font></div>
<div><font face=3D"courier new, monospace">=A0 =A0The extension negotiation=
 accept </font><span style=3D"font-family:&#39;courier new&#39;,monospace">=
parameter value MUST have a decimal=A0</span></div><div><span style=3D"font=
-family:&#39;courier new&#39;,monospace">=A0 =A0integer value without leadi=
ng zeroes=A0</span><span style=3D"font-family:&#39;courier new&#39;,monospa=
ce">between 8 to 15 inclusive=A0</span></div>
<div><span style=3D"font-family:&#39;courier new&#39;,monospace">=A0 =A0ind=
icating the base-2 logarithm of the LZ77=A0</span><span style=3D"font-famil=
y:&#39;courier new&#39;,monospace">sliding window size.</span></div><div><f=
ont face=3D"courier new, monospace"><br>
</font></div><div><font face=3D"courier new, monospace">=A0 =A0 =A0 =A0clie=
nt_max_window_bits =3D 1*DIGIT</font></div><div><font face=3D"courier new, =
monospace"><br></font></div><div><font face=3D"courier new, monospace">=A0 =
=A0The use of the extension negotiation response parameter allows a server =
to limit the LZ77</font></div>
<div><font face=3D"courier new, monospace">=A0 =A0sliding window size that =
the client uses to compress messages. =A0This</font></div><div><font face=
=3D"courier new, monospace">=A0 =A0reduces the amount of memory that the se=
rver has to reserve for the</font></div>
<div><font face=3D"courier new, monospace">=A0 =A0connection, in the same w=
ay the &quot;server_max_window_bits&quot; extension</font></div><div><font =
face=3D"courier new, monospace">=A0 =A0parameter does for the client.</font=
></div><div>
<font face=3D"courier new, monospace"><br></font></div><div><font face=3D"c=
ourier new, monospace">=A0 =A0If a received extension negotiation offer doe=
sn&#39;t have the &quot;client_max_window_bits&quot; extension</font></div>=
<div>
<font face=3D"courier new, monospace">=A0 =A0parameter, the server MUST NOT=
 include the &quot;client_max_window_bits&quot;</font></div><div><font face=
=3D"courier new, monospace">=A0 =A0extension parameter in the extension neg=
otiation response to the offer</font>.</div>
</div><div><div><br class=3D"">Hope this helps explain where we are coming =
from.</div></div><div><br></div></div><div class=3D"gmail_extra"><br clear=
=3D"all"><div><div dir=3D"ltr"><div>--</div><div>Joakim Erdfelt &lt;<a href=
=3D"mailto:joakim@intalio.com" target=3D"_blank">joakim@intalio.com</a>&gt;=
</div>
<div><a href=3D"http://www.webtide.com/" target=3D"_blank">webtide.com</a>=
=A0- <a href=3D"http://intalio.com/jetty" target=3D"_blank">intalio.com/jet=
ty</a></div><div><span>Expert advice, services and support from=A0</span><s=
pan>from the Jetty &amp; CometD experts</span></div>
<div><a href=3D"http://eclipse.org/jetty/" target=3D"_blank">eclipse.org/je=
tty</a>=A0-=A0<a href=3D"http://cometd.org/" target=3D"_blank">cometd.org</=
a></div></div></div>
<br><br><div class=3D"gmail_quote">On Tue, Oct 15, 2013 at 7:08 AM, Takeshi=
 Yoshino <span dir=3D"ltr">&lt;<a href=3D"mailto:tyoshino@google.com" targe=
t=3D"_blank">tyoshino@google.com</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">
<div dir=3D"ltr">Thanks, all.<div><br></div><div>Joakim, please show Jetty&=
#39;s opinion again. Then, I&#39;ll make decision to move forward.</div><di=
v><br></div><div>Tobias: neutral</div><div>Peter: neutral slight preference=
 for s2c_</div>



<div>Takeshi: neutral slight preference for s2c_</div><div>Joakim: preferen=
ce for server_</div><div>=A0</div></div>
</blockquote></div><br></div>

--047d7b3440f4a6b5ef04e8c906b6--

From webmaster@zaphoyd.com  Tue Oct 15 11:34:38 2013
Return-Path: <webmaster@zaphoyd.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB3A611E8153 for <hybi@ietfa.amsl.com>; Tue, 15 Oct 2013 11:34:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.001,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z9xTtB2URKDW for <hybi@ietfa.amsl.com>; Tue, 15 Oct 2013 11:34:32 -0700 (PDT)
Received: from sh78.surpasshosting.com (sh78.surpasshosting.com [72.29.64.142]) by ietfa.amsl.com (Postfix) with ESMTP id 8362111E8166 for <hybi@ietf.org>; Tue, 15 Oct 2013 11:34:25 -0700 (PDT)
Received: from ranna.uchicago.edu ([128.135.45.206]:60780) by sh78.surpasshosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80.1) (envelope-from <webmaster@zaphoyd.com>) id 1VW9Rf-0004U5-Ki for hybi@ietf.org; Tue, 15 Oct 2013 14:34:16 -0400
From: Peter Thorson <webmaster@zaphoyd.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <FD138330-7D7E-4450-B4F5-64551F92F26D@zaphoyd.com>
Date: Tue, 15 Oct 2013 13:34:13 -0500
To: "hybi@ietf.org" <hybi@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
X-Mailer: Apple Mail (2.1510)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - sh78.surpasshosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - zaphoyd.com
X-Get-Message-Sender-Via: sh78.surpasshosting.com: authenticated_id: webmaster@zaphoyd.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Subject: [hybi] permessage-deflate performance tuning statistics
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 15 Oct 2013 18:34:38 -0000

Hi all,

I've been doing a bit of research and testing on the compression =
performance and memory usage of permessage-deflate on WebSocket like =
workloads. I plan to write about this with more final numbers once the =
spec is official, but some of the intermediate results and tools may be =
of interest to this group during the standardization process so I'm =
sharing some of those notes here.

Some highlights:
- Permessage-deflate offers significant bandwidth savings.
- How the extension performs depends greatly on the type of data that is =
being compressed and the compression settings given to deflate.
- Settings that work well for HTTP and the zlib/permessage-deflate =
defaults are inefficient for some common WebSocket workflows.
- The two parameters presently in the draft specification both provide =
significant and meaningful options for tuning compression performance =
for those workflows. Implementations (especially browsers) are greatly =
encouraged to support all options.

Details & Methods:

My goal is to explore a number of the settings offered by deflate and =
determine what effect they have on compression performance, as well as =
CPU/memory usage. To this end I have written a tool =
(https://github.com/zaphoyd/ws-pmce-stats) that will produce a report of =
compression related statistics when fed a transcript of messages.

The first workflow I have explored in detail is a WebSocket service that =
uses a JSON based protocol to deliver short streaming updates. My some =
of my sample data is present in the datasets folder of the above git =
repository. Some examples include a mock chat service with data seeded =
from publicly logged mediawiki IRC channel and a mock stock ticker =
service with data seeded with historical stock quote data.

I explored the effects of the context takeover and window bits settings =
from the permessage-deflate draft spec as well as a few zlib settings =
that can be unilaterally specified without any extension negotiation. =
Some, but not all of these, are presently exposed in higher level =
languages that use zlib as their underlying compression library. I =
looked at two of these settings in particular, the "Compression Level" =
and the "Memory Level". The former affects speed vs compression ratio, =
the latter memory usage vs compression ratio.

Preliminary results for the JSON short message service workflow:

Context Takeover
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Allowing context takeover drastically improves compression ratios. With =
other stats at defaults, no_context_takeover achieves a compression =
ratio of 0.84, with takeover 0.30. This is a significant gain. Note: =
this gain comes at a fairly high cost. Enabling context takeover =
requires a separate context to be maintained for every connection, =
rather than fixed number for all connections.

Window Bits
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Window bits has a sizable but well distributed effect on ratios. It has =
a significant effect on memory usage though. With all other stats at =
defaults:
window bits =3D compression ratio / buffer size per connection
08 =3D 0.510 / 1+128=3D129KiB
09 =3D 0.510 / 2+128=3D130KiB
10 =3D 0.435 / 4+128=3D132KiB
11 =3D 0.384 / 8+128=3D136KiB
12 =3D 0.353 / 16+128=3D144KiB
13 =3D 0.330 / 32+128=3D160KiB
14 =3D 0.315 / 64+128=3D192KiB
15 =3D 0.304 / 128+128=3D256KiB
Reducing window bits from the default (15) to 11 provides an 8% =
reduction in compression but nearly a 50% savings in per connection =
memory usage. Reduced window bits to very small values (8-9) also =
increases compression runtime by 40-50%. 10 Is less slow, 11+ appear to =
all be about the same speed.

Compression Level
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Compression level does not have a material impact on performance or =
ratios for this workflow.

Memory Level
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Memory level does not have a significant impact on compression ratios. A =
value of 9 produces the ratio 0.304 and a value of 1 produces the ratio =
0.307. It does affect memory usage and compression speed however:
mem_level value =3D runtime / memory usage
1 =3D 13.05ms / 128+1=3D129KiB
2 =3D 10.41ms / 128+2=3D130KiB
3 =3D 10.15ms / 128+4=3D132KiB
4 =3D 8.18ms / 128+8=3D136KiB
5 =3D 7.63ms / 128+16=3D144KiB
6 =3D 7.69ms / 128+32=3D160KiB
7 =3D 7.92ms / 128+64=3D192KiB
8 =3D 7.69ms / 128+128=3D256KiB
9 =3D 7.84ms / 128+256=3D386KiB

All of the stats above show the effects of changing one parameter in =
isolation. Additional gains, especially with respect to memory usage per =
connection can be had by combinations of parameters. Many of the speed, =
compression, and memory effects of parameters are dependent on each =
other. Two nice balances of all factors for the JSON short message =
service data set (vs defaults) are something like..

context-takeover=3Don
window bits=3D11
memory level=3D4
This provides memory usage of 16KiB/connection vs 256KiB, has no runtime =
speed penalty, and achieves a 0.384 vs 0.304 compression ratio.

context-takeover=3Don
window bits=3D11
memory level=3D1
This provides memory usage of 5KiB/connection vs 256KiB, runs ~15% =
slower, and achieves a similar 0.385 vs 0.304 compression ratio.

The ws-pmce-stats tool can help you plug in values and get a sense for =
which combinations of settings are optimal for your traffic mix. In =
general I have found that the shorter your messages, the less you =
benefit from high window bit and memory level values. If you routinely =
send WebSocket messages with payloads in the high hundreds of KB or MBs =
you will benefit from higher values for memory level and window bits. If =
you have extremely limited memory, no context takeover will allow fixed =
memory usage for all connections. Its price is heavy for small messages =
& JSON protocols, but less problematic for large ones. I've found that =
11 window bits and compression memory level 4 is still quite effective =
even up to message payloads of ~200KB.

I'd love to hear any feedback anyone has about the methods or results. I =
am particularly interested in collecting more sample WebSocket =
workflows. I haven't run any numbers for binary connections yet. I'd =
love to hear details about other workflows that might have different =
properties than the ones studied here so far, especially if you have =
sample transcripts.

I'd also be interested in any feedback on the ws-pmce-stats program. Is =
something like this useful to anyone else? It meets my needs right now, =
but I have a few ideas of how to expand it (binary message support, =
other compression algorithms, machine readable output) if it sounds =
useful to others.=

From joakim@intalio.com  Tue Oct 15 11:49:08 2013
Return-Path: <joakim@intalio.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1814311E81F7 for <hybi@ietfa.amsl.com>; Tue, 15 Oct 2013 11:49:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ohGofEKjVU4F for <hybi@ietfa.amsl.com>; Tue, 15 Oct 2013 11:49:04 -0700 (PDT)
Received: from mail-ea0-f170.google.com (mail-ea0-f170.google.com [209.85.215.170]) by ietfa.amsl.com (Postfix) with ESMTP id 3666011E81A4 for <hybi@ietf.org>; Tue, 15 Oct 2013 11:48:53 -0700 (PDT)
Received: by mail-ea0-f170.google.com with SMTP id h14so4204932eak.29 for <hybi@ietf.org>; Tue, 15 Oct 2013 11:48:52 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=uoQz7fxRrtI81bFJA2BNrNnT8aXf1KtZ3G2pxwhgZXE=; b=aRbmW66THiRisMCbmLkjmCGCocsgPhweSuDipOMvrVP1W7i+QFzfNZoLZ4RVS3pTdn LvVQbebLXHfapaPnOh1UAZdkQcUJe1LkDm1LnrCm5KQ0W7mKdQ9PLi0Lh44cr8Nyrux+ i1WUxpCR0znyaRtwVztTOoNnIuX9pau6YpIn1Cw3YETTaAG8PbEe48jSkkBbMmbsx8Ug 9T/5wRwwyXlyLYSPKlM9+UUwnhxEtcq3shpse4UnIB6nq6mH9XdwhJ/BgQmyXdsa18G/ bTrbMzDGBggOZexVUDgCnSYeHEMVhlfebzkVyqQjkhlsMSXhE/NXumUZTx0/lIeYNbRF 7YbA==
X-Gm-Message-State: ALoCoQlYNEQMafPQtpK/EMKzJLxy44vqvajeH6zg/8dUB2ql5kaL5UdCsjTw1QCWaoqr5mPINPoK
MIME-Version: 1.0
X-Received: by 10.14.109.66 with SMTP id r42mr2782860eeg.43.1381862932261; Tue, 15 Oct 2013 11:48:52 -0700 (PDT)
Received: by 10.14.133.74 with HTTP; Tue, 15 Oct 2013 11:48:52 -0700 (PDT)
In-Reply-To: <FD138330-7D7E-4450-B4F5-64551F92F26D@zaphoyd.com>
References: <FD138330-7D7E-4450-B4F5-64551F92F26D@zaphoyd.com>
Date: Tue, 15 Oct 2013 11:48:52 -0700
Message-ID: <CAG4zZZBFVoYt7RLir_EZ+brW_heThO7D-CdQxWc4gicZBG2fCA@mail.gmail.com>
From: Joakim Erdfelt <joakim@intalio.com>
To: Peter Thorson <webmaster@zaphoyd.com>
Content-Type: multipart/alternative; boundary=001a11c1ac1234bd6104e8cc09f6
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] permessage-deflate performance tuning statistics
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 15 Oct 2013 18:49:08 -0000

--001a11c1ac1234bd6104e8cc09f6
Content-Type: text/plain; charset=ISO-8859-1

Nice.  Was meaning to do this myself, but just haven't had the free time to
devote to it.
I imagine that the results of this will serve the community well.

Is your experimental data testing if fragmentation has any impact? (lots of
smaller fragments for a larger message, commonly seen in streaming
behaviors)

Are you testing just a single type of data on the connection?
Are you testing multiple types of data during the same connection, such as
a theoretical protocol that has markup + metadata + and pre compressed
media?



--
Joakim Erdfelt <joakim@intalio.com>
webtide.com <http://www.webtide.com/> - intalio.com/jetty
Expert advice, services and support from from the Jetty & CometD experts
eclipse.org/jetty - cometd.org


On Tue, Oct 15, 2013 at 11:34 AM, Peter Thorson <webmaster@zaphoyd.com>wrote:

> Hi all,
>
> I've been doing a bit of research and testing on the compression
> performance and memory usage of permessage-deflate on WebSocket like
> workloads. I plan to write about this with more final numbers once the spec
> is official, but some of the intermediate results and tools may be of
> interest to this group during the standardization process so I'm sharing
> some of those notes here.
>
> Some highlights:
> - Permessage-deflate offers significant bandwidth savings.
> - How the extension performs depends greatly on the type of data that is
> being compressed and the compression settings given to deflate.
> - Settings that work well for HTTP and the zlib/permessage-deflate
> defaults are inefficient for some common WebSocket workflows.
> - The two parameters presently in the draft specification both provide
> significant and meaningful options for tuning compression performance for
> those workflows. Implementations (especially browsers) are greatly
> encouraged to support all options.
>
> Details & Methods:
>
> My goal is to explore a number of the settings offered by deflate and
> determine what effect they have on compression performance, as well as
> CPU/memory usage. To this end I have written a tool (
> https://github.com/zaphoyd/ws-pmce-stats) that will produce a report of
> compression related statistics when fed a transcript of messages.
>
> The first workflow I have explored in detail is a WebSocket service that
> uses a JSON based protocol to deliver short streaming updates. My some of
> my sample data is present in the datasets folder of the above git
> repository. Some examples include a mock chat service with data seeded from
> publicly logged mediawiki IRC channel and a mock stock ticker service with
> data seeded with historical stock quote data.
>
> I explored the effects of the context takeover and window bits settings
> from the permessage-deflate draft spec as well as a few zlib settings that
> can be unilaterally specified without any extension negotiation. Some, but
> not all of these, are presently exposed in higher level languages that use
> zlib as their underlying compression library. I looked at two of these
> settings in particular, the "Compression Level" and the "Memory Level". The
> former affects speed vs compression ratio, the latter memory usage vs
> compression ratio.
>
> Preliminary results for the JSON short message service workflow:
>
> Context Takeover
> ================
> Allowing context takeover drastically improves compression ratios. With
> other stats at defaults, no_context_takeover achieves a compression ratio
> of 0.84, with takeover 0.30. This is a significant gain. Note: this gain
> comes at a fairly high cost. Enabling context takeover requires a separate
> context to be maintained for every connection, rather than fixed number for
> all connections.
>
> Window Bits
> ===========
> Window bits has a sizable but well distributed effect on ratios. It has a
> significant effect on memory usage though. With all other stats at defaults:
> window bits = compression ratio / buffer size per connection
> 08 = 0.510 / 1+128=129KiB
> 09 = 0.510 / 2+128=130KiB
> 10 = 0.435 / 4+128=132KiB
> 11 = 0.384 / 8+128=136KiB
> 12 = 0.353 / 16+128=144KiB
> 13 = 0.330 / 32+128=160KiB
> 14 = 0.315 / 64+128=192KiB
> 15 = 0.304 / 128+128=256KiB
> Reducing window bits from the default (15) to 11 provides an 8% reduction
> in compression but nearly a 50% savings in per connection memory usage.
> Reduced window bits to very small values (8-9) also increases compression
> runtime by 40-50%. 10 Is less slow, 11+ appear to all be about the same
> speed.
>
> Compression Level
> =================
> Compression level does not have a material impact on performance or ratios
> for this workflow.
>
> Memory Level
> ============
> Memory level does not have a significant impact on compression ratios. A
> value of 9 produces the ratio 0.304 and a value of 1 produces the ratio
> 0.307. It does affect memory usage and compression speed however:
> mem_level value = runtime / memory usage
> 1 = 13.05ms / 128+1=129KiB
> 2 = 10.41ms / 128+2=130KiB
> 3 = 10.15ms / 128+4=132KiB
> 4 = 8.18ms / 128+8=136KiB
> 5 = 7.63ms / 128+16=144KiB
> 6 = 7.69ms / 128+32=160KiB
> 7 = 7.92ms / 128+64=192KiB
> 8 = 7.69ms / 128+128=256KiB
> 9 = 7.84ms / 128+256=386KiB
>
> All of the stats above show the effects of changing one parameter in
> isolation. Additional gains, especially with respect to memory usage per
> connection can be had by combinations of parameters. Many of the speed,
> compression, and memory effects of parameters are dependent on each other.
> Two nice balances of all factors for the JSON short message service data
> set (vs defaults) are something like..
>
> context-takeover=on
> window bits=11
> memory level=4
> This provides memory usage of 16KiB/connection vs 256KiB, has no runtime
> speed penalty, and achieves a 0.384 vs 0.304 compression ratio.
>
> context-takeover=on
> window bits=11
> memory level=1
> This provides memory usage of 5KiB/connection vs 256KiB, runs ~15% slower,
> and achieves a similar 0.385 vs 0.304 compression ratio.
>
> The ws-pmce-stats tool can help you plug in values and get a sense for
> which combinations of settings are optimal for your traffic mix. In general
> I have found that the shorter your messages, the less you benefit from high
> window bit and memory level values. If you routinely send WebSocket
> messages with payloads in the high hundreds of KB or MBs you will benefit
> from higher values for memory level and window bits. If you have extremely
> limited memory, no context takeover will allow fixed memory usage for all
> connections. Its price is heavy for small messages & JSON protocols, but
> less problematic for large ones. I've found that 11 window bits and
> compression memory level 4 is still quite effective even up to message
> payloads of ~200KB.
>
> I'd love to hear any feedback anyone has about the methods or results. I
> am particularly interested in collecting more sample WebSocket workflows. I
> haven't run any numbers for binary connections yet. I'd love to hear
> details about other workflows that might have different properties than the
> ones studied here so far, especially if you have sample transcripts.
>
> I'd also be interested in any feedback on the ws-pmce-stats program. Is
> something like this useful to anyone else? It meets my needs right now, but
> I have a few ideas of how to expand it (binary message support, other
> compression algorithms, machine readable output) if it sounds useful to
> others.
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi
>

--001a11c1ac1234bd6104e8cc09f6
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Nice. =A0Was meaning to do this myself, but just haven&#39=
;t had the free time to devote to it.<div>I imagine that the results of thi=
s will serve the community well.<br><div><br></div><div>Is your experimenta=
l data testing if fragmentation has any impact? (lots of smaller fragments =
for a larger message, commonly seen in streaming behaviors)</div>
<div><br></div><div>Are you testing just a single type of data on the conne=
ction?</div><div>Are you testing multiple types of data during the same con=
nection, such as a theoretical protocol that has markup + metadata + and pr=
e compressed media?</div>
<div><br></div></div><div><br></div></div><div class=3D"gmail_extra"><br cl=
ear=3D"all"><div><div dir=3D"ltr"><div>--</div><div>Joakim Erdfelt &lt;<a h=
ref=3D"mailto:joakim@intalio.com" target=3D"_blank">joakim@intalio.com</a>&=
gt;</div>
<div><a href=3D"http://www.webtide.com/" target=3D"_blank">webtide.com</a>=
=A0- <a href=3D"http://intalio.com/jetty" target=3D"_blank">intalio.com/jet=
ty</a></div><div><span>Expert advice, services and support from=A0</span><s=
pan>from the Jetty &amp; CometD experts</span></div>
<div><a href=3D"http://eclipse.org/jetty/" target=3D"_blank">eclipse.org/je=
tty</a>=A0-=A0<a href=3D"http://cometd.org/" target=3D"_blank">cometd.org</=
a></div></div></div>
<br><br><div class=3D"gmail_quote">On Tue, Oct 15, 2013 at 11:34 AM, Peter =
Thorson <span dir=3D"ltr">&lt;<a href=3D"mailto:webmaster@zaphoyd.com" targ=
et=3D"_blank">webmaster@zaphoyd.com</a>&gt;</span> wrote:<br><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex">
Hi all,<br>
<br>
I&#39;ve been doing a bit of research and testing on the compression perfor=
mance and memory usage of permessage-deflate on WebSocket like workloads. I=
 plan to write about this with more final numbers once the spec is official=
, but some of the intermediate results and tools may be of interest to this=
 group during the standardization process so I&#39;m sharing some of those =
notes here.<br>

<br>
Some highlights:<br>
- Permessage-deflate offers significant bandwidth savings.<br>
- How the extension performs depends greatly on the type of data that is be=
ing compressed and the compression settings given to deflate.<br>
- Settings that work well for HTTP and the zlib/permessage-deflate defaults=
 are inefficient for some common WebSocket workflows.<br>
- The two parameters presently in the draft specification both provide sign=
ificant and meaningful options for tuning compression performance for those=
 workflows. Implementations (especially browsers) are greatly encouraged to=
 support all options.<br>

<br>
Details &amp; Methods:<br>
<br>
My goal is to explore a number of the settings offered by deflate and deter=
mine what effect they have on compression performance, as well as CPU/memor=
y usage. To this end I have written a tool (<a href=3D"https://github.com/z=
aphoyd/ws-pmce-stats" target=3D"_blank">https://github.com/zaphoyd/ws-pmce-=
stats</a>) that will produce a report of compression related statistics whe=
n fed a transcript of messages.<br>

<br>
The first workflow I have explored in detail is a WebSocket service that us=
es a JSON based protocol to deliver short streaming updates. My some of my =
sample data is present in the datasets folder of the above git repository. =
Some examples include a mock chat service with data seeded from publicly lo=
gged mediawiki IRC channel and a mock stock ticker service with data seeded=
 with historical stock quote data.<br>

<br>
I explored the effects of the context takeover and window bits settings fro=
m the permessage-deflate draft spec as well as a few zlib settings that can=
 be unilaterally specified without any extension negotiation. Some, but not=
 all of these, are presently exposed in higher level languages that use zli=
b as their underlying compression library. I looked at two of these setting=
s in particular, the &quot;Compression Level&quot; and the &quot;Memory Lev=
el&quot;. The former affects speed vs compression ratio, the latter memory =
usage vs compression ratio.<br>

<br>
Preliminary results for the JSON short message service workflow:<br>
<br>
Context Takeover<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
Allowing context takeover drastically improves compression ratios. With oth=
er stats at defaults, no_context_takeover achieves a compression ratio of 0=
.84, with takeover 0.30. This is a significant gain. Note: this gain comes =
at a fairly high cost. Enabling context takeover requires a separate contex=
t to be maintained for every connection, rather than fixed number for all c=
onnections.<br>

<br>
Window Bits<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
Window bits has a sizable but well distributed effect on ratios. It has a s=
ignificant effect on memory usage though. With all other stats at defaults:=
<br>
window bits =3D compression ratio / buffer size per connection<br>
08 =3D 0.510 / 1+128=3D129KiB<br>
09 =3D 0.510 / 2+128=3D130KiB<br>
10 =3D 0.435 / 4+128=3D132KiB<br>
11 =3D 0.384 / 8+128=3D136KiB<br>
12 =3D 0.353 / 16+128=3D144KiB<br>
13 =3D 0.330 / 32+128=3D160KiB<br>
14 =3D 0.315 / 64+128=3D192KiB<br>
15 =3D 0.304 / 128+128=3D256KiB<br>
Reducing window bits from the default (15) to 11 provides an 8% reduction i=
n compression but nearly a 50% savings in per connection memory usage. Redu=
ced window bits to very small values (8-9) also increases compression runti=
me by 40-50%. 10 Is less slow, 11+ appear to all be about the same speed.<b=
r>

<br>
Compression Level<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
Compression level does not have a material impact on performance or ratios =
for this workflow.<br>
<br>
Memory Level<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
Memory level does not have a significant impact on compression ratios. A va=
lue of 9 produces the ratio 0.304 and a value of 1 produces the ratio 0.307=
. It does affect memory usage and compression speed however:<br>
mem_level value =3D runtime / memory usage<br>
1 =3D 13.05ms / 128+1=3D129KiB<br>
2 =3D 10.41ms / 128+2=3D130KiB<br>
3 =3D 10.15ms / 128+4=3D132KiB<br>
4 =3D 8.18ms / 128+8=3D136KiB<br>
5 =3D 7.63ms / 128+16=3D144KiB<br>
6 =3D 7.69ms / 128+32=3D160KiB<br>
7 =3D 7.92ms / 128+64=3D192KiB<br>
8 =3D 7.69ms / 128+128=3D256KiB<br>
9 =3D 7.84ms / 128+256=3D386KiB<br>
<br>
All of the stats above show the effects of changing one parameter in isolat=
ion. Additional gains, especially with respect to memory usage per connecti=
on can be had by combinations of parameters. Many of the speed, compression=
, and memory effects of parameters are dependent on each other. Two nice ba=
lances of all factors for the JSON short message service data set (vs defau=
lts) are something like..<br>

<br>
context-takeover=3Don<br>
window bits=3D11<br>
memory level=3D4<br>
This provides memory usage of 16KiB/connection vs 256KiB, has no runtime sp=
eed penalty, and achieves a 0.384 vs 0.304 compression ratio.<br>
<br>
context-takeover=3Don<br>
window bits=3D11<br>
memory level=3D1<br>
This provides memory usage of 5KiB/connection vs 256KiB, runs ~15% slower, =
and achieves a similar 0.385 vs 0.304 compression ratio.<br>
<br>
The ws-pmce-stats tool can help you plug in values and get a sense for whic=
h combinations of settings are optimal for your traffic mix. In general I h=
ave found that the shorter your messages, the less you benefit from high wi=
ndow bit and memory level values. If you routinely send WebSocket messages =
with payloads in the high hundreds of KB or MBs you will benefit from highe=
r values for memory level and window bits. If you have extremely limited me=
mory, no context takeover will allow fixed memory usage for all connections=
. Its price is heavy for small messages &amp; JSON protocols, but less prob=
lematic for large ones. I&#39;ve found that 11 window bits and compression =
memory level 4 is still quite effective even up to message payloads of ~200=
KB.<br>

<br>
I&#39;d love to hear any feedback anyone has about the methods or results. =
I am particularly interested in collecting more sample WebSocket workflows.=
 I haven&#39;t run any numbers for binary connections yet. I&#39;d love to =
hear details about other workflows that might have different properties tha=
n the ones studied here so far, especially if you have sample transcripts.<=
br>

<br>
I&#39;d also be interested in any feedback on the ws-pmce-stats program. Is=
 something like this useful to anyone else? It meets my needs right now, bu=
t I have a few ideas of how to expand it (binary message support, other com=
pression algorithms, machine readable output) if it sounds useful to others=
.<br>

_______________________________________________<br>
hybi mailing list<br>
<a href=3D"mailto:hybi@ietf.org">hybi@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/hybi" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/hybi</a><br>
</blockquote></div><br></div>

--001a11c1ac1234bd6104e8cc09f6--

From tobias.oberstein@tavendo.de  Tue Oct 15 12:01:58 2013
Return-Path: <tobias.oberstein@tavendo.de>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2289421F9FAE for <hybi@ietfa.amsl.com>; Tue, 15 Oct 2013 12:01:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S94DYdbJbBCg for <hybi@ietfa.amsl.com>; Tue, 15 Oct 2013 12:01:51 -0700 (PDT)
Received: from EXHUB020-1.exch020.serverdata.net (exhub020-1.exch020.serverdata.net [206.225.164.28]) by ietfa.amsl.com (Postfix) with ESMTP id 1DC3D11E8156 for <hybi@ietf.org>; Tue, 15 Oct 2013 12:01:47 -0700 (PDT)
Received: from EXVMBX020-12.exch020.serverdata.net ([169.254.3.240]) by EXHUB020-1.exch020.serverdata.net ([206.225.164.28]) with mapi; Tue, 15 Oct 2013 12:01:46 -0700
From: Tobias Oberstein <tobias.oberstein@tavendo.de>
To: Peter Thorson <webmaster@zaphoyd.com>, "hybi@ietf.org" <hybi@ietf.org>
Date: Tue, 15 Oct 2013 12:01:43 -0700
Thread-Topic: [hybi] permessage-deflate performance tuning statistics
Thread-Index: Ac7J1TgI93EbKEIiSiKEI1JXVmJz1QAA2mgg
Message-ID: <634914A010D0B943A035D226786325D44469B06DCF@EXVMBX020-12.exch020.serverdata.net>
References: <FD138330-7D7E-4450-B4F5-64551F92F26D@zaphoyd.com>
In-Reply-To: <FD138330-7D7E-4450-B4F5-64551F92F26D@zaphoyd.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [hybi] permessage-deflate performance tuning statistics
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 15 Oct 2013 19:01:58 -0000

Hi Peter,

this is fantastic empirical evidence - very much appreciated!

As a first concrete action from this, I'll take the following issue to the =
Python
community:

"Expose the 'Memory Level' knob on the Python zlib wrapper"

Cheers,
Tobias
=20
> -----Urspr=FCngliche Nachricht-----
> Von: hybi-bounces@ietf.org [mailto:hybi-bounces@ietf.org] Im Auftrag von
> Peter Thorson
> Gesendet: Dienstag, 15. Oktober 2013 20:34
> An: hybi@ietf.org
> Betreff: [hybi] permessage-deflate performance tuning statistics
>=20
> Hi all,
>=20
> I've been doing a bit of research and testing on the compression
> performance and memory usage of permessage-deflate on WebSocket like
> workloads. I plan to write about this with more final numbers once the sp=
ec
> is official, but some of the intermediate results and tools may be of int=
erest
> to this group during the standardization process so I'm sharing some of t=
hose
> notes here.
>=20
> Some highlights:
> - Permessage-deflate offers significant bandwidth savings.
> - How the extension performs depends greatly on the type of data that is
> being compressed and the compression settings given to deflate.
> - Settings that work well for HTTP and the zlib/permessage-deflate defaul=
ts
> are inefficient for some common WebSocket workflows.
> - The two parameters presently in the draft specification both provide
> significant and meaningful options for tuning compression performance for
> those workflows. Implementations (especially browsers) are greatly
> encouraged to support all options.
>=20
> Details & Methods:
>=20
> My goal is to explore a number of the settings offered by deflate and
> determine what effect they have on compression performance, as well as
> CPU/memory usage. To this end I have written a tool
> (https://github.com/zaphoyd/ws-pmce-stats) that will produce a report of
> compression related statistics when fed a transcript of messages.
>=20
> The first workflow I have explored in detail is a WebSocket service that =
uses a
> JSON based protocol to deliver short streaming updates. My some of my
> sample data is present in the datasets folder of the above git repository=
.
> Some examples include a mock chat service with data seeded from publicly
> logged mediawiki IRC channel and a mock stock ticker service with data
> seeded with historical stock quote data.
>=20
> I explored the effects of the context takeover and window bits settings f=
rom
> the permessage-deflate draft spec as well as a few zlib settings that can=
 be
> unilaterally specified without any extension negotiation. Some, but not a=
ll of
> these, are presently exposed in higher level languages that use zlib as t=
heir
> underlying compression library. I looked at two of these settings in part=
icular,
> the "Compression Level" and the "Memory Level". The former affects speed
> vs compression ratio, the latter memory usage vs compression ratio.
>=20
> Preliminary results for the JSON short message service workflow:
>=20
> Context Takeover
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Allowing context takeover drastically improves compression ratios. With
> other stats at defaults, no_context_takeover achieves a compression ratio=
 of
> 0.84, with takeover 0.30. This is a significant gain. Note: this gain com=
es at a
> fairly high cost. Enabling context takeover requires a separate context t=
o be
> maintained for every connection, rather than fixed number for all
> connections.
>=20
> Window Bits
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Window bits has a sizable but well distributed effect on ratios. It has a
> significant effect on memory usage though. With all other stats at defaul=
ts:
> window bits =3D compression ratio / buffer size per connection
> 08 =3D 0.510 / 1+128=3D129KiB
> 09 =3D 0.510 / 2+128=3D130KiB
> 10 =3D 0.435 / 4+128=3D132KiB
> 11 =3D 0.384 / 8+128=3D136KiB
> 12 =3D 0.353 / 16+128=3D144KiB
> 13 =3D 0.330 / 32+128=3D160KiB
> 14 =3D 0.315 / 64+128=3D192KiB
> 15 =3D 0.304 / 128+128=3D256KiB
> Reducing window bits from the default (15) to 11 provides an 8% reduction=
 in
> compression but nearly a 50% savings in per connection memory usage.
> Reduced window bits to very small values (8-9) also increases compression
> runtime by 40-50%. 10 Is less slow, 11+ appear to all be about the same
> speed.
>=20
> Compression Level
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Compression level does not have a material impact on performance or ratio=
s
> for this workflow.
>=20
> Memory Level
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Memory level does not have a significant impact on compression ratios. A
> value of 9 produces the ratio 0.304 and a value of 1 produces the ratio 0=
.307.
> It does affect memory usage and compression speed however:
> mem_level value =3D runtime / memory usage
> 1 =3D 13.05ms / 128+1=3D129KiB
> 2 =3D 10.41ms / 128+2=3D130KiB
> 3 =3D 10.15ms / 128+4=3D132KiB
> 4 =3D 8.18ms / 128+8=3D136KiB
> 5 =3D 7.63ms / 128+16=3D144KiB
> 6 =3D 7.69ms / 128+32=3D160KiB
> 7 =3D 7.92ms / 128+64=3D192KiB
> 8 =3D 7.69ms / 128+128=3D256KiB
> 9 =3D 7.84ms / 128+256=3D386KiB
>=20
> All of the stats above show the effects of changing one parameter in
> isolation. Additional gains, especially with respect to memory usage per
> connection can be had by combinations of parameters. Many of the speed,
> compression, and memory effects of parameters are dependent on each
> other. Two nice balances of all factors for the JSON short message servic=
e
> data set (vs defaults) are something like..
>=20
> context-takeover=3Don
> window bits=3D11
> memory level=3D4
> This provides memory usage of 16KiB/connection vs 256KiB, has no runtime
> speed penalty, and achieves a 0.384 vs 0.304 compression ratio.
>=20
> context-takeover=3Don
> window bits=3D11
> memory level=3D1
> This provides memory usage of 5KiB/connection vs 256KiB, runs ~15% slower=
,
> and achieves a similar 0.385 vs 0.304 compression ratio.
>=20
> The ws-pmce-stats tool can help you plug in values and get a sense for wh=
ich
> combinations of settings are optimal for your traffic mix. In general I h=
ave
> found that the shorter your messages, the less you benefit from high
> window bit and memory level values. If you routinely send WebSocket
> messages with payloads in the high hundreds of KB or MBs you will benefit
> from higher values for memory level and window bits. If you have extremel=
y
> limited memory, no context takeover will allow fixed memory usage for all
> connections. Its price is heavy for small messages & JSON protocols, but =
less
> problematic for large ones. I've found that 11 window bits and compressio=
n
> memory level 4 is still quite effective even up to message payloads of
> ~200KB.
>=20
> I'd love to hear any feedback anyone has about the methods or results. I =
am
> particularly interested in collecting more sample WebSocket workflows. I
> haven't run any numbers for binary connections yet. I'd love to hear deta=
ils
> about other workflows that might have different properties than the ones
> studied here so far, especially if you have sample transcripts.
>=20
> I'd also be interested in any feedback on the ws-pmce-stats program. Is
> something like this useful to anyone else? It meets my needs right now, b=
ut I
> have a few ideas of how to expand it (binary message support, other
> compression algorithms, machine readable output) if it sounds useful to
> others.
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi

From webmaster@zaphoyd.com  Tue Oct 15 13:50:32 2013
Return-Path: <webmaster@zaphoyd.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04F4E21F9A10 for <hybi@ietfa.amsl.com>; Tue, 15 Oct 2013 13:50:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JkfEOiysAbuj for <hybi@ietfa.amsl.com>; Tue, 15 Oct 2013 13:50:24 -0700 (PDT)
Received: from sh78.surpasshosting.com (sh78.surpasshosting.com [72.29.64.142]) by ietfa.amsl.com (Postfix) with ESMTP id 4975621F8B9C for <hybi@ietf.org>; Tue, 15 Oct 2013 13:50:21 -0700 (PDT)
Received: from ranna.uchicago.edu ([128.135.45.206]:62725) by sh78.surpasshosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80.1) (envelope-from <webmaster@zaphoyd.com>) id 1VWBZK-0002oT-5t; Tue, 15 Oct 2013 16:50:19 -0400
Content-Type: multipart/alternative; boundary="Apple-Mail=_31691780-3236-4A76-A7B4-4BE467733BC4"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Peter Thorson <webmaster@zaphoyd.com>
In-Reply-To: <CAG4zZZBFVoYt7RLir_EZ+brW_heThO7D-CdQxWc4gicZBG2fCA@mail.gmail.com>
Date: Tue, 15 Oct 2013 15:50:17 -0500
Message-Id: <64654145-6171-47C8-B990-D11F34E8B67B@zaphoyd.com>
References: <FD138330-7D7E-4450-B4F5-64551F92F26D@zaphoyd.com> <CAG4zZZBFVoYt7RLir_EZ+brW_heThO7D-CdQxWc4gicZBG2fCA@mail.gmail.com>
To: Joakim Erdfelt <joakim@intalio.com>
X-Mailer: Apple Mail (2.1510)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - sh78.surpasshosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - zaphoyd.com
X-Get-Message-Sender-Via: sh78.surpasshosting.com: authenticated_id: webmaster@zaphoyd.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] permessage-deflate performance tuning statistics
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 15 Oct 2013 20:50:32 -0000

--Apple-Mail=_31691780-3236-4A76-A7B4-4BE467733BC4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Oct 15, 2013, at 13:48 , Joakim Erdfelt <joakim@intalio.com> wrote:

> Nice.  Was meaning to do this myself, but just haven't had the free =
time to devote to it.
> I imagine that the results of this will serve the community well.
>=20
> Is your experimental data testing if fragmentation has any impact? =
(lots of smaller fragments for a larger message, commonly seen in =
streaming behaviors)

I have not explicitly looked at fragmentation yet. Theoretically...

For cases with context takeover I'd assume a Z_SYNC_FLUSH for each =
outgoing fragment to align on a byte boundary. In which case, fragmented =
compression will behave exactly as if you had sent the content in =
multiple messages but worse than if you had sent it in one un-fragmented =
message.

For cases without context takeover it would get more complicated, do you =
retain context between fragments? If so that negates all of the memory =
benefits of no-context-takeover=85 This needs to be clarified in the =
permessage-compress draft spec.

> Are you testing just a single type of data on the connection?
> Are you testing multiple types of data during the same connection, =
such as a theoretical protocol that has markup + metadata + and pre =
compressed media?

The ws-pmce-stats utility takes as input right now a line delimited =
input and considers each line one message. Other than the present =
restriction of text messages only (not a fundamental restriction, I just =
haven't written something that handles binary input yet) you can feed =
any sort of data to the application and get stats. Supporting binary =
and/or fragmented messages will require a different and more complicated =
input scheme (probably eat a canned WebSocket feed rather than a =
unix-like line delimited stream). WebSocket++ will do offline decoding =
of a stream like that so it should be easy to set up, but not something =
I'll do unless someone would actually use it. =3D)

The data I've tested with has been "a single type" in the sense that all =
messages belong to the same JSON protocol. There are different types of =
messages though. For example the chat data set starts off with a few =
setup messages that are largish, including a channel welcome message and =
full list of channel participants. Future messages are small (individual =
chat messages going back and forth). The individual messages are also =
mixed type. A chat message for example has a fixed length numeric =
timestamp, a username, and an arbitrary length field of english text. =
The stock ticker example is more uniform, with more numbers and no =
english. All the JSON data has whitespace removed as I am trying to =
model as accurately as possible what might really be sent over the wire. =
For the most part the exact composition of the JSON fields doesn't make =
as much of a difference as the memory related parameters. Text in =
general compresses well.

A few things I've done that deviate a bit from the above examples:

I've tried the stock ticker JSON data in two variants, one that uses =
text labels (larger and more redundant, but more human readable) the =
other where the order of values in an array determines which field it =
is. The value with text labels compressed better (13.769KB -> 3.428KB, =
ratio=3D0.248965) but not quite better enough (7.417KB -> 2.84KB, =
ratio=3D0.382904) to have a smaller wire size . Labels + compression is =
more than twice as small as no labels without compression however.

I've tried larger chunks of non-JSON text data, like sending entire =
Project Gutenberg books in a single message. They compress well but not =
as well as JSON 0.4-0.5 ratios rather than 0.2-0.4. The larger messages =
are a bit more sensitive to window bits and compress memory level, but =
not *that* much. 4 is just fine, 8 (default) is overkill.

It would definitely be worth experimenting with a connection that =
multiplexes small messages with large ones, say for the example case =
where you are delivering new documents over the WebSocket connection as =
we'll as small updates. Getting some tests with binary/compressed data =
intermixed would also be useful it sounds. Does anyone have any sample =
data for such a connection?

>=20
>=20
> --
> Joakim Erdfelt <joakim@intalio.com>
> webtide.com - intalio.com/jetty
> Expert advice, services and support from from the Jetty & CometD =
experts
> eclipse.org/jetty - cometd.org
>=20
>=20
> On Tue, Oct 15, 2013 at 11:34 AM, Peter Thorson =
<webmaster@zaphoyd.com> wrote:
> Hi all,
>=20
> I've been doing a bit of research and testing on the compression =
performance and memory usage of permessage-deflate on WebSocket like =
workloads. I plan to write about this with more final numbers once the =
spec is official, but some of the intermediate results and tools may be =
of interest to this group during the standardization process so I'm =
sharing some of those notes here.
>=20
> Some highlights:
> - Permessage-deflate offers significant bandwidth savings.
> - How the extension performs depends greatly on the type of data that =
is being compressed and the compression settings given to deflate.
> - Settings that work well for HTTP and the zlib/permessage-deflate =
defaults are inefficient for some common WebSocket workflows.
> - The two parameters presently in the draft specification both provide =
significant and meaningful options for tuning compression performance =
for those workflows. Implementations (especially browsers) are greatly =
encouraged to support all options.
>=20
> Details & Methods:
>=20
> My goal is to explore a number of the settings offered by deflate and =
determine what effect they have on compression performance, as well as =
CPU/memory usage. To this end I have written a tool =
(https://github.com/zaphoyd/ws-pmce-stats) that will produce a report of =
compression related statistics when fed a transcript of messages.
>=20
> The first workflow I have explored in detail is a WebSocket service =
that uses a JSON based protocol to deliver short streaming updates. My =
some of my sample data is present in the datasets folder of the above =
git repository. Some examples include a mock chat service with data =
seeded from publicly logged mediawiki IRC channel and a mock stock =
ticker service with data seeded with historical stock quote data.
>=20
> I explored the effects of the context takeover and window bits =
settings from the permessage-deflate draft spec as well as a few zlib =
settings that can be unilaterally specified without any extension =
negotiation. Some, but not all of these, are presently exposed in higher =
level languages that use zlib as their underlying compression library. I =
looked at two of these settings in particular, the "Compression Level" =
and the "Memory Level". The former affects speed vs compression ratio, =
the latter memory usage vs compression ratio.
>=20
> Preliminary results for the JSON short message service workflow:
>=20
> Context Takeover
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Allowing context takeover drastically improves compression ratios. =
With other stats at defaults, no_context_takeover achieves a compression =
ratio of 0.84, with takeover 0.30. This is a significant gain. Note: =
this gain comes at a fairly high cost. Enabling context takeover =
requires a separate context to be maintained for every connection, =
rather than fixed number for all connections.
>=20
> Window Bits
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Window bits has a sizable but well distributed effect on ratios. It =
has a significant effect on memory usage though. With all other stats at =
defaults:
> window bits =3D compression ratio / buffer size per connection
> 08 =3D 0.510 / 1+128=3D129KiB
> 09 =3D 0.510 / 2+128=3D130KiB
> 10 =3D 0.435 / 4+128=3D132KiB
> 11 =3D 0.384 / 8+128=3D136KiB
> 12 =3D 0.353 / 16+128=3D144KiB
> 13 =3D 0.330 / 32+128=3D160KiB
> 14 =3D 0.315 / 64+128=3D192KiB
> 15 =3D 0.304 / 128+128=3D256KiB
> Reducing window bits from the default (15) to 11 provides an 8% =
reduction in compression but nearly a 50% savings in per connection =
memory usage. Reduced window bits to very small values (8-9) also =
increases compression runtime by 40-50%. 10 Is less slow, 11+ appear to =
all be about the same speed.
>=20
> Compression Level
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Compression level does not have a material impact on performance or =
ratios for this workflow.
>=20
> Memory Level
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Memory level does not have a significant impact on compression ratios. =
A value of 9 produces the ratio 0.304 and a value of 1 produces the =
ratio 0.307. It does affect memory usage and compression speed however:
> mem_level value =3D runtime / memory usage
> 1 =3D 13.05ms / 128+1=3D129KiB
> 2 =3D 10.41ms / 128+2=3D130KiB
> 3 =3D 10.15ms / 128+4=3D132KiB
> 4 =3D 8.18ms / 128+8=3D136KiB
> 5 =3D 7.63ms / 128+16=3D144KiB
> 6 =3D 7.69ms / 128+32=3D160KiB
> 7 =3D 7.92ms / 128+64=3D192KiB
> 8 =3D 7.69ms / 128+128=3D256KiB
> 9 =3D 7.84ms / 128+256=3D386KiB
>=20
> All of the stats above show the effects of changing one parameter in =
isolation. Additional gains, especially with respect to memory usage per =
connection can be had by combinations of parameters. Many of the speed, =
compression, and memory effects of parameters are dependent on each =
other. Two nice balances of all factors for the JSON short message =
service data set (vs defaults) are something like..
>=20
> context-takeover=3Don
> window bits=3D11
> memory level=3D4
> This provides memory usage of 16KiB/connection vs 256KiB, has no =
runtime speed penalty, and achieves a 0.384 vs 0.304 compression ratio.
>=20
> context-takeover=3Don
> window bits=3D11
> memory level=3D1
> This provides memory usage of 5KiB/connection vs 256KiB, runs ~15% =
slower, and achieves a similar 0.385 vs 0.304 compression ratio.
>=20
> The ws-pmce-stats tool can help you plug in values and get a sense for =
which combinations of settings are optimal for your traffic mix. In =
general I have found that the shorter your messages, the less you =
benefit from high window bit and memory level values. If you routinely =
send WebSocket messages with payloads in the high hundreds of KB or MBs =
you will benefit from higher values for memory level and window bits. If =
you have extremely limited memory, no context takeover will allow fixed =
memory usage for all connections. Its price is heavy for small messages =
& JSON protocols, but less problematic for large ones. I've found that =
11 window bits and compression memory level 4 is still quite effective =
even up to message payloads of ~200KB.
>=20
> I'd love to hear any feedback anyone has about the methods or results. =
I am particularly interested in collecting more sample WebSocket =
workflows. I haven't run any numbers for binary connections yet. I'd =
love to hear details about other workflows that might have different =
properties than the ones studied here so far, especially if you have =
sample transcripts.
>=20
> I'd also be interested in any feedback on the ws-pmce-stats program. =
Is something like this useful to anyone else? It meets my needs right =
now, but I have a few ideas of how to expand it (binary message support, =
other compression algorithms, machine readable output) if it sounds =
useful to others.
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi
>=20
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi


--Apple-Mail=_31691780-3236-4A76-A7B4-4BE467733BC4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Oct 15, 2013, at 13:48 , Joakim Erdfelt &lt;<a =
href=3D"mailto:joakim@intalio.com">joakim@intalio.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div dir=3D"ltr">Nice. &nbsp;Was meaning to do this =
myself, but just haven't had the free time to devote to it.<div>I =
imagine that the results of this will serve the community =
well.<br><div><br></div><div>Is your experimental data testing if =
fragmentation has any impact? (lots of smaller fragments for a larger =
message, commonly seen in streaming =
behaviors)</div></div></div></blockquote><div><br></div><div>I have not =
explicitly looked at fragmentation yet. =
Theoretically...</div><div><br></div><div>For cases with context =
takeover I'd assume a Z_SYNC_FLUSH for each outgoing fragment to align =
on a byte boundary. In which case, fragmented compression will behave =
exactly as if you had sent the content in multiple messages but worse =
than if you had sent it in one un-fragmented =
message.</div><div><br></div><div>For cases without context takeover it =
would get more complicated, do you retain context between fragments? If =
so that negates all of the memory benefits of no-context-takeover=85 =
This needs to be clarified in the permessage-compress draft =
spec.</div><br><blockquote type=3D"cite"><div dir=3D"ltr"><div><div>Are =
you testing just a single type of data on the =
connection?</div></div></div></blockquote><blockquote type=3D"cite"><div =
dir=3D"ltr"><div><div>Are you testing multiple types of data during the =
same connection, such as a theoretical protocol that has markup + =
metadata + and pre compressed =
media?</div></div></div></blockquote><div><br></div><div>The =
ws-pmce-stats utility takes as input right now a line delimited input =
and considers each line one message. Other than the present restriction =
of text messages only (not a fundamental restriction, I just haven't =
written something that handles binary input yet) you can feed any sort =
of data to the application and get stats.&nbsp;Supporting binary and/or =
fragmented messages will require a different and more complicated input =
scheme (probably eat a canned WebSocket feed rather than a unix-like =
line delimited stream). WebSocket++ will do offline decoding of a stream =
like that so it should be easy to set up, but not something I'll do =
unless someone would actually use it. =3D)</div><div><br></div><div>The =
data I've tested with has been "a single type" in the sense that all =
messages belong to the same JSON protocol. There are different types of =
messages though. For example the chat data set starts off with a few =
setup messages that are largish, including a channel welcome message and =
full list of channel participants. Future messages are small (individual =
chat messages going back and forth). The individual messages are also =
mixed type. A chat message for example has a fixed length numeric =
timestamp, a username, and an arbitrary length field of english text. =
The stock ticker example is more uniform, with more numbers and no =
english. All the JSON data has whitespace removed as I am trying to =
model as accurately as possible what might really be sent over the wire. =
For the most part the exact composition of the JSON fields doesn't make =
as much of a difference as the memory related parameters. Text in =
general compresses well.</div><div><br></div><div>A few things I've done =
that deviate a bit from the above =
examples:</div><div><br></div><div>I've tried the stock ticker JSON data =
in two variants, one that uses text labels (larger and more redundant, =
but more human readable) the other where the order of values in an array =
determines which field it is. The value with text labels compressed =
better (13.769KB -&gt; 3.428KB, ratio=3D0.248965) but not quite better =
enough&nbsp;(7.417KB -&gt; 2.84KB, ratio=3D0.382904)&nbsp;to have a =
smaller wire size . Labels + compression is more than twice as small as =
no labels without compression however.</div><div><br></div><div>I've =
tried larger chunks of non-JSON text data, like sending entire Project =
Gutenberg books in a single message. They compress well but not as well =
as JSON 0.4-0.5 ratios rather than 0.2-0.4. The larger messages are a =
bit more sensitive to window bits and compress memory level, but not =
*that* much. 4 is just fine, 8 (default) is =
overkill.</div><div><br></div><div>It would definitely be worth =
experimenting with a connection that multiplexes small messages with =
large ones, say for the example case where you are delivering new =
documents over the WebSocket connection as we'll as small updates. =
Getting some tests with binary/compressed data intermixed would also be =
useful it sounds. Does anyone have any sample data for such a =
connection?</div><br><blockquote type=3D"cite"><div =
dir=3D"ltr"><div><br></div></div><div class=3D"gmail_extra"><br =
clear=3D"all"><div><div dir=3D"ltr"><div>--</div><div>Joakim Erdfelt =
&lt;<a href=3D"mailto:joakim@intalio.com" =
target=3D"_blank">joakim@intalio.com</a>&gt;</div>
<div><a href=3D"http://www.webtide.com/" =
target=3D"_blank">webtide.com</a>&nbsp;- <a =
href=3D"http://intalio.com/jetty" =
target=3D"_blank">intalio.com/jetty</a></div><div><span>Expert advice, =
services and support from&nbsp;</span><span>from the Jetty &amp; CometD =
experts</span></div>
<div><a href=3D"http://eclipse.org/jetty/" =
target=3D"_blank">eclipse.org/jetty</a>&nbsp;-&nbsp;<a =
href=3D"http://cometd.org/" =
target=3D"_blank">cometd.org</a></div></div></div>
<br><br><div class=3D"gmail_quote">On Tue, Oct 15, 2013 at 11:34 AM, =
Peter Thorson <span dir=3D"ltr">&lt;<a =
href=3D"mailto:webmaster@zaphoyd.com" =
target=3D"_blank">webmaster@zaphoyd.com</a>&gt;</span> =
wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi all,<br>
<br>
I've been doing a bit of research and testing on the compression =
performance and memory usage of permessage-deflate on WebSocket like =
workloads. I plan to write about this with more final numbers once the =
spec is official, but some of the intermediate results and tools may be =
of interest to this group during the standardization process so I'm =
sharing some of those notes here.<br>

<br>
Some highlights:<br>
- Permessage-deflate offers significant bandwidth savings.<br>
- How the extension performs depends greatly on the type of data that is =
being compressed and the compression settings given to deflate.<br>
- Settings that work well for HTTP and the zlib/permessage-deflate =
defaults are inefficient for some common WebSocket workflows.<br>
- The two parameters presently in the draft specification both provide =
significant and meaningful options for tuning compression performance =
for those workflows. Implementations (especially browsers) are greatly =
encouraged to support all options.<br>

<br>
Details &amp; Methods:<br>
<br>
My goal is to explore a number of the settings offered by deflate and =
determine what effect they have on compression performance, as well as =
CPU/memory usage. To this end I have written a tool (<a =
href=3D"https://github.com/zaphoyd/ws-pmce-stats" =
target=3D"_blank">https://github.com/zaphoyd/ws-pmce-stats</a>) that =
will produce a report of compression related statistics when fed a =
transcript of messages.<br>

<br>
The first workflow I have explored in detail is a WebSocket service that =
uses a JSON based protocol to deliver short streaming updates. My some =
of my sample data is present in the datasets folder of the above git =
repository. Some examples include a mock chat service with data seeded =
from publicly logged mediawiki IRC channel and a mock stock ticker =
service with data seeded with historical stock quote data.<br>

<br>
I explored the effects of the context takeover and window bits settings =
from the permessage-deflate draft spec as well as a few zlib settings =
that can be unilaterally specified without any extension negotiation. =
Some, but not all of these, are presently exposed in higher level =
languages that use zlib as their underlying compression library. I =
looked at two of these settings in particular, the "Compression Level" =
and the "Memory Level". The former affects speed vs compression ratio, =
the latter memory usage vs compression ratio.<br>

<br>
Preliminary results for the JSON short message service workflow:<br>
<br>
Context Takeover<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
Allowing context takeover drastically improves compression ratios. With =
other stats at defaults, no_context_takeover achieves a compression =
ratio of 0.84, with takeover 0.30. This is a significant gain. Note: =
this gain comes at a fairly high cost. Enabling context takeover =
requires a separate context to be maintained for every connection, =
rather than fixed number for all connections.<br>

<br>
Window Bits<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
Window bits has a sizable but well distributed effect on ratios. It has =
a significant effect on memory usage though. With all other stats at =
defaults:<br>
window bits =3D compression ratio / buffer size per connection<br>
08 =3D 0.510 / 1+128=3D129KiB<br>
09 =3D 0.510 / 2+128=3D130KiB<br>
10 =3D 0.435 / 4+128=3D132KiB<br>
11 =3D 0.384 / 8+128=3D136KiB<br>
12 =3D 0.353 / 16+128=3D144KiB<br>
13 =3D 0.330 / 32+128=3D160KiB<br>
14 =3D 0.315 / 64+128=3D192KiB<br>
15 =3D 0.304 / 128+128=3D256KiB<br>
Reducing window bits from the default (15) to 11 provides an 8% =
reduction in compression but nearly a 50% savings in per connection =
memory usage. Reduced window bits to very small values (8-9) also =
increases compression runtime by 40-50%. 10 Is less slow, 11+ appear to =
all be about the same speed.<br>

<br>
Compression Level<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
Compression level does not have a material impact on performance or =
ratios for this workflow.<br>
<br>
Memory Level<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
Memory level does not have a significant impact on compression ratios. A =
value of 9 produces the ratio 0.304 and a value of 1 produces the ratio =
0.307. It does affect memory usage and compression speed however:<br>
mem_level value =3D runtime / memory usage<br>
1 =3D 13.05ms / 128+1=3D129KiB<br>
2 =3D 10.41ms / 128+2=3D130KiB<br>
3 =3D 10.15ms / 128+4=3D132KiB<br>
4 =3D 8.18ms / 128+8=3D136KiB<br>
5 =3D 7.63ms / 128+16=3D144KiB<br>
6 =3D 7.69ms / 128+32=3D160KiB<br>
7 =3D 7.92ms / 128+64=3D192KiB<br>
8 =3D 7.69ms / 128+128=3D256KiB<br>
9 =3D 7.84ms / 128+256=3D386KiB<br>
<br>
All of the stats above show the effects of changing one parameter in =
isolation. Additional gains, especially with respect to memory usage per =
connection can be had by combinations of parameters. Many of the speed, =
compression, and memory effects of parameters are dependent on each =
other. Two nice balances of all factors for the JSON short message =
service data set (vs defaults) are something like..<br>

<br>
context-takeover=3Don<br>
window bits=3D11<br>
memory level=3D4<br>
This provides memory usage of 16KiB/connection vs 256KiB, has no runtime =
speed penalty, and achieves a 0.384 vs 0.304 compression ratio.<br>
<br>
context-takeover=3Don<br>
window bits=3D11<br>
memory level=3D1<br>
This provides memory usage of 5KiB/connection vs 256KiB, runs ~15% =
slower, and achieves a similar 0.385 vs 0.304 compression ratio.<br>
<br>
The ws-pmce-stats tool can help you plug in values and get a sense for =
which combinations of settings are optimal for your traffic mix. In =
general I have found that the shorter your messages, the less you =
benefit from high window bit and memory level values. If you routinely =
send WebSocket messages with payloads in the high hundreds of KB or MBs =
you will benefit from higher values for memory level and window bits. If =
you have extremely limited memory, no context takeover will allow fixed =
memory usage for all connections. Its price is heavy for small messages =
&amp; JSON protocols, but less problematic for large ones. I've found =
that 11 window bits and compression memory level 4 is still quite =
effective even up to message payloads of ~200KB.<br>

<br>
I'd love to hear any feedback anyone has about the methods or results. I =
am particularly interested in collecting more sample WebSocket =
workflows. I haven't run any numbers for binary connections yet. I'd =
love to hear details about other workflows that might have different =
properties than the ones studied here so far, especially if you have =
sample transcripts.<br>

<br>
I'd also be interested in any feedback on the ws-pmce-stats program. Is =
something like this useful to anyone else? It meets my needs right now, =
but I have a few ideas of how to expand it (binary message support, =
other compression algorithms, machine readable output) if it sounds =
useful to others.<br>

_______________________________________________<br>
hybi mailing list<br>
<a href=3D"mailto:hybi@ietf.org">hybi@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/hybi" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/hybi</a><br>
</blockquote></div><br></div>
_______________________________________________<br>hybi mailing =
list<br><a =
href=3D"mailto:hybi@ietf.org">hybi@ietf.org</a><br>https://www.ietf.org/ma=
ilman/listinfo/hybi<br></blockquote></div><br></body></html>=

--Apple-Mail=_31691780-3236-4A76-A7B4-4BE467733BC4--

From internet-drafts@ietf.org  Wed Oct 16 02:11:09 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7F4C11E82A5; Wed, 16 Oct 2013 02:11:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.591
X-Spam-Level: 
X-Spam-Status: No, score=-102.591 tagged_above=-999 required=5 tests=[AWL=0.009, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RcPUe+z9biqI; Wed, 16 Oct 2013 02:11:09 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 22BAB21F9FD6; Wed, 16 Oct 2013 02:11:01 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131016091101.32139.80378.idtracker@ietfa.amsl.com>
Date: Wed, 16 Oct 2013 02:11:01 -0700
Cc: hybi@ietf.org
Subject: [hybi] I-D Action: draft-ietf-hybi-permessage-compression-15.txt
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 16 Oct 2013 09:11:09 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the BiDirectional or Server-Initiated HTTP Wo=
rking Group of the IETF.

	Title           : Compression Extensions for WebSocket
	Author(s)       : Takeshi Yoshino
	Filename        : draft-ietf-hybi-permessage-compression-15.txt
	Pages           : 32
	Date            : 2013-10-16

Abstract:
   This document specifies 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 non-control WebSocket messages on a per-message basis using
   parameters negotiated during the opening handshake.  This framework
   provides a general method to apply a compression algorithm to the
   contents of WebSocket messages.  For each compression algorithm, an
   extension is defined by specifying parameter negotiation and
   compression algorithm in detail.  This document also specifies one
   specific compression extension using the DEFLATE algorithm.

   Please send feedback to the hybi@ietf.org mailing list.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-hybi-permessage-compression

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-hybi-permessage-compression-15

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-hybi-permessage-compression-15


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From tyoshino@google.com  Wed Oct 16 02:13:57 2013
Return-Path: <tyoshino@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC8BB11E82A4 for <hybi@ietfa.amsl.com>; Wed, 16 Oct 2013 02:13:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[AWL=0.076,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y9xqB5K6P46C for <hybi@ietfa.amsl.com>; Wed, 16 Oct 2013 02:13:56 -0700 (PDT)
Received: from mail-we0-x235.google.com (mail-we0-x235.google.com [IPv6:2a00:1450:400c:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id C14B011E82A6 for <hybi@ietf.org>; Wed, 16 Oct 2013 02:13:51 -0700 (PDT)
Received: by mail-we0-f181.google.com with SMTP id t60so388055wes.40 for <hybi@ietf.org>; Wed, 16 Oct 2013 02:13:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=H8TvUeC1Fsj4kEq8adB9vxdz34P8ixKHXtcr0MmXn0M=; b=Vx7ph2a7Cc93T65rzgGxP9EUJdNfSRQlE+6m0+YX+rtn+2TXlmZKXIitARwN+e5H/m j3PzDWPt440RLVszQx9aBn2CqxNGFaSAVfdDiCSsqfiWFQdLVh5nKCJ2wm8qGwbGLJan Y2tyfqw8Wm5snf3Efey6CrxB+a4G+9dH7iB5bdEbqpxsThBMuaY7BtmJJpWExvmej7h1 /00JYCb1f8rKAe/lSQA0VZxbXdHcgQCcE4j0n9D604NbeS9pM9fApy1NeIOijH+k6MHZ s6QsJDfj4GerOvt+4XSXnqsXckUvwUsqHcxUAw/5EmjD36SoGzZcAhudbkxpxb+7ualf EeYA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=H8TvUeC1Fsj4kEq8adB9vxdz34P8ixKHXtcr0MmXn0M=; b=Pg3TmpKUmKx/U6D6hyh0wspVKkD41bb7a+fUt733yAlvsWBV9dQBtamRMZFagyFBE/ HuhNSxnqD5ldGIcIzjVUGm2hWytuQTB/4/tBIP4CuuiF3Gmsmrxj0ZyXLeoDfH6AhU0F +Usq56GsVtLog/xCfVbQmyKyb27+lfHU03F+03CbIiW85jzNj3h601lyefZsuCrOz6CY D+3fdYkKh5SVah+SvsgXtJhM3DK2oiXHA9R/WDs+iM7nO4AZRmQhGUMATJ/0kLp7f2Z2 0Ig5Lid3eCS33XRckCOgXwIdjiHbm8TmNOlcj39L0wmDf0AWTFRnl4+HjYUJM7pT2dS1 Ydaw==
X-Gm-Message-State: ALoCoQkPVekZ4/E18vjfiSruTeCCE43H6sd9I2U/f2wrwVOzDVfxJQlXdJiltmoAuBHh8k0eAQWbAfLsqmonoqsAkenvbHKs6RUm/gtT6Vd2ApM8T4GcF0N3YsFULobdh8nYYxWu5nIMR8KudHzD/FxDN7J1AVE82vx5sXtJgRD8AJMkMcUTpV2Ah9+X6DUrDOZ0GjyXctpj
X-Received: by 10.180.211.71 with SMTP id na7mr23646061wic.5.1381914829037; Wed, 16 Oct 2013 02:13:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.15.133 with HTTP; Wed, 16 Oct 2013 02:13:28 -0700 (PDT)
In-Reply-To: <CAH9hSJYjwnJQLAaeVQvmEX2+_b8q_gzE_+zuq_6XW=-_u-4R8g@mail.gmail.com>
References: <20131008034344.3492.4171.idtracker@ietfa.amsl.com> <CAH9hSJZKwBhmMg5jAa1U93g+Q1Hfv0nRDx=m_ZAbj-oi=_Ba7g@mail.gmail.com> <CAG4zZZC2umzmq2vXPJGmR5+hZuRiRO7BN+9via8dBK7Og4XhBg@mail.gmail.com> <CAH9hSJYjwnJQLAaeVQvmEX2+_b8q_gzE_+zuq_6XW=-_u-4R8g@mail.gmail.com>
From: Takeshi Yoshino <tyoshino@google.com>
Date: Wed, 16 Oct 2013 18:13:28 +0900
Message-ID: <CAH9hSJYXvFNKWx8dLmW+xy+K0iGktmz4gzWo3T+BytzKoTfv0w@mail.gmail.com>
To: Joakim Erdfelt <joakim@intalio.com>
Content-Type: multipart/alternative; boundary=001a11c347e07ee28004e8d81e35
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] I-D Action: draft-ietf-hybi-permessage-compression-13.txt
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 16 Oct 2013 09:13:58 -0000

--001a11c347e07ee28004e8d81e35
Content-Type: text/plain; charset=ISO-8859-1

Addressed the rest for -15.


On Tue, Oct 15, 2013 at 11:00 PM, Takeshi Yoshino <tyoshino@google.com>wrote:

>
>
>>
>>      6.1.  Compression  . . . . . . . . . . . . . . . . . . . . . . . 10
>>
>>    2.  If this PMCE is the last extension to process outgoing messages,
>>        build frame(s) by using the compressed data instead of the
>>        original data for the message payload, and setting the
>>
>>  > The condition "if this PCME is the last extension to process
>>  > outgoing messages" is meaningless, here and further down in this
>>  > section.  The process is the same for all PMCEs regardless if it is
>>  > the first, middle, or last extension.
>>  >
>>  > Also, with the current spec, we would argue that it is impossible
>>  > to have multiple active PMCEs anyway (due to the RSV1 bit requirement)
>>
>>
>
> [TBA]
>

This sentence corresponds to the next sentence with "otherwise". It
explains how to pass the result of compression to the next entity in the
chain. If it's another extension, the sentence starting with "Otherwise"
applies while if there's no more extension, we should follow the first
sentence to pass the result to the RFC 6455 send/receive algorithm.


>
>
>>      6.2.  Decompression  . . . . . . . . . . . . . . . . . . . . . . 11
>>
>>  > Again, same commentary about the "PCME is the last extension"
>>  > condition being irrelevant
>>
>>
>
> [TBA]
>

Ditto.


>
>
>>    7.  Intermediaries . . . . . . . . . . . . . . . . . . . . . . . . 13
>>
>>  > good, but could use some commentary that if the intermediaries are
>>  > not aware of the opening handshake, then they should make no
>>  > modifications to the frames.  See [Section 5.4] of [RFC6455]
>>  > 3rd paragraph for similar text.
>>
>>
>
> [TBA]
>

Done.


>
>
>>    8.  permessage-deflate extension . . . . . . . . . . . . . . . . . 14
>>
>>  > OK, some suggestions on how to clean this section up.
>>  >
>>  > Introduce the 4 extension parameters first.
>>  >
>>  >   Use the language found elsewhere in the spec now about the
>> asymmetric
>>  >   nature of the extension parameter configuration.
>>  >
>>  >   The following 2 extension parameters control the behavior of the
>>  >   deflate configuration for Client-to-Server messages:
>>  >   (We took this notation from the title of [Section 5.3] of [RFC-6455],
>>  >    including the capitalization)
>>  >
>>  >     o  "c2s_no_context_takeover"
>>  >     o  "c2s_max_window_bits"
>>  >
>>  >   The following 2 extension parameters control the behavior of the
>>  >   deflate configuration for Server-to-Client messages:
>>  >
>>  >     o  "s2c_no_context_takeover"
>>  >     o  "s2c_max_window_bits"
>>  >
>>  > Then describe how the Offer works. (essentially the language you
>>  > have now in the doc, with careful attention to not mix your intro
>>  > and then bullets)
>>
> done


>   >    Request: desired client behavior + desired server behavior
>>  >    Response: acknowledge client behavior + server chosen behavior
>>  >
>>  > Example of confusing language:
>>
>>    For an offer for this extension, the following 4 extension parameters
>>    are defined.  If needed to distinguish from ones for a response,
>>    these parameters are called with a prefix "client-to-server".
>>
>>    o  "s2c_no_context_takeover"
>>
>>    o  "c2s_no_context_takeover"
>>
>>    o  "s2c_max_window_bits"
>>
>>    o  "c2s_max_window_bits"
>>
>>  > This section introduces you to "client-to-server", then lists
>>  > s2c_*, why?  Same for the next section, but in reverse.
>>  > Don't mix the introduction of the extension parameters and
>>  > the behavior of the request and response together.
>>  >
>>  > Finally, go into the MUST rules for Client and Server like you
>>  > currently have in the spec documentation.
>>
>
done

used Peter's texts.


>    >
>>  > Include wording for Client MUST pointing back to close code
>>  > 1010 from [RC6455] as a recommended behavior for dealing with
>>  > bad extension negotiation.
>>  > Even for things like a server saying s2c_max_window_bits=1024
>>
>>
>
> replied in another post.


>
>
>>      8.1.  Method Parameters  . . . . . . . . . . . . . . . . . . . . 15
>>        8.1.1.  Context Takeover Control . . . . . . . . . . . . . . . 15
>>
>>  > Include explicit language indicating default behavior for
>>  > context takeover.
>>
>
done


>
>>  > When documenting one side, for example "s2c_", do not make references
>>  > to the opposite direction.  Its confusing, noisy, and adds no value.
>>  >
>>
>
done. removed "in the same ..." sentences


>   > For example, Section 8.1.2.2. c2s_max_window_bits, start out talking
>>  > about the c2s_max_window_bits, then has suddenly talks about
>>  > "server-to-client parameter", mentioning behavior and server limits.
>>  > This is confusing.
>>  > Fix this, clarify it, eliminate the noise, or simplify it.
>>  >
>>  > Eg of simplification:
>>  >
>>  >  See [Section 8.1.2.1.] "s2c_max_window_bits" for server side
>>  >  equivalent
>>  >
>>  > We suspect that the use of "c2s" and "client-to-server" to
>>  > interchangably refer to either the "extension parameter token" itself
>>  > or the phase of the extension negotiation (request or response) is
>>  > the cause of the confusion.
>>  >
>>  > Either choose new terminology for the extension parameter token, or
>>  > choose new terminology for the phase of the extension negotiation
>>  > (request side or response side)
>>  >
>>
>
> [TBA]
>

done i think...


>
>

--001a11c347e07ee28004e8d81e35
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Addressed the rest for -15.</div><br><div class=3D"gm=
ail_extra"><br><div class=3D"gmail_quote">On Tue, Oct 15, 2013 at 11:00 PM,=
 Takeshi Yoshino <span dir=3D"ltr">&lt;<a href=3D"mailto:tyoshino@google.co=
m" target=3D"_blank">tyoshino@google.com</a>&gt;</span> wrote:<br>


<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div><br></div><div class=
=3D"gmail_extra"><div class=3D"gmail_quote"><div><blockquote class=3D"gmail=
_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left=
-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">


<div dir=3D"ltr"><div>=A0=A0</div><div><br></div></div>

</blockquote><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px =
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-=
style:solid;padding-left:1ex"><div dir=3D"ltr"><div>=A0 =A0 =A06.1. =A0Comp=
ression =A0. . . . . . . . . . . . . . . . . . . . . . . 10</div>





<div>=A0 =A0 =A0</div><div>=A0 =A02. =A0If this PMCE is the last extension =
to process outgoing messages,</div><div>=A0 =A0 =A0 =A0build frame(s) by us=
ing the compressed data instead of the</div><div>=A0 =A0 =A0 =A0original da=
ta for the message payload, and setting the</div>





<div><br></div><div>=A0&gt; The condition &quot;if this PCME is the last ex=
tension to process</div><div>=A0&gt; outgoing messages&quot; is meaningless=
, here and further down in this=A0</div><div>=A0&gt; section. =A0The proces=
s is the same for all PMCEs regardless if it is</div>





<div>=A0&gt; the first, middle, or last extension.</div><div>=A0&gt;</div><=
div>=A0&gt; Also, with the current spec, we would argue that it is impossib=
le</div><div>=A0&gt; to have multiple active PMCEs anyway (due to the RSV1 =
bit requirement)</div>





<div>=A0</div></div></blockquote><div><br></div></div><div>[TBA]</div><div>=
<div></div></div></div></div></div></blockquote><div><br></div><div>This se=
ntence corresponds to the next sentence with &quot;otherwise&quot;. It expl=
ains how to pass the result of compression to the next entity in the chain.=
 If it&#39;s another extension, the sentence starting with &quot;Otherwise&=
quot; applies while if there&#39;s no more extension, we should follow the =
first sentence to pass the result to the RFC 6455 send/receive algorithm.</=
div>


<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D=
"gmail_extra"><div class=3D"gmail_quote"><div><div>=A0</div><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;=
border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex=
">




<div dir=3D"ltr"><div>=A0 =A0 =A06.2. =A0Decompression =A0. . . . . . . . .=
 . . . . . . . . . . . . . 11</div><div>=A0 =A0 =A0</div><div>=A0&gt; Again=
, same commentary about the &quot;PCME is the last extension&quot;</div><di=
v>=A0&gt; condition being irrelevant</div>





<div>=A0 =A0 =A0</div></div></blockquote><div><br></div></div><div>[TBA]</d=
iv></div></div></div></blockquote><div><br></div><div>Ditto.</div><div>=A0<=
/div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex">


<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div=
><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p=
x 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-lef=
t-style:solid;padding-left:1ex">




<div dir=3D"ltr"><div>=A0 =A07. =A0Intermediaries . . . . . . . . . . . . .=
 . . . . . . . . . . . 13</div><div>=A0 =A0</div><div>=A0&gt; good, but cou=
ld use some commentary that if the intermediaries are</div><div>=A0&gt; not=
 aware of the opening handshake, then they should make no</div>





<div>=A0&gt; modifications to the frames. =A0See [Section 5.4] of [RFC6455]=
</div><div>=A0&gt; 3rd paragraph for similar text.</div><div>=A0 =A0</div><=
/div></blockquote><div><br></div></div><div>[TBA]</div></div></div></div></=
blockquote>


<div><br></div><div>Done.</div><div>=A0</div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
><div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><di=
v><div>


<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left=
-style:solid;padding-left:1ex">

<div dir=3D"ltr"><div>=A0 =A08. =A0permessage-deflate extension . . . . . .=
 . . . . . . . . . . . 14</div>
<div>=A0 =A0</div><div>=A0&gt; OK, some suggestions on how to clean this se=
ction up.</div><div>=A0&gt;</div><div>=A0&gt; Introduce the 4 extension par=
ameters first.</div><div>=A0&gt;</div><div>=A0&gt; =A0 Use the language fou=
nd elsewhere in the spec now about the asymmetric=A0</div>





<div>=A0&gt; =A0 nature of the extension parameter configuration.</div><div=
>=A0&gt; =A0=A0</div><div>=A0&gt; =A0 The following 2 extension parameters =
control the behavior of the</div><div>=A0&gt; =A0 deflate configuration for=
 Client-to-Server messages:</div>





<div>=A0&gt; =A0 (We took this notation from the title of [Section 5.3] of =
[RFC-6455],</div><div>=A0&gt; =A0 =A0including the capitalization)</div><di=
v>=A0&gt;</div><div>=A0&gt; =A0 =A0 o =A0&quot;c2s_no_context_takeover&quot=
;</div><div>=A0&gt; =A0 =A0 o =A0&quot;c2s_max_window_bits&quot;</div>





<div>=A0&gt;</div><div>=A0&gt; =A0 The following 2 extension parameters con=
trol the behavior of the</div><div>=A0&gt; =A0 deflate configuration for Se=
rver-to-Client messages:</div><div>=A0&gt;</div><div>=A0&gt; =A0 =A0 o =A0&=
quot;s2c_no_context_takeover&quot;</div>





<div>=A0&gt; =A0 =A0 o =A0&quot;s2c_max_window_bits&quot;</div><div>=A0&gt;=
</div><div>=A0&gt; Then describe how the Offer works. (essentially the lang=
uage you</div><div>=A0&gt; have now in the doc, with careful attention to n=
ot mix your intro</div>





<div>=A0&gt; and then bullets)</div></div></blockquote></div></div></div></=
div></div></blockquote><div>done</div><div>=A0</div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex">


<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div=
><div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:s=
olid;padding-left:1ex">


<div dir=3D"ltr"><div>=A0&gt; =A0 =A0Request: desired client behavior + des=
ired server behavior</div><div>=A0&gt; =A0 =A0Response: acknowledge client =
behavior + server chosen behavior</div><div>=A0&gt;</div><div>=A0&gt; Examp=
le of confusing language:</div>





<div>=A0</div><div>=A0 =A0For an offer for this extension, the following 4 =
extension parameters</div><div>=A0 =A0are defined. =A0If needed to distingu=
ish from ones for a response,</div><div>=A0 =A0these parameters are called =
with a prefix &quot;client-to-server&quot;.</div>





<div><br></div><div>=A0 =A0o =A0&quot;s2c_no_context_takeover&quot;</div><d=
iv><br></div><div>=A0 =A0o =A0&quot;c2s_no_context_takeover&quot;</div><div=
><br></div><div>=A0 =A0o =A0&quot;s2c_max_window_bits&quot;</div><div><br><=
/div><div>=A0 =A0o =A0&quot;c2s_max_window_bits&quot;</div>





<div>=A0 =A0</div><div>=A0&gt; This section introduces you to &quot;client-=
to-server&quot;, then lists</div><div>=A0&gt; s2c_*, why? =A0Same for the n=
ext section, but in reverse.</div><div>=A0&gt; Don&#39;t mix the introducti=
on of the extension parameters and</div>





<div>=A0&gt; the behavior of the request and response together.</div><div>=
=A0&gt;</div><div>=A0&gt; Finally, go into the MUST rules for Client and Se=
rver like you</div><div>=A0&gt; currently have in the spec documentation.</=
div>


</div></blockquote></div></div></div></div></div></blockquote><div><br></di=
v><div>done</div><div><br></div><div>used Peter&#39;s texts.</div><div>=A0<=
/div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex">


<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div=
><div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:s=
olid;padding-left:1ex">


<div dir=3D"ltr">

<div>
=A0&gt;</div><div>=A0&gt; Include wording for Client MUST pointing back to =
close code</div><div>=A0&gt; 1010 from [RC6455] as a recommended behavior f=
or dealing with</div><div>=A0&gt; bad extension negotiation.</div><div>=A0&=
gt; Even for things like a server saying s2c_max_window_bits=3D1024</div>





<div>=A0 =A0</div></div></blockquote><div><br></div></div></div></div></div=
></div></blockquote><div>replied in another post.</div><div>=A0</div><block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex">


<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div=
><div><div></div></div></div><div><div>=A0</div><blockquote class=3D"gmail_=
quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-=
color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">




<div dir=3D"ltr"><div>=A0 =A0 =A08.1. =A0Method Parameters =A0. . . . . . .=
 . . . . . . . . . . . . . 15</div><div>=A0 =A0 =A0 =A08.1.1. =A0Context Ta=
keover Control . . . . . . . . . . . . . . . 15</div><div>=A0 =A0 =A0 =A0</=
div><div>=A0&gt; Include explicit language indicating default behavior for<=
/div>





<div>=A0&gt; context takeover.</div><div></div></div></blockquote></div></d=
iv></div></div></blockquote><div><br></div><div>done</div><div>=A0</div><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex">


<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;=
padding-left:1ex">


<div dir=3D"ltr"><div>=A0</div><div>=A0&gt; When documenting one side, for =
example &quot;s2c_&quot;, do not make references</div><div>=A0&gt; to the o=
pposite direction. =A0Its confusing, noisy, and adds no value.</div>


<div>=A0&gt;</div><div></div></div></blockquote></div></div></div></div></b=
lockquote><div><br></div><div>done. removed &quot;in the same ...&quot; sen=
tences</div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">


<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;=
padding-left:1ex">


<div dir=3D"ltr"><div>=A0&gt; For example, Section 8.1.2.2. c2s_max_window_=
bits, start out talking</div><div>=A0&gt; about the c2s_max_window_bits, th=
en has suddenly talks about=A0</div><div>=A0&gt; &quot;server-to-client par=
ameter&quot;, mentioning behavior and server limits.</div>





<div>=A0&gt; This is confusing.</div><div>=A0&gt; Fix this, clarify it, eli=
minate the noise, or simplify it.</div><div>=A0&gt;</div><div>=A0&gt; Eg of=
 simplification:</div><div>=A0&gt;</div><div>=A0&gt; =A0See [Section 8.1.2.=
1.] &quot;s2c_max_window_bits&quot; for server side</div>





<div>=A0&gt; =A0equivalent</div><div>=A0&gt;</div><div>=A0&gt; We suspect t=
hat the use of &quot;c2s&quot; and &quot;client-to-server&quot; to=A0</div>=
<div>=A0&gt; interchangably refer to either the &quot;extension parameter t=
oken&quot; itself=A0</div>





<div>=A0&gt; or the phase of the extension negotiation (request or response=
) is</div><div>=A0&gt; the cause of the confusion.</div><div>=A0&gt;=A0</di=
v><div>=A0&gt; Either choose new terminology for the extension parameter to=
ken, or=A0</div>





<div>=A0&gt; choose new terminology for the phase of the extension negotiat=
ion</div><div>=A0&gt; (request side or response side)</div><div>=A0&gt;</di=
v></div></blockquote><div><br></div></div><div>[TBA]</div></div></div></div=
>


</blockquote><div><br></div><div>done i think...</div><div>=A0</div><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra"><div cl=
ass=3D"gmail_quote">


<div><div>=A0</div></div></div></div></div></blockquote></div></div></div>

--001a11c347e07ee28004e8d81e35--

From tyoshino@google.com  Wed Oct 16 02:14:09 2013
Return-Path: <tyoshino@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA07611E82BA for <hybi@ietfa.amsl.com>; Wed, 16 Oct 2013 02:14:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.905
X-Spam-Level: 
X-Spam-Status: No, score=-1.905 tagged_above=-999 required=5 tests=[AWL=0.072,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 16f4LHtAB5Kg for <hybi@ietfa.amsl.com>; Wed, 16 Oct 2013 02:14:09 -0700 (PDT)
Received: from mail-wi0-x22e.google.com (mail-wi0-x22e.google.com [IPv6:2a00:1450:400c:c05::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 428FA11E8267 for <hybi@ietf.org>; Wed, 16 Oct 2013 02:14:06 -0700 (PDT)
Received: by mail-wi0-f174.google.com with SMTP id cb5so6329655wib.1 for <hybi@ietf.org>; Wed, 16 Oct 2013 02:14:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=7P9j/vILtf3T0ZlkqysY0luA5ijMlyVUJ7l94eZ0Ndk=; b=PhIzSgjDBfDxg12cgEh3pmTHqK5WK+o5R0AvcXf0jP9qBIGYeQFRMtJpfdm28T/Vkb dARzrNG5wbaDvh4DLFyEW9IbkO/+ILAD/OhW04k0zjoKYGyGS7F1uybMDs9RCbvFlZmx NcxVZY+1vG4I/zmeDa5PIVKJODD8BY7WH5+WiLgRvTSAeg4RztiK3mC3gzB761LSab6E 3d6n0r+jVEVHvF/WeQuv2RyI3e8F7Sucp1UuNw88KXbYPIh6vI9UfTL9OuurYB62V+92 jHQzullMERzDlo/BqAalmA5ke2DReEmk5kW/qf1aT9aomGLvtHKybXAU9lBpMwuy/h6k OEQg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=7P9j/vILtf3T0ZlkqysY0luA5ijMlyVUJ7l94eZ0Ndk=; b=DS+ygL/xnfUq0nfIaZPOdfgz+pKPGjVGmyMwnZAQctLqhZYYsTmGvGCm8/uKyNaBVt aRtQ8L2RL+7AEMdeIfd2m3/sMcDaVSe4UHQU26t1ysA4QvXP/BA69t+RavZJ+A8df+na iEaNiH2kpZyBx6DcfpjPR2ZubaT3eO5874VaG7Zfjndx56F8BwnkHFO0K4vcZZJwW6B1 Lq9HkLe6SJuMnxrjQ3vEDOvjbvZxd8ffErCKcZzQQezJZuIydl+futbRamtIrNjPX/m+ oRQA3xFgkQgzEtWCo5IagglZnqYApfVG7Adk1PRMJzMNcvURQqR7sBJD6JX4D/AMlNir SlPA==
X-Gm-Message-State: ALoCoQnAocEC5+jeIL20oRE1P4K6bqGNLQBr34ik8hKjfTW4ZW02ddtJejqNAt+nDBpnrqmpLiblXw/Wc6Z0oYrLaLMNBNikOua2giFjpByKCms5yk9QRct8b3p26UxKIcAngPDLaqE+e2v8Sdd9vCgf7loGJHkq9HeM8WtU/RrLxyMAQTdd8IjE0CODfsqfkJflB1bwHb/t
X-Received: by 10.180.188.197 with SMTP id gc5mr23210503wic.42.1381914845306;  Wed, 16 Oct 2013 02:14:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.15.133 with HTTP; Wed, 16 Oct 2013 02:13:45 -0700 (PDT)
In-Reply-To: <CAG4zZZDtUEnvgPmcKWsE9mFockUYA0PDFUE1SxNr+ubN0v9=xg@mail.gmail.com>
References: <CAH9hSJant3VBw0FBM69V9wPvi3WmJLikZdX4ySELy+CShgoOKA@mail.gmail.com> <5BEA69BA-D0D4-4F4A-8CFB-741A433EAAA6@zaphoyd.com> <CAH9hSJYNrBkf=2=2DHdipvXwN4XEKDe2BOc4g1eZr38U7m7jdw@mail.gmail.com> <CAG4zZZDtUEnvgPmcKWsE9mFockUYA0PDFUE1SxNr+ubN0v9=xg@mail.gmail.com>
From: Takeshi Yoshino <tyoshino@google.com>
Date: Wed, 16 Oct 2013 18:13:45 +0900
Message-ID: <CAH9hSJZqR6L8fWTN_p915atXniuAbh-Nxb6FnPapoVwpdY3bAg@mail.gmail.com>
To: Joakim Erdfelt <joakim@intalio.com>
Content-Type: multipart/alternative; boundary=001a11c3841a77051204e8d81fb7
Cc: "hybi@ietf.org" <hybi@ietf.org>, Peter Thorson <webmaster@zaphoyd.com>
Subject: Re: [hybi] [permessage-deflate] Renaming s2c_ and c2s_ prefix to server_ and client_
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 16 Oct 2013 09:14:10 -0000

--001a11c3841a77051204e8d81fb7
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Oct 16, 2013 at 12:13 AM, Joakim Erdfelt <joakim@intalio.com> wrote:

> We start by talking of "c2s_" then half way through the first paragraph we
> start talking about "server-to-client" and even point out the "c2s_"
> parameter as an example of the "server-to-client".
>
> The spec mixes the use of "c2s" and "client-to-server" in various places,
> in what we can only assume is sometimes it refers the parameter, sometimes
> it refers to the direction of the conversation, sometimes it refers to the
> extension negotiation step, sometimes it refers to the extension
> negotiation phase.
>

Makes sense.


>
> Months have been spent trying to decipher this spec by multiple people
> with years of experience on ietf specs, both as consumers and participants.
>  the spec should be able to sit on its own, with as clear of definition as
> possible at the time, reducing as much of the "interpretation" and question
> asking that will arise from the spec.
>
> The "2s" and "2c" portions are irrelevant, and actually cause confusion as
> you use the same language elsewhere.
>
> proposal:
>
> "c2s_" used in extension-param tokens should be "client_" to refer to
> "client produced compression"
> "s2c_" used in extension-param tokens should be "server_" to refer to
> "server produced compression"
>
>
Hmm. The key here is the fact that compression is made only on traffic
after connection establishment. That may clarifies things. Only
client-produced and server-produced are still with ambiguity. Server and
client do produce extension parameters. Client_transmitted,
Client_outgoing, Client_egress, ... I think this applies to any of them.

As there's no strong opinion to keep c2s_ and s2c_, I've renamed them to
server_ and client_.


> "client-to-server", and "server-to-client" use within spec should be
> clarified, and never be left without a clarification.
>    when referring to the extension negotiation request phase.
>       consider "extension negotiation request" or "extension negotiation
> offer" for current "client-to-server" use
>       consider "extension negotiation response" or "extension negotiation
> accept" for current "server-to-client" use.
>

Good point. I put these for clarification but they lead to confusions. I
understand. Thanks.


>    when referring to the flow of frames on a connected websocket.
>       this is where the existing "Client-to-Server" terminology is
> consistent with RFC6455 (see Section 5.3<http://tools.ietf.org/html/rfc6455#section-5.3>
> ).
>       so feel free to start using for "Server-to-Client" here as well, but
> not in the above.
>
>
Makes sense! Done.


> another choice is to never leave "Client-to-Server" alone with no
> clarification, always follow it with consistent verbiage, like RFC6455 does.
>
> Its never "Client-to-Server" just to refer to a directionality, its a
> compound concept, such as "Client-to-Server Masking" or "Client-to-Server
> message".
>
> Suspicions/Theories:
>
> The language choices of this spec probably come from the overall attempt
> at being neutral to what side (client or server) the spec is documenting
> from.
> If you look at the overall language of RFC6455, you see that it is
> presented from the point of view of the Client, with the Server roles and
> responsibilities being explained only when needed to.  Otherwise, both
> sides are assumed to be the same in behavior.
> If RFC6455 used the same techniques as the permessage-deflate spec, then
> you'd have 2 sections: Client, fully documented with barely a mention of
> server, then Server, fully documented we barely a mention of client.
>
>
I see, yeah. It must be the source of complexity.


>
> Permessage-deflate could have been documented the same way as RFC6455, but
> it isn't, so now you have extra work to be careful in your language
> choices, eliminate ambiguity, make things more clear.
>
>
> Our the final translation of the permessage-deflate extension spec, as
> written:
>
> Simplified Neutral Language:
> Incoming frames/messages are compressed when RSV1 is set
> Outgoing frames/messages can be compressed, but set RSV1 if you do.
> Configuration of Incoming frames/messages compression is controlled by
> Extension Parameters for the opposite side of yourself.
> Configuration of Outgoing frames/messages compression is controlled by
> Extension Parameters for your side.
>
> Side Specific Language:
> client_* Extension Parameters are for controlling frames/messages
> compression produced by client
> server_* Extension Parameters are for controlling frames/messages
> compression produced by server
>
>
Refined. Please take a look again.


> Here's the example of same Section 8.1.2.2 with the proposed change:
> (quick edit)
>
>
Thanks for providing an example. I believe the new text addressed all of
the edit you made in the same or a bit different way.

--001a11c3841a77051204e8d81fb7
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra">On Wed, Oct 16, 2013 at 12:13 A=
M, Joakim Erdfelt <span dir=3D"ltr">&lt;<a href=3D"mailto:joakim@intalio.co=
m" target=3D"_blank">joakim@intalio.com</a>&gt;</span> wrote:<br><div class=
=3D"gmail_quote">


<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>We start by talking of=
 &quot;c2s_&quot; then half way through the first paragraph we start talkin=
g about &quot;server-to-client&quot; and even point out the &quot;c2s_&quot=
; parameter as an example of the &quot;server-to-client&quot;.<br>


</div>
<div><br></div><div>The spec mixes the use of &quot;c2s&quot; and &quot;cli=
ent-to-server&quot; in various places, in what we can only assume is someti=
mes it refers the parameter, sometimes it refers to the direction of the co=
nversation, sometimes it refers to the extension negotiation step, sometime=
s it refers to the extension negotiation phase.</div>


</div></blockquote><div><br></div><div>Makes sense.</div><div>=A0</div><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex"><div dir=3D"ltr">
<div><br></div><div>Months have been spent trying to decipher this spec by =
multiple people with years of experience on ietf specs, both as consumers a=
nd participants. =A0the spec should be able to sit on its own, with as clea=
r of definition as possible at the time, reducing as much of the &quot;inte=
rpretation&quot; and question asking that will arise from the spec.<br>



</div><div><br></div><div>The &quot;2s&quot; and &quot;2c&quot; portions ar=
e irrelevant, and actually cause confusion as you use the same language els=
ewhere.</div><div><br></div><div>proposal:</div><div><br></div><div>&quot;c=
2s_&quot; used in extension-param tokens should be &quot;client_&quot; to r=
efer to &quot;client produced compression&quot;</div>



<div>&quot;s2c_&quot; used in extension-param tokens should be &quot;server=
_&quot; to refer to &quot;server produced compression&quot;</div><div><br><=
/div></div></blockquote><div><br></div><div>Hmm. The key here is the fact t=
hat compression is made only on traffic after connection establishment. Tha=
t may clarifies things. Only client-produced and server-produced are still =
with ambiguity. Server and client do produce extension parameters. Client_t=
ransmitted, Client_outgoing, Client_egress, ... I think this applies to any=
 of them.</div>


<div><br></div><div>As there&#39;s no strong opinion to keep c2s_ and s2c_,=
 I&#39;ve renamed them to server_ and client_.</div><div>=A0</div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex">


<div dir=3D"ltr"><div></div><div>&quot;client-to-server&quot;, and &quot;se=
rver-to-client&quot; use within spec should be clarified, and never be left=
 without a clarification.</div>
<div>=A0 =A0when referring to the extension negotiation request phase.</div=
><div>=A0 =A0 =A0 consider &quot;extension negotiation request&quot; or &qu=
ot;extension negotiation offer&quot; for current &quot;client-to-server&quo=
t; use</div>



<div>=A0 =A0 =A0 consider &quot;extension negotiation response&quot; or &qu=
ot;extension negotiation accept&quot; for current &quot;server-to-client&qu=
ot; use.</div></div></blockquote><div><br></div><div>Good point. I put thes=
e for clarification but they lead to confusions. I understand. Thanks.</div=
>


<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>=A0 =A0w=
hen referring to the flow of frames on a connected websocket.</div>
<div>=A0 =A0 =A0 this is where the existing &quot;Client-to-Server&quot; te=
rminology is consistent with RFC6455 (see <a href=3D"http://tools.ietf.org/=
html/rfc6455#section-5.3" target=3D"_blank">Section 5.3</a>).</div><div>=A0=
 =A0 =A0 so feel free to start using for &quot;Server-to-Client&quot; here =
as well, but not in the above.</div>



<div><br></div></div></blockquote><div><br></div><div>Makes sense! Done.</d=
iv><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div></div=
><div>


another choice is to never leave &quot;Client-to-Server&quot; alone with no=
 clarification, always follow it with consistent verbiage, like RFC6455 doe=
s.</div><div><br></div><div>Its never &quot;Client-to-Server&quot; just to =
refer to a directionality, its a compound concept, such as &quot;Client-to-=
Server Masking&quot; or &quot;Client-to-Server message&quot;.</div>



<div><br></div><div>Suspicions/Theories:</div><blockquote style=3D"margin:0=
 0 0 40px;border:none;padding:0px"><div>The language choices of this spec p=
robably come from the overall attempt at being neutral to what side (client=
 or server) the spec is documenting from.</div>



<div>If you look at the overall language of RFC6455, you see that it is pre=
sented from the point of view of the Client, with the Server roles and resp=
onsibilities being explained only when needed to. =A0Otherwise, both sides =
are assumed to be the same in behavior.=A0</div>



<div>If RFC6455 used the same techniques as the permessage-deflate spec, th=
en you&#39;d have 2 sections: Client, fully documented with barely a mentio=
n of server, then Server, fully documented we barely a mention of client.</=
div>


</blockquote></div></blockquote><div><br></div><div>I see, yeah. It must be=
 the source of complexity.</div><div>=A0</div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
">


<div dir=3D"ltr"><blockquote style=3D"margin:0 0 0 40px;border:none;padding=
:0px">
<div><br></div><div>Permessage-deflate could have been documented the same =
way as RFC6455, but it isn&#39;t, so now you have extra work to be careful =
in your language choices, eliminate ambiguity, make things more clear.</div=
>



</blockquote><div><br></div><div>Our the final translation of the permessag=
e-deflate extension spec, as written:</div><div><br></div><div>Simplified N=
eutral Language:</div><div>Incoming=A0frames/messages=A0are compressed when=
 RSV1 is set</div>



<div>Outgoing=A0frames/messages=A0can be compressed, but set RSV1 if you do=
.</div><div>Configuration of Incoming=A0frames/messages=A0compression is co=
ntrolled by Extension Parameters for the opposite side of yourself.</div><d=
iv>


Configuration of Outgoing=A0frames/messages=A0compression is controlled by =
Extension Parameters for your side.</div>
<div><br></div><div>Side Specific Language:</div><div>client_* Extension Pa=
rameters are for controlling frames/messages compression produced by client=
</div><div>server_* Extension Parameters are for controlling frames/message=
s compression produced by server</div>



<div><br></div></div></blockquote><div><br></div><div>Refined. Please take =
a look again.</div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D=
"ltr">


<div></div><div>Here&#39;s the example of same Section 8.1.2.2 with the pro=
posed change: (quick edit)</div><div><br></div></div></blockquote><div><br>=
</div><div>Thanks for providing an example. I believe the new text addresse=
d all of the edit you made in the same or a bit different way.</div>


<div><br></div></div></div></div>

--001a11c3841a77051204e8d81fb7--

From tyoshino@google.com  Wed Oct 16 02:14:55 2013
Return-Path: <tyoshino@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D5CA11E82B9 for <hybi@ietfa.amsl.com>; Wed, 16 Oct 2013 02:14:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.263
X-Spam-Level: 
X-Spam-Status: No, score=-1.263 tagged_above=-999 required=5 tests=[AWL=-0.578, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MISSING_HEADERS=1.292, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bVPEseUdlBvs for <hybi@ietfa.amsl.com>; Wed, 16 Oct 2013 02:14:54 -0700 (PDT)
Received: from mail-wi0-x233.google.com (mail-wi0-x233.google.com [IPv6:2a00:1450:400c:c05::233]) by ietfa.amsl.com (Postfix) with ESMTP id BBACE21F9CE8 for <hybi@ietf.org>; Wed, 16 Oct 2013 02:14:49 -0700 (PDT)
Received: by mail-wi0-f179.google.com with SMTP id hm4so413856wib.12 for <hybi@ietf.org>; Wed, 16 Oct 2013 02:14:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:cc :content-type; bh=D8fCz6A5YGpAsSA0ctKYgIYSMdkfgpe87ywWIa7fQSE=; b=km3TDCvwYykwrt8+eoJPlfoDZ4D9YbkIR8Ca98a42g/ccCxLU+AIxlvfi4vbXhSpv4 oFXSfPVdYKyTVLhlVzl/pim461AC3hLrSmiAwP0+c9VzCuo51VrL4Zco49AYq46tcZyc Cnmv8zu4O8zwq2tfsQsWWv4kGsDtkoDbImUr1DNKz/j3QbbLt6eXbDPSf9jjTzL8MKCJ zB7hc92munUJJvUlCLj/YQMYplsiX1LtWMuYxiZymDYsD9c8HBRWl6CsTshQTJ+oRaao gQCvOyRzPAj8AECxZUqd8TyD5KJE1lud00HHRRlMBPrbC2hL7ZUGq805R5WBTCF299d6 03Hg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:cc:content-type; bh=D8fCz6A5YGpAsSA0ctKYgIYSMdkfgpe87ywWIa7fQSE=; b=HT5nPS9b+z3lbq0d0HjH+eLnTTvaGD0s04VMX63Z3lE8SJj80FGrQyVMjg/n157VYO nBZQHCL9DjYo3MviXlmAiVbLJ+MaDXkl8w0z/vIAvPATGirvvYiQDlxX7HG0eQnq7yng MtEr/nYGU8i7PsR5h0zPup+LMa+gWPCz4ISLBTwAqosI9jInzHiPjPWsx6eXUyxfWFuI wotqNW6Dgk3k4hFjK5NG0rDCyLKlMOsBMBV2GvvFFx+md4Fgg1pC70BGXCyqg5bxJY1A uofRbMz5ZPJR7hIucyAoQuun3Dac9PLj+t0qXVm3SJzMtIGD6FcFRRbC9e3zZkY+puvh b/ZA==
X-Gm-Message-State: ALoCoQmrBhHK8fQYNn6y2HaZo5o1aKRqXHFCmDL9k3WbcsCq1+Sa5s5fjJ9AJJ901vUcETKBn7n4xxc6/ZXgRQESjhow5+Ct/UPJWGkqt/SvlmMpl8+AhbjNmSQe6F4pHw8ePnIMgK/UwNtopWySD8mMQ2qg5F+tpN23prvpGlcWf44t61A3n56NGcyf1TX5cKkGQ/YK5teT
X-Received: by 10.180.99.99 with SMTP id ep3mr1374638wib.11.1381914888906; Wed, 16 Oct 2013 02:14:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.15.133 with HTTP; Wed, 16 Oct 2013 02:14:28 -0700 (PDT)
In-Reply-To: <20131016091101.32139.80378.idtracker@ietfa.amsl.com>
References: <20131016091101.32139.80378.idtracker@ietfa.amsl.com>
From: Takeshi Yoshino <tyoshino@google.com>
Date: Wed, 16 Oct 2013 18:14:28 +0900
Message-ID: <CAH9hSJYwfHqMRP2cbbZUPutAwx4GSLnfCNZVyKGNTM2MdsTxPw@mail.gmail.com>
Cc: "hybi@ietf.org" <hybi@ietf.org>
Content-Type: multipart/alternative; boundary=f46d044283c01045a004e8d82224
Subject: Re: [hybi] I-D Action: draft-ietf-hybi-permessage-compression-15.txt
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 16 Oct 2013 09:14:55 -0000

--f46d044283c01045a004e8d82224
Content-Type: text/plain; charset=ISO-8859-1

Addressed Joakim's suggestions.

s2c_ and c2s_ prefix are renamed to server_ and client_ respectively.

Takeshi


On Wed, Oct 16, 2013 at 6:11 PM, <internet-drafts@ietf.org> wrote:

>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>  This draft is a work item of the BiDirectional or Server-Initiated HTTP
> Working Group of the IETF.
>
>         Title           : Compression Extensions for WebSocket
>         Author(s)       : Takeshi Yoshino
>         Filename        : draft-ietf-hybi-permessage-compression-15.txt
>         Pages           : 32
>         Date            : 2013-10-16
>
> Abstract:
>    This document specifies 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 non-control WebSocket messages on a per-message basis using
>    parameters negotiated during the opening handshake.  This framework
>    provides a general method to apply a compression algorithm to the
>    contents of WebSocket messages.  For each compression algorithm, an
>    extension is defined by specifying parameter negotiation and
>    compression algorithm in detail.  This document also specifies one
>    specific compression extension using the DEFLATE algorithm.
>
>    Please send feedback to the hybi@ietf.org mailing list.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-hybi-permessage-compression
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-hybi-permessage-compression-15
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-hybi-permessage-compression-15
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi
>

--f46d044283c01045a004e8d82224
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Addressed Joakim&#39;s suggestions.<br></div><div><br=
></div><div>s2c_ and c2s_ prefix are renamed to server_ and client_ respect=
ively.</div></div><div class=3D"gmail_extra"><br clear=3D"all"><div>Takeshi=
</div>


<br><br><div class=3D"gmail_quote">On Wed, Oct 16, 2013 at 6:11 PM,  <span =
dir=3D"ltr">&lt;<a href=3D"mailto:internet-drafts@ietf.org" target=3D"_blan=
k">internet-drafts@ietf.org</a>&gt;</span> wrote:<br><blockquote class=3D"g=
mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex">

<br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
=A0This draft is a work item of the BiDirectional or Server-Initiated HTTP =
Working Group of the IETF.<br>
<br>
=A0 =A0 =A0 =A0 Title =A0 =A0 =A0 =A0 =A0 : Compression Extensions for WebS=
ocket<br>
=A0 =A0 =A0 =A0 Author(s) =A0 =A0 =A0 : Takeshi Yoshino<br>
=A0 =A0 =A0 =A0 Filename =A0 =A0 =A0 =A0: draft-ietf-hybi-permessage-compre=
ssion-15.txt<br>
=A0 =A0 =A0 =A0 Pages =A0 =A0 =A0 =A0 =A0 : 32<br>
=A0 =A0 =A0 =A0 Date =A0 =A0 =A0 =A0 =A0 =A0: 2013-10-16<br>
<br>
Abstract:<br>
=A0 =A0This document specifies a framework for creating WebSocket extension=
s<br>
=A0 =A0that add compression functionality to the WebSocket Protocol. =A0An<=
br>
=A0 =A0extension based on this framework compresses the payload data portio=
n<br>
=A0 =A0of non-control WebSocket messages on a per-message basis using<br>
=A0 =A0parameters negotiated during the opening handshake. =A0This framewor=
k<br>
=A0 =A0provides a general method to apply a compression algorithm to the<br=
>
=A0 =A0contents of WebSocket messages. =A0For each compression algorithm, a=
n<br>
=A0 =A0extension is defined by specifying parameter negotiation and<br>
=A0 =A0compression algorithm in detail. =A0This document also specifies one=
<br>
=A0 =A0specific compression extension using the DEFLATE algorithm.<br>
<br>
=A0 =A0Please send feedback to the <a href=3D"mailto:hybi@ietf.org">hybi@ie=
tf.org</a> mailing list.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-hybi-permessage-comp=
ression" target=3D"_blank">https://datatracker.ietf.org/doc/draft-ietf-hybi=
-permessage-compression</a><br>
<br>
There&#39;s also a htmlized version available at:<br>
<a href=3D"http://tools.ietf.org/html/draft-ietf-hybi-permessage-compressio=
n-15" target=3D"_blank">http://tools.ietf.org/html/draft-ietf-hybi-permessa=
ge-compression-15</a><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-hybi-permessage-co=
mpression-15" target=3D"_blank">http://www.ietf.org/rfcdiff?url2=3Ddraft-ie=
tf-hybi-permessage-compression-15</a><br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" target=3D"_blank">ftp://ftp=
.ietf.org/internet-drafts/</a><br>
<br>
_______________________________________________<br>
hybi mailing list<br>
<a href=3D"mailto:hybi@ietf.org">hybi@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/hybi" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/hybi</a><br>
</blockquote></div><br></div>

--f46d044283c01045a004e8d82224--

From tyoshino@google.com  Wed Oct 16 02:19:46 2013
Return-Path: <tyoshino@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07C3111E8267 for <hybi@ietfa.amsl.com>; Wed, 16 Oct 2013 02:19:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.88
X-Spam-Level: 
X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[AWL=0.097,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8WJ5Sx+vdAwO for <hybi@ietfa.amsl.com>; Wed, 16 Oct 2013 02:19:44 -0700 (PDT)
Received: from mail-wi0-x231.google.com (mail-wi0-x231.google.com [IPv6:2a00:1450:400c:c05::231]) by ietfa.amsl.com (Postfix) with ESMTP id F37A911E8169 for <hybi@ietf.org>; Wed, 16 Oct 2013 02:19:43 -0700 (PDT)
Received: by mail-wi0-f177.google.com with SMTP id h11so421612wiv.16 for <hybi@ietf.org>; Wed, 16 Oct 2013 02:19:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=GEZrI9qh9aqU62IiYMCvXsOpcSvtazbzSpn7MB8hnP0=; b=GpJ+d0MUylnHzGd++WZZhrI0SMVneO8efVHNlyFOMXO95Zam/fpPJl1bW6ALxTAFvV 1pKP7fewxK6nibeFrXt+TcxtYCHIPYXL6Sfw82XhDfkyBEMljqJRgyBpx7PT4d90+39F 7AI2GHaKqcym3+DOvtPd3UOsZLH46nxO0tKmLSHDnzXESd14cnGluWgoW/tlfHhKqpoS itjdapsmWCAJgBpUShiRlinJJw27aDyxnqp1r6vgcD8Z9333LnHouThyKawI/yPUn9Ql F1iXBiziI21tXntlCoTuQorYf3WKdMe+k3y+GnwtGr0kGhNNSStTpLQc7QIV5gQm+bbS 9IoQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=GEZrI9qh9aqU62IiYMCvXsOpcSvtazbzSpn7MB8hnP0=; b=SV+NSrEzqWlbaWqKF0eFbosiiOiqo3XWUrVyCUvvbK8TtP5cIEKsV8n8uR1dafCmY4 mkgaSxZ1WAl91pZ2VUs82doKdeV7iB+3hT/FAA7PgL4B3/Vj6KgtfL/Dc+GUOqdA40/C K1bl3xgPrBZ5mbhPznyzyvefj4yJJyPQymnJm4nfL2Vgi+PmIR/+OS/CtwZepS8xA7Xt 5idH4Hinbz9Ar6ctQfQAUwlHu+CHd1nepYtOX7dUcwXgHbXRYq2dTAlr8peB+xVnbQTW GupDNrDvRzGygBlgUKv7Y6ArcNMkgp+eS7JYi/h3GhYAOmd43KskKv471TgwZQaiiS1N tN9A==
X-Gm-Message-State: ALoCoQlayAdfpZXi5IGmEWbxyrbeJlSZCwZ37d4p9kyzz/lj20ndVosPPiOx08XNGFNFqjowL7tcwsifF0xmZAGVyV1SE2RfIrkKCMLN6rz6CplutSApY3L23qtF3QPuDHILoOq4DxGJu7/0eNxJlUpEclivVfXX/j5WQeGY77OnEafYysEV0CjPgIlfEgtBZMqQnsFIGEOZ
X-Received: by 10.180.99.99 with SMTP id ep3mr1393129wib.11.1381915183154; Wed, 16 Oct 2013 02:19:43 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.15.133 with HTTP; Wed, 16 Oct 2013 02:19:23 -0700 (PDT)
In-Reply-To: <CAH9hSJZqR6L8fWTN_p915atXniuAbh-Nxb6FnPapoVwpdY3bAg@mail.gmail.com>
References: <CAH9hSJant3VBw0FBM69V9wPvi3WmJLikZdX4ySELy+CShgoOKA@mail.gmail.com> <5BEA69BA-D0D4-4F4A-8CFB-741A433EAAA6@zaphoyd.com> <CAH9hSJYNrBkf=2=2DHdipvXwN4XEKDe2BOc4g1eZr38U7m7jdw@mail.gmail.com> <CAG4zZZDtUEnvgPmcKWsE9mFockUYA0PDFUE1SxNr+ubN0v9=xg@mail.gmail.com> <CAH9hSJZqR6L8fWTN_p915atXniuAbh-Nxb6FnPapoVwpdY3bAg@mail.gmail.com>
From: Takeshi Yoshino <tyoshino@google.com>
Date: Wed, 16 Oct 2013 18:19:23 +0900
Message-ID: <CAH9hSJY-=jti+AVPZjVJCpN9zTDTFpgbM_2WSQfnQYj-or9cgg@mail.gmail.com>
To: "hybi@ietf.org" <hybi@ietf.org>
Content-Type: multipart/alternative; boundary=f46d044283c09a1b0a04e8d833d5
Subject: Re: [hybi] [permessage-deflate] Renaming s2c_ and c2s_ prefix to server_ and client_
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 16 Oct 2013 09:19:46 -0000

--f46d044283c09a1b0a04e8d833d5
Content-Type: text/plain; charset=ISO-8859-1

Decision: rename to server_ and client_

Published -15. Please take a look.

With Chrome developer hat: We'll try to turn on permessage-deflate with the
new parameter naming on Chrome by default soon unless we see any objection
to the renaming with reasonable justification.

Thanks.

--f46d044283c09a1b0a04e8d833d5
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Decision: rename to server_ and client_<div><br></div><div=
>Published -15. Please take a look.</div><div><br></div><div>With Chrome de=
veloper hat: We&#39;ll try to turn on permessage-deflate with the new param=
eter naming on Chrome by default soon unless we see any objection to the re=
naming with reasonable justification.</div>

<div><br></div><div>Thanks.</div><div><br></div></div>

--f46d044283c09a1b0a04e8d833d5--

From ricea@google.com  Wed Oct 16 23:53:40 2013
Return-Path: <ricea@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 340C411E80FA for <hybi@ietfa.amsl.com>; Wed, 16 Oct 2013 23:53:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KDGOs1dkNQAB for <hybi@ietfa.amsl.com>; Wed, 16 Oct 2013 23:53:39 -0700 (PDT)
Received: from mail-oa0-x22c.google.com (mail-oa0-x22c.google.com [IPv6:2607:f8b0:4003:c02::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 4F13611E80E6 for <hybi@ietf.org>; Wed, 16 Oct 2013 23:53:36 -0700 (PDT)
Received: by mail-oa0-f44.google.com with SMTP id l20so1356426oag.17 for <hybi@ietf.org>; Wed, 16 Oct 2013 23:53:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=QhK+cM7EIPXaSqF5qRiBc6Q3xMsF1JmFl+61/EaFCH8=; b=GlFB054ccyXPb45paO0BNFvUGtPnZgkMeymVCJkPLM4DFcOhXlsTFJHTTqcJ5eJR8V iSjnRp8bIkEI+XF8DWepgdxqAsBueZ03TJ682AL5HTBGUSPzOl7hWDV51WcDE4Pt/EQ8 O06VkRpxyxCPDiEvMn8IVW/9qqLk3iWdm5Z6rwvPFByEwVECK9fCCy262GvsAoGz01Tp wpejrb0COfIOONDaCNAdW/eWCJKtXfpwkuHNCd2nl7scjK0AxQARIyOE0akD7iENkVSZ Mz+9jhpQb2N0pHP6tspVr2GZ3GFDNW5Ji1BJ+R8gbo1Gf6YXMTSc4WyNz/AlLBm8eOfT 0y3A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=QhK+cM7EIPXaSqF5qRiBc6Q3xMsF1JmFl+61/EaFCH8=; b=awqyj3TvSm/SQCsU6eZm+efdqVFty4OpYx6I6pMZ2YMjamtTfh02YmpcaJKqP4vOA8 ffTLdSQBQoMmYwgGn2tesJZ/F3JY/UbicnaPl62N0IDKGJGHE1UqMDJRUuMF0Y+NED7w mVfQFWSdxeaauEWnbnbaSYKzTUbySs9IP83O33JfauSOossm9TsTfH7j2c4At7eL2jk4 BIraWBm32NGmCtl3oWjyGtaRm/xVeEts9DNRqtl3h6gVHyFY9Slt6n/+sv2gxjTf7QoC EcDqQskH6JUJy7JqfQOdHENeCRE+NZdTjbmJREwaKRxBqdhTHmDi3bDMfWZM/e3y5SwT acUA==
X-Gm-Message-State: ALoCoQmCynrIuoYLklZx5DI2/x3YnTo6V0XJgRjskpwtTJhui5hnp2ggYwDUeU2yU9JkqlORtyMKodcPJUcc7cGFgeRvB3W3FuGIr2GLksH5H+ECVzkfhbXJ7g84RtCf5vhN5QOPMvASGVWw1Vgs1X52ch4iNdBtAXGDq8zgsGu/vkV3oIipVLz5mS9c9xD3d6VvtPQ5VVxY
MIME-Version: 1.0
X-Received: by 10.182.129.201 with SMTP id ny9mr11610879obb.0.1381992815760; Wed, 16 Oct 2013 23:53:35 -0700 (PDT)
Received: by 10.182.39.36 with HTTP; Wed, 16 Oct 2013 23:53:35 -0700 (PDT)
In-Reply-To: <64654145-6171-47C8-B990-D11F34E8B67B@zaphoyd.com>
References: <FD138330-7D7E-4450-B4F5-64551F92F26D@zaphoyd.com> <CAG4zZZBFVoYt7RLir_EZ+brW_heThO7D-CdQxWc4gicZBG2fCA@mail.gmail.com> <64654145-6171-47C8-B990-D11F34E8B67B@zaphoyd.com>
Date: Thu, 17 Oct 2013 15:53:35 +0900
Message-ID: <CAHixhFqH4V8GUay6cXpAvnRtH00=JXAQQfvnW+qwu5Mf-4fyjQ@mail.gmail.com>
From: Adam Rice <ricea@google.com>
To: Peter Thorson <webmaster@zaphoyd.com>
Content-Type: multipart/alternative; boundary=089e015366b4ddad0f04e8ea4667
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] permessage-deflate performance tuning statistics
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 17 Oct 2013 06:53:40 -0000

--089e015366b4ddad0f04e8ea4667
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Very interesting results, thank you!

On 16 October 2013 05:50, Peter Thorson <webmaster@zaphoyd.com> wrote:
>
> For cases without context takeover it would get more complicated, do you
> retain context between fragments? If so that negates all of the memory
> benefits of no-context-takeover=85 This needs to be clarified in the
> permessage-compress draft spec.
>

Context *is* retained between frames. This is the meaning of "permessage"
in "permessage-compression". The wording in the spec could maybe be
clearer. I was confused about this myself for a long time.

The consequence is that you are not guaranteed to need less compression
contexts than connections, unless you know something about the traffic you
are handling. Specifically, if you know all your messages will be smaller
than the size of the compression context, then you know you can save memory
by only keeping one compression context around. So a browser or a proxy
cannot be certain to benefit from no-content-takeover, but a server can
usefully use it on applications where it makes sense.


> It would definitely be worth experimenting with a connection that
> multiplexes small messages with large ones, say for the example case wher=
e
> you are delivering new documents over the WebSocket connection as we'll a=
s
> small updates. Getting some tests with binary/compressed data intermixed
> would also be useful it sounds. Does anyone have any sample data for such=
 a
> connection?
>
>
An interesting property of valid UTF-8 data is that given a sufficiently
large quantity, it is always compressible. Binary data, on the other hand,
is quite likely to have had compression applied to it already and be
incompressible by a generic algorithm like deflate. So a WebSocket with a
mixture of text and binary messages is challenging to compress effectively
and efficiently.

Thanks,
Adam Rice

--089e015366b4ddad0f04e8ea4667
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Very interesting results, thank you!<br><div class=3D"gmai=
l_extra"><br><div class=3D"gmail_quote">On 16 October 2013 05:50, Peter Tho=
rson <span dir=3D"ltr">&lt;<a href=3D"mailto:webmaster@zaphoyd.com" target=
=3D"_blank" class=3D"cremed">webmaster@zaphoyd.com</a>&gt;</span> wrote:<bl=
ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word"><div><div>For cases without context tak=
eover it would get more complicated, do you retain context between fragment=
s? If so that negates all of the memory benefits of no-context-takeover=85 =
This needs to be clarified in the permessage-compress draft spec.</div>
</div></div></blockquote><div><br></div><div>Context *is* retained between =
frames. This is the meaning of &quot;permessage&quot; in &quot;permessage-c=
ompression&quot;. The wording in the spec could maybe be clearer. I was con=
fused about this myself for a long time.</div>
<div><br></div><div>The consequence is that you are not guaranteed to need =
less compression contexts than connections, unless you know something about=
 the traffic you are handling. Specifically, if you know all your messages =
will be smaller than the size of the compression context, then you know you=
 can save memory by only keeping one compression context around. So a brows=
er or a proxy cannot be certain to benefit from no-content-takeover, but a =
server can usefully use it on applications where it makes sense.</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-=
word"><div><div>It would definitely be worth experimenting with a connectio=
n that multiplexes small messages with large ones, say for the example case=
 where you are delivering new documents over the WebSocket connection as we=
&#39;ll as small updates. Getting some tests with binary/compressed data in=
termixed would also be useful it sounds. Does anyone have any sample data f=
or such a connection?</div>
<div><div class=3D"h5"><br></div></div></div></div></blockquote><div><br></=
div><div>An interesting property of valid UTF-8 data is that given a suffic=
iently large quantity, it is always compressible. Binary data, on the other=
 hand, is quite likely to have had compression applied to it already and be=
 incompressible by a generic algorithm like deflate. So a WebSocket with a =
mixture of text and binary messages is challenging to compress effectively =
and efficiently.</div>
<div><br></div><div>Thanks,</div><div>Adam Rice</div></div><br></div></div>

--089e015366b4ddad0f04e8ea4667--

From tobias.oberstein@tavendo.de  Thu Oct 17 00:38:17 2013
Return-Path: <tobias.oberstein@tavendo.de>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2A3E11E8254 for <hybi@ietfa.amsl.com>; Thu, 17 Oct 2013 00:38:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z86R+rhSgOm1 for <hybi@ietfa.amsl.com>; Thu, 17 Oct 2013 00:38:11 -0700 (PDT)
Received: from EXHUB020-4.exch020.serverdata.net (exhub020-4.exch020.serverdata.net [206.225.164.31]) by ietfa.amsl.com (Postfix) with ESMTP id CF8F011E8250 for <hybi@ietf.org>; Thu, 17 Oct 2013 00:38:10 -0700 (PDT)
Received: from EXVMBX020-12.exch020.serverdata.net ([169.254.3.240]) by EXHUB020-4.exch020.serverdata.net ([206.225.164.31]) with mapi; Thu, 17 Oct 2013 00:38:09 -0700
From: Tobias Oberstein <tobias.oberstein@tavendo.de>
To: Takeshi Yoshino <tyoshino@google.com>, "hybi@ietf.org" <hybi@ietf.org>
Date: Thu, 17 Oct 2013 00:38:07 -0700
Thread-Topic: [hybi] [permessage-deflate] Renaming s2c_ and c2s_ prefix to server_ and client_
Thread-Index: Ac7KUN40V+f+jtO4S3+K0/8gyuIb3QAurGUw
Message-ID: <634914A010D0B943A035D226786325D44469CD51AB@EXVMBX020-12.exch020.serverdata.net>
References: <CAH9hSJant3VBw0FBM69V9wPvi3WmJLikZdX4ySELy+CShgoOKA@mail.gmail.com> <5BEA69BA-D0D4-4F4A-8CFB-741A433EAAA6@zaphoyd.com> <CAH9hSJYNrBkf=2=2DHdipvXwN4XEKDe2BOc4g1eZr38U7m7jdw@mail.gmail.com> <CAG4zZZDtUEnvgPmcKWsE9mFockUYA0PDFUE1SxNr+ubN0v9=xg@mail.gmail.com> <CAH9hSJZqR6L8fWTN_p915atXniuAbh-Nxb6FnPapoVwpdY3bAg@mail.gmail.com> <CAH9hSJY-=jti+AVPZjVJCpN9zTDTFpgbM_2WSQfnQYj-or9cgg@mail.gmail.com>
In-Reply-To: <CAH9hSJY-=jti+AVPZjVJCpN9zTDTFpgbM_2WSQfnQYj-or9cgg@mail.gmail.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [hybi] [permessage-deflate] Renaming s2c_ and c2s_ prefix to server_ and client_
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 17 Oct 2013 07:38:17 -0000

>With Chrome developer hat: We'll try to turn on permessage-deflate with th=
e new parameter naming on Chrome by default soon unless we see any objectio=
n to >the renaming with reasonable justification.

Ok, fine. If possible, please drop a notification here when Chrome/Chromium=
 has done so .. so we can test asap.

/Tobias

From tobias.oberstein@tavendo.de  Thu Oct 17 01:11:39 2013
Return-Path: <tobias.oberstein@tavendo.de>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EFF211E824C for <hybi@ietfa.amsl.com>; Thu, 17 Oct 2013 01:11:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 34kzYjFHSjPO for <hybi@ietfa.amsl.com>; Thu, 17 Oct 2013 01:11:27 -0700 (PDT)
Received: from EXHUB020-5.exch020.serverdata.net (exhub020-5.exch020.serverdata.net [206.225.164.32]) by ietfa.amsl.com (Postfix) with ESMTP id 00ABF11E80F9 for <hybi@ietf.org>; Thu, 17 Oct 2013 01:11:17 -0700 (PDT)
Received: from EXVMBX020-12.exch020.serverdata.net ([169.254.3.240]) by EXHUB020-5.exch020.serverdata.net ([206.225.164.32]) with mapi; Thu, 17 Oct 2013 01:11:17 -0700
From: Tobias Oberstein <tobias.oberstein@tavendo.de>
To: Tobias Oberstein <tobias.oberstein@tavendo.de>, Peter Thorson <webmaster@zaphoyd.com>, "hybi@ietf.org" <hybi@ietf.org>
Date: Thu, 17 Oct 2013 01:11:15 -0700
Thread-Topic: [hybi] permessage-deflate performance tuning statistics
Thread-Index: Ac7J1TgI93EbKEIiSiKEI1JXVmJz1QAA2mggAE3QRtA=
Message-ID: <634914A010D0B943A035D226786325D44469CD51AD@EXVMBX020-12.exch020.serverdata.net>
References: <FD138330-7D7E-4450-B4F5-64551F92F26D@zaphoyd.com> <634914A010D0B943A035D226786325D44469B06DCF@EXVMBX020-12.exch020.serverdata.net>
In-Reply-To: <634914A010D0B943A035D226786325D44469B06DCF@EXVMBX020-12.exch020.serverdata.net>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [hybi] permessage-deflate performance tuning statistics
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 17 Oct 2013 08:11:39 -0000

> As a first concrete action from this, I'll take the following issue to th=
e Python
> community:
>=20
> "Expose the 'Memory Level' knob on the Python zlib wrapper"

http://bugs.python.org/issue19278
http://bugs.python.org/issue19277


From tyoshino@google.com  Sat Oct 19 11:21:13 2013
Return-Path: <tyoshino@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA05921F9F50 for <hybi@ietfa.amsl.com>; Sat, 19 Oct 2013 11:21:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.885
X-Spam-Level: 
X-Spam-Status: No, score=-1.885 tagged_above=-999 required=5 tests=[AWL=0.092,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IqQwDfqqUbCf for <hybi@ietfa.amsl.com>; Sat, 19 Oct 2013 11:21:13 -0700 (PDT)
Received: from mail-wg0-x22b.google.com (mail-wg0-x22b.google.com [IPv6:2a00:1450:400c:c00::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 91B3011E824F for <hybi@ietf.org>; Sat, 19 Oct 2013 11:21:05 -0700 (PDT)
Received: by mail-wg0-f43.google.com with SMTP id b13so5016167wgh.10 for <hybi@ietf.org>; Sat, 19 Oct 2013 11:20:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=xWblbQ1GysA9ssL5gni+zNCCKpVrIeEpyj2k1g5rNgA=; b=QZc4i4uh/hNmIbxbKf6fSrwaGmZnViTvTa4WKzQ4KPUgi6/QnFNy4TUMY2klRddXn7 Edt7TAsDzsk3HESbZwK9phkJL2CdRtqb+2nAyzv1bIcexDY5SZXRH73eD5VAxOpPdb0a xpdSjpUNtl0jL2kSWwUxWIdobVrUfAUIBkvFhne1wc1JgWtPfbQcK5vB5J1dnZyM0UyT DGFNe8/R/ck/Se7tiOVHYEmRct4TbhJc3er9T3Aihtu4BIszmpA3Crk6soB65ewiEfAO 8dh3T8sUIZsyRvjRzGsJ3SLku3n9wfn4UHjcLlMfeGByn5pk4sJkMwKlWf/aK5Qn+hAR Ag9A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=xWblbQ1GysA9ssL5gni+zNCCKpVrIeEpyj2k1g5rNgA=; b=mL5F9VxgaLQ1NcbtQsL+RyVjRBqiWoh7xoOJmNHWzMUcXnIBFzZWb2CuQF6xBq4ZhV 1nxYGCdJwp+d12RbissSqwKo9EQYtq1uNDjPvVpMQ6I4OIKQx1lo9Wt/RZainZwTNq4V o1Xo32qSiNCgAddUKiCJ36HSU608Hpd7cvZs8YeIILBUUA6d5U1nkxcjhuoTIUYN0ouJ nLLonrl6iMg1+vPM+ZleAsBivN/aAXCNZam08/WS6Z10EPFNyRmOOpvBgsmHA/OrbzsW BtGxCkYfWnb48rMCVHp50JOhvLbOEqaQFuxVo9aRPwpKddAYL/GQ7FkLfzoau3w96hnQ q9oQ==
X-Gm-Message-State: ALoCoQlyEGptwu1imw5Xx8/5LOFw8VcSU5K3tOPtblPQ98+dE4RSXhuJrEMSE0RTz0+8Uui0GPYbjaQ7+pWErAvA6MtQT4T63IYS94O5jm+OYNvgB4eXfgknTD1gNef7CKYTGiM/yqS7s3EE0vtMKw6qxJ9+ZQ8edHf90MPTXE3tyNxeeWV5yPMg5rAwDLlcWi0Xtspl4Zs1
X-Received: by 10.180.185.101 with SMTP id fb5mr3770717wic.11.1382206858022; Sat, 19 Oct 2013 11:20:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.15.133 with HTTP; Sat, 19 Oct 2013 11:20:37 -0700 (PDT)
In-Reply-To: <634914A010D0B943A035D226786325D44469CD51AB@EXVMBX020-12.exch020.serverdata.net>
References: <CAH9hSJant3VBw0FBM69V9wPvi3WmJLikZdX4ySELy+CShgoOKA@mail.gmail.com> <5BEA69BA-D0D4-4F4A-8CFB-741A433EAAA6@zaphoyd.com> <CAH9hSJYNrBkf=2=2DHdipvXwN4XEKDe2BOc4g1eZr38U7m7jdw@mail.gmail.com> <CAG4zZZDtUEnvgPmcKWsE9mFockUYA0PDFUE1SxNr+ubN0v9=xg@mail.gmail.com> <CAH9hSJZqR6L8fWTN_p915atXniuAbh-Nxb6FnPapoVwpdY3bAg@mail.gmail.com> <CAH9hSJY-=jti+AVPZjVJCpN9zTDTFpgbM_2WSQfnQYj-or9cgg@mail.gmail.com> <634914A010D0B943A035D226786325D44469CD51AB@EXVMBX020-12.exch020.serverdata.net>
From: Takeshi Yoshino <tyoshino@google.com>
Date: Sun, 20 Oct 2013 03:20:37 +0900
Message-ID: <CAH9hSJawMaDt1dUBjvu9GvPMMtw0L=QAHOzmMrZWjHtq1MfchQ@mail.gmail.com>
To: Tobias Oberstein <tobias.oberstein@tavendo.de>
Content-Type: multipart/alternative; boundary=001a11c2448ec7763904e91c1cd4
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] [permessage-deflate] Renaming s2c_ and c2s_ prefix to server_ and client_
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Sat, 19 Oct 2013 18:21:13 -0000

--001a11c2448ec7763904e91c1cd4
Content-Type: text/plain; charset=ISO-8859-1

Renaming is done and rolled out to canary (32.0.1675.*). Still behind flag
(use --enable-experimental-web-platform-features or turn it on at
chrome://flags).


On Thu, Oct 17, 2013 at 4:38 PM, Tobias Oberstein <
tobias.oberstein@tavendo.de> wrote:

> >With Chrome developer hat: We'll try to turn on permessage-deflate with
> the new parameter naming on Chrome by default soon unless we see any
> objection to >the renaming with reasonable justification.
>
> Ok, fine. If possible, please drop a notification here when
> Chrome/Chromium has done so .. so we can test asap.
>
> /Tobias
>

--001a11c2448ec7763904e91c1cd4
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Renaming is done and rolled out to canary (32.0.1675.*). S=
till behind flag (use --enable-experimental-web-platform-features or turn i=
t on at chrome://flags).<div class=3D"gmail_extra">
<br><br><div class=3D"gmail_quote">On Thu, Oct 17, 2013 at 4:38 PM, Tobias =
Oberstein <span dir=3D"ltr">&lt;<a href=3D"mailto:tobias.oberstein@tavendo.=
de" target=3D"_blank">tobias.oberstein@tavendo.de</a>&gt;</span> wrote:<br>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">


<div>&gt;With Chrome developer hat: We&#39;ll try to turn on permessage-def=
late with the new parameter naming on Chrome by default soon unless we see =
any objection to &gt;the renaming with reasonable justification.<br>

<br>
</div>Ok, fine. If possible, please drop a notification here when Chrome/Ch=
romium has done so .. so we can test asap.<br>
<span><font color=3D"#888888"><br>
/Tobias<br>
</font></span></blockquote></div><br></div></div>

--001a11c2448ec7763904e91c1cd4--

From tyoshino@google.com  Sun Oct 20 20:36:14 2013
Return-Path: <tyoshino@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D306A11E8492 for <hybi@ietfa.amsl.com>; Sun, 20 Oct 2013 20:36:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level: 
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[AWL=0.088,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nWSGWvDtfJXp for <hybi@ietfa.amsl.com>; Sun, 20 Oct 2013 20:36:14 -0700 (PDT)
Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) by ietfa.amsl.com (Postfix) with ESMTP id 2B21011E8332 for <hybi@ietf.org>; Sun, 20 Oct 2013 20:36:14 -0700 (PDT)
Received: by mail-wi0-f169.google.com with SMTP id cb5so4586287wib.2 for <hybi@ietf.org>; Sun, 20 Oct 2013 20:36:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=IV/DScKFHEEOzLZQiX1wAQSQDkNElqUeURWU9mN0nKQ=; b=FGqvi4GQ+2MWGhrhuTerSQTxioSbaEA4bsws7RtWlKHEHfhuYJrP6dM0zoelxS8I45 36zCOo7Nj97bEgWUTVHtidUvDvmtEmcA1l6ITJFBxxdRAe5Qi0vn2hLBrdQf9yHTntN4 8GX0FEMGQmyAb+vfz3uGnaSqjvM1mjzAJVvD/+PgQyFRJX7JVoj2QLyaKt1yY+AOnOFZ lNgyZ15SIUn869cr60BigpT0Sp5iOtaAHj7wA5YQOpRV7US0K2uQo/KO2VGF5yH7qdYY j4XJg95lEsGf0Z4hMUtmNReVqHBhQVOA6BEGGoVcvBrLdVRo7S01ZqOKoeRSQMgrPhS7 zW2Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=IV/DScKFHEEOzLZQiX1wAQSQDkNElqUeURWU9mN0nKQ=; b=CRGpx4O6bn2qNV1eRVGxMPGIKMl3YW6SQ6qVBtqhtlPYhCxzMwSK53ag/rLqVvgtz+ R9Z/y6SgB11XhKqRmMSTB1g201pRZuZn9QtNs8+KZ9bsctKGIET5s4VIAw0R7ZjO8+Bz mHWTo0zLcb9LZrj7NEnXpbAIe5MUwlZZeJ1YZI2pAsOCZ3hFK8TU5du34eEFhNkHlJsM XLJ2pzTc6jn7Q3L/vQs8tCyBDx3WcESVqBmevFBzcq7VYWTkIm0A078o89ia1V8f+xZK mmZjkq2gvKu4YPJ60OdGXJaD1VPkNJl/5DFOBG1pFnxTR7efbA13NNIEu+vMxAmsZIm3 eLnw==
X-Gm-Message-State: ALoCoQn2nWJmIJ1svLNHVz6aopH7gqPLFkLQMjr0FAC3ZI1Yn9sHnpMGvYn0b9Jyh3uPSDSRvVFC62ZOm6IUvrhHqY+bHHQ0CiDiAJAf2/Q0x6zgMuEZa146vZ6UjnFtbv2AhIS3VsS8t2efSnM3AqsjojIQ0tgOjJfTHzSsw+Kgd/A5vzcbSIn+j6/h3gIKLJNHhUBlzSPf
X-Received: by 10.180.211.71 with SMTP id na7mr8044836wic.5.1382326573126; Sun, 20 Oct 2013 20:36:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.15.133 with HTTP; Sun, 20 Oct 2013 20:35:53 -0700 (PDT)
In-Reply-To: <CAH9hSJawMaDt1dUBjvu9GvPMMtw0L=QAHOzmMrZWjHtq1MfchQ@mail.gmail.com>
References: <CAH9hSJant3VBw0FBM69V9wPvi3WmJLikZdX4ySELy+CShgoOKA@mail.gmail.com> <5BEA69BA-D0D4-4F4A-8CFB-741A433EAAA6@zaphoyd.com> <CAH9hSJYNrBkf=2=2DHdipvXwN4XEKDe2BOc4g1eZr38U7m7jdw@mail.gmail.com> <CAG4zZZDtUEnvgPmcKWsE9mFockUYA0PDFUE1SxNr+ubN0v9=xg@mail.gmail.com> <CAH9hSJZqR6L8fWTN_p915atXniuAbh-Nxb6FnPapoVwpdY3bAg@mail.gmail.com> <CAH9hSJY-=jti+AVPZjVJCpN9zTDTFpgbM_2WSQfnQYj-or9cgg@mail.gmail.com> <634914A010D0B943A035D226786325D44469CD51AB@EXVMBX020-12.exch020.serverdata.net> <CAH9hSJawMaDt1dUBjvu9GvPMMtw0L=QAHOzmMrZWjHtq1MfchQ@mail.gmail.com>
From: Takeshi Yoshino <tyoshino@google.com>
Date: Mon, 21 Oct 2013 12:35:53 +0900
Message-ID: <CAH9hSJZ3y4pmmdFh0DJeJQi4e3S8NdAxphrJ2NaCteFU=E570A@mail.gmail.com>
To: Tobias Oberstein <tobias.oberstein@tavendo.de>
Content-Type: multipart/alternative; boundary=001a11c347e05afeb604e937fca6
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] [permessage-deflate] Renaming s2c_ and c2s_ prefix to server_ and client_
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Mon, 21 Oct 2013 03:36:15 -0000

--001a11c347e05afeb604e937fca6
Content-Type: text/plain; charset=ISO-8859-1

On Sun, Oct 20, 2013 at 3:20 AM, Takeshi Yoshino <tyoshino@google.com>wrote:

> Renaming is done and rolled out to canary (32.0.1675.*). Still behind flag
> (use --enable-experimental-web-platform-features or turn it on at
> chrome://flags).
>

Sorry. The commandline flag doesn't work. Please go to
chrome://flags/#enable-websocket-experimental-implementation and click
"Enable".

--001a11c347e05afeb604e937fca6
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Sun, Oct 20, 2013 at 3:20 AM, Takeshi Yoshino <span dir=
=3D"ltr">&lt;<a href=3D"mailto:tyoshino@google.com" target=3D"_blank">tyosh=
ino@google.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div cla=
ss=3D"gmail_quote">

<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div dir=3D"ltr">Renaming is done and rolled out to canary=
 (32.0.1675.*). Still behind flag (use --enable-experimental-web-platform-f=
eatures or turn it on at chrome://flags).</div>

</blockquote><div><br></div><div>Sorry. The commandline flag doesn&#39;t wo=
rk. Please go to chrome://flags/#enable-websocket-experimental-implementati=
on and click &quot;Enable&quot;.</div></div></div></div>

--001a11c347e05afeb604e937fca6--

From tobias.oberstein@tavendo.de  Mon Oct 21 08:51:52 2013
Return-Path: <tobias.oberstein@tavendo.de>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34B1811E83FC for <hybi@ietfa.amsl.com>; Mon, 21 Oct 2013 08:51:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.854
X-Spam-Level: 
X-Spam-Status: No, score=-1.854 tagged_above=-999 required=5 tests=[AWL=-0.744, BAYES_05=-1.11]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LXf8K24paaI2 for <hybi@ietfa.amsl.com>; Mon, 21 Oct 2013 08:51:48 -0700 (PDT)
Received: from EXHUB020-5.exch020.serverdata.net (exhub020-5.exch020.serverdata.net [206.225.164.32]) by ietfa.amsl.com (Postfix) with ESMTP id 9278C11E83F7 for <hybi@ietf.org>; Mon, 21 Oct 2013 08:50:54 -0700 (PDT)
Received: from EXVMBX020-12.exch020.serverdata.net ([169.254.3.240]) by EXHUB020-5.exch020.serverdata.net ([206.225.164.32]) with mapi; Mon, 21 Oct 2013 08:50:53 -0700
From: Tobias Oberstein <tobias.oberstein@tavendo.de>
To: Takeshi Yoshino <tyoshino@google.com>
Date: Mon, 21 Oct 2013 08:50:49 -0700
Thread-Topic: [hybi] [permessage-deflate] Renaming s2c_ and c2s_ prefix to server_ and client_
Thread-Index: Ac7M9/YApSL63iBER96IHwXDj3aoSgBZUyFg
Message-ID: <634914A010D0B943A035D226786325D44469CD5BA7@EXVMBX020-12.exch020.serverdata.net>
References: <CAH9hSJant3VBw0FBM69V9wPvi3WmJLikZdX4ySELy+CShgoOKA@mail.gmail.com> <5BEA69BA-D0D4-4F4A-8CFB-741A433EAAA6@zaphoyd.com> <CAH9hSJYNrBkf=2=2DHdipvXwN4XEKDe2BOc4g1eZr38U7m7jdw@mail.gmail.com> <CAG4zZZDtUEnvgPmcKWsE9mFockUYA0PDFUE1SxNr+ubN0v9=xg@mail.gmail.com> <CAH9hSJZqR6L8fWTN_p915atXniuAbh-Nxb6FnPapoVwpdY3bAg@mail.gmail.com> <CAH9hSJY-=jti+AVPZjVJCpN9zTDTFpgbM_2WSQfnQYj-or9cgg@mail.gmail.com> <634914A010D0B943A035D226786325D44469CD51AB@EXVMBX020-12.exch020.serverdata.net> <CAH9hSJawMaDt1dUBjvu9GvPMMtw0L=QAHOzmMrZWjHtq1MfchQ@mail.gmail.com>
In-Reply-To: <CAH9hSJawMaDt1dUBjvu9GvPMMtw0L=QAHOzmMrZWjHtq1MfchQ@mail.gmail.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] [permessage-deflate] Renaming s2c_ and c2s_ prefix to server_ and client_
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Mon, 21 Oct 2013 15:51:52 -0000

Hi Takeshi,

AutobahnPython 0.6.4 has been adjusted and published:

https://pypi.python.org/pypi/autobahn
https://github.com/tavendo/AutobahnPython/blob/master/CHANGELOG.md

Tested with canary 32.0.1677.0: no issues found .. I've tested a couple of =
negotiated parameter sets also.

We will extend AutobahnTestsuite for _systematic_ testing of various parame=
ter sets ..

>From my side, there is only 1 minor point left .. see below. I just want to=
 raise it for completeness, but am happy if Draft-15 makes it into final RF=
C also.

Sidenote: I've seen that Chrome will log extensions negotiated in Web inspe=
ctor also. Nice nice. Thanks. It seems just hours away .. mine does not hav=
e it yet. Anyway: reckless pace! Awesome.

/Tobias


Proposal: Make support for "no context takeover" optional, and consequently=
 announce "client_no_context_takeover".

That makes the whole parameter negotiation more "consistent" and allows imp=
lementors who do not want to implement "no context takeover" for whatever r=
easons (technically, it should be possible to do always, but ..).

Chrome announces:

1. Sec-WebSocket-Extensions:
permessage-deflate; client_max_window_bits, x-webkit-deflate-frame
and supports "client_no_context_takeover", but that is implicit, not explic=
it.

Autobahn (client) currently (deliberately) announces:

Sec-WebSocket-Extensions: permessage-deflate; client_no_context_takeover; c=
lient_max_window_bits

hence _explicitly_ announces "client_no_context_takeover"

=3D=3D=3D

Should above _not_ go into the final spec, AutobahnPython will then of cour=
se comply (and remove the announcement) when the RFC is issued.

From tyoshino@google.com  Mon Oct 21 23:17:19 2013
Return-Path: <tyoshino@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54C2C11E8174 for <hybi@ietfa.amsl.com>; Mon, 21 Oct 2013 23:17:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.893
X-Spam-Level: 
X-Spam-Status: No, score=-1.893 tagged_above=-999 required=5 tests=[AWL=0.084,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y8m+GQ7JGWz0 for <hybi@ietfa.amsl.com>; Mon, 21 Oct 2013 23:17:18 -0700 (PDT)
Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) by ietfa.amsl.com (Postfix) with ESMTP id C2D2A11E8474 for <hybi@ietf.org>; Mon, 21 Oct 2013 23:17:17 -0700 (PDT)
Received: by mail-wi0-f172.google.com with SMTP id ez12so5034293wid.11 for <hybi@ietf.org>; Mon, 21 Oct 2013 23:17:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=iL1UdXU6SBM5IlOR38h2O8wUfWherqNRYEbsMqIK/6U=; b=RFrQU/65Xt7txJobG5ogKPT/2H6I5LDhSHJQxbr92l5RkwHJVOeIx4A5cxwqGZAYNx TUOGxave2mvaPtFIyE96AYYIVXkzXp9Y+4+IwzibM2cIiAn4gJjQLFoOdEWKPh3MFgEP /3XB2CuwAuIdvmXXvBMuwZymwxWaf49LCUJzSZKNB20xzr5CjP8lrVOx1kmzF8+s0sUg R7IoDlDSIZ/ghHzIiC1/aCUJC4WzgLN7lccGzXRXVImRHBiF+Ut8n1Gmzu0ICoLUIiO4 5F3HpbwXeQnlJ4GB/AKnaqqsBFq5hV6G06UAUp8ml/NOb4uArXVyHOLObq7/rfH7WdXg 1DkQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=iL1UdXU6SBM5IlOR38h2O8wUfWherqNRYEbsMqIK/6U=; b=LlnuHfew7KMfolH713zW6mWHbt9NFE1RE+qK/YhtFqoIY4DJzYV8YgWhP/vn0eo7aE tMbkTIbpnHAeAbJU0XccA38PubA5JbUm2qdKzJkhisJebv8AE922cWMPRBs0GXHGlUhf TzxJ+IRlO+w0AI04YjHIDfQi4DXm+bp00CrssdTW6Ac+ix2jcLosTX2KpxQyxGzxPJVx oVYOWrvNPI7tayCIOxUa+Ola7sKxY+DcJ+UDiN2tNomAbqgvnZM2bFJz7kDbw/xiVpU8 mrU1mfojcVXQmUJheBtkTvfIxYFK6Mi98qPYbjB24avOEO1uiGaZA6KtKNAA/4tWbgCu O8Yw==
X-Gm-Message-State: ALoCoQnmdyLL58K+eI8iQgEjwjvqkVHvRPaJ9/yLtAo6CZjGfIx9eRR+miBy1yXjz4mp5Gzpeiv6rhesXMPkedqtwJvfQU+aTi6B7/XH+xMJFbvJ/mOSjnUcJkFYETE2h5QqYbeJ2sqIewfZVy5x2osLf84NwxO/qrKG37U9dNfUTzt2pCx/mcA8zpRwQbl5+ET199vuVZ8k
X-Received: by 10.180.99.99 with SMTP id ep3mr12911860wib.11.1382422625719; Mon, 21 Oct 2013 23:17:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.15.133 with HTTP; Mon, 21 Oct 2013 23:16:44 -0700 (PDT)
In-Reply-To: <634914A010D0B943A035D226786325D44469CD5BA7@EXVMBX020-12.exch020.serverdata.net>
References: <CAH9hSJant3VBw0FBM69V9wPvi3WmJLikZdX4ySELy+CShgoOKA@mail.gmail.com> <5BEA69BA-D0D4-4F4A-8CFB-741A433EAAA6@zaphoyd.com> <CAH9hSJYNrBkf=2=2DHdipvXwN4XEKDe2BOc4g1eZr38U7m7jdw@mail.gmail.com> <CAG4zZZDtUEnvgPmcKWsE9mFockUYA0PDFUE1SxNr+ubN0v9=xg@mail.gmail.com> <CAH9hSJZqR6L8fWTN_p915atXniuAbh-Nxb6FnPapoVwpdY3bAg@mail.gmail.com> <CAH9hSJY-=jti+AVPZjVJCpN9zTDTFpgbM_2WSQfnQYj-or9cgg@mail.gmail.com> <634914A010D0B943A035D226786325D44469CD51AB@EXVMBX020-12.exch020.serverdata.net> <CAH9hSJawMaDt1dUBjvu9GvPMMtw0L=QAHOzmMrZWjHtq1MfchQ@mail.gmail.com> <634914A010D0B943A035D226786325D44469CD5BA7@EXVMBX020-12.exch020.serverdata.net>
From: Takeshi Yoshino <tyoshino@google.com>
Date: Tue, 22 Oct 2013 15:16:44 +0900
Message-ID: <CAH9hSJbMdie=Wf3Zc8C27fqBQ3sJNTxXWWgmS6sO8Mnp_oY3rg@mail.gmail.com>
To: Tobias Oberstein <tobias.oberstein@tavendo.de>
Content-Type: multipart/alternative; boundary=f46d044283c0893c8404e94e59fc
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] [permessage-deflate] Renaming s2c_ and c2s_ prefix to server_ and client_
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 22 Oct 2013 06:17:19 -0000

--f46d044283c0893c8404e94e59fc
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Oct 22, 2013 at 12:50 AM, Tobias Oberstein <
tobias.oberstein@tavendo.de> wrote:

> AutobahnPython 0.6.4 has been adjusted and published:
>
> https://pypi.python.org/pypi/autobahn
> https://github.com/tavendo/AutobahnPython/blob/master/CHANGELOG.md
>
> Tested with canary 32.0.1677.0: no issues found .. I've tested a couple of
> negotiated parameter sets also.
>
> We will extend AutobahnTestsuite for _systematic_ testing of various
> parameter sets ..
>

Thank you!


> From my side, there is only 1 minor point left .. see below. I just want
> to raise it for completeness, but am happy if Draft-15 makes it into final
> RFC also.
>
> Sidenote: I've seen that Chrome will log extensions negotiated in Web
> inspector also. Nice nice. Thanks. It seems just hours away .. mine does
> not have it yet. Anyway: reckless pace! Awesome.
>

Yes. It has been unexpectedly dropped. We've fixed it recently.


>
> /Tobias
>
>
> Proposal: Make support for "no context takeover" optional, and
> consequently announce "client_no_context_takeover".
>
> That makes the whole parameter negotiation more "consistent" and allows
> implementors who do not want to implement "no context takeover" for
> whatever reasons (technically, it should be possible to do always, but ..).
>
>
As you know, we've given the role as a hint to client_no_context_takeover
parameter in a negotiation offer, that syntax is not available for
capability announcement now. So, we need to introduce a new syntax for hint
like:

client_no_context_takeover=likely

to free the syntax "client_no_context_takeover without a value" for
capability announcement. Or instead, we need to drop the hint feature.

Maybe Java users like Joakim would be happier with having MUST there than
SHOULD?


> Chrome announces:
>
> 1. Sec-WebSocket-Extensions:
> permessage-deflate; client_max_window_bits, x-webkit-deflate-frame
> and supports "client_no_context_takeover", but that is implicit, not
> explicit.
>
> Autobahn (client) currently (deliberately) announces:
>
> Sec-WebSocket-Extensions: permessage-deflate; client_no_context_takeover;
> client_max_window_bits
>
> hence _explicitly_ announces "client_no_context_takeover"
>
> ===
>
> Should above _not_ go into the final spec, AutobahnPython will then of
> course comply (and remove the announcement) when the RFC is issued.
>

--f46d044283c0893c8404e94e59fc
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Tue, Oct 22, 2013 at 12:50 AM, Tobias Oberstein <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:tobias.oberstein@tavendo.de" target=3D"_bl=
ank">tobias.oberstein@tavendo.de</a>&gt;</span> wrote:<br><div class=3D"gma=
il_extra">


<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">AutobahnPython 0.=
6.4 has been adjusted and published:<br>
<br>
<a href=3D"https://pypi.python.org/pypi/autobahn" target=3D"_blank">https:/=
/pypi.python.org/pypi/autobahn</a><br>
<a href=3D"https://github.com/tavendo/AutobahnPython/blob/master/CHANGELOG.=
md" target=3D"_blank">https://github.com/tavendo/AutobahnPython/blob/master=
/CHANGELOG.md</a><br>
<br>
Tested with canary 32.0.1677.0: no issues found .. I&#39;ve tested a couple=
 of negotiated parameter sets also.<br>
<br>
We will extend AutobahnTestsuite for _systematic_ testing of various parame=
ter sets ..<br></blockquote><div><br></div><div>Thank you!</div><div>=A0</d=
iv><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex">



>From my side, there is only 1 minor point left .. see below. I just want to=
 raise it for completeness, but am happy if Draft-15 makes it into final RF=
C also.<br>
<br>
Sidenote: I&#39;ve seen that Chrome will log extensions negotiated in Web i=
nspector also. Nice nice. Thanks. It seems just hours away .. mine does not=
 have it yet. Anyway: reckless pace! Awesome.<br></blockquote><div><br>


</div><div>Yes. It has been unexpectedly dropped. We&#39;ve fixed it recent=
ly.</div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
/Tobias<br>
<br>
<br>
Proposal: Make support for &quot;no context takeover&quot; optional, and co=
nsequently announce &quot;client_no_context_takeover&quot;.<br>
<br>
That makes the whole parameter negotiation more &quot;consistent&quot; and =
allows implementors who do not want to implement &quot;no context takeover&=
quot; for whatever reasons (technically, it should be possible to do always=
, but ..).<br>



<br></blockquote><div><br></div><div>As you know, we&#39;ve given the role =
as a hint to client_no_context_takeover parameter in a negotiation offer, t=
hat syntax is not available for capability announcement now. So, we need to=
 introduce a new syntax for hint like:</div>

<div><br></div><div>client_no_context_takeover=3Dlikely</div><div><br></div=
><div>to free the syntax &quot;client_no_context_takeover without a value&q=
uot; for capability announcement. Or instead, we need to drop the hint feat=
ure.</div>

<div><br></div><div>Maybe Java users like Joakim would be happier with havi=
ng MUST there than SHOULD?</div><div>=A0</div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
">


Chrome announces:<br>
<br>
1. Sec-WebSocket-Extensions:<br>
permessage-deflate; client_max_window_bits, x-webkit-deflate-frame<br>
and supports &quot;client_no_context_takeover&quot;, but that is implicit, =
not explicit.<br>
<br>
Autobahn (client) currently (deliberately) announces:<br>
<br>
Sec-WebSocket-Extensions: permessage-deflate; client_no_context_takeover; c=
lient_max_window_bits<br>
<br>
hence _explicitly_ announces &quot;client_no_context_takeover&quot;<br>
<br>
=3D=3D=3D<br>
<br>
Should above _not_ go into the final spec, AutobahnPython will then of cour=
se comply (and remove the announcement) when the RFC is issued.<br>
</blockquote></div><br></div></div>

--f46d044283c0893c8404e94e59fc--

From ricea@google.com  Tue Oct 22 20:17:45 2013
Return-Path: <ricea@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA01B11E8113 for <hybi@ietfa.amsl.com>; Tue, 22 Oct 2013 20:17:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pEWheOdVwkcw for <hybi@ietfa.amsl.com>; Tue, 22 Oct 2013 20:17:45 -0700 (PDT)
Received: from mail-ob0-x229.google.com (mail-ob0-x229.google.com [IPv6:2607:f8b0:4003:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id E7E7B11E80EC for <hybi@ietf.org>; Tue, 22 Oct 2013 20:17:44 -0700 (PDT)
Received: by mail-ob0-f169.google.com with SMTP id wp4so278710obc.28 for <hybi@ietf.org>; Tue, 22 Oct 2013 20:17:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=O6v527k7VnVM+WPpm4tlT1qhGTH/B0OmVeVlD+WJbpQ=; b=jzxAOEGvwZqoOXsPKULF3Sv/ogvg2mpcD+Nj7LpiKn84B6qpB4RbbNqY3UYAD/JFYL 7G5LPI7c9NV/ghtlmRzHqqLDZVSGHj/5y59phMDOs+9qKCY80ebqgieaVn+qQIiSzg5s 91TXRwzqoMiQVUxxHZYrxxDTW0/Oxcowwptndkf+kVdpBp3OAGOLEzlQ1C/VNA9FeAjY MxYO1FtF4XHSQ0Wp5/8FYLPMftiFJQratfBZz1wcw4ZQk9zT+Y/ZBbcEBRdt0I8plxkO Ca1HuWAT94Gj3Xt+EX1zdB49Q86tYf4CcG4PIRvi+rmssgv4+LVd8cNQ+JJC6K3Jovao M+LQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=O6v527k7VnVM+WPpm4tlT1qhGTH/B0OmVeVlD+WJbpQ=; b=g8PvNC1yFTAJehZh6NmzFdjt/4/tsJ8rB1ukyCLefQVhNS4exyIv2tqwxO388uJ27l pHaLNwoEMTVfFNYGN85FSLT2QxOa0zc3vOaLC7eSoCdp7xysIRtM4Gd4f0Ks0oVr/fQ8 6UUO+x10fHc2lUh9Dyzs6qvsHtoR/I5n8H0LXqnuQuctPIXaoESTpM0iR7fb/EjnXFBK +mhu4k9/894VvX4wAvIar9AVlfioqHHgfxSwbBmSL6AWuyAuKJc17Z45vacuUhNsPIfC KmpefFIO9CdoMna8DMihxsYnmAMPHtSB+PaWakpqFBSXqgSXjU8jsZmthH7ErRbfCyKi natA==
X-Gm-Message-State: ALoCoQk/gOyKTWblBvhOGxXoCdeV85c/Fpdw52cpSjJp8E0601TKEr+FnyX+DWQkyv91xZ9bWVW63i+JuFdW38TslyR844EJeIxU/qtCRKrA3ciGfKt1fhKhaiKWxWQQm7QsRQb8+WP3btDHy0k0Jy9IzCcfD/bjedodnSb9B3SfrI5CAOwIf92uF/By5NIOP1fiPzpk3KYQ
MIME-Version: 1.0
X-Received: by 10.60.51.196 with SMTP id m4mr4753518oeo.1.1382498264282; Tue, 22 Oct 2013 20:17:44 -0700 (PDT)
Received: by 10.182.39.36 with HTTP; Tue, 22 Oct 2013 20:17:44 -0700 (PDT)
Date: Wed, 23 Oct 2013 12:17:44 +0900
Message-ID: <CAHixhFr6mnoQW5wLaYFsd1=pLUdq8D3Y4VFHtNcu4WSe+5CjuQ@mail.gmail.com>
From: Adam Rice <ricea@google.com>
To: "hybi@ietf.org" <hybi@ietf.org>
Content-Type: multipart/alternative; boundary=001a11c30920f20ce204e95ff5e7
Subject: [hybi] SPNEGO with WebSockets
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 23 Oct 2013 03:17:45 -0000

--001a11c30920f20ce204e95ff5e7
Content-Type: text/plain; charset=ISO-8859-1

Has anyone implemented SPNEGO authentication in conjunction with the
WebSocket handshake? I am wondering whether it is necessary and also
whether it is possible to do it in an RFC6455-compliant manner.

Thanks,
Adam Rice

--001a11c30920f20ce204e95ff5e7
Content-Type: text/html; charset=ISO-8859-1

<div dir="ltr">Has anyone implemented SPNEGO authentication in conjunction with the WebSocket handshake? I am wondering whether it is necessary and also whether it is possible to do it in an RFC6455-compliant manner.<div><br>
</div><div>Thanks,</div><div>Adam Rice</div></div>

--001a11c30920f20ce204e95ff5e7--

From tyoshino@google.com  Wed Oct 23 02:20:57 2013
Return-Path: <tyoshino@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02E4711E8182 for <hybi@ietfa.amsl.com>; Wed, 23 Oct 2013 02:20:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level: 
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[AWL=0.081,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l9+CrzoZyM0j for <hybi@ietfa.amsl.com>; Wed, 23 Oct 2013 02:20:56 -0700 (PDT)
Received: from mail-wi0-x235.google.com (mail-wi0-x235.google.com [IPv6:2a00:1450:400c:c05::235]) by ietfa.amsl.com (Postfix) with ESMTP id 6528321F968B for <hybi@ietf.org>; Wed, 23 Oct 2013 02:20:56 -0700 (PDT)
Received: by mail-wi0-f181.google.com with SMTP id l12so522289wiv.14 for <hybi@ietf.org>; Wed, 23 Oct 2013 02:20:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=kl/61dqUxACqCBFwSf4UYL1B5KS5VYYkS8Rbfi6xOag=; b=LfAk41tlidAMF02dsXPIEo/Fc8RKHrPIEj3+dBeYp8BvHoGmFXO4D6OSaC2+RTCNW1 lpBF5eXenIUNgERAJEU0amj4xOmUd+JBc5q3gfHAKFw79iRrP3Se5/um83nclIKgwwC2 LboullqEl0pn2UrZAGB2n+IIt2EyeJdaBaQmX5ZUUt0Z9tq40peZ3U1dPvFyzfkKJa32 ee8U0Th4vs2ETKIqpn1nmYFKAjd7NHRBnv1u4pZ1I56dj9G8RvoMx9KDLQ2UosdMFDT7 1VfTSZPUxu4R7DjlSnhBeZ5T/zeEvUHhntpFAbyMfZVEPucbNPo/cr3ooFRDkvwsKR7g oCAA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=kl/61dqUxACqCBFwSf4UYL1B5KS5VYYkS8Rbfi6xOag=; b=IEuX8CsR/akkN5lspA6Dp0uABODJSAmJPu6S4aiXUtJBpHvE0T5bjeh2vYPyH2Gy05 1ClDS6IbXBvHtX42GdP5r7+d0Q/+g+dxUly0R/24Q0WXFdlWQAfH+GdufI0N0LgusMa0 i8WfPq2byIl8QKYEyb5l9WWM60XGNTR19yb97eYWW6PU/ndH85blL6tC/R5Qk99WVP8I u2mUWuiow7lWHik8Baa4Ib7zbtckF0VJaue5gHsvNQKIfj6AHutdJqs3MihsQCwTVPMD SxqUh8Osdgh6fFytUmF/oWBGANDh6Se/g/tUnivatV7jYXBXhQenvfnq7rk0Cbzf1Dwv sJFg==
X-Gm-Message-State: ALoCoQnXEnE4CjPaXyA7Qe/N57Alxt8Fox3dvrYa+AUORYYiO+rrQ1ueRBPBhM3EooZSzLsMp/Ui4qY6SCYZdHF6Qn2hyIjoURfQBYQ5Ld4mxgN+QEEzJRVDzvElu4parnJTTQUaZTRXn6gIoG9t53VfuVLLnRnRUkBNAzIIviVtwf2j0LPssqqfOIpwExRNAV3lZb0VavdM
X-Received: by 10.180.211.71 with SMTP id na7mr1176309wic.5.1382520055357; Wed, 23 Oct 2013 02:20:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.15.133 with HTTP; Wed, 23 Oct 2013 02:20:35 -0700 (PDT)
In-Reply-To: <CAH9hSJZ3y4pmmdFh0DJeJQi4e3S8NdAxphrJ2NaCteFU=E570A@mail.gmail.com>
References: <CAH9hSJant3VBw0FBM69V9wPvi3WmJLikZdX4ySELy+CShgoOKA@mail.gmail.com> <5BEA69BA-D0D4-4F4A-8CFB-741A433EAAA6@zaphoyd.com> <CAH9hSJYNrBkf=2=2DHdipvXwN4XEKDe2BOc4g1eZr38U7m7jdw@mail.gmail.com> <CAG4zZZDtUEnvgPmcKWsE9mFockUYA0PDFUE1SxNr+ubN0v9=xg@mail.gmail.com> <CAH9hSJZqR6L8fWTN_p915atXniuAbh-Nxb6FnPapoVwpdY3bAg@mail.gmail.com> <CAH9hSJY-=jti+AVPZjVJCpN9zTDTFpgbM_2WSQfnQYj-or9cgg@mail.gmail.com> <634914A010D0B943A035D226786325D44469CD51AB@EXVMBX020-12.exch020.serverdata.net> <CAH9hSJawMaDt1dUBjvu9GvPMMtw0L=QAHOzmMrZWjHtq1MfchQ@mail.gmail.com> <CAH9hSJZ3y4pmmdFh0DJeJQi4e3S8NdAxphrJ2NaCteFU=E570A@mail.gmail.com>
From: Takeshi Yoshino <tyoshino@google.com>
Date: Wed, 23 Oct 2013 18:20:35 +0900
Message-ID: <CAH9hSJboVJ=6LYgwL2qPjT9=Y5a_ffYocZDzTgao_Ob3fb1h+g@mail.gmail.com>
To: Tobias Oberstein <tobias.oberstein@tavendo.de>
Content-Type: multipart/alternative; boundary=001a11c347e0cb807c04e96508e2
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] [permessage-deflate] Renaming s2c_ and c2s_ prefix to server_ and client_
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 23 Oct 2013 09:20:57 -0000

--001a11c347e0cb807c04e96508e2
Content-Type: text/plain; charset=ISO-8859-1

Now permessage-deflate is enabled by default on Chrome canary.

--001a11c347e0cb807c04e96508e2
Content-Type: text/html; charset=ISO-8859-1

<div dir="ltr"><div class="gmail_extra">Now permessage-deflate is enabled by default on Chrome canary.</div></div>

--001a11c347e0cb807c04e96508e2--

From joakim@intalio.com  Thu Oct 24 16:29:05 2013
Return-Path: <joakim@intalio.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 247C811E825F for <hybi@ietfa.amsl.com>; Thu, 24 Oct 2013 16:29:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s4X5j240zaNF for <hybi@ietfa.amsl.com>; Thu, 24 Oct 2013 16:29:01 -0700 (PDT)
Received: from mail-ee0-f46.google.com (mail-ee0-f46.google.com [74.125.83.46]) by ietfa.amsl.com (Postfix) with ESMTP id A108811E8262 for <hybi@ietf.org>; Thu, 24 Oct 2013 16:28:58 -0700 (PDT)
Received: by mail-ee0-f46.google.com with SMTP id c1so1470528eek.5 for <hybi@ietf.org>; Thu, 24 Oct 2013 16:28:57 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=c5FsSkGam7L0CShZ34+uTuM4pNOZuPNaVaKWCpabm+k=; b=nJhiMxShPrga742Bbo6FU1Y/4GFoyWpajqIZaDQJO/w7oEaPMhXrZQhupGzfohwC68 IFKxuODYUiL+Lhbe+lLpuvh4oYmb7BG5Bhpd/bn21D7wTq/8xCwTViI1zeN3pQWGTiMk v8ylFZ5+UTW/ApBuRN//kvYPp3bGHpz/4gg3k9OPd0/R5Cf0gdB1KoPchuzKjZLExd5X G/jrCK4uz4Dog+ptcnjdA7HO5Z+nhFBbKTakq7LhX7NlJlVR5+Rh1LVbPOo+rQTv7scQ 35b2x4FG/Q8zY1oZt0Q3khkk0Ubm/9TEiv656q0t2DZEbB8+SR1+np2AmlP/+1CnnR3y m6cA==
X-Gm-Message-State: ALoCoQkRkIvkduIvMwF2O0R84io1W91wtRz3EzF+EG14raHLr6lMbPmKatKb2EpKmVEP+mzZ5V7a
MIME-Version: 1.0
X-Received: by 10.14.180.73 with SMTP id i49mr4524431eem.55.1382657337508; Thu, 24 Oct 2013 16:28:57 -0700 (PDT)
Received: by 10.14.203.199 with HTTP; Thu, 24 Oct 2013 16:28:57 -0700 (PDT)
In-Reply-To: <CAHixhFr6mnoQW5wLaYFsd1=pLUdq8D3Y4VFHtNcu4WSe+5CjuQ@mail.gmail.com>
References: <CAHixhFr6mnoQW5wLaYFsd1=pLUdq8D3Y4VFHtNcu4WSe+5CjuQ@mail.gmail.com>
Date: Thu, 24 Oct 2013 16:28:57 -0700
Message-ID: <CAG4zZZDBBCfDMSkZffwQupfw2P5cLa3QOOs5pKOFJWdEdDMCig@mail.gmail.com>
From: Joakim Erdfelt <joakim@intalio.com>
To: Adam Rice <ricea@google.com>
Content-Type: multipart/alternative; boundary=047d7b62226c72d96f04e984ff1d
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] SPNEGO with WebSockets
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 24 Oct 2013 23:29:05 -0000

--047d7b62226c72d96f04e984ff1d
Content-Type: text/plain; charset=ISO-8859-1

The Jetty Project [1] has several SPNEGO modules for hooking up SPNEGO into
the Java Servlet Engine.
(Providing Login Services [2], User Principals [3], User Identity [4],
Authenticators [5], etc ...)
While we have not tried a SPNEGO + websocket upgrade, we see no reason it
wouldn't work.

[1] http://eclipse.org/jetty/
[2]
http://download.eclipse.org/jetty/stable-9/apidocs/org/eclipse/jetty/security/SpnegoLoginService.html
[3]
http://download.eclipse.org/jetty/stable-9/apidocs/org/eclipse/jetty/security/SpnegoUserPrincipal.html
[4]
http://download.eclipse.org/jetty/stable-9/apidocs/org/eclipse/jetty/security/SpnegoUserIdentity.html
[5]
http://download.eclipse.org/jetty/stable-9/apidocs/org/eclipse/jetty/security/authentication/SpnegoAuthenticator.html


--
Joakim Erdfelt <joakim@intalio.com>
webtide.com <http://www.webtide.com/> - intalio.com/jetty
Expert advice, services and support from from the Jetty & CometD experts
eclipse.org/jetty - cometd.org


On Tue, Oct 22, 2013 at 8:17 PM, Adam Rice <ricea@google.com> wrote:

> Has anyone implemented SPNEGO authentication in conjunction with the
> WebSocket handshake? I am wondering whether it is necessary and also
> whether it is possible to do it in an RFC6455-compliant manner.
>
> Thanks,
> Adam Rice
>
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi
>
>

--047d7b62226c72d96f04e984ff1d
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">The Jetty Project [1] has several SPNEGO modules for hooki=
ng up SPNEGO into the Java Servlet Engine.<div>(Providing Login Services [2=
], User Principals [3], User Identity [4], Authenticators [5], etc ...)<br>
<div>While we have not tried a SPNEGO + websocket upgrade, we see no reason=
 it wouldn&#39;t work.</div></div><div><br></div><div>[1]=A0<a href=3D"http=
://eclipse.org/jetty/">http://eclipse.org/jetty/</a></div><div>[2]=A0<a hre=
f=3D"http://download.eclipse.org/jetty/stable-9/apidocs/org/eclipse/jetty/s=
ecurity/SpnegoLoginService.html">http://download.eclipse.org/jetty/stable-9=
/apidocs/org/eclipse/jetty/security/SpnegoLoginService.html</a></div>
<div>[3]=A0<a href=3D"http://download.eclipse.org/jetty/stable-9/apidocs/or=
g/eclipse/jetty/security/SpnegoUserPrincipal.html">http://download.eclipse.=
org/jetty/stable-9/apidocs/org/eclipse/jetty/security/SpnegoUserPrincipal.h=
tml</a></div>
<div>[4]=A0<a href=3D"http://download.eclipse.org/jetty/stable-9/apidocs/or=
g/eclipse/jetty/security/SpnegoUserIdentity.html">http://download.eclipse.o=
rg/jetty/stable-9/apidocs/org/eclipse/jetty/security/SpnegoUserIdentity.htm=
l</a></div>
<div>[5]=A0<a href=3D"http://download.eclipse.org/jetty/stable-9/apidocs/or=
g/eclipse/jetty/security/authentication/SpnegoAuthenticator.html">http://do=
wnload.eclipse.org/jetty/stable-9/apidocs/org/eclipse/jetty/security/authen=
tication/SpnegoAuthenticator.html</a></div>
<div><br></div></div><div class=3D"gmail_extra"><br clear=3D"all"><div><div=
 dir=3D"ltr"><div>--</div><div>Joakim Erdfelt &lt;<a href=3D"mailto:joakim@=
intalio.com" target=3D"_blank">joakim@intalio.com</a>&gt;</div><div><a href=
=3D"http://www.webtide.com/" target=3D"_blank">webtide.com</a>=A0- <a href=
=3D"http://intalio.com/jetty" target=3D"_blank">intalio.com/jetty</a></div>
<div><span>Expert advice, services and support from=A0</span><span>from the=
 Jetty &amp; CometD experts</span></div><div><a href=3D"http://eclipse.org/=
jetty/" target=3D"_blank">eclipse.org/jetty</a>=A0-=A0<a href=3D"http://com=
etd.org/" target=3D"_blank">cometd.org</a></div>
</div></div>
<br><br><div class=3D"gmail_quote">On Tue, Oct 22, 2013 at 8:17 PM, Adam Ri=
ce <span dir=3D"ltr">&lt;<a href=3D"mailto:ricea@google.com" target=3D"_bla=
nk">ricea@google.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
">
<div dir=3D"ltr">Has anyone implemented SPNEGO authentication in conjunctio=
n with the WebSocket handshake? I am wondering whether it is necessary and =
also whether it is possible to do it in an RFC6455-compliant manner.<div>
<br>
</div><div>Thanks,</div><div>Adam Rice</div></div>
<br>_______________________________________________<br>
hybi mailing list<br>
<a href=3D"mailto:hybi@ietf.org">hybi@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/hybi" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/hybi</a><br>
<br></blockquote></div><br></div>

--047d7b62226c72d96f04e984ff1d--

From jesse.mcconnell@gmail.com  Thu Oct 24 17:00:51 2013
Return-Path: <jesse.mcconnell@gmail.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8533811E8249 for <hybi@ietfa.amsl.com>; Thu, 24 Oct 2013 17:00:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hTXg+IuPEvLw for <hybi@ietfa.amsl.com>; Thu, 24 Oct 2013 17:00:50 -0700 (PDT)
Received: from mail-oa0-x230.google.com (mail-oa0-x230.google.com [IPv6:2607:f8b0:4003:c02::230]) by ietfa.amsl.com (Postfix) with ESMTP id B54BA11E8224 for <hybi@ietf.org>; Thu, 24 Oct 2013 17:00:50 -0700 (PDT)
Received: by mail-oa0-f48.google.com with SMTP id m17so269181oag.21 for <hybi@ietf.org>; Thu, 24 Oct 2013 17:00:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=FPNEJ5wrbeUNKZMQl6FfuL0ndVWdH3ceW9DdoBnZ3k4=; b=jv4k9r8AN7UU2T83i/LWw7AHh8Ed78oU+0W5snL8WN22IxNrf0jhZpBqVJ1bggTbU0 oRlVdrmXDuqhIcease4HZAiMKHjOkoRyOmyKduqaXPpqRkKvhKDDQdV2rF8REiXcRXJB 9u77kl2iKHl7lFQZ3JxKhDOZKWD75zDlwkjToxARJkZq76ZRJDTQouaTU75jTelt0Hau hVMMGEtkOpz4/zMhsRLNZqY9GPeG/q5moDCy5S4LyOs2K2uv2ePXFRgq+EMFSJ9I+c4z p1NIHQQCVKKjobdJoJVDVSqHBVuQ8YPXO6oY8P1P6tWiTFeNMcj5K+0Q7ex9EvZJ4VVq ZPOQ==
X-Received: by 10.182.22.18 with SMTP id z18mr731504obe.42.1382659250113; Thu, 24 Oct 2013 17:00:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.47.170 with HTTP; Thu, 24 Oct 2013 17:00:30 -0700 (PDT)
In-Reply-To: <CAG4zZZDBBCfDMSkZffwQupfw2P5cLa3QOOs5pKOFJWdEdDMCig@mail.gmail.com>
References: <CAHixhFr6mnoQW5wLaYFsd1=pLUdq8D3Y4VFHtNcu4WSe+5CjuQ@mail.gmail.com> <CAG4zZZDBBCfDMSkZffwQupfw2P5cLa3QOOs5pKOFJWdEdDMCig@mail.gmail.com>
From: Jesse McConnell <jesse.mcconnell@gmail.com>
Date: Thu, 24 Oct 2013 19:00:30 -0500
Message-ID: <CAPHPUs+PA7-9XTZByJoFxKD4cgUu1BPpH8o3eVd_J+EZAE1PkA@mail.gmail.com>
To: Joakim Erdfelt <joakim@intalio.com>
Content-Type: text/plain; charset=UTF-8
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] SPNEGO with WebSockets
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Fri, 25 Oct 2013 00:00:51 -0000

and some docs on all that:

http://www.eclipse.org/jetty/documentation/current/spnego-support.html
--
jesse mcconnell
jesse.mcconnell@gmail.com


On Thu, Oct 24, 2013 at 6:28 PM, Joakim Erdfelt <joakim@intalio.com> wrote:
> The Jetty Project [1] has several SPNEGO modules for hooking up SPNEGO into
> the Java Servlet Engine.
> (Providing Login Services [2], User Principals [3], User Identity [4],
> Authenticators [5], etc ...)
> While we have not tried a SPNEGO + websocket upgrade, we see no reason it
> wouldn't work.
>
> [1] http://eclipse.org/jetty/
> [2]
> http://download.eclipse.org/jetty/stable-9/apidocs/org/eclipse/jetty/security/SpnegoLoginService.html
> [3]
> http://download.eclipse.org/jetty/stable-9/apidocs/org/eclipse/jetty/security/SpnegoUserPrincipal.html
> [4]
> http://download.eclipse.org/jetty/stable-9/apidocs/org/eclipse/jetty/security/SpnegoUserIdentity.html
> [5]
> http://download.eclipse.org/jetty/stable-9/apidocs/org/eclipse/jetty/security/authentication/SpnegoAuthenticator.html
>
>
> --
> Joakim Erdfelt <joakim@intalio.com>
> webtide.com - intalio.com/jetty
> Expert advice, services and support from from the Jetty & CometD experts
> eclipse.org/jetty - cometd.org
>
>
> On Tue, Oct 22, 2013 at 8:17 PM, Adam Rice <ricea@google.com> wrote:
>>
>> Has anyone implemented SPNEGO authentication in conjunction with the
>> WebSocket handshake? I am wondering whether it is necessary and also whether
>> it is possible to do it in an RFC6455-compliant manner.
>>
>> Thanks,
>> Adam Rice
>>
>> _______________________________________________
>> hybi mailing list
>> hybi@ietf.org
>> https://www.ietf.org/mailman/listinfo/hybi
>>
>
>
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi
>

From ricea@google.com  Thu Oct 24 21:10:04 2013
Return-Path: <ricea@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C2BE11E80F5 for <hybi@ietfa.amsl.com>; Thu, 24 Oct 2013 21:10:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6grQUQEs9Fxs for <hybi@ietfa.amsl.com>; Thu, 24 Oct 2013 21:10:03 -0700 (PDT)
Received: from mail-oa0-x22a.google.com (mail-oa0-x22a.google.com [IPv6:2607:f8b0:4003:c02::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 26FE411E810D for <hybi@ietf.org>; Thu, 24 Oct 2013 21:10:00 -0700 (PDT)
Received: by mail-oa0-f42.google.com with SMTP id k14so446779oag.1 for <hybi@ietf.org>; Thu, 24 Oct 2013 21:09:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=tocjh5nKJtFUNuq4mMhQhA7m2QGZ0E9LvPKpLmkFMGE=; b=hBqDSn9andFv9FujOG9MXu+fHr3MGmtSUitSGNhtWevdbsBc6ppiwwOFm+6U+ZOt2s 7E57GBJ+96wiJFc9O3QK50CkgBRdO3vdt8A3mt5PKWMguOVa8LLogXL+Aasu4EcPz3WL A1XR06M2FuUOnuocjMtsTqDTNQSXZnR5f1OV7u1/uyZ1w1chwDI6klRxq/cwv3mxvzD4 Vkg3XkiJhS/FWCxi16vD0/IyxjZKAVfaFrZDg/rNp7x0AywXUtp/AlAfOIonFLot64lR VBEkiSjkUlgUxp+ek1LitCA+pS8UbVAzSkmkRbhBAfNGkrWjjcMSdX8W3VxfqkT5ixhZ 9Epw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=tocjh5nKJtFUNuq4mMhQhA7m2QGZ0E9LvPKpLmkFMGE=; b=Brda6Aq51GVEGFxeiA1kqDckr4CbKXPiwLSegWYN65Y7z9CGdWcoOKxrVcQ8OBVKzE R8/UvrPMtN15aS70UcH4x0Vua7JKw6BV8G4ilu2Ofc606lgfu+osm5bG+6YNweVjOjbV eXLF05xLcUD0bveqKGt099KqeJoOviatV1xGib71BXocAAxUgvLImFLheyrH5lAvc5Dq OVfYukz5TMLTCDMASPetci8wOjDvlpAg6vw0AjTq75Y/faRB5ns+Z5QUCLw7+OVNv+eK 817t1QKpuBUwKnygmXBwoXIKHRw7xLyYyMvZ5L/wyCOTr8op2nPrjcK52k0Snlvvq9Lo omQw==
X-Gm-Message-State: ALoCoQnSs/8ws6666Eq7gFKUdtacroON34DI9U2Rr2IHytkOgNmGlHJ/MliJE6KAncLj6GH8QDhSS7zOS3Oj3PetD8WkwT46C3KOGBP4lYIXcKAn7E0rexlsU066k/k/i6QeZXUQGJvoDgV9synekSydILEtdDaYfoSJmV3nr34XSoTnU16p1+wZyaYYNgoNfylP22V9AUPK
MIME-Version: 1.0
X-Received: by 10.182.227.136 with SMTP id sa8mr1363492obc.39.1382674199448; Thu, 24 Oct 2013 21:09:59 -0700 (PDT)
Received: by 10.182.39.36 with HTTP; Thu, 24 Oct 2013 21:09:59 -0700 (PDT)
In-Reply-To: <CAPHPUs+PA7-9XTZByJoFxKD4cgUu1BPpH8o3eVd_J+EZAE1PkA@mail.gmail.com>
References: <CAHixhFr6mnoQW5wLaYFsd1=pLUdq8D3Y4VFHtNcu4WSe+5CjuQ@mail.gmail.com> <CAG4zZZDBBCfDMSkZffwQupfw2P5cLa3QOOs5pKOFJWdEdDMCig@mail.gmail.com> <CAPHPUs+PA7-9XTZByJoFxKD4cgUu1BPpH8o3eVd_J+EZAE1PkA@mail.gmail.com>
Date: Fri, 25 Oct 2013 13:09:59 +0900
Message-ID: <CAHixhFrzrAOU6=Xs7u_c2xCxCKedzoJtFqdAjeyqQPohSXMfgQ@mail.gmail.com>
From: Adam Rice <ricea@google.com>
To: Jesse McConnell <jesse.mcconnell@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c303507faf8f04e988ec9c
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] SPNEGO with WebSockets
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Fri, 25 Oct 2013 04:10:04 -0000

--001a11c303507faf8f04e988ec9c
Content-Type: text/plain; charset=ISO-8859-1

Thank you. If someone has already tried it please speak up, otherwise I
will give it a try when I have some time.


On 25 October 2013 09:00, Jesse McConnell <jesse.mcconnell@gmail.com> wrote:

> and some docs on all that:
>
> http://www.eclipse.org/jetty/documentation/current/spnego-support.html
> --
> jesse mcconnell
> jesse.mcconnell@gmail.com
>
>
> On Thu, Oct 24, 2013 at 6:28 PM, Joakim Erdfelt <joakim@intalio.com>
> wrote:
> > The Jetty Project [1] has several SPNEGO modules for hooking up SPNEGO
> into
> > the Java Servlet Engine.
> > (Providing Login Services [2], User Principals [3], User Identity [4],
> > Authenticators [5], etc ...)
> > While we have not tried a SPNEGO + websocket upgrade, we see no reason it
> > wouldn't work.
> >
> > [1] http://eclipse.org/jetty/
> > [2]
> >
> http://download.eclipse.org/jetty/stable-9/apidocs/org/eclipse/jetty/security/SpnegoLoginService.html
> > [3]
> >
> http://download.eclipse.org/jetty/stable-9/apidocs/org/eclipse/jetty/security/SpnegoUserPrincipal.html
> > [4]
> >
> http://download.eclipse.org/jetty/stable-9/apidocs/org/eclipse/jetty/security/SpnegoUserIdentity.html
> > [5]
> >
> http://download.eclipse.org/jetty/stable-9/apidocs/org/eclipse/jetty/security/authentication/SpnegoAuthenticator.html
> >
> >
> > --
> > Joakim Erdfelt <joakim@intalio.com>
> > webtide.com - intalio.com/jetty
> > Expert advice, services and support from from the Jetty & CometD experts
> > eclipse.org/jetty - cometd.org
> >
> >
> > On Tue, Oct 22, 2013 at 8:17 PM, Adam Rice <ricea@google.com> wrote:
> >>
> >> Has anyone implemented SPNEGO authentication in conjunction with the
> >> WebSocket handshake? I am wondering whether it is necessary and also
> whether
> >> it is possible to do it in an RFC6455-compliant manner.
> >>
> >> Thanks,
> >> Adam Rice
> >>
> >> _______________________________________________
> >> hybi mailing list
> >> hybi@ietf.org
> >> https://www.ietf.org/mailman/listinfo/hybi
> >>
> >
> >
> > _______________________________________________
> > hybi mailing list
> > hybi@ietf.org
> > https://www.ietf.org/mailman/listinfo/hybi
> >
>

--001a11c303507faf8f04e988ec9c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thank you. If someone has already tried it please speak up=
, otherwise I will give it a try when I have some time.</div><div class=3D"=
gmail_extra"><br><br><div class=3D"gmail_quote">On 25 October 2013 09:00, J=
esse McConnell <span dir=3D"ltr">&lt;<a href=3D"mailto:jesse.mcconnell@gmai=
l.com" target=3D"_blank">jesse.mcconnell@gmail.com</a>&gt;</span> wrote:<br=
>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">and some docs on all that:<br>
<br>
<a href=3D"http://www.eclipse.org/jetty/documentation/current/spnego-suppor=
t.html" target=3D"_blank">http://www.eclipse.org/jetty/documentation/curren=
t/spnego-support.html</a><br>
--<br>
jesse mcconnell<br>
<a href=3D"mailto:jesse.mcconnell@gmail.com">jesse.mcconnell@gmail.com</a><=
br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
On Thu, Oct 24, 2013 at 6:28 PM, Joakim Erdfelt &lt;<a href=3D"mailto:joaki=
m@intalio.com">joakim@intalio.com</a>&gt; wrote:<br>
&gt; The Jetty Project [1] has several SPNEGO modules for hooking up SPNEGO=
 into<br>
&gt; the Java Servlet Engine.<br>
&gt; (Providing Login Services [2], User Principals [3], User Identity [4],=
<br>
&gt; Authenticators [5], etc ...)<br>
&gt; While we have not tried a SPNEGO + websocket upgrade, we see no reason=
 it<br>
&gt; wouldn&#39;t work.<br>
&gt;<br>
&gt; [1] <a href=3D"http://eclipse.org/jetty/" target=3D"_blank">http://ecl=
ipse.org/jetty/</a><br>
&gt; [2]<br>
&gt; <a href=3D"http://download.eclipse.org/jetty/stable-9/apidocs/org/ecli=
pse/jetty/security/SpnegoLoginService.html" target=3D"_blank">http://downlo=
ad.eclipse.org/jetty/stable-9/apidocs/org/eclipse/jetty/security/SpnegoLogi=
nService.html</a><br>

&gt; [3]<br>
&gt; <a href=3D"http://download.eclipse.org/jetty/stable-9/apidocs/org/ecli=
pse/jetty/security/SpnegoUserPrincipal.html" target=3D"_blank">http://downl=
oad.eclipse.org/jetty/stable-9/apidocs/org/eclipse/jetty/security/SpnegoUse=
rPrincipal.html</a><br>

&gt; [4]<br>
&gt; <a href=3D"http://download.eclipse.org/jetty/stable-9/apidocs/org/ecli=
pse/jetty/security/SpnegoUserIdentity.html" target=3D"_blank">http://downlo=
ad.eclipse.org/jetty/stable-9/apidocs/org/eclipse/jetty/security/SpnegoUser=
Identity.html</a><br>

&gt; [5]<br>
&gt; <a href=3D"http://download.eclipse.org/jetty/stable-9/apidocs/org/ecli=
pse/jetty/security/authentication/SpnegoAuthenticator.html" target=3D"_blan=
k">http://download.eclipse.org/jetty/stable-9/apidocs/org/eclipse/jetty/sec=
urity/authentication/SpnegoAuthenticator.html</a><br>

&gt;<br>
&gt;<br>
&gt; --<br>
&gt; Joakim Erdfelt &lt;<a href=3D"mailto:joakim@intalio.com">joakim@intali=
o.com</a>&gt;<br>
&gt; <a href=3D"http://webtide.com" target=3D"_blank">webtide.com</a> - <a =
href=3D"http://intalio.com/jetty" target=3D"_blank">intalio.com/jetty</a><b=
r>
&gt; Expert advice, services and support from from the Jetty &amp; CometD e=
xperts<br>
&gt; <a href=3D"http://eclipse.org/jetty" target=3D"_blank">eclipse.org/jet=
ty</a> - <a href=3D"http://cometd.org" target=3D"_blank">cometd.org</a><br>
&gt;<br>
&gt;<br>
&gt; On Tue, Oct 22, 2013 at 8:17 PM, Adam Rice &lt;<a href=3D"mailto:ricea=
@google.com">ricea@google.com</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; Has anyone implemented SPNEGO authentication in conjunction with t=
he<br>
&gt;&gt; WebSocket handshake? I am wondering whether it is necessary and al=
so whether<br>
&gt;&gt; it is possible to do it in an RFC6455-compliant manner.<br>
&gt;&gt;<br>
&gt;&gt; Thanks,<br>
&gt;&gt; Adam Rice<br>
&gt;&gt;<br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; hybi mailing list<br>
&gt;&gt; <a href=3D"mailto:hybi@ietf.org">hybi@ietf.org</a><br>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/hybi" target=3D"_=
blank">https://www.ietf.org/mailman/listinfo/hybi</a><br>
&gt;&gt;<br>
&gt;<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; hybi mailing list<br>
&gt; <a href=3D"mailto:hybi@ietf.org">hybi@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/hybi" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/hybi</a><br>
&gt;<br>
</div></div></blockquote></div><br></div>

--001a11c303507faf8f04e988ec9c--

From jesse.mcconnell@gmail.com  Fri Oct 25 07:14:57 2013
Return-Path: <jesse.mcconnell@gmail.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A399E11E81A8 for <hybi@ietfa.amsl.com>; Fri, 25 Oct 2013 07:14:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 71CTsdyB8G43 for <hybi@ietfa.amsl.com>; Fri, 25 Oct 2013 07:14:54 -0700 (PDT)
Received: from mail-oa0-x22e.google.com (mail-oa0-x22e.google.com [IPv6:2607:f8b0:4003:c02::22e]) by ietfa.amsl.com (Postfix) with ESMTP id CE2F411E8270 for <hybi@ietf.org>; Fri, 25 Oct 2013 07:14:51 -0700 (PDT)
Received: by mail-oa0-f46.google.com with SMTP id g12so959617oah.5 for <hybi@ietf.org>; Fri, 25 Oct 2013 07:14:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=7GpLM1KPjRVi0xQiAxvuBPXPmkOEbRboob0Qr1a1gMA=; b=KQ5zqyw/Kk6Um+YQJ9QXqzFlJxmFaPNNdcTwzSHQR22Bcvb+eAxTp/Uykd2TAxgtbM JxWL0bNlXTvOXGlv4pYNTW546pet7Vl85ZSV4cCnoY5Ic8TU1t52PsknAm1s7B8tQAWT 9XtDjnGxzgmKsXqWnArFnTYsO/tPHaBkdOhpGo8NP1HwL1YSro+JyLeF3JBlst8VFRQm KydhgXbz0EVUJf1SJm/tKcrLtt04p6Fkmb/u+ApyNCgXziJKt+sQ2NwHJ/DwbKmGU6w4 XzbxobCTs0P/Xfcsgwtb//vgyHKzgDEsigA0P0RoBYmT0C5lPcp4PjOOrty5h53Nak3e ayKA==
X-Received: by 10.60.130.163 with SMTP id of3mr27950oeb.96.1382710491376; Fri, 25 Oct 2013 07:14:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.47.170 with HTTP; Fri, 25 Oct 2013 07:14:31 -0700 (PDT)
In-Reply-To: <CAHixhFrzrAOU6=Xs7u_c2xCxCKedzoJtFqdAjeyqQPohSXMfgQ@mail.gmail.com>
References: <CAHixhFr6mnoQW5wLaYFsd1=pLUdq8D3Y4VFHtNcu4WSe+5CjuQ@mail.gmail.com> <CAG4zZZDBBCfDMSkZffwQupfw2P5cLa3QOOs5pKOFJWdEdDMCig@mail.gmail.com> <CAPHPUs+PA7-9XTZByJoFxKD4cgUu1BPpH8o3eVd_J+EZAE1PkA@mail.gmail.com> <CAHixhFrzrAOU6=Xs7u_c2xCxCKedzoJtFqdAjeyqQPohSXMfgQ@mail.gmail.com>
From: Jesse McConnell <jesse.mcconnell@gmail.com>
Date: Fri, 25 Oct 2013 09:14:31 -0500
Message-ID: <CAPHPUs+ATYawKZka9AHX0zYX2shbPRntDF+Uh39f+xDZzf4yxg@mail.gmail.com>
To: Adam Rice <ricea@google.com>
Content-Type: text/plain; charset=UTF-8
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] SPNEGO with WebSockets
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Fri, 25 Oct 2013 14:14:59 -0000

we would give it a try but none of us have access to the environment
required to test that any longer, should be straight forward though so
long as all of the bits in the Note: section at the bottom are taken
into account

if you have issues lemme know, I wired that stuff up originally

cheers,
jesse
--
jesse mcconnell
jesse.mcconnell@gmail.com


On Thu, Oct 24, 2013 at 11:09 PM, Adam Rice <ricea@google.com> wrote:
> Thank you. If someone has already tried it please speak up, otherwise I will
> give it a try when I have some time.
>
>
> On 25 October 2013 09:00, Jesse McConnell <jesse.mcconnell@gmail.com> wrote:
>>
>> and some docs on all that:
>>
>> http://www.eclipse.org/jetty/documentation/current/spnego-support.html
>> --
>> jesse mcconnell
>> jesse.mcconnell@gmail.com
>>
>>
>> On Thu, Oct 24, 2013 at 6:28 PM, Joakim Erdfelt <joakim@intalio.com>
>> wrote:
>> > The Jetty Project [1] has several SPNEGO modules for hooking up SPNEGO
>> > into
>> > the Java Servlet Engine.
>> > (Providing Login Services [2], User Principals [3], User Identity [4],
>> > Authenticators [5], etc ...)
>> > While we have not tried a SPNEGO + websocket upgrade, we see no reason
>> > it
>> > wouldn't work.
>> >
>> > [1] http://eclipse.org/jetty/
>> > [2]
>> >
>> > http://download.eclipse.org/jetty/stable-9/apidocs/org/eclipse/jetty/security/SpnegoLoginService.html
>> > [3]
>> >
>> > http://download.eclipse.org/jetty/stable-9/apidocs/org/eclipse/jetty/security/SpnegoUserPrincipal.html
>> > [4]
>> >
>> > http://download.eclipse.org/jetty/stable-9/apidocs/org/eclipse/jetty/security/SpnegoUserIdentity.html
>> > [5]
>> >
>> > http://download.eclipse.org/jetty/stable-9/apidocs/org/eclipse/jetty/security/authentication/SpnegoAuthenticator.html
>> >
>> >
>> > --
>> > Joakim Erdfelt <joakim@intalio.com>
>> > webtide.com - intalio.com/jetty
>> > Expert advice, services and support from from the Jetty & CometD experts
>> > eclipse.org/jetty - cometd.org
>> >
>> >
>> > On Tue, Oct 22, 2013 at 8:17 PM, Adam Rice <ricea@google.com> wrote:
>> >>
>> >> Has anyone implemented SPNEGO authentication in conjunction with the
>> >> WebSocket handshake? I am wondering whether it is necessary and also
>> >> whether
>> >> it is possible to do it in an RFC6455-compliant manner.
>> >>
>> >> Thanks,
>> >> Adam Rice
>> >>
>> >> _______________________________________________
>> >> hybi mailing list
>> >> hybi@ietf.org
>> >> https://www.ietf.org/mailman/listinfo/hybi
>> >>
>> >
>> >
>> > _______________________________________________
>> > hybi mailing list
>> > hybi@ietf.org
>> > https://www.ietf.org/mailman/listinfo/hybi
>> >
>
>

From tyoshino@google.com  Wed Oct 30 03:53:11 2013
Return-Path: <tyoshino@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA09621F9EBE for <hybi@ietfa.amsl.com>; Wed, 30 Oct 2013 03:53:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[AWL=0.078,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5P0zTjnPUhw0 for <hybi@ietfa.amsl.com>; Wed, 30 Oct 2013 03:53:11 -0700 (PDT)
Received: from mail-we0-x234.google.com (mail-we0-x234.google.com [IPv6:2a00:1450:400c:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id 4654021F9FA5 for <hybi@ietf.org>; Wed, 30 Oct 2013 03:53:07 -0700 (PDT)
Received: by mail-we0-f180.google.com with SMTP id q59so1079980wes.39 for <hybi@ietf.org>; Wed, 30 Oct 2013 03:53:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=DiNpoIMip+EhYBSz4USVv4tcLZlkEb7WA6CWWL3pgJw=; b=AEhk3bwD9itpEq+QuAZHEBT+c8oEu94oEBOpIkYj/S6y5GjUnktMSCX6Sbv9WCzHaC XI5owg1MVu7pSbpFqW3HgvRXQMeISCZIVTMz1vorLFm0FpLXRJx2VvzCthQ8PLhm0GOt SlyH8i90QUzMDZe7ogweN7M/mKtg7dLcH+bVqP+4ApuV5W3oyMqCmbk1dEkPiHLGMUIK jyDXlnYuiztWufBpM7SmVoJrhbvdNxYWH8IQwLmtr8VXf3C/BK1crPjw19zNilQXxrBW uLzJ4qZiR1XDl6kJsnvpjU/c7TzI0elmSf62SmLvVQXskTh976bSHdnff44p25W5GEm5 NLpw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-type; bh=DiNpoIMip+EhYBSz4USVv4tcLZlkEb7WA6CWWL3pgJw=; b=ZEh9cfiOn5xv9T2kkLkSCtICTxE4UHOiG6qmXGrSIxHnJZ94ywWMH+H4fSMP+0WV/c 0PXNY7F8hXNmx5s9E6vE3LRpi4g00LDHVvJ0kjsd5dFr6+eG6v4BFj+lQaNJ0BleMPE0 xsq3eCVVWa80VwPAHbrWRJcHaqWgNb9eYSVz8fDyTYRkPDeM1rAZ81jWz3DA43Z6bRlo 4bDO36IYx96a6Hpu9DrED30SVdrkIkvzrMgJUH/uW1UP8DmD+G965O+s20X53y5scOl7 9TY7WEusvkuRBm27Ovh4uK41SmJZIo3MN/GNqvsZleLq7jZeBPT86K7OwjoF966wm4jx ENDQ==
X-Gm-Message-State: ALoCoQmpfu/Gqvi1wMb2rxV/UJAnvTwIIvlRtJxgpxAyYjvbTBlpvFXv224ianX/JmU2TebXFErUdYNtQJxTPRNLA1SteECF0+b0c/zXeHfAQN29U0vB5eOde2vDDtzloMERvfZLU5713hkiX/se9p33xJZHQ3n/Ty25TKD98lD6d7sGSPmUwyFQHc+zwpujhQr7l8JRc5TQ
X-Received: by 10.180.188.197 with SMTP id gc5mr2156414wic.42.1383130387359; Wed, 30 Oct 2013 03:53:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.15.133 with HTTP; Wed, 30 Oct 2013 03:52:47 -0700 (PDT)
From: Takeshi Yoshino <tyoshino@google.com>
Date: Wed, 30 Oct 2013 19:52:47 +0900
Message-ID: <CAH9hSJbW7FkJX+Le+euAGcX5tJoddV-dWNfk_aQfjFQfNOwx5g@mail.gmail.com>
To: "hybi@ietf.org" <hybi@ietf.org>
Content-Type: multipart/alternative; boundary=001a11c3841a6ac5b204e9f323c5
Subject: [hybi] Dispatch an error event when no handshake response is received?
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 30 Oct 2013 10:53:11 -0000

--001a11c3841a6ac5b204e9f323c5
Content-Type: text/plain; charset=ISO-8859-1

I think it makes sense to _fail_ when the underlying connection is opened
successfully but is closed by the server before the client receives a
handshake response.

But it's not explicitly specified in RFC 6455.

Maybe we can refer to this text to handle the case by _fail_.

> If the server's response does not conform to the requirements for the
> server's handshake as defined in this section and in Section 4.2.2,
> the client MUST _Fail the WebSocket Connection_.

Any concern?

--001a11c3841a6ac5b204e9f323c5
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I think it makes sense to _fail_ when the underlying conne=
ction is opened successfully but is closed by the server before the client =
receives a handshake response.
<div><br></div><div>But it&#39;s not explicitly specified in RFC 6455.</div=
><div><br></div><div>Maybe we can refer to this text to handle the case by =
_fail_.</div><div><br></div><div><div>&gt; If the server&#39;s response doe=
s not conform to the requirements for the</div>

<div>&gt; server&#39;s handshake as defined in this section and in Section =
4.2.2,</div><div>&gt; the client MUST _Fail the WebSocket Connection_.</div=
></div><div><br></div><div>Any concern?</div></div>

--001a11c3841a6ac5b204e9f323c5--

From tyoshino@google.com  Wed Oct 30 05:39:45 2013
Return-Path: <tyoshino@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3E7C21E8083 for <hybi@ietfa.amsl.com>; Wed, 30 Oct 2013 05:39:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d3p6nn1QC2Su for <hybi@ietfa.amsl.com>; Wed, 30 Oct 2013 05:39:45 -0700 (PDT)
Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) by ietfa.amsl.com (Postfix) with ESMTP id 15ECE11E80FA for <hybi@ietf.org>; Wed, 30 Oct 2013 05:39:44 -0700 (PDT)
Received: by mail-wi0-f182.google.com with SMTP id ez12so1358052wid.9 for <hybi@ietf.org>; Wed, 30 Oct 2013 05:39:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=KF8EKKYeDDWqRj/3hCNgAIz7KHpuju4TP/eufFTC51c=; b=TRfKxhNvRL4wh1+CKghSJiF22HF82ke2MigUVBJOv4P68dCfAs1uboQASvUIQ9FvEk PvAnGyOAM+ozh0FVBSDiwOJECRAzYahmW7taSIADPt8g6MQ2ypEZXgxXYfu4c8VEPrPX rR012xSxnPLYLXgqTYhoOmU0jbVJYocwB/gwQdCiZUKIl30CgxG+VF/bheiV7FhhvpM2 h0Wh8y+aMM6vuY4xOWxD6iX+LQtxLSlAIAjs+TtWUZHVeN/lBz6XaFK3U2yH8YezCda3 SGiG9xoQp8tyPkjh3E0pzGlZbgg+HNs8TIWKnwi8aMc5uyIsaYX//pUx2ZArKLJZJPWw Qzag==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-type; bh=KF8EKKYeDDWqRj/3hCNgAIz7KHpuju4TP/eufFTC51c=; b=ckOM2OEXhkqS1xjRxOECAIu5RYlUdrv86Qdji8zaybQPUJQZhaD9qgZ0gVdzhQdXrM pGOniOEiLC5WbX5+cTEpio2myQkrsBTPmogwZ+AIax0M2IDU0Saomxzu1Ykh7/h1aK9r qchMieEFKlu2v8UOWkPudI2PLiSt4P4B+D2KsKiVk2g8YIpayQd7S40In+QeRafhAVmG kU0ZRSRV6zV4QeSBM6ckJ8C7G0WN0OcI78LeZ1Ez/blUjX0YH51Rf7rzcONrt28A3b3K akaK0vaMyv3XaVOf3iG5WoYM8+kd45w3nJGI+7F7xZ5PsQ8LsWgplrwrslWlXttmzfoV e6eA==
X-Gm-Message-State: ALoCoQkdywYk9w6yhhY9Id3YSK5DTwkSIrLd4SV8QKcn2nc5H2yrgbj0JsdRk+atgrRKUq7e5ES2N42MHlqfswf/zp9l8OPah5Lh7K9iG0/vXWtIBzuyCN09KKbXobrSS8Y3ZnAP5CrqiSR86W1TUDfv39KJTuGy+qU5z+zk4acAm4hDdsJyDSRnZMhw6pRHjHjaJnZPW2rG
X-Received: by 10.194.118.169 with SMTP id kn9mr1553290wjb.71.1383136784052; Wed, 30 Oct 2013 05:39:44 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.15.133 with HTTP; Wed, 30 Oct 2013 05:39:23 -0700 (PDT)
From: Takeshi Yoshino <tyoshino@google.com>
Date: Wed, 30 Oct 2013 21:39:23 +0900
Message-ID: <CAH9hSJaVoTo4YyNY=sjoFGSbxOgbvD6KdtzEum_YYneYjRnerQ@mail.gmail.com>
To: "hybi@ietf.org" <hybi@ietf.org>
Content-Type: multipart/alternative; boundary=089e01176463b16d4104e9f4a071
Subject: [hybi] Call for comment: Making "no context takeover" optional
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 30 Oct 2013 12:39:45 -0000

--089e01176463b16d4104e9f4a071
Content-Type: text/plain; charset=ISO-8859-1

Any comment about Tobias's proposal to make "no context takeover" support
optional for client?
http://www.ietf.org/mail-archive/web/hybi/current/msg10236.html
 http://www.ietf.org/mail-archive/web/hybi/current/msg10237.html

Unless we receive more support, I'd like to skip it.

--089e01176463b16d4104e9f4a071
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Any comment about Tobias&#39;s proposal to make &quot=
;no context takeover&quot; support optional for client?</div><div><a href=
=3D"http://www.ietf.org/mail-archive/web/hybi/current/msg10236.html">http:/=
/www.ietf.org/mail-archive/web/hybi/current/msg10236.html</a><br>

</div>
<div><a href=3D"http://www.ietf.org/mail-archive/web/hybi/current/msg10237.=
html">http://www.ietf.org/mail-archive/web/hybi/current/msg10237.html</a><b=
r></div><div><br></div><div>Unless we receive more support, I&#39;d like to=
 skip it.</div>

</div>

--089e01176463b16d4104e9f4a071--

From tobias.oberstein@tavendo.de  Wed Oct 30 05:49:57 2013
Return-Path: <tobias.oberstein@tavendo.de>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D564011E813F for <hybi@ietfa.amsl.com>; Wed, 30 Oct 2013 05:49:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.546
X-Spam-Level: 
X-Spam-Status: No, score=-2.546 tagged_above=-999 required=5 tests=[AWL=0.053,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wik8HE0zhm4n for <hybi@ietfa.amsl.com>; Wed, 30 Oct 2013 05:49:52 -0700 (PDT)
Received: from EXHUB020-3.exch020.serverdata.net (exhub020-3.exch020.serverdata.net [206.225.164.30]) by ietfa.amsl.com (Postfix) with ESMTP id AFB9011E815A for <hybi@ietf.org>; Wed, 30 Oct 2013 05:49:52 -0700 (PDT)
Received: from EXVMBX020-12.exch020.serverdata.net ([169.254.3.240]) by EXHUB020-3.exch020.serverdata.net ([206.225.164.30]) with mapi; Wed, 30 Oct 2013 05:49:51 -0700
From: Tobias Oberstein <tobias.oberstein@tavendo.de>
To: Takeshi Yoshino <tyoshino@google.com>, "hybi@ietf.org" <hybi@ietf.org>
Date: Wed, 30 Oct 2013 05:49:51 -0700
Thread-Topic: [hybi] Dispatch an error event when no handshake response is received?
Thread-Index: Ac7VXj1J9PmgbRkESne6C2Mfn82ejQADy/Rg
Message-ID: <634914A010D0B943A035D226786325D44469E6FE20@EXVMBX020-12.exch020.serverdata.net>
References: <SPAM_CAH9hSJbW7FkJX+Le+euAGcX5tJoddV-dWNfk_aQfjFQfNOwx5g@mail.gmail.com>
In-Reply-To: <SPAM_CAH9hSJbW7FkJX+Le+euAGcX5tJoddV-dWNfk_aQfjFQfNOwx5g@mail.gmail.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [hybi] Dispatch an error event when no handshake response is	received?
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 30 Oct 2013 12:49:58 -0000

>I think it makes sense to _fail_ when the underlying connection is opened =
successfully but is closed by the server before the client receives a hands=
hake response.=20

Not sure I understand:

When a server encounters an error during handshake processing, the only 2 o=
ptions it has are:
S1) return HTTP error
S2) immediately drop/close the underlying TCP

I think both are fine, S1 being more "cooperative", but S1 more resilant to=
 DoS.

When a client encounters an error during handshake processing it might have=
 2 options (depending on error severity):

C1) perform a WS closing HS
C2) drop/close the underlying TCP

Not sure if C1 makes any sense .. since the client cannot be sure the serve=
r actually is a WS server in this case.

E.g. if a mandatory WS HS response header is missing: C2
If WS subprotocol mismatch, client _could_ perform C1.

Not sure.

/Tobias

From tyoshino@google.com  Wed Oct 30 05:59:55 2013
Return-Path: <tyoshino@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C62011E81D6 for <hybi@ietfa.amsl.com>; Wed, 30 Oct 2013 05:59:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.905
X-Spam-Level: 
X-Spam-Status: No, score=-1.905 tagged_above=-999 required=5 tests=[AWL=0.072,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pIfuWTqThRI6 for <hybi@ietfa.amsl.com>; Wed, 30 Oct 2013 05:59:55 -0700 (PDT)
Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 2125711E8149 for <hybi@ietf.org>; Wed, 30 Oct 2013 05:59:50 -0700 (PDT)
Received: by mail-wi0-f170.google.com with SMTP id ex4so4060428wid.5 for <hybi@ietf.org>; Wed, 30 Oct 2013 05:59:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=T8CPA2CQTvDYO4HpxbaW3T82vTXHxwCaoAo7Jqnz3lk=; b=pwmpr4VbYjxivnY7nKvN4NuvlruoieJ3E0b8TH3B3XSdni1LPnWUL/cn9lj5SWnF08 NN42F8O51thd5Kr6O6D+2V8iYU1QTcqogcUYfXQK8Dr5+Vcpq2qYLxKTn8JhlYkbWyUC MwE+Dj0xqCC8PDTKY/JZ7zFgBw1BNlYykDavm8MnkZVlKHjcpssRKFD6bMBtyng9osjX UHtgJrLHTK3McokYJnDThgLBmdsAKUtyDTPnOAxYmqjH6H0fjd3dOcNFUWf4f3ntk5eL ceaShi6uOAfntt0aN5bmmDRKqvlmnGiAXH3dg7l2p2O59abu9I3/qKvXmQIJGKciZJE0 pmoA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=T8CPA2CQTvDYO4HpxbaW3T82vTXHxwCaoAo7Jqnz3lk=; b=gNYXbx6LZjbtEfqYesLM3D8YQVUx3lCj92XTkJ3KlYxs/OH2Oxsg/ExOKAGVz065AB w8HzWu0bFpfjZahuise3Yb8b3+tW8hdACDAl9QrO43I8TpdjcCcIF18iUNY51dRvITU5 tuQCk08+79zUDavTuspTnvfl/kyxoQK5s/wiWdk4Q2GIDbsBDtvas8OoDJ8hkVQ5zBbk xxyBoLRCiUuTtWop44TLS4Qrzp66VrMvaJ6QqwD+lDoHMnkHJjtuNcgtMxCehHwx/Y41 2XNddR3rnb2L11wFl2dQT8EchWU4TwEohFY7pTHdbyWQlxe+H7T5f1Jnc+GaHu8nf/ga ELPg==
X-Gm-Message-State: ALoCoQnconC7fxjdvR4C4Py+Dfgikj2mxxmyqt+YQ/pIPyGzqoIiHu+ABXBrwh2CDAGpBGri8kjbjv0o97yVoLxZJinONVfbMoStuZTdK76Zm06bSgv8ig7cB3fDX39iivo5pj+fTo/n2mQ7YqFDc7bYkuDF+QEVopqW/+YtTjipMyXWrrADZ3+YliDtKqSjmMIWnNnVawt3
X-Received: by 10.194.60.73 with SMTP id f9mr1800668wjr.65.1383137990238; Wed, 30 Oct 2013 05:59:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.15.133 with HTTP; Wed, 30 Oct 2013 05:59:30 -0700 (PDT)
In-Reply-To: <634914A010D0B943A035D226786325D44469E6FE20@EXVMBX020-12.exch020.serverdata.net>
References: <SPAM_CAH9hSJbW7FkJX+Le+euAGcX5tJoddV-dWNfk_aQfjFQfNOwx5g@mail.gmail.com> <634914A010D0B943A035D226786325D44469E6FE20@EXVMBX020-12.exch020.serverdata.net>
From: Takeshi Yoshino <tyoshino@google.com>
Date: Wed, 30 Oct 2013 21:59:30 +0900
Message-ID: <CAH9hSJaaoE1z_DzBFbxaUDiY8j3Wm1i5h_Mvxuvqk5WnSF_KtQ@mail.gmail.com>
To: Tobias Oberstein <tobias.oberstein@tavendo.de>
Content-Type: multipart/alternative; boundary=047d7b86de829582ff04e9f4e857
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] Dispatch an error event when no handshake response is received?
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 30 Oct 2013 12:59:55 -0000

--047d7b86de829582ff04e9f4e857
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Oct 30, 2013 at 9:49 PM, Tobias Oberstein <
tobias.oberstein@tavendo.de> wrote:

> >I think it makes sense to _fail_ when the underlying connection is opened
> successfully but is closed by the server before the client receives a
> handshake response.
>
> Not sure I understand:
>
> When a server encounters an error during handshake processing, the only 2
> options it has are:
> S1) return HTTP error
> S2) immediately drop/close the underlying TCP
>
> I think both are fine, S1 being more "cooperative", but S1 more resilant
> to DoS.
>
> When a client encounters an error during handshake processing it might
> have 2 options (depending on error severity):
>
> C1) perform a WS closing HS
> C2) drop/close the underlying TCP
>
> Not sure if C1 makes any sense .. since the client cannot be sure the
> server actually is a WS server in this case.
>
> E.g. if a mandatory WS HS response header is missing: C2
> If WS subprotocol mismatch, client _could_ perform C1.
>
> Not sure.


This is yet another topic. Sorry for being unclear. I was just wondering if
we should fire error event or not, and I believe we should...

--047d7b86de829582ff04e9f4e857
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra">On Wed, Oct 30, 2013 at 9:49 PM=
, Tobias Oberstein <span dir=3D"ltr">&lt;<a href=3D"mailto:tobias.oberstein=
@tavendo.de" target=3D"_blank">tobias.oberstein@tavendo.de</a>&gt;</span> w=
rote:<br>

<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=3D"im"=
>&gt;I think it makes sense to _fail_ when the underlying connection is ope=
ned successfully but is closed by the server before the client receives a h=
andshake response.<br>


<br>
</div>Not sure I understand:<br>
<br>
When a server encounters an error during handshake processing, the only 2 o=
ptions it has are:<br>
S1) return HTTP error<br>
S2) immediately drop/close the underlying TCP<br>
<br>
I think both are fine, S1 being more &quot;cooperative&quot;, but S1 more r=
esilant to DoS.<br>
<br>
When a client encounters an error during handshake processing it might have=
 2 options (depending on error severity):<br>
<br>
C1) perform a WS closing HS<br>
C2) drop/close the underlying TCP<br>
<br>
Not sure if C1 makes any sense .. since the client cannot be sure the serve=
r actually is a WS server in this case.<br>
<br>
E.g. if a mandatory WS HS response header is missing: C2<br>
If WS subprotocol mismatch, client _could_ perform C1.<br>
<br>
Not sure.</blockquote><div><br></div><div>This is yet another topic. Sorry =
for being unclear. I was just wondering if we should fire error event or no=
t, and I believe we should...=A0<br></div></div><br></div></div>

--047d7b86de829582ff04e9f4e857--

From tobias.oberstein@tavendo.de  Wed Oct 30 06:10:47 2013
Return-Path: <tobias.oberstein@tavendo.de>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA4F411E822D for <hybi@ietfa.amsl.com>; Wed, 30 Oct 2013 06:10:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level: 
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l8fu0RYI-qGU for <hybi@ietfa.amsl.com>; Wed, 30 Oct 2013 06:10:42 -0700 (PDT)
Received: from EXHUB020-2.exch020.serverdata.net (exhub020-2.exch020.serverdata.net [206.225.164.29]) by ietfa.amsl.com (Postfix) with ESMTP id F293D11E8276 for <hybi@ietf.org>; Wed, 30 Oct 2013 06:10:37 -0700 (PDT)
Received: from EXVMBX020-12.exch020.serverdata.net ([169.254.3.240]) by EXHUB020-2.exch020.serverdata.net ([206.225.164.29]) with mapi; Wed, 30 Oct 2013 06:10:37 -0700
From: Tobias Oberstein <tobias.oberstein@tavendo.de>
To: Takeshi Yoshino <tyoshino@google.com>
Date: Wed, 30 Oct 2013 06:10:36 -0700
Thread-Topic: [hybi] Dispatch an error event when no handshake response is received?
Thread-Index: Ac7Vb+yXhfTZNv39SzKb+kpZAuneUAAAER0g
Message-ID: <634914A010D0B943A035D226786325D44469E6FE3A@EXVMBX020-12.exch020.serverdata.net>
References: <SPAM_CAH9hSJbW7FkJX+Le+euAGcX5tJoddV-dWNfk_aQfjFQfNOwx5g@mail.gmail.com> <634914A010D0B943A035D226786325D44469E6FE20@EXVMBX020-12.exch020.serverdata.net> <CAH9hSJaaoE1z_DzBFbxaUDiY8j3Wm1i5h_Mvxuvqk5WnSF_KtQ@mail.gmail.com>
In-Reply-To: <CAH9hSJaaoE1z_DzBFbxaUDiY8j3Wm1i5h_Mvxuvqk5WnSF_KtQ@mail.gmail.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] Dispatch an error event when no handshake response is received?
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 30 Oct 2013 13:10:48 -0000

>This is yet another topic. Sorry for being unclear. I was just wondering i=
f we should fire error event or not, and I believe we should...=A0

Ahh. So you refer to the WebSocket _API_ ... in browsers? If so, would that=
 be IETF's/RFC6455's business or WHATWG's?

In the substance matter I agree: the WS browser API should fire an error ev=
ent upon the initial handshake failing. It probably even should fire error =
if no handshake is started at all because e.g. I provide a invalid WS URI.

Since developers might just expect that: handle any WS error (be it before =
handshake, during handshake or thereafter) in one place: the WS object's er=
ror event handler.

There is one aspect: somewhere/someone brought up that the error reason MUS=
T NOT disclose unwanted info (to a potentially evil script): e.g. HS failed=
 because TLS cert invalid. Otherwise scripts could probe around in intranet=
s etc. It is however a pain (this TLS fail in particular): browser won't re=
nder a dialog (since WS is a subresource) and WS error won't disclose TLS e=
rror also. So a good script has no chance of giving the user useful feedbac=
k .. like check site cert, import some cert or such.

/Tobias

From tyoshino@google.com  Wed Oct 30 06:19:58 2013
Return-Path: <tyoshino@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A90621F9F21 for <hybi@ietfa.amsl.com>; Wed, 30 Oct 2013 06:19:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level: 
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[AWL=0.069,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pj0OsMOdhLwr for <hybi@ietfa.amsl.com>; Wed, 30 Oct 2013 06:19:57 -0700 (PDT)
Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 3C2AA11E8174 for <hybi@ietf.org>; Wed, 30 Oct 2013 06:19:37 -0700 (PDT)
Received: by mail-wi0-f172.google.com with SMTP id ez12so6776909wid.5 for <hybi@ietf.org>; Wed, 30 Oct 2013 06:19:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=1wjnIbaM7NHe0lBUUqk301EylTgNeYP9Pu4yAi7S60o=; b=CpBieMDVvFt4yd054LKVmFNpDDj5wjpf6PsYa4H+Ys95g7bvqYDwcyU/CwsGSQ3nxN edn2t88RxNfgeCz3h89Z8ZDHTTaAnrccZ+7GaBUQT+HNzj7IrRTuM16CRw92jvH755F+ doW+yyaEAk55cmwC2B1oYEpjoaRBUvKUvXHBbJ86dVAx1AXJxcmAp0yigeDZXd4immlt IGwb4ok1+KEZUdNv7ND4AVgL8bcg5fOdjr/EH3OyBX7YYsesp/b2w13JcEOP52Qv2o5u yQ9hViXyVln8t9TRnyTitxhAO99sIelyUCdv/U62ziCTbXu1SVzY8wu+xIlXDtfJXv0z /W+g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=1wjnIbaM7NHe0lBUUqk301EylTgNeYP9Pu4yAi7S60o=; b=RPG071AdjcCQ7FfsFkbT6/uja0tb4DjX8Xv/wtX0zMY9OPhtHPEClrMjI1dfDXvHQZ VZBm9GHWeZBzZNdOM2kSl0S9Y/Fg+Q8WouwDKtP0KYkZuS1cdbw5kWRT/3KpADmBcI89 PDHfxvjlDWS/p7yYzg4OjrmwtkObsLtIMSTD1gRuP+R5KYPeBVNktMiROSr0r7SK1MOl JtYwMwzxkje+EW4qmNRgHp+RIqjyT3rH5dWT6K9SX0ecyvRnPMvCw3tCQcOxlXV0mX+K 4ZauOmDIaZUejFe7tCluB07o3IAQzTwDWR8BhN9jw0N1PVl4rjp+2ijbVyojCRxWDnuz 9k7w==
X-Gm-Message-State: ALoCoQlkf/g9hxoiyYpCx9aIEpMCU6e22BqHuBRd/K2ifTHsF+tAoDEvGsxxy51Xffv46qsQH8eSB4NqzlfALQKC2HKPba5utqhwIeQqcEyCt9f/+d2GFBO/gXoegvUGAhdBtgzZu1ht0AhHtQ/Ij4JVXsagHTnqEZ5qTnQ19wdo9qvGY+OuufziOWmIGGuhMksGnKhjoGv5
X-Received: by 10.194.60.73 with SMTP id f9mr1896791wjr.65.1383139176070; Wed, 30 Oct 2013 06:19:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.15.133 with HTTP; Wed, 30 Oct 2013 06:19:15 -0700 (PDT)
In-Reply-To: <634914A010D0B943A035D226786325D44469E6FE3A@EXVMBX020-12.exch020.serverdata.net>
References: <SPAM_CAH9hSJbW7FkJX+Le+euAGcX5tJoddV-dWNfk_aQfjFQfNOwx5g@mail.gmail.com> <634914A010D0B943A035D226786325D44469E6FE20@EXVMBX020-12.exch020.serverdata.net> <CAH9hSJaaoE1z_DzBFbxaUDiY8j3Wm1i5h_Mvxuvqk5WnSF_KtQ@mail.gmail.com> <634914A010D0B943A035D226786325D44469E6FE3A@EXVMBX020-12.exch020.serverdata.net>
From: Takeshi Yoshino <tyoshino@google.com>
Date: Wed, 30 Oct 2013 22:19:15 +0900
Message-ID: <CAH9hSJZyp5AOEkV7MwRxJwB3aK-8LkJZgccpNfoT1xYqmTGT8Q@mail.gmail.com>
To: Tobias Oberstein <tobias.oberstein@tavendo.de>
Content-Type: multipart/alternative; boundary=047d7b86de8243d7a004e9f52fcc
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] Dispatch an error event when no handshake response is received?
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 30 Oct 2013 13:19:58 -0000

--047d7b86de8243d7a004e9f52fcc
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Oct 30, 2013 at 10:10 PM, Tobias Oberstein <
tobias.oberstein@tavendo.de> wrote:

> >This is yet another topic. Sorry for being unclear. I was just wondering
> if we should fire error event or not, and I believe we should...
>
> Ahh. So you refer to the WebSocket _API_ ... in browsers? If so, would
> that be IETF's/RFC6455's business or WHATWG's?
>

We can cover this case by adding texts to the WebSocket API. But unless
there's no mistake in RFC 6455, the WebSocket API just refers to events
defined in RFC 6455. For example,

> If the user agent was required to fail the WebSocket connection or the
WebSocket connection is closed with prejudice, fire a simple event named
error at the WebSocket object. [WSP]

It's connecting _fail the WebSocket connection_ defined in RFC 6455 with
the error event defined in the WebSocket API. The issue I pointed is that
in RFC 6455, it's not explicitly defined how to deal with connection close
without no handshake response data. The client will _close_ or _fail_.


>
> In the substance matter I agree: the WS browser API should fire an error
> event upon the initial handshake failing. It probably even should fire
> error if no handshake is started at all because e.g. I provide a invalid WS
> URI.
>
>
OK!


> Since developers might just expect that: handle any WS error (be it before
> handshake, during handshake or thereafter) in one place: the WS object's
> error event handler.
>

Agreed.

>
> There is one aspect: somewhere/someone brought up that the error reason
> MUST NOT disclose unwanted info (to a potentially evil script): e.g. HS
> failed because TLS cert invalid. Otherwise scripts could probe around in
> intranets etc. It is however a pain (this TLS fail in particular): browser
> won't render a dialog (since WS is a subresource) and WS error won't
> disclose TLS error also. So a good script has no chance of giving the user
> useful feedback .. like check site cert, import some cert or such.
>

Right. Error detail must not be delivered. Just making "connection close
without no handshake response data" fire an error event doesn't break the
rule. Yes.

--047d7b86de8243d7a004e9f52fcc
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Wed, Oct 30, 2013 at 10:10 PM, Tobias Oberstein <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:tobias.oberstein@tavendo.de" target=3D"_bl=
ank">tobias.oberstein@tavendo.de</a>&gt;</span> wrote:<br><div class=3D"gma=
il_extra">

<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204=
);border-left-style:solid;padding-left:1ex"><div class=3D"im">&gt;This is y=
et another topic. Sorry for being unclear. I was just wondering if we shoul=
d fire error event or not, and I believe we should...=A0<br>


<br>
</div>Ahh. So you refer to the WebSocket _API_ ... in browsers? If so, woul=
d that be IETF&#39;s/RFC6455&#39;s business or WHATWG&#39;s?<br></blockquot=
e><div><br></div><div>We can cover this case by adding texts to the WebSock=
et API. But unless there&#39;s no mistake in RFC 6455, the WebSocket API ju=
st refers to events defined in RFC 6455. For example,</div>

<div><br></div><div>&gt; If the user agent was required to fail the WebSock=
et connection or the WebSocket connection is closed with prejudice, fire a =
simple event named error at the WebSocket object. [WSP]<br></div><div>
<br>
</div><div>It&#39;s connecting _fail the WebSocket connection_ defined in R=
FC 6455 with the error event defined in the WebSocket API. The issue I poin=
ted is that in RFC 6455, it&#39;s not explicitly defined how to deal with c=
onnection close without no handshake response data. The client will _close_=
 or _fail_.</div>

<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left=
-style:solid;padding-left:1ex">
<br>
In the substance matter I agree: the WS browser API should fire an error ev=
ent upon the initial handshake failing. It probably even should fire error =
if no handshake is started at all because e.g. I provide a invalid WS URI.<=
br>


<br></blockquote><div><br></div><div>OK!</div><div>=A0</div><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;=
border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex=
">


Since developers might just expect that: handle any WS error (be it before =
handshake, during handshake or thereafter) in one place: the WS object&#39;=
s error event handler.<br></blockquote><div><br></div><div>Agreed.=A0</div>

<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">
<br>
There is one aspect: somewhere/someone brought up that the error reason MUS=
T NOT disclose unwanted info (to a potentially evil script): e.g. HS failed=
 because TLS cert invalid. Otherwise scripts could probe around in intranet=
s etc. It is however a pain (this TLS fail in particular): browser won&#39;=
t render a dialog (since WS is a subresource) and WS error won&#39;t disclo=
se TLS error also. So a good script has no chance of giving the user useful=
 feedback .. like check site cert, import some cert or such.<br>

</blockquote><div><br></div><div>Right. Error detail must not be delivered.=
 Just making &quot;connection close without no handshake response data&quot=
; fire an error event doesn&#39;t break the rule. Yes.</div><div>=A0</div>

</div></div></div>

--047d7b86de8243d7a004e9f52fcc--

From godjonez@codepad.info  Wed Oct 30 06:23:22 2013
Return-Path: <godjonez@codepad.info>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C1FF21E80D9 for <hybi@ietfa.amsl.com>; Wed, 30 Oct 2013 06:23:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xx4+L+GViwed for <hybi@ietfa.amsl.com>; Wed, 30 Oct 2013 06:23:15 -0700 (PDT)
Received: from smtpout.kotinet.com (smtpout.kotinet.com [212.50.215.76]) by ietfa.amsl.com (Postfix) with ESMTP id B528F11E81DB for <hybi@ietf.org>; Wed, 30 Oct 2013 06:22:28 -0700 (PDT)
Received: from codepad.info (codepad.info [62.240.71.135]) by smtpout.kotinet.com (Postfix) with ESMTP id 7611DE0CD9 for <hybi@ietf.org>; Wed, 30 Oct 2013 15:22:27 +0200 (EET)
Received: from jfy-10031.uefad.uef.fi (jns-gw.uef.fi [193.167.41.1]) by codepad.info (Postfix) with ESMTPSA id 66F62640A4B for <hybi@ietf.org>; Wed, 30 Oct 2013 15:22:26 +0200 (EET)
Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
To: hybi@ietf.org
References: <SPAM_CAH9hSJbW7FkJX+Le+euAGcX5tJoddV-dWNfk_aQfjFQfNOwx5g@mail.gmail.com> <634914A010D0B943A035D226786325D44469E6FE20@EXVMBX020-12.exch020.serverdata.net> <CAH9hSJaaoE1z_DzBFbxaUDiY8j3Wm1i5h_Mvxuvqk5WnSF_KtQ@mail.gmail.com> <634914A010D0B943A035D226786325D44469E6FE3A@EXVMBX020-12.exch020.serverdata.net>
Date: Wed, 30 Oct 2013 15:22:25 +0200
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: "Joonas Lehtolahti" <godjonez@codepad.info>
Message-ID: <op.w5rrfn2muykfxw@jfy-10031.uefad.uef.fi>
In-Reply-To: <634914A010D0B943A035D226786325D44469E6FE3A@EXVMBX020-12.exch020.serverdata.net>
User-Agent: Opera Mail/12.15 (Win64)
Subject: Re: [hybi] Dispatch an error event when no handshake response is received?
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 30 Oct 2013 13:23:22 -0000

On Wed, 30 Oct 2013 15:10:36 +0200, Tobias Oberstein  
<tobias.oberstein@tavendo.de> wrote:
> There is one aspect: somewhere/someone brought up that the error reason  
> MUST NOT disclose unwanted info (to a potentially evil script): e.g. HS  
> failed because TLS cert invalid. Otherwise scripts could probe around in  
> intranets etc. It is however a pain (this TLS fail in particular):  
> browser won't render a dialog (since WS is a subresource) and WS error  
> won't disclose TLS error also. So a good script has no chance of giving  
> the user useful feedback .. like check site cert, import some cert or  
> such.

Who says that a browser cannot give the user a sensible feedback even if  
an error happens with subresource? It actually bothers me that browsers  
usually don't give any info to users when some resource on a page has a  
problem. The user just sees a broken website but has no clue as to why it  
is broken. The last example of this was Twitter having no stylesheet or  
images because the resource server certificate check was not temporarily  
working, but all the user saw was the broken page even though the browser  
knew exactly why it didn't load the extra resources. So in my opinion the  
browser can and should display, not necessarily a dialog, but some  
indicator (red mark on address bar, for example) from which the user can  
click to get a dialog with detailed information on what has gone wrong.  
And this would apply to WebSocket also, the script can be clueless about  
certificate problem, but the user could have the option of seeing that and  
possibly remedy the situation (accept invalid cert, get missing root cert,  
etc.).

Just my few cents on this a bit off-topic part.

- Joonas

From tobias.oberstein@tavendo.de  Wed Oct 30 06:42:25 2013
Return-Path: <tobias.oberstein@tavendo.de>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2939C11E81D6 for <hybi@ietfa.amsl.com>; Wed, 30 Oct 2013 06:42:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.552
X-Spam-Level: 
X-Spam-Status: No, score=-2.552 tagged_above=-999 required=5 tests=[AWL=0.047,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cCncAO12ZsYG for <hybi@ietfa.amsl.com>; Wed, 30 Oct 2013 06:42:20 -0700 (PDT)
Received: from EXHUB020-2.exch020.serverdata.net (exhub020-2.exch020.serverdata.net [206.225.164.29]) by ietfa.amsl.com (Postfix) with ESMTP id 9340621F9928 for <hybi@ietf.org>; Wed, 30 Oct 2013 06:42:07 -0700 (PDT)
Received: from EXVMBX020-12.exch020.serverdata.net ([169.254.3.240]) by EXHUB020-2.exch020.serverdata.net ([206.225.164.29]) with mapi; Wed, 30 Oct 2013 06:41:59 -0700
From: Tobias Oberstein <tobias.oberstein@tavendo.de>
To: Joonas Lehtolahti <godjonez@codepad.info>, "hybi@ietf.org" <hybi@ietf.org>
Date: Wed, 30 Oct 2013 06:41:58 -0700
Thread-Topic: [hybi] Dispatch an error event when no handshake response is received?
Thread-Index: Ac7Vc1Cm8xrGH0ctTCmWztfbHMXjEQAAdVAw
Message-ID: <634914A010D0B943A035D226786325D44469E6FE72@EXVMBX020-12.exch020.serverdata.net>
References: <SPAM_CAH9hSJbW7FkJX+Le+euAGcX5tJoddV-dWNfk_aQfjFQfNOwx5g@mail.gmail.com> <634914A010D0B943A035D226786325D44469E6FE20@EXVMBX020-12.exch020.serverdata.net> <CAH9hSJaaoE1z_DzBFbxaUDiY8j3Wm1i5h_Mvxuvqk5WnSF_KtQ@mail.gmail.com> <634914A010D0B943A035D226786325D44469E6FE3A@EXVMBX020-12.exch020.serverdata.net> <op.w5rrfn2muykfxw@jfy-10031.uefad.uef.fi>
In-Reply-To: <op.w5rrfn2muykfxw@jfy-10031.uefad.uef.fi>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [hybi] Dispatch an error event when no handshake response is received?
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 30 Oct 2013 13:42:25 -0000

> load the extra resources. So in my opinion the browser can and should dis=
play,
> not necessarily a dialog, but some indicator (red mark on address bar, fo=
r
> example) from which the user can click to get a dialog with detailed
> information on what has gone wrong.

Thats a good idea! It solves the issue of no user feedback, and is e.g done=
 today already for mixed content sites (insecure subresources for secure pa=
ge).

FWIW, we have been working around this TLS issues in the context of WS usin=
g 2 approaches (besides making the cert valid of course):

1) Redirecting the user to the WS URL, but HTTP(S) scheme, and having the W=
S server render a status HTML page itself (when it gets a HTTP/GET without =
Upgrade to WS header). The user can then accept cert and such.

2) Serving all content and WS from same server.

/Tobias

From joakim@intalio.com  Wed Oct 30 07:22:59 2013
Return-Path: <joakim@intalio.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A07A011E812D for <hybi@ietfa.amsl.com>; Wed, 30 Oct 2013 07:22:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8TyhoeY1mfTw for <hybi@ietfa.amsl.com>; Wed, 30 Oct 2013 07:22:55 -0700 (PDT)
Received: from mail-ea0-f180.google.com (mail-ea0-f180.google.com [209.85.215.180]) by ietfa.amsl.com (Postfix) with ESMTP id 62EF411E8221 for <hybi@ietf.org>; Wed, 30 Oct 2013 07:22:50 -0700 (PDT)
Received: by mail-ea0-f180.google.com with SMTP id l9so584155eaj.11 for <hybi@ietf.org>; Wed, 30 Oct 2013 07:22:49 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=sZbOAxPRuxjZD8+HTuwZEDA2wfRwjS7Nij99LWSfuaA=; b=Jtj78GPKK0iuq/pmmmtAhZ9Ta86fy3ntuVBm9/2NRhcUL4UDyviZYIOZ+/LCObFFp7 C7Kf0K9jCzcckoKZbncQxI0syEOWUWNHVJeixKCPbo03w5SunGmUQe2P2eP2/sr6uiq6 tmKgmxvjvV2bZjTy2lfji5tTAFrshlWy6HrcyN+266CGsvn+qQb4xjWbf8ruNowWC4Cl U/Bx2Y9YUt+RwPXhROCfrfI/KwmTYX20iWojnJ5mNqNPFEDMLntQCaevqSWC9Zi3dGjC UVXPjByNO7fgSfvK0tX2ag2l64gfGXzGWA+FwPk1VSEmcpzs7nzITHAO+cgUz/rXHq4J K8XQ==
X-Gm-Message-State: ALoCoQkR4PAWzXGU3vXaTzQq02FuuYjvsltPWbYyq7UgFF4fKsZU+83jpmOtRyp53cjF9cg7kqD1
MIME-Version: 1.0
X-Received: by 10.15.21.12 with SMTP id c12mr144997eeu.114.1383142969386; Wed, 30 Oct 2013 07:22:49 -0700 (PDT)
Received: by 10.14.203.199 with HTTP; Wed, 30 Oct 2013 07:22:49 -0700 (PDT)
In-Reply-To: <CAH9hSJbW7FkJX+Le+euAGcX5tJoddV-dWNfk_aQfjFQfNOwx5g@mail.gmail.com>
References: <CAH9hSJbW7FkJX+Le+euAGcX5tJoddV-dWNfk_aQfjFQfNOwx5g@mail.gmail.com>
Date: Wed, 30 Oct 2013 07:22:49 -0700
Message-ID: <CAG4zZZAuWNbrCN80YZQvUjWqBbwrVkL1rvy5=5+fQvPDReVffg@mail.gmail.com>
From: Joakim Erdfelt <joakim@intalio.com>
To: Takeshi Yoshino <tyoshino@google.com>
Content-Type: multipart/alternative; boundary=089e0160d1805d39e504e9f61165
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] Dispatch an error event when no handshake response is received?
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 30 Oct 2013 14:22:59 -0000

--089e0160d1805d39e504e9f61165
Content-Type: text/plain; charset=ISO-8859-1

Since this is about the API, the section you pasted has a number of
pre-existing failure examples that I would think you have cases for already.
Just mimic the behavior of those existing errors.

Currently, in Chrome and Firefox, those situations don't report, via
javascript, the details of _why_ it failed, just that it failed.
The Chrome javascript console, however, does log some additional detail on
the error condition.

Some test cases that the jetty project uses.

Client request with Sec-WebSocket-Protocol, server response with none.
Client request without Connection header.
Client request with multi-value Connection header (aka: "Connection,
keep-alive")
Client request without Sec-WebSocket-Accept header.
Client request with bad Sec-WebSocket-Accept header.
Server response without Sec-WebSocket-Accept header.
Server response with bad Sec-WebSocket-Accept header.
Server response with Sec-WebSocket-Extension token not present on Client
handshake request.
Server response with Sec-WebSocket-Extension configuration that client
cannot handle.
Client request without Upgrade header.
Client request with bad Upgrade header.
Server response without Upgrade header.
Server response with bad Upgrade header.
Server response to upgrade that is not 101 Switching Protocols (such as
200, or 403)

With the possible exception of the 403 response to upgrade, the rest are
error conditions that should be reported to the users of the client API.
I say just use whatever you currently have.


--
Joakim Erdfelt <joakim@intalio.com>
webtide.com <http://www.webtide.com/> - intalio.com/jetty
Expert advice, services and support from from the Jetty & CometD experts
eclipse.org/jetty - cometd.org


On Wed, Oct 30, 2013 at 3:52 AM, Takeshi Yoshino <tyoshino@google.com>wrote:

> I think it makes sense to _fail_ when the underlying connection is opened
> successfully but is closed by the server before the client receives a
> handshake response.
>
> But it's not explicitly specified in RFC 6455.
>
> Maybe we can refer to this text to handle the case by _fail_.
>
> > If the server's response does not conform to the requirements for the
> > server's handshake as defined in this section and in Section 4.2.2,
> > the client MUST _Fail the WebSocket Connection_.
>
> Any concern?
>
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi
>
>

--089e0160d1805d39e504e9f61165
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Since this is about the API, the section you pasted has a =
number of pre-existing failure examples that I would think you have cases f=
or already.<div>Just mimic the behavior of those existing errors.</div><div=
>
<br></div><div>Currently, in Chrome and Firefox, those situations don&#39;t=
 report, via javascript, the details of _why_ it failed, just that it faile=
d.</div><div>The Chrome javascript console, however, does log some addition=
al detail on the error condition.</div>
<div><br></div><div>Some test cases that the jetty project uses.</div><div>=
<br></div><div>Client request with Sec-WebSocket-Protocol, server response =
with none.</div><div>Client request without Connection header.</div><div>
Client request with multi-value Connection header (aka: &quot;Connection, k=
eep-alive&quot;)</div><div>Client request without Sec-WebSocket-Accept head=
er.</div><div>Client request with bad Sec-WebSocket-Accept header.</div>
<div>Server response without Sec-WebSocket-Accept header.</div><div>Server =
response with bad Sec-WebSocket-Accept header.</div><div>Server response wi=
th Sec-WebSocket-Extension token not present on Client handshake request.</=
div>
<div>Server response with Sec-WebSocket-Extension configuration that client=
 cannot handle.</div><div>Client request without Upgrade header.</div><div>=
Client request with bad Upgrade header.</div><div>Server response without U=
pgrade header.</div>
<div>Server response with bad Upgrade header.</div><div>Server response to =
upgrade that is not 101 Switching Protocols (such as 200, or 403)</div><div=
><br></div><div>With the possible exception of the 403 response to upgrade,=
 the rest are error conditions that should be reported to the users of the =
client API.</div>
<div>I say just use whatever you currently have.</div><div><br></div></div>=
<div class=3D"gmail_extra"><br clear=3D"all"><div><div dir=3D"ltr"><div>--<=
/div><div>Joakim Erdfelt &lt;<a href=3D"mailto:joakim@intalio.com" target=
=3D"_blank">joakim@intalio.com</a>&gt;</div>
<div><a href=3D"http://www.webtide.com/" target=3D"_blank">webtide.com</a>=
=A0- <a href=3D"http://intalio.com/jetty" target=3D"_blank">intalio.com/jet=
ty</a></div><div><span>Expert advice, services and support from=A0</span><s=
pan>from the Jetty &amp; CometD experts</span></div>
<div><a href=3D"http://eclipse.org/jetty/" target=3D"_blank">eclipse.org/je=
tty</a>=A0-=A0<a href=3D"http://cometd.org/" target=3D"_blank">cometd.org</=
a></div></div></div>
<br><br><div class=3D"gmail_quote">On Wed, Oct 30, 2013 at 3:52 AM, Takeshi=
 Yoshino <span dir=3D"ltr">&lt;<a href=3D"mailto:tyoshino@google.com" targe=
t=3D"_blank">tyoshino@google.com</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">
<div dir=3D"ltr">I think it makes sense to _fail_ when the underlying conne=
ction is opened successfully but is closed by the server before the client =
receives a handshake response.
<div><br></div><div>But it&#39;s not explicitly specified in RFC 6455.</div=
><div><br></div><div>Maybe we can refer to this text to handle the case by =
_fail_.</div><div><br></div><div><div>&gt; If the server&#39;s response doe=
s not conform to the requirements for the</div>


<div>&gt; server&#39;s handshake as defined in this section and in Section =
4.2.2,</div><div>&gt; the client MUST _Fail the WebSocket Connection_.</div=
></div><div><br></div><div>Any concern?</div></div>
<br>_______________________________________________<br>
hybi mailing list<br>
<a href=3D"mailto:hybi@ietf.org">hybi@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/hybi" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/hybi</a><br>
<br></blockquote></div><br></div>

--089e0160d1805d39e504e9f61165--
