Re: [TLS] TLS Charter Revision

Stephen Farrell <stephen.farrell@cs.tcd.ie> Tue, 10 December 2013 08:59 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
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 1E9801AE0C4 for <tls@ietfa.amsl.com>; Tue, 10 Dec 2013 00:59:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-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 M9Xy8WNL6jWF for <tls@ietfa.amsl.com>; Tue, 10 Dec 2013 00:59:35 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id B2D5F1ADF33 for <tls@ietf.org>; Tue, 10 Dec 2013 00:59:35 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id A79F0BE4D; Tue, 10 Dec 2013 08:59:29 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hLBK7UpYrK03; Tue, 10 Dec 2013 08:59:27 +0000 (GMT)
Received: from [10.2.3.4] (unknown [95.83.250.203]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 560A2BE4C; Tue, 10 Dec 2013 08:59:27 +0000 (GMT)
User-Agent: K-9 Mail for Android
In-Reply-To: <A86275E1-44B7-444B-9E50-FD6DE5CC5190@cisco.com>
References: <2F2286E3-7717-4E8F-B1EA-B2E4155F7C17@cisco.com> <A86275E1-44B7-444B-9E50-FD6DE5CC5190@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Date: Tue, 10 Dec 2013 08:59:23 +0000
To: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>, "<tls@ietf.org>" <tls@ietf.org>
Message-ID: <7e7fa1fa-f889-4f3a-907d-670bb218d952@email.android.com>
Subject: Re: [TLS] TLS Charter Revision
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: Tue, 10 Dec 2013 08:59:39 -0000

Hi Joe

Wouid it be reasonable to add a "better privacy" goal for the tls 1.3 work? 

Ta
S


"Joseph Salowey (jsalowey)" <jsalowey@cisco.com> wrote:
>Updated Charter text based on the discussion so far is below.  Changes:
>
>
>1. Fixed typos 
>2. Third bullet to "Update record payload protection cryptographic
>mechanisms and algorithms to address known weaknesses
>in the CBC block cipher modes and to replace RC4."
>
>Thanks,
>
>Joe
>
>The TLS (Transport Layer Security) working group was
>established in 1996 to standardize a 'transport layer'
>security protocol.  The basis for the work was SSL
>(Secure Socket Layer) v3.0.  The TLS working group has
>completed a series of specifications that describe the
>TLS protocol v1.0, v1.1, and v1.2 and DTLS
>(Datagram TLS) v1.2 as well as extensions to the
>protocols and ciphersuites.
>
>The primary purpose of the working group is to develop
>(D)TLS v1.3.  Some of the main design goals are as follows,
>in no particular order:
>
>o Develop a mode that encrypts as much of the handshake as
>is possible to reduce the amount of observable data to
>both passive and active attackers.
>
>o Develop modes to reduce handshake latency, which primarily
>support HTTP-based applications, aiming for one roundtrip
>for a full handshake and one or zero roundtrip for repeated
>handshakes.
>
>o Update record payload protection cryptographic
>mechanisms and algorithms to address known weaknesses
>in the CBC block cipher modes and to replace RC4.
>
>o Reevaluate handshake contents, e.g.,: Is time needed in
>client hello?  Should signature in server key exchange
>cover entire handshake?  Are bigger randoms required?
>Should there be distinct cipher list for each version?
>
>A secondary purpose is to maintain previous version of
>the (D)TLS protocols as well as to specify the use of
>(D)TLS, recommendations for use of (D)TLS, extensions to
>(D)TLS, and cipher suites.  However, changes or additions
>to older versions of (D)TLS whether via extensions or
>ciphersuites are discouraged and require significant
>justification to be taken on as work items.
>
>With these objectives in mind, the TLS WG will also place a priority
>in minimizing gratuitous changes to TLS.
>
>Milestone/Dates:
>
>201311 - Out-of-Band Public Key Validation for TLS to IESG
>201401 - Secure Password Ciphersuites for TLS to IESG
>201404 - TLS ALPN (Application Layer Protocol Negotiation)
>      Extension to IESG
>201411 - (D)TLS 1.3 to IESG
>_______________________________________________
>TLS mailing list
>TLS@ietf.org
>https://www.ietf.org/mailman/listinfo/tls