Re: [TLS] Fixing TLS

Dave Garrett <davemgarrett@gmail.com> Tue, 12 January 2016 18:06 UTC

Return-Path: <davemgarrett@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 616621A0252 for <tls@ietfa.amsl.com>; Tue, 12 Jan 2016 10:06:37 -0800 (PST)
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 uscRC-DoePdu for <tls@ietfa.amsl.com>; Tue, 12 Jan 2016 10:06:35 -0800 (PST)
Received: from mail-qg0-x22c.google.com (mail-qg0-x22c.google.com [IPv6:2607:f8b0:400d:c04::22c]) (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 60AFD1A024E for <tls@ietf.org>; Tue, 12 Jan 2016 10:06:35 -0800 (PST)
Received: by mail-qg0-x22c.google.com with SMTP id 6so356462946qgy.1 for <tls@ietf.org>; Tue, 12 Jan 2016 10:06:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:user-agent:cc:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; bh=GmeHU+y2xSccMHJe/O7OAx8yMjpUkzVVqdDYfNJt7IQ=; b=yx1Ghra0MiffNOsZDfM5ccImxEk65NucSkeHv+JWq5YppDdCl3kwriq3NsM7eIiN1w jaWqQSEa+kfQLPcTVhBl1T6UNdOFJIohrCC3XL8sCItVmhGj7JG3sgF4zezTFi9xCnXR xuquBGpTVS5FipmQRWm4smUtM07u2LBQ3aibJNAGCkj2X5gSf0AYdZRPQ4ppJJJ7PUO2 wnzEidD/tMwIKaTUU7g/dvTpHxMtkNhAIDM/c+l21HQ6oxQ5k1uFPd5fjrTTxr4Jh767 yvErqLo3L96ud97G1X206tpeoby+RZ3gKgmxtyXu9Hy4NCdj/4n3v/ODNdOSij2i5I5y WOrw==
X-Received: by 10.140.137.199 with SMTP id 190mr179843807qhj.91.1452621994406; Tue, 12 Jan 2016 10:06:34 -0800 (PST)
Received: from dave-laptop.localnet (pool-72-94-152-197.phlapa.fios.verizon.net. [72.94.152.197]) by smtp.gmail.com with ESMTPSA id o75sm10598915qgd.12.2016.01.12.10.06.33 (version=TLS1 cipher=AES128-SHA bits=128/128); Tue, 12 Jan 2016 10:06:33 -0800 (PST)
From: Dave Garrett <davemgarrett@gmail.com>
To: Peter Bowen <pzbowen@gmail.com>
Date: Tue, 12 Jan 2016 13:06:32 -0500
User-Agent: KMail/1.13.5 (Linux/2.6.32-74-generic-pae; KDE/4.4.5; i686; ; )
References: <9A043F3CF02CD34C8E74AC1594475C73F4BC6849@uxcn10-5.UoA.auckland.ac.nz> <CAK6vND9x-QOsvfA4bmz-GbbF8kEx8kv22mDPbCm=mEqXe_XvAg@mail.gmail.com> <CAK6vND_SbHY_mY4VXH+C4E6d6k_6ChLT7trTfz3PfQytnN=Khg@mail.gmail.com>
In-Reply-To: <CAK6vND_SbHY_mY4VXH+C4E6d6k_6ChLT7trTfz3PfQytnN=Khg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: Text/Plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-Id: <201601121306.32859.davemgarrett@gmail.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/tls/mwzAegn97kZw8648ytc_r7TVKMw>
Cc: "tls@ietf.org" <tls@ietf.org>
Subject: Re: [TLS] Fixing TLS
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 12 Jan 2016 18:06:37 -0000

On Tuesday, January 12, 2016 12:51:28 pm Peter Bowen wrote:
> On Tue, Jan 12, 2016 at 9:27 AM, Peter Bowen <pzbowen@gmail.com>; wrote:
> > - No TLS_ECDHE_PSK_WITH_AES_128_GCM_SHA256 cipher suite allocated
> > (BoringSSL has an implementation using cipher suite 0xca,0xfe)
> 
> Correction: draft-mattsson-tls-ecdhe-psk-aead-03 defines this suite.
> Still no cipher suite allocated, but there is an active draft.

I have a short WIP PR for integrating these suites into the TLS 1.3 draft sitting on GitHub, by the way.

https://github.com/tlswg/tls13-spec/pull/381

Unless I'm misunderstanding the procedure here, though, that draft needs to progress to WG adoption before we're ready for it here. (hence the WIP label)


Dave