Re: [TLS] Result of Working Group Last Call for draft-ietf-tls-padding-01

Yoav Nir <ynir.ietf@gmail.com> Sun, 22 March 2015 18:21 UTC

Return-Path: <ynir.ietf@gmail.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 E509A1A0022 for <tls@ietfa.amsl.com>; Sun, 22 Mar 2015 11:21:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 wDEeuK6Ol2tr for <tls@ietfa.amsl.com>; Sun, 22 Mar 2015 11:21:26 -0700 (PDT)
Received: from mail-wg0-x232.google.com (mail-wg0-x232.google.com [IPv6:2a00:1450:400c:c00::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 333C21A0030 for <tls@ietf.org>; Sun, 22 Mar 2015 11:21:26 -0700 (PDT)
Received: by wgs2 with SMTP id 2so22422425wgs.1 for <tls@ietf.org>; Sun, 22 Mar 2015 11:21:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=crRDJlCg6Ha8G01QRSn/lCu9JHHA9NcaU1v34XPlxU4=; b=FYzt/15GdH7SnvWH7m/k3S26HMJjYohsICweo8Gzg8xR3FvzoRtRJ6EiEO7w9PUt80 KsuHEKruABbBu+et67/KVnFmCmJ/qT2dia63rCIyRtiehvxM3rcLHjlVqggM9GYgvx1f ++LSg3JqxQ5Xc3814EuL6fK8LnO2zwVkkO4XcZz9yVOYB0Qj4/0THV0H3MJmc0dYuq4E tnG+zho1KN3Ydp8VXu1XjUmPz0scmd/tSkh/wTiGF2U3VSuuLVQPvgAzWdl2b796yaaW y7NgYZzymoQQ7DhHNDGzUA4DduCPlcBJMmuhOOvWAiKnUsAdUDeaO+mELVADgnV0ysQo il6w==
X-Received: by 10.194.200.8 with SMTP id jo8mr146709208wjc.64.1427048483956; Sun, 22 Mar 2015 11:21:23 -0700 (PDT)
Received: from ?IPv6:2001:67c:370:176:688d:9ee:8096:9d38? ([2001:67c:370:176:688d:9ee:8096:9d38]) by mx.google.com with ESMTPSA id ha10sm15850801wjc.37.2015.03.22.11.21.22 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 22 Mar 2015 11:21:23 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <CABkgnnX=jD3b22U55Cj8uAXpaAqh72PBPjaCCqc2un_FYjfweg@mail.gmail.com>
Date: Sun, 22 Mar 2015 13:21:20 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <0E4D835E-0FCB-48C3-8F25-E93967957A75@gmail.com>
References: <CAOgPGoB76fiaThKb_TvWpzqRtNjbneqhvm2+Vn7-Xp+htux5ZA@mail.gmail.com> <CABkgnnX=jD3b22U55Cj8uAXpaAqh72PBPjaCCqc2un_FYjfweg@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tls/I2WUaau5sWMpLVjPbL7OBHYBsLU>
Cc: "tls@ietf.org" <tls@ietf.org>
Subject: Re: [TLS] Result of Working Group Last Call for draft-ietf-tls-padding-01
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: Sun, 22 Mar 2015 18:21:28 -0000

> On Mar 22, 2015, at 12:54 PM, Martin Thomson <martin.thomson@gmail.com>; wrote:
> 
> On 22 March 2015 at 10:29, Joseph Salowey <joe@salowey.net>; wrote:
>> Below is my proto writeup for the draft-ietf-tls-padding-01.  Since there
>> were no comments on the draft during the last call I am going to request the
>> intended status as informational as the draft is documenting specific
>> practice that was used to work around a few specific implementations
>> problems that are being phased out.   If you would rather see the draft as
>> historic or standards track please respond to this message by March 27,
>> 2015.
> 
> I see no reason not to move for PS, but could live with Info.

The question is whether this is behavior that we want to standardize or a workaround that we want to document. 

Five years from now, and giving you the power to force everyone to upgrade their software, do you want this being used?

Yoav