Re: [TLS] Multi-Threaded Applications over TLS

Nicolas Williams <Nicolas.Williams@sun.com> Mon, 20 April 2009 21:08 UTC

Return-Path: <Nicolas.Williams@sun.com>
X-Original-To: tls@core3.amsl.com
Delivered-To: tls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 24FCB3A6DE9 for <tls@core3.amsl.com>; Mon, 20 Apr 2009 14:08:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.871
X-Spam-Level:
X-Spam-Status: No, score=-5.871 tagged_above=-999 required=5 tests=[AWL=0.175, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nipxWyQ12Ivb for <tls@core3.amsl.com>; Mon, 20 Apr 2009 14:08:50 -0700 (PDT)
Received: from sca-ea-mail-4.sun.com (sca-ea-mail-4.Sun.COM [192.18.43.22]) by core3.amsl.com (Postfix) with ESMTP id 2B96D3A68C4 for <tls@ietf.org>; Mon, 20 Apr 2009 14:08:50 -0700 (PDT)
Received: from dm-central-02.central.sun.com ([129.147.62.5]) by sca-ea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n3KLA6GP000040 for <tls@ietf.org>; Mon, 20 Apr 2009 21:10:06 GMT
Received: from binky.Central.Sun.COM (binky.Central.Sun.COM [129.153.128.104]) by dm-central-02.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL, v2.2) with ESMTP id n3KLA5ur012295 for <tls@ietf.org>; Mon, 20 Apr 2009 15:10:05 -0600 (MDT)
Received: from binky.Central.Sun.COM (localhost [127.0.0.1]) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3) with ESMTP id n3KL0ZRc014876; Mon, 20 Apr 2009 16:00:35 -0500 (CDT)
Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3/Submit) id n3KL0XO6014875; Mon, 20 Apr 2009 16:00:33 -0500 (CDT)
X-Authentication-Warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f
Date: Mon, 20 Apr 2009 16:00:33 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Badra <badra@isima.fr>
Message-ID: <20090420210033.GC1500@Sun.COM>
References: <c24c21d80904200553q3143219dk97e70709208db13b@mail.gmail.com> <20090420183341.81FB6185AE0@kilo.networkresonance.com> <c24c21d80904201151w1deb8fd7ob715df0741e2b839@mail.gmail.com> <20090420194154.E72DC185B38@kilo.networkresonance.com> <c24c21d80904201323l656c8105ud64938cf3ddca671@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <c24c21d80904201323l656c8105ud64938cf3ddca671@mail.gmail.com>
User-Agent: Mutt/1.5.7i
Cc: tls@ietf.org
Subject: Re: [TLS] Multi-Threaded Applications over TLS
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.9
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/listinfo/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: Mon, 20 Apr 2009 21:08:51 -0000

On Mon, Apr 20, 2009 at 10:23:16PM +0200, Badra wrote:
> On Mon, Apr 20, 2009 at 9:41 PM, Eric Rescorla <ekr@networkresonance.com>wrote:
> > Has anyone from the Web community expressed interest in this feature?
> 
> Eric, honestly I don't see why all these questions. The document is posted
> since only 7 hours, and I didn't contact offline any persons "off-line" for
> their comments.

I do.  Eric is quite right to point out that retrofitting existing apps
to use this facility may be difficult to the point that it won't happen.
If it won't happen then why do it?  Also, Eric's interest in whether
there is IETF interest in this for use in Internet protocols is
important to determining how much interest TLS WG (and other)
participants may have.

I also agree that this should be a separate layer, but negotiation of it
in TLS handshakes is useful as a way to start that layer sooner rather
than having to have an application-layer round-trip to negotiate its
use.

Nico
--