Re: [hybi] I-D Action: draft-ietf-hybi-permessage-compression-09.txt

[Tobias Oberstein <[e-mail]>]

Am 04.06.2013 13:35, schrieb Takeshi Yoshino:> On Sun, Jun 2, 2013 at 7:29 AM, Tobias Oberstein 
> <[e-mail] <mailto:[e-mail]>> wrote:
> 
>      > Please post your opinions and experience (implemented, faced any
>     difficulties, found issues, etc.).
> 
>     """
>         A client MAY attach the "c2s_max_window_bits" extension parameter if
>         the client can adjust LZ77 sliding window size based on the
>         "c2s_max_window_bits" sent by the server.  This parameter has no
>         value.
>     """
> 
>     Any reason there is no "c2s_no_context_takeover" parameter that
>     allows the client to _announce_ it supports the feature?
> 
> 
> I assumed that there's no platform/language where it's difficult to 
> implement c2s_no_context_takeover. It means that DEFLATE context is 
> singleton and can never be reset (or reset operation is very heavy).
> 
> Unless there's any existing difficulty, c2s_no_context_takeover should 
> be supported widely, I think.

The current draft reads:

" It is RECOMMENDED that clients implement the
   "c2s_no_context_takeover" parameter."

It's not "MUST implement" .. so there might be client which won't, and then a server has no chance to adapt it's response to the client and maximize likelihood of connection success given it ideally wants to activate "c2s_no_context_takeover".

> 
> Your suggestion allows a client to force a server which is reluctant to 
> but can enable c2s_context_takeover to enable it. Do you think it's 
> important functionality?

Why is that?

The presence of "c2s_no_context_takeover" in the client's offer would just signal to the server that the client supports the feature and the server MAY enable it.

Why signal feature presence for "c2s_max_window_bits", but not "c2s_no_context_takeover"?

Maybe it's just me, but the asymmetry was a source of confusion to me.

I think it would make the spec more consequent, and the change is minimal, e.g. it's a 1 liner for Chrome:

String CompressionMessageExtensionProcessor::handshakeString()
{
    return ASCIILiteral("permessage-deflate; c2s_max_window_bits");
}

=>

String CompressionMessageExtensionProcessor::handshakeString()
{
    return ASCIILiteral("permessage-deflate; c2s_max_window_bits; c2s_no_context_takeover;");
}

/Tobias