Re: HTTP/2 States and Frame Types <draft-ietf-httpbis-http2-17>

Ilari Liusvaara <ilari.liusvaara@elisanet.fi> Sat, 07 March 2015 15:48 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ietf.org@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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 091601A8A67 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sat, 7 Mar 2015 07:48:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.912
X-Spam-Level:
X-Spam-Status: No, score=-6.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 ZtjaKwAk4qSQ for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sat, 7 Mar 2015 07:48:45 -0800 (PST)
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 00B481A1A62 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Sat, 7 Mar 2015 07:48:45 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1YUGvb-0003O2-Q7 for ietf-http-wg-dist@listhub.w3.org; Sat, 07 Mar 2015 15:46:11 +0000
Resent-Date: Sat, 07 Mar 2015 15:46:11 +0000
Resent-Message-Id: <E1YUGvb-0003O2-Q7@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.80) (envelope-from <ilari.liusvaara@elisanet.fi>) id 1YUGvW-0003NL-1w for ietf-http-wg@listhub.w3.org; Sat, 07 Mar 2015 15:46:06 +0000
Received: from emh01.mail.saunalahti.fi ([62.142.5.107]) by lisa.w3.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <ilari.liusvaara@elisanet.fi>) id 1YUGvV-0002xa-0P for ietf-http-wg@w3.org; Sat, 07 Mar 2015 15:46:06 +0000
Received: from LK-Perkele-VII (a88-112-44-140.elisa-laajakaista.fi [88.112.44.140]) by emh01.mail.saunalahti.fi (Postfix) with ESMTP id 1A7DC9007D; Sat, 7 Mar 2015 17:45:40 +0200 (EET)
Date: Sat, 07 Mar 2015 17:45:40 +0200
From: Ilari Liusvaara <ilari.liusvaara@elisanet.fi>
To: Bob Briscoe <bob.briscoe@bt.com>
Cc: Martin Thomson <martin.thomson@gmail.com>, Mike Belshe <mbelshe@chromium.org>, "fenix@google.com" <fenix@google.com>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <20150307154540.GA21625@LK-Perkele-VII>
References: <201503061905.t26J5JmY015035@bagheera.jungle.bt.co.uk> <CABkgnnXSGmXH4w_9QGPfu8-ty6tQ3yiVLqCcENfxiEU1JHYPTw@mail.gmail.com> <201503071515.t27FFXAa022983@bagheera.jungle.bt.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
In-Reply-To: <201503071515.t27FFXAa022983@bagheera.jungle.bt.co.uk>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: Ilari Liusvaara <ilari.liusvaara@elisanet.fi>
Received-SPF: pass client-ip=62.142.5.107; envelope-from=ilari.liusvaara@elisanet.fi; helo=emh01.mail.saunalahti.fi
X-W3C-Hub-Spam-Status: No, score=-3.1
X-W3C-Hub-Spam-Report: AWL=-3.149, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001
X-W3C-Scan-Sig: lisa.w3.org 1YUGvV-0002xa-0P b44578973847bd71f5ec3ed41987112d
X-Original-To: ietf-http-wg@w3.org
Subject: Re: HTTP/2 States and Frame Types <draft-ietf-httpbis-http2-17>
Archived-At: <http://www.w3.org/mid/20150307154540.GA21625@LK-Perkele-VII>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/28909
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 Sat, Mar 07, 2015 at 03:15:33PM +0000, Bob Briscoe wrote:
> 
> If, as in HTTP/2, the length of the padding field is given in the protocol
> header (which is then encrypted), I believe the padding can be arbitrary,
> and I assume it's best for the padding not to be structured (predictable).

Any encryption algorithm that is anywhere even near secure can easily
deal with predictable padding (any that have problem with it should be
phased out immediately). Protocols are usually full of known plaintext
anyway.

And random padding actually causes problems (possibility of data
leakage).


-Ilari