IETF Logo Mail Archive

Re: [TLS] Next steps for draft-agl-tls-padding

Adam Langley <agl@google.com> Wed, 08 January 2014 19:29 UTC

Return-Path: <agl@google.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 748701ADFF7 for <tls@ietfa.amsl.com>; Wed, 8 Jan 2014 11:29:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.917
X-Spam-Level:
X-Spam-Status: No, score=-1.917 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] 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 ZzOGMteHxnE4 for <tls@ietfa.amsl.com>; Wed, 8 Jan 2014 11:29:53 -0800 (PST)
Received: from mail-vb0-x22b.google.com (mail-vb0-x22b.google.com [IPv6:2607:f8b0:400c:c02::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 6AB901ADFCB for <tls@ietf.org>; Wed, 8 Jan 2014 11:29:53 -0800 (PST)
Received: by mail-vb0-f43.google.com with SMTP id p6so1473733vbe.2 for <tls@ietf.org>; Wed, 08 Jan 2014 11:29:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=921NSC4/daidsBs9Bh2d1Jffb4zbpbORIBqvx6uJmYU=; b=Xa22DHJHx8l5bJXGqyms8kklQeXWTtfKoUAdDMQvQvg6FPtYy8EjSgaGk5JNqGXds7 gQfPKiJspP2j6Zq57RGAMGAb63Cg4RCPSadJiJwGrlOKmf/1snk4Y9/lMtOUtzkI6gxg sNqUvxtjCWfm674adY2gr0mlt2zjoLFlgz6ojxYurVhUFTcyuKf1qvUpk+VQvU1Y7Xze YVdzsS6Zr21Cz08VyNLNbfwwZOfIi0JrurcsqM+c2/lMxN+c8G/1VTKZJEesGs9v4P9S Eh1VE3tI1KZZnbRF1cmGFnzzlOnTnbNrQz+/Xsfb3nXAmmNtidUYvvYhsHo5/rmMlYIK BV4g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=921NSC4/daidsBs9Bh2d1Jffb4zbpbORIBqvx6uJmYU=; b=K+WhzKMh2GAEu+sSyEMTxia9cgkjtHszU+J1RTf6xBytU27jeTrrfJsxrkd5DNfSn1 XOeaR3e4Vz0di5u0lSNXTpnVbIOnXKbDFTz8IsAPy6pEvHJGPTtHClCclKS4gYJTNcOY yLWqgeScpIc3cy5QIplgxEWE3yi66BzZd9LpgkMX+DijG6W8MJAYbdY8p5s/0vAE9bYg fomj7FP/KVNqMGPr4lNLmIENsQda+eoyIgIl+NMhHO3CAYPLpegzhOVgmzRJR4FsWxmW 2GQVcN/iEFTVbPEeAD+PJXDoPIlLkZhu0v2vfgRcBn0e22rBWkH1d0YNxIpfy22OcJrQ O3tg==
X-Gm-Message-State: ALoCoQlUU8mrmy2kly5E1dpqe3Pcr+I9rCHKFWDnUeLdfb89NQ1aKnpb7eDq6FF+JalGXjd2vaSwr20+vVCUHblk4jGpgP88hNnC5S+qw63Toug5uTU9qE2jH8ymcRmcR6+VVVix38GnOxZwNJB3X0hX3eETbsQm1ZeTZhnz0Xokq07fcrDlZ4W/6xnPlbOkKZGOlzWouThw
X-Received: by 10.58.152.130 with SMTP id uy2mr4581757veb.71.1389209383823; Wed, 08 Jan 2014 11:29:43 -0800 (PST)
MIME-Version: 1.0
Received: by 10.52.96.134 with HTTP; Wed, 8 Jan 2014 11:29:23 -0800 (PST)
In-Reply-To: <20140107201722.ECDA01AB93@ld9781.wdf.sap.corp>
References: <cf049a7104934cc7a4bddced33cd00a2@BL2PR03MB419.namprd03.prod.outlook.com> <20140107201722.ECDA01AB93@ld9781.wdf.sap.corp>
From: Adam Langley <agl@google.com>
Date: Wed, 08 Jan 2014 14:29:23 -0500
Message-ID: <CAL9PXLzawuetexEvU5PECUwuuiLvq5T0bxnhiky3cevQpetjNQ@mail.gmail.com>
To: mrex@sap.com
Content-Type: text/plain; charset="UTF-8"
Cc: "tls@ietf.org" <tls@ietf.org>
Subject: Re: [TLS] Next steps for draft-agl-tls-padding
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jan 2014 19:29:55 -0000

On Tue, Jan 7, 2014 at 3:17 PM, Martin Rex <mrex@sap.com> wrote:
> A provisional code point would be nice, but I had to read the
> description of the extension contents several times and cross-check
> with other TLS extension documents to figure out (and assure myself)
> what draft-agl-tls-padding-02 really means implementation-wise.

Thanks for the comments. I think you make a good point and I've
updated the draft
(https://tools.ietf.org/html/draft-agl-tls-padding-03) to include your
suggestions. (It'll need to be updated with the precise extension
type, if assigned.)


Cheers

AGL

v2.23.0 | Report a Bug | By Email