IETF Logo Mail Archive

Re: [TLS] security levels for TLS

"Steven M. Bellovin" <smb@cs.columbia.edu> Thu, 11 October 2007 18:26 UTC

Return-path: <tls-bounces@lists.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ig2kA-0003sz-Kx; Thu, 11 Oct 2007 14:26:46 -0400
Received: from tls by megatron.ietf.org with local (Exim 4.43) id 1Ig2k9-0003nv-B9 for tls-confirm+ok@megatron.ietf.org; Thu, 11 Oct 2007 14:26:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ig2k9-0003nn-1T for tls@lists.ietf.org; Thu, 11 Oct 2007 14:26:45 -0400
Received: from machshav.com ([198.180.150.44]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ig2k3-0006Gh-Tw for tls@lists.ietf.org; Thu, 11 Oct 2007 14:26:45 -0400
Received: by machshav.com (Postfix, from userid 512) id BAB0B5B4; Thu, 11 Oct 2007 18:26:27 +0000 (GMT)
Received: from berkshire.machshav.com (localhost [127.0.0.1]) by machshav.com (Postfix) with ESMTP id 86C0A171; Thu, 11 Oct 2007 18:26:27 +0000 (GMT)
Received: from berkshire.machshav.com (localhost [127.0.0.1]) by berkshire.machshav.com (Postfix) with ESMTP id AE299766013; Thu, 11 Oct 2007 14:26:27 -0400 (EDT)
Date: Thu, 11 Oct 2007 18:26:27 +0000
From: "Steven M. Bellovin" <smb@cs.columbia.edu>
To: Eric Rescorla <ekr@networkresonance.com>
Subject: Re: [TLS] security levels for TLS
Message-ID: <20071011182627.72bc12fd@berkshire.machshav.com>
In-Reply-To: <20071011162312.7722A33C28@delta.rtfm.com>
References: <c331d99a0710080621g7c0ec91et35c46553c23f4402@mail.gmail.com> <p0624082fc331b0ed0ecc@[192.168.1.100]> <FA998122A677CF4390C1E291BFCF59890849871E@EXCH.missi.ncsc.mil> <470D0243.3050009@pobox.com> <20071010180324.7ABC533C21@delta.rtfm.com> <470E4399.3010008@pobox.com> <20071011155829.965C733C28@delta.rtfm.com> <20071011162153.GO24532@Sun.COM> <20071011162312.7722A33C28@delta.rtfm.com>
Organization: Columbia University
X-Mailer: Claws Mail 3.0.1 (GTK+ 2.10.14; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: tls@lists.ietf.org, Nicolas Williams <Nicolas.Williams@sun.com>
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>
Errors-To: tls-bounces@lists.ietf.org

On Thu, 11 Oct 2007 09:23:11 -0700
Eric Rescorla <ekr@networkresonance.com> wrote:

> At Thu, 11 Oct 2007 11:21:53 -0500,
> Nicolas Williams wrote:
> > On Thu, Oct 11, 2007 at 08:58:27AM -0700, Eric Rescorla wrote:
> > > And again, this is an API/local isssue. IETF doesn't do
> > > those.
> > 
> > There you go again.  The IETF most certainly deals in APIs.
> 
> Let me rephrase: the IETF generally doesn't deal in APIs with a few
> prominent exceptions. The TLS-WG has never done so and I don't think
> it's a good idea to do so now.
> 
And certainly not where the goal is this dubious.  I'm with ekr: this
is a bad idea.


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


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

v2.26.15 | Report a Bug | By Email | System Status