Re: I-D Action: draft-ietf-httpbis-encryption-encoding-04.txt

Martin Thomson <> Wed, 02 November 2016 03:21 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6B38F1294F9 for <>; Tue, 1 Nov 2016 20:21:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -7.998
X-Spam-Status: No, score=-7.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-1.497, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 7EKVfeoqup0l for <>; Tue, 1 Nov 2016 20:21:12 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 8917F129851 for <>; Tue, 1 Nov 2016 20:21:10 -0700 (PDT)
Received: from lists by with local (Exim 4.80) (envelope-from <>) id 1c1m2t-0008TA-Uq for; Wed, 02 Nov 2016 03:16:59 +0000
Resent-Date: Wed, 02 Nov 2016 03:16:59 +0000
Resent-Message-Id: <>
Received: from ([]) by with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <>) id 1c1m2o-0008Dp-C7 for; Wed, 02 Nov 2016 03:16:54 +0000
Received: from ([]) by with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from <>) id 1c1m2i-00071J-2M for; Wed, 02 Nov 2016 03:16:49 +0000
Received: by with SMTP id x190so2006129qkb.0 for <>; Tue, 01 Nov 2016 20:16:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ERZcRr9WWEajJNOJoJHGfb9NewaMA7hGd1puHfyN+mk=; b=jyojfEjbETP3J3QetQmVkUV/RfhAsTYkv6LfXgc4nV/aOwoXa+yLho11u6c8HHk3Jv GsNar8tk3LOFvrDnRzrQnRztE16DPEYzLKi3BU8KbERJ203AdgLbHBP1yqXplL8v38dX 9zfObqnH1ftqgx0yeVTL7qr9VqnDKbZ4R1+zfFav/JNJBx5cKX9sq4CCWDtSfPPsWVkp 4c6/SN0W4tNAoD08CmjMjAM1LF1e6V8ktU3Ia6/nC9h33QUbu7qEq520HMM+eaPS70CF Wz1gEG6XPu4TjpgLlX5l+KR1/gS6RLeVDb5rODsKI62Q4Zwwmzim1hLLD18eINTeuJP5 bzLw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ERZcRr9WWEajJNOJoJHGfb9NewaMA7hGd1puHfyN+mk=; b=hWoqyYoyfro4lZ5KlDqSe1pV0sXvSw20pzh8eVC8XV8jsPRTUc9otIIMiTr68Huye/ 9EOL7BI+b4ybZ1nP0GpugpL882gFDbAYBOH3BWwe5sPJK7JmBW8Rt9bu5u0DUcIB1Dxb DX1isuv8GbYr7PGXEEK3u3/jf3WloNMxP1k8Lz7nt9xQgBDnMGv2hM50+zOqjBPW1q8/ 3kGWYOF//v6CqjOxhklKKN6NtUMB+0VCx3E4/vHqF1tpFslFoahJVZuI4nspq97Sxr/p 3VhQ+GtL1aQVxf85Rr2N24+uhkkKEzmU09UvhC+HJ/4e7/UkNAA2S/n8n8taXEPn3M+U 2IDw==
X-Gm-Message-State: ABUngvcxGN50hs7XYDcLNdJMb2BPMc1G9aSNYMc62928BT4P8kpcNuaWbPGsvrrIYHBLsPqgFZ5oDacelJbY/A==
X-Received: by with SMTP id i65mr1237931qkf.5.1478056581937; Tue, 01 Nov 2016 20:16:21 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Tue, 1 Nov 2016 20:16:21 -0700 (PDT)
In-Reply-To: <>
References: <> <>
From: Martin Thomson <>
Date: Wed, 2 Nov 2016 14:16:21 +1100
Message-ID: <>
To: Julian Reschke <>
Cc: HTTP Working Group <>
Content-Type: text/plain; charset=UTF-8
Received-SPF: pass client-ip=;;
X-W3C-Hub-Spam-Status: No, score=-6.1
X-W3C-Hub-Spam-Report: AWL=0.097, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: 1c1m2i-00071J-2M d538413d7554ce0aa8666bb7c5b58690
Subject: Re: I-D Action: draft-ietf-httpbis-encryption-encoding-04.txt
Archived-At: <>
X-Mailing-List: <> archive/latest/32803
Precedence: list
List-Id: <>
List-Help: <>
List-Post: <>
List-Unsubscribe: <>

On 2 November 2016 at 01:39, Julian Reschke <> wrote:
> 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...).

I've gone through and carefully checked the examples and updated them.
They should now be correct.

> 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?

Padding is hard to provide recommendations about.  I will try to find
some way to provide some guidance, but the generally accepted view is
that padding is hard.