Re: I-D Action: draft-ietf-httpbis-encryption-encoding-04.txt
Julian Reschke <julian.reschke@gmx.de> Tue, 01 November 2016 14:44 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 567A212960B for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 1 Nov 2016 07:44:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.398
X-Spam-Level:
X-Spam-Status: No, score=-8.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.497, 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 2zUG8OoUXPvy for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 1 Nov 2016 07:44:08 -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 23E021297CF for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 1 Nov 2016 07:43:57 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1c1aE2-00068p-G7 for ietf-http-wg-dist@listhub.w3.org; Tue, 01 Nov 2016 14:39:42 +0000
Resent-Date: Tue, 01 Nov 2016 14:39:42 +0000
Resent-Message-Id: <E1c1aE2-00068p-G7@frink.w3.org>
Received: from titan.w3.org ([128.30.52.76]) by frink.w3.org with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <julian.reschke@gmx.de>) id 1c1aDw-000680-5d for ietf-http-wg@listhub.w3.org; Tue, 01 Nov 2016 14:39:36 +0000
Received: from mout.gmx.net ([212.227.15.18]) by titan.w3.org with esmtps (TLS1.2:DHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from <julian.reschke@gmx.de>) id 1c1aDp-0000Qh-Pg for ietf-http-wg@w3.org; Tue, 01 Nov 2016 14:39:30 +0000
Received: from [192.168.178.20] ([93.217.118.239]) by mail.gmx.com (mrgmx003) with ESMTPSA (Nemesis) id 0MGSgq-1c5xwc05fk-00DH65 for <ietf-http-wg@w3.org>; Tue, 01 Nov 2016 15:39:02 +0100
References: <147795659288.23177.2369869731985386138.idtracker@ietfa.amsl.com>
To: ietf-http-wg@w3.org
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <9de93353-e86d-9d57-6ea9-a802d18c7305@gmx.de>
Date: Tue, 01 Nov 2016 15:39:00 +0100
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: <147795659288.23177.2369869731985386138.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:v9NQVkQvNteOAvOUJxvNCMZrlEXzunJ9se39J4loimFSEvik4hO v2z9p6FgvFfzEjoL7cNlLAY6aLoSnAXNuW17A3FlH5R+TEoM1ya+I/yonnVVXHdD2a1s0mY 95h817frVnN7yprUWesBwQsA2t/1ZQ0VFgEsC95F+VKumVYZxtwRXN6wQC8PcN2KF6KU/+V L6IT5KBwz9pfvVDmZzkaA==
X-UI-Out-Filterresults: notjunk:1;V01:K0:2jIPcmA/tPk=:cQoCzvkpXGWvqNHiJkDiY6 OGXUJwGOEAZAxCIR8ubRBzSXz0q1KgWR/74r51kHincv32Na/gcgw8l2uZ2eFpZKrnAZ07DI4 HgnWd0hqOD9ydxTwR8Kohai9+1Clv9LKXas4oIiqafzDVXandPYQX21bmmbKqv68J/5AO6wyg FHW8aLNWXi4r1fE5h2reFfu+1NkOzerv1E12/0XyJpcCjR3pIE12u/pBokR5zYY5ca0uPjm3A x6DqLUXYk5duCpOVOZGryNgrnLMeYQk74UGzdgXT8gvhpHQWuvfKvBUKVY05XtVpo1K/oRB4U zGfMWLJB6dBPzFqVlHAsyubWhyv5Lp+WO/nlK2swXSe8V/gDqYrqCMqYupodKYD7vupWlC526 xi1ONa2Ds9bbir9BilkOiEs4gyF9cGkpzH5Y7//Cz73QVgaqo3hXB59kHEZknq0JiqJ/x1d3m XTnjclVGbRO+QWGnL8rzuLp5ZBintyQMNAdIg+ENRmqFlm29RKkgmWe+jd7gXIEIQg+Aq4Bjz oEWq1AQSqGGhVHK4uXJp3kx/zPGIE+BzR78rTfcDuVLncf4+hKI7HSR15lN+r48tgeDBUEKaF ECy3JDMnEBj9uCpCMkMSMVub2QMlfpIURRvRn92fd65AxwugF+PKBYRkzRv6kdOcTTSUCJ+Ql qjM2TEJu4rKTKwJ9PVdXktbuKi3it1x4dtT/VpY5Kv9fGXFVCorQgBWB/M2cOXFoyC//XqLyH CVFqxws+t9+CCm1I1W+3I2WCmkOsFGJbI3KpH1gvAaW6sZccJDhua96weE3UC5fdYOlR5p4rh FqFqsEy
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=-6.7
X-W3C-Hub-Spam-Report: AWL=-0.064, BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: titan.w3.org 1c1aDp-0000Qh-Pg 3ff63684a5b3ab47a94306f60f1ba434
X-Original-To: ietf-http-wg@w3.org
Subject: Re: I-D Action: draft-ietf-httpbis-encryption-encoding-04.txt
Archived-At: <http://www.w3.org/mid/9de93353-e86d-9d57-6ea9-a802d18c7305@gmx.de>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/32787
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>
On 2016-11-01 00:29, 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 Hypertext Transfer Protocol of the IETF. > > Title : Encrypted Content-Encoding for HTTP > Author : Martin Thomson > Filename : draft-ietf-httpbis-encryption-encoding-04.txt > Pages : 16 > Date : 2016-10-31 > > Abstract: > This memo introduces a content coding for HTTP that allows message > payloads to be encrypted. > ... I have updated my Java P.o.C. at <https://gist.github.com/reschke/46659c912b426dffeac41d9a21421c95> accordingly. However, there's some weirdness in <https://greenbytes.de/tech/webdav/draft-ietf-httpbis-encryption-encoding-04.html#rfc.section.4.1> - the record size now used appears to be 41626 (it doesn't matter a lot because it's a single truncated record, but still). I assume that wasn't intentional, as the version in git has an updated example, but that gives me even a weirder rs. In general I'd like the examples to be a bit more verbose - spell out the record size and salt (previously the salt was in a header field), and maybe mention what padding was used (the second example uses two records, where one has 0 padding bytes, and the other has 1 -- you really have to implement...). Which leads me to another thought: it would be good to explain somewhat more when padding would be useful. In particular, if you write a library that implements an encoder, what would be a good way to specify padding? Having the same padding in every record probably wouldn't be good, right? Best regards, Julian
- I-D Action: draft-ietf-httpbis-encryption-encodin… internet-drafts
- Re: I-D Action: draft-ietf-httpbis-encryption-enc… Julian Reschke
- Re: I-D Action: draft-ietf-httpbis-encryption-enc… Martin Thomson