Re: [hybi] Payload only compression extension, again

Brodie Thiesfield <brodie@jellycan.com> Thu, 28 April 2011 01:38 UTC

Return-Path: <brofield@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 C7C27E0907 for <hybi@ietfa.amsl.com>; Wed, 27 Apr 2011 18:38:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level:
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[AWL=0.375, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LeCr4UCeySwA for <hybi@ietfa.amsl.com>; Wed, 27 Apr 2011 18:38:29 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4C3E2E0849 for <hybi@ietf.org>; Wed, 27 Apr 2011 18:38:29 -0700 (PDT)
Received: by pzk5 with SMTP id 5so1679403pzk.31 for <hybi@ietf.org>; Wed, 27 Apr 2011 18:38:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=qyJyN7Km/fxhMDmK/STS0mILnYfjl0LHlgNtikzud40=; b=DMqL/Prb8e48iR54WNWRLwA415gQOFPVJzcyuir4vaImsfg/CqDOHn7qXF1gPpO3Qp 2S5OG+EIY2OxxzzxM3rG9CBlWP8nHKEPPKc2tRsS8DqpXXo4amu8ozz/7onpA8YrkV79 5gC4sE1jpBhKoK+k9lHgKUGoPfSS5VXw335zw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=S0Kjg+1PpazRCEzenWhtcLmWSsTvAff4O+hPZnz7xs1Zl7TRC+WtNAjnTPUWiOvme/ V13aMuLJuAycC/Sdam7S6cI+oMhj5sTX2Gsd8sffyZGcXfrz1Ybi0n5B2A1iqqqMITT6 rBV2ZNi2fLyZsAeX9O42fM07hrWmFVpFpCEY8=
MIME-Version: 1.0
Received: by 10.68.15.134 with SMTP id x6mr2955234pbc.308.1303954708358; Wed, 27 Apr 2011 18:38:28 -0700 (PDT)
Sender: brofield@gmail.com
Received: by 10.68.54.35 with HTTP; Wed, 27 Apr 2011 18:38:28 -0700 (PDT)
In-Reply-To: <BANLkTikWFwfs0FOuET5ZS1HEzjweNO0_CA@mail.gmail.com>
References: <AANLkTik2LqCC2-ZLLdWNNaQ18ypcQU_5djJobkYtYk6T@mail.gmail.com> <AANLkTik+uh98b0n7U=xrE0Aaa7MyBfZVXSwj+8wfVTKW@mail.gmail.com> <AANLkTinCtDepu+wDt4=8GyXqhfn=SQ7v2SjJhKzP2Mzr@mail.gmail.com> <AANLkTinhw0j5U_tvfCCrcEx=J6b7wBua4XzhWkvthUjL@mail.gmail.com> <BANLkTi=SjQwGQu-3v2wjniyp9DrQ1ZcQdA@mail.gmail.com> <BANLkTi=dqFN-57GV3rYDv4feTAaZFQko1g@mail.gmail.com> <BANLkTikWFwfs0FOuET5ZS1HEzjweNO0_CA@mail.gmail.com>
Date: Thu, 28 Apr 2011 10:38:28 +0900
X-Google-Sender-Auth: s9GB1ToLyvJwZguzDr3nAFcLOZ4
Message-ID: <BANLkTinp8hKzUmG-uyBXeCryhdNgh=zLdA@mail.gmail.com>
From: Brodie Thiesfield <brodie@jellycan.com>
To: John Tamplin <jat@google.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: hybi@ietf.org
Subject: Re: [hybi] Payload only compression extension, again
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, 28 Apr 2011 01:38:29 -0000

On Thu, Apr 28, 2011 at 10:22 AM, John Tamplin <jat@google.com> wrote:
> On Wed, Apr 27, 2011 at 8:18 PM, Brodie Thiesfield <brodie@jellycan.com>
> wrote:
>>
>> Since you have spent the effort to create this spec, which is much
>> better than the current deflate-stream method that we have at the
>> moment, wouldn't it be worthwhile to also take over one of the
>> reserved bits and use it to specify if the frame is compressed or not?
>>
>> That way we get the data only compression with an uncompressed data
>> option. Pretty much ticks all of the boxes.
>
> This was exactly what was proposed a year ago when we were talking about
> framing, and we couldn't come to consensus on exactly how it would work
> then.  I am not sure there is any reason to believe it is more likely to
> achieve consensus now.  Among other considerations, you have to define how
> an implementation can choose when to send a compressed frame versus an
> uncompressed frame.  Do you allow/require the sender to try and compress it

No, this does not have to be defined. Only the ability to send
uncompressed frames needs to be defined. It is completely up to the
implementation whether it makes use of that ability, and if it does,
then how. The protocol just needs to enable it.

In any case, at the present time, this proposal is an extension and
not part of the base spec. It therefore has no affect on the release
of the base spec.

On an unrelated point, I would love to search for these discussions in
the archive, but I haven't found a way to do so. Do you know if there
is a searchable archive of the hybi mail list? It's not linked to from
the main list archive info.

Regards,
Brodie