Re: [TLS] TLS 1.2

"Steven M. Bellovin" <smb@cs.columbia.edu> Sat, 27 August 2005 01:14 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E8pHV-0003Qm-Ja; Fri, 26 Aug 2005 21:14:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E8pHU-0003Qh-CT for tls@megatron.ietf.org; Fri, 26 Aug 2005 21:14:48 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA04579 for <tls@ietf.org>; Fri, 26 Aug 2005 21:14:46 -0400 (EDT)
Received: from machshav.com ([147.28.0.16]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E8pIJ-0006TP-7I for tls@ietf.org; Fri, 26 Aug 2005 21:15:40 -0400
Received: by machshav.com (Postfix, from userid 512) id D7DDCFB27D; Fri, 26 Aug 2005 21:14:37 -0400 (EDT)
Received: from berkshire.machshav.com (localhost [127.0.0.1]) by machshav.com (Postfix) with ESMTP id 139DBFB262; Fri, 26 Aug 2005 21:14:37 -0400 (EDT)
Received: from cs.columbia.edu (localhost [127.0.0.1]) by berkshire.machshav.com (Postfix) with ESMTP id 02AEF3BFFF4; Fri, 26 Aug 2005 21:14:35 -0400 (EDT)
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4
From: "Steven M. Bellovin" <smb@cs.columbia.edu>
To: Eric Rescorla <ekr@rtfm.com>
Subject: Re: [TLS] TLS 1.2
In-Reply-To: Your message of "Fri, 26 Aug 2005 16:49:34 PDT." <20050827003010.19815285E3@sierra.rtfm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Fri, 26 Aug 2005 21:14:35 -0400
Message-Id: <20050827011435.02AEF3BFFF4@berkshire.machshav.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: tls@ietf.org
X-BeenThere: tls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/tls>
List-Post: <mailto:tls@lists.ietf.org>
List-Help: <mailto:tls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@lists.ietf.org?subject=subscribe>
Sender: tls-bounces@lists.ietf.org
Errors-To: tls-bounces@lists.ietf.org

In message <20050827003010.19815285E3@sierra.rtfm.com>, Eric Rescorla writes:
>Folks,
>
>I'd like to start a discussion on whether we should be thinking
>about a TLS 1.2 that was more oriented towards newer hash 
>functions. Obviously, we're not at a point where there's
>a crisis yet but it doesn't hurt to be prepared.
>
>Steve Bellovin's and my take on this can be found at:
>
>http://www.educatedguesswork.org/movabletype/archives/2005/07/deploying_a_new.
>html
>
>Thinking ahead, if we get much list discussion we should probably
>plan to have some time in Vancouver...
>

Obviously, I agree that we should do something...  

At some point, we *will* need new hash functions.  That's probably 
years in the future, but realistically what we do will take years to 
deploy as well.  I figure 2 years for the spec to appear as an RFC 
(wg time, IESG time, RFC editor queues, etc.), another 1-2 years for 
vendors to design, code, and test, and 3-5 years for deployment.

		--Steven M. Bellovin, http://www.cs.columbia.edu/~smb



_______________________________________________
TLS mailing list
TLS@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/tls