Re: 2nd Working Group Last Call: draft-ietf-httpbis-encryption-encoding-03.txt

Julian Reschke <julian.reschke@gmx.de> Wed, 19 October 2016 06:16 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D09E31293F8 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 18 Oct 2016 23:16:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.332
X-Spam-Level:
X-Spam-Status: No, score=-7.332 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.431, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UdpvSUZWt0oA for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 18 Oct 2016 23:16:32 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3FCB31293D8 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 18 Oct 2016 23:16:32 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1bwk6m-0003jF-FZ for ietf-http-wg-dist@listhub.w3.org; Wed, 19 Oct 2016 06:12:12 +0000
Resent-Date: Wed, 19 Oct 2016 06:12:12 +0000
Resent-Message-Id: <E1bwk6m-0003jF-FZ@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <julian.reschke@gmx.de>) id 1bwk6g-0003iR-BZ for ietf-http-wg@listhub.w3.org; Wed, 19 Oct 2016 06:12:06 +0000
Received: from mout.gmx.net ([212.227.15.18]) by maggie.w3.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from <julian.reschke@gmx.de>) id 1bwk6U-00079g-6a for ietf-http-wg@w3.org; Wed, 19 Oct 2016 06:12:05 +0000
Received: from [192.168.178.20] ([93.217.104.58]) by mail.gmx.com (mrgmx001) with ESMTPSA (Nemesis) id 0MLeoF-1bvush3DG7-000wew; Wed, 19 Oct 2016 08:11:16 +0200
To: Martin Thomson <martin.thomson@gmail.com>
References: <147607568231.30483.6721771001967558206.idtracker@ietfa.amsl.com> <06660B0E-6F8D-42DF-A909-C216B49FB590@mnot.net> <03fb16fd-35d4-e5d3-86d4-317b1016829e@gmx.de> <CABkgnnWKOTheZ9Gf9WLfVWAsQwNWi=EM6LhX=Za+UXnXQkf6AQ@mail.gmail.com>
Cc: Mark Nottingham <mnot@mnot.net>, HTTP working group mailing list <ietf-http-wg@w3.org>, Patrick McManus <pmcmanus@mozilla.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <90ee7958-5697-23ad-6f52-060f58800067@gmx.de>
Date: Wed, 19 Oct 2016 08:11:16 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <CABkgnnWKOTheZ9Gf9WLfVWAsQwNWi=EM6LhX=Za+UXnXQkf6AQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:0vl39KKAZnKCIMPAWJKbXRIjaGsckKxdDOWtUAdm3wY1d+YPtif 4QV4rxlQMywBrs4kB2n+hljar04NrReLeA2sn/nMNbOirEDEI9NZfw+qkUcvGZsDSkEusEb n/KahsYxjG/mt0g9oYwXE63zylCEy4VMY/tjli+8P6HhoWdA88a/8YMNWo2aDxMoMM+sg05 rdSu0yld3iwyEQhiCye5Q==
X-UI-Out-Filterresults: notjunk:1;V01:K0:3vyYABUUx2k=:SccP+DSpP6GU2N+AsIemP2 dihxiKrGD+3GctxfaW6ju/i7lygBlreEdv+oWwt6K0eV5f5u0X0s3mbDhVOSHtddxaQajfzJk P4ZExVcdq/KcYF6mWdAQaT20/oGJlzs7QRVmvFd9ffSHhRIs3EkZTVMgxzpyXmx/CNQsd2w8m GDk7Hz8pNLgLEX+w4wOO/k9JWLxSSlZrH8wpovrzVPQ/MV+ArtwVfScrfHLnTlG3IYEGBWX79 kbk1tKeQZ0lfBs5FG74k3ESd6I6mUmUlUk5ZJ00Cq02CTDsOiycPwxB2eyU+6oW9MGH6SpFc3 NXWKP53DOIYcJN6GB29w0j72fq32RJSgVRm4yPmwoMgBA3lqge+DW6GUV9sSa1iKc1t+bZE2d sAlYnKkTmz5BvMWXI7zjMvZpL8Dqa4zaRDgrHTXHvMrTkZl1l5ylBAtCUHkcBdKLEiIuvwnm3 hS+QKnLceSg3hBaAQY547jaOAbbnNkLs/ru6mupiJmZcKlaoOSNOFaqTlg9l7D8jIdoaZ5NTH vI2RIPx6mkFAxo44/YC5ndZYtndqMnVBsw7sCwOQMSGc4M7r73YlhOt7ELrpG9Ri6Z+LwlzsJ eLEjqSoBoMjmMmi7E3GjQykJDry4Dl/TwbqflBmTwNloLnw7HUF7L1yh7GZpYHGYf5Y89ZNqH zWvki7eMem3UidKt56b4ZvID6OAt+AgvbnBYq03JWhMWlEtQEFn6GIMtHf7sFHkKMzxuN5+h2 H/pgaoVEn80RSTl36oxnuY7UCbyV/+xFljdpmONZMTt5xNh6qOmIpvHRIJKmTpisCvJg8t/o5 2/3xOWO
Received-SPF: pass client-ip=212.227.15.18; envelope-from=julian.reschke@gmx.de; helo=mout.gmx.net
X-W3C-Hub-Spam-Status: No, score=-8.2
X-W3C-Hub-Spam-Report: AWL=1.421, BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_IRR=-3, W3C_WL=-1
X-W3C-Scan-Sig: maggie.w3.org 1bwk6U-00079g-6a d7c0094999b355f242b613e1f6a170d6
X-Original-To: ietf-http-wg@w3.org
Subject: Re: 2nd Working Group Last Call: draft-ietf-httpbis-encryption-encoding-03.txt
Archived-At: <http://www.w3.org/mid/90ee7958-5697-23ad-6f52-060f58800067@gmx.de>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/32626
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

Thanks for the changes, Martin!

On 2016-10-19 06:13, Martin Thomson wrote:
> ...
>> I believe we need to clarify the precise interaction between new content
>> codings and this header field. I'll assume any new content coding needs to
>> opt-in to use this field value as well, so it's clear how to remove entries
>> when unwrapping codings.
>
> I think that I have some text that will help.  I think that the answer is:
>
> Content codings that use the Encryption header field MUST always include a
> value for the header field when the content coding has been applied.  If no
> parameters are needed, then a dummy value is necessary to avoid confusion about
> which set of parameters applies to which content coding.  This requirement
> applies to uses of the `aesgcm` content coding, which does not need a dummy
> value because the `salt` parameter is mandatory.
> [97b3c12] and [67b65df]
> ...

"applies" -> "does not apply"?

In any case: this sounds like a band-aid. I think it would be good to 
discuss the whole parametrization of content codings...

> ...
>> Might be better to cite the slightly newer
>> <https://www.w3.org/TR/2013/REC-xmlenc-core1-20130411/>. In any case, please
>> add the W3C short name to the series element, such as in:
> [8ea4739]
>
> Interesting thing I learned from this: there are rules for "fixing"
> non-ASCII names in xml2rfc.
> ...

But they are unreliable...

Best regards, Julian