Re: [TLS] TLS 1.3 process

Peter Gutmann <pgut001@cs.auckland.ac.nz> Sat, 29 March 2014 06:49 UTC

Return-Path: <pgut001@cs.auckland.ac.nz>
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 A60941A077B for <tls@ietfa.amsl.com>; Fri, 28 Mar 2014 23:49:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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 AIGDt9zs9dOL for <tls@ietfa.amsl.com>; Fri, 28 Mar 2014 23:49:30 -0700 (PDT)
Received: from mx2.auckland.ac.nz (mx2.auckland.ac.nz [130.216.125.245]) by ietfa.amsl.com (Postfix) with ESMTP id 5DC081A0775 for <tls@ietf.org>; Fri, 28 Mar 2014 23:49:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=auckland.ac.nz; i=@auckland.ac.nz; q=dns/txt; s=uoa; t=1396075768; x=1427611768; h=from:to:subject:date:message-id: content-transfer-encoding:mime-version; bh=steEr/EL9vCY26HKjskgxfoCj5XFT0oBnaAu6s91uow=; b=fagaGS6yhIhxw+FH4aEOfo1SMA3vr3xIHQX+Vx84OiuvfEMJszQ0dmBS +jLmQRjBgL3acGPC4T7M35T8UZYjE2Bcq5b4X5QX3N0B+Y2o5aClwbcme 0xJ3EinTP+wpjz5+BRWwsOjxaTQ4CFmpyvn+LV6E5dtt5q8Hpkk8Kn/y1 w=;
X-IronPort-AV: E=Sophos;i="4.97,755,1389697200"; d="scan'208";a="243520329"
X-Ironport-HAT: MAIL-SERVERS - $RELAYED
X-Ironport-Source: 130.216.4.171 - Outgoing - Outgoing
Received: from uxchange10-fe4.uoa.auckland.ac.nz ([130.216.4.171]) by mx2-int.auckland.ac.nz with ESMTP/TLS/AES128-SHA; 29 Mar 2014 19:49:27 +1300
Received: from UXCN10-6.UoA.auckland.ac.nz ([169.254.10.53]) by uxchange10-fe4.UoA.auckland.ac.nz ([130.216.4.171]) with mapi id 14.03.0174.001; Sat, 29 Mar 2014 19:49:27 +1300
From: Peter Gutmann <pgut001@cs.auckland.ac.nz>
To: "<tls@ietf.org>" <tls@ietf.org>
Thread-Topic: [TLS] TLS 1.3 process
Thread-Index: Ac9LGstTO2tDjcoISSCDrCseSVscCQ==
Date: Sat, 29 Mar 2014 06:49:26 +0000
Message-ID: <9A043F3CF02CD34C8E74AC1594475C7372395465@uxcn10-6.UoA.auckland.ac.nz>
Accept-Language: en-NZ, en-GB, en-US
Content-Language: en-NZ
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.216.158.4]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/tls/dwpPajUShQfi92ncrv_Sw5IGmvo
Subject: Re: [TLS] TLS 1.3 process
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: Sat, 29 Mar 2014 06:49:31 -0000

Adam Langley <agl@imperialviolet.org> writes:

>I would rather like to see a TLS 1.3 that is a tidying up of 1.2: merging the
>various RFCs into one, editing and pulling in some of the drafts that are
>floating around. The more significant changes could be 1.4.

Absolutely!  I don't want to have to add yet another parallel implementation
of a protocol that's just different enough that it's yet another set of code
and functionality to test, alongside SSLv3, TLS 1.0, and TLS 1.2.  All of the
previous updates have been compatible enough that you don't want to do a new
implementation, but incompatible enough that it's a different protocol.  Make
1.3 purely fixes for 1.2 and then start again with 2.0 so we can ditch all the
old baggage, complexity, and attack surface.

Peter.