Re: [TLS] Fwd: I-D Action:draft-bmoeller-tls-falsestart-00.txt

Bodo Moeller <bmoeller@acm.org> Fri, 04 June 2010 09:48 UTC

Return-Path: <SRS0=h2jj=NM=acm.org=bmoeller@srs.kundenserver.de>
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 E47443A6824 for <tls@core3.amsl.com>; Fri, 4 Jun 2010 02:48:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.223
X-Spam-Level:
X-Spam-Status: No, score=-100.223 tagged_above=-999 required=5 tests=[AWL=-0.574, BAYES_50=0.001, HELO_EQ_DE=0.35, USER_IN_WHITELIST=-100]
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 VJQGhQUXA-NO for <tls@core3.amsl.com>; Fri, 4 Jun 2010 02:48:03 -0700 (PDT)
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.8]) by core3.amsl.com (Postfix) with ESMTP id 51C883A6A1F for <tls@ietf.org>; Fri, 4 Jun 2010 02:47:29 -0700 (PDT)
Received: from [172.16.124.10] ([74.125.121.49]) by mrelayeu.kundenserver.de (node=mreu1) with ESMTP (Nemesis) id 0LkUgR-1Os9DQ1UTL-00bj7M; Fri, 04 Jun 2010 11:47:12 +0200
From: Bodo Moeller <bmoeller@acm.org>
To: Michael D'Errico <mike-list@pobox.com>
In-Reply-To: <4C07E6F8.2090102@pobox.com>
References: <AANLkTik3ZhyzI7-Re8FjNtC5xpH-aDplSyzcmgWoDgNd@mail.gmail.com> <2728902C-B235-4AAB-8EAE-19D673A38CB6@acm.org> <4C07E6F8.2090102@pobox.com>
Message-Id: <2F96175B-434C-4581-9C87-C68CF840D5FA@acm.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Fri, 4 Jun 2010 11:47:09 +0200
X-Mailer: Apple Mail (2.936)
X-Provags-ID: V01U2FsdGVkX1/1iGzyFMZuOrqAj5+vugpuD6kbZsPGIoQEiFE i3JVUPkeQNyUTze24IYIxYj0+1rtE/o8LUf8YKXPjvgsGCd4we MorQsQCSwrvsJxPO4xkZw==
Cc: TLS Working Group <tls@ietf.org>, Nagendra Modadugu <nagendra@cs.stanford.edu>
Subject: Re: [TLS] Fwd: I-D Action:draft-bmoeller-tls-falsestart-00.txt
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: Fri, 04 Jun 2010 09:51:05 -0000

On Jun 3, 2010, at 7:31 PM, Michael D'Errico wrote:

> I think the current name doesn't describe the feature very well.   
> SMTP and
> HTTP call it "pipelining" so perhaps you could use that name instead.

Michael,

thanks for the comment.

Yes, "TLS False Start" is an application of the pipelining principle.   
However, I think the name "pipelining" isn't sufficiently specific,  
and thus misleading: even without "False Start", you can have  
pipelining with TLS (for application data).

Furthermore, there are important non-obvious security considerations,  
and if we just called this "pipelining", implementors might mistakenly  
believe they know what's going on because they know pipelining from  
other protocols.  We do want them to read the security considerations  
first.  I hope that the name "False Start" becomes clear once you've  
got the idea behind it: a party starts before it has received a "go"  
signal.

Bodo