IETF Logo Mail Archive

Re: [TLS] security levels for TLS

Eric Rescorla <ekr@networkresonance.com> Thu, 11 October 2007 16:27 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 1Ig0sb-0006de-UR; Thu, 11 Oct 2007 12:27:21 -0400
Received: from tls by megatron.ietf.org with local (Exim 4.43) id 1Ig0sa-0006cb-MN for tls-confirm+ok@megatron.ietf.org; Thu, 11 Oct 2007 12:27:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ig0sa-0006YS-9q for tls@lists.ietf.org; Thu, 11 Oct 2007 12:27:20 -0400
Received: from [74.95.2.169] (helo=delta.rtfm.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ig0sZ-00019v-3l for tls@lists.ietf.org; Thu, 11 Oct 2007 12:27:20 -0400
Received: from delta.rtfm.com (localhost.rtfm.com [127.0.0.1]) by delta.rtfm.com (Postfix) with ESMTP id 7722A33C28; Thu, 11 Oct 2007 09:23:12 -0700 (PDT)
Date: Thu, 11 Oct 2007 09:23:11 -0700
From: Eric Rescorla <ekr@networkresonance.com>
To: Nicolas Williams <Nicolas.Williams@sun.com>
Subject: Re: [TLS] security levels for TLS
In-Reply-To: <20071011162153.GO24532@Sun.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>
User-Agent: Wanderlust/2.14.0 (Africa) Emacs/21.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20071011162312.7722A33C28@delta.rtfm.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: tls@lists.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>
Errors-To: tls-bounces@lists.ietf.org

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.

-Ekr


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

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