Re: [tcpm] SYN/ACK Payloads, draft 01

Eric Rescorla <ekr@networkresonance.com> Wed, 13 August 2008 18:05 UTC

Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 268E63A6990; Wed, 13 Aug 2008 11:05:47 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6D8343A683E for <tcpm@core3.amsl.com>; Wed, 13 Aug 2008 11:05:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.944
X-Spam-Level:
X-Spam-Status: No, score=-0.944 tagged_above=-999 required=5 tests=[AWL=1.655, BAYES_00=-2.599]
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 2-3OMVWb6hN2 for <tcpm@core3.amsl.com>; Wed, 13 Aug 2008 11:05:44 -0700 (PDT)
Received: from romeo.rtfm.com (romeo.rtfm.com [74.95.2.173]) by core3.amsl.com (Postfix) with ESMTP id 6CB233A6A0B for <tcpm@ietf.org>; Wed, 13 Aug 2008 11:05:44 -0700 (PDT)
Received: from romeo.rtfm.com (localhost.rtfm.com [127.0.0.1]) by romeo.rtfm.com (Postfix) with ESMTP id A1E6750848; Wed, 13 Aug 2008 11:16:30 -0700 (PDT)
Date: Wed, 13 Aug 2008 11:16:30 -0700
From: Eric Rescorla <ekr@networkresonance.com>
To: "Adam Langley" <agl@imperialviolet.org>
In-Reply-To: <396556a20808131047q781675a3if23d727ef5ae918f@mail.gmail.com>
References: <396556a20808111035s2b974233o1e9d3671e82e3350@mail.gmail.com> <20080813172752.AA7A650846@romeo.rtfm.com> <396556a20808131047q781675a3if23d727ef5ae918f@mail.gmail.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")
Message-Id: <20080813181630.A1E6750848@romeo.rtfm.com>
Cc: tcpm@ietf.org
Subject: Re: [tcpm] SYN/ACK Payloads, draft 01
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

At Wed, 13 Aug 2008 10:47:57 -0700,
Adam Langley wrote:
> 
> On Wed, Aug 13, 2008 at 10:27 AM, Eric Rescorla
> <ekr@networkresonance.com> wrote:
> > S 4. Opportunistic HTTP Encryption
> >
> > As I understand this mechanism, what's being proposed is this:
> [snip]
> > Do I have that right?
> 
> Yep,
> 
> > 1. The PPExt payload is overloaded here. First, it's signalling
> >   a transport message "it's OK to put stuff in the SYN/ACK". Second,
> >   it's signalling an application layer message "It's OK to send me
> >   a crypto handshake as the first thing you send." Note that in
> >   an ordinary HTTP connection, this data would be invalid.
> 
> Actually, it's only signaling the application extension. The SYNACK
> payloads are valid in any TCP connection, although this spec does make
> some guarantees about weather the stacks will process them.

I'm srory, I don't understand what you're saying here. Does this
data appear to the application to be part of the data stream
or not? 


> >   This overloading seems fairly unwise, since it would preclude
> >   any other use of this SYN/ACK payload in the future.
> 
> The format of the SYNACK payload for this scheme is similar to the
> option space: i.e. it's a tagged, extensible payload.

OK, this wasn't entirely clear from reading the draft.


 
> > 2. It's not clear to me that opportunistic security for HTTP is that
> >   great. Unlike, for instance, SMTP, HTTP fetches are nearly always
> >   the result of some URI, so it's very easy to simply indicate
> >   in the URI that the server supports HTTPS. This is superior
> >   from a security perspective for the usual reasons (referential
> >   integrity, etc...)
> 
> I believe that there's a use for a low-cost cryptographic scheme, such
> as this. Despite widespread TLS deployment, most traffic is still in
> the clear, including semi-sensitive information. I would rather that
> traffic be protected with TLS but, since that isn't happening, I would
> rather this than nothing.

But the premise of this scheme is that people don't do TLS
because of either (1) latency or (2) lack of opportunistic 
negotiation. As far as I can tell, neither is correct. Rather,
it's concerns about server performance. And server performance
can be improved by a number of mechanisms within TLS that
are (1) backward compatible with TLS and (2) don't require
modifying the kernel. 

That said, if you're willing to burn even very small amounts
of data in the SYN, you can do something TLS-compatible by
passing a compressed ClientHello of some kind + FastTrack.
This only works with static RSA one the server side, but
so does the scheme you propose.


> Opinions on this vary. Some folks think it's a great idea (including
> some working on implementing the TLS Fast-Track you cite below), some,
> like you are unimpressed. Fundamentally, I'm only asking for an option
> number to try it out.

As I indicated earlier, I'm not taking a position on whether you
should be assigned an 


> > 4. Some of the latency benefit you're getting here is from not
> >   negotiating the crypto algorithms; this is why in TLS the
> >   client speaks first. This isn't an issue for the symmetric
> >   algorithm since the server could provide a list, but it's
> >   a real issue for the asymmetric algorithm, since it provides
> >   no agility in the case of upgrade or compromise. If, for
> >   instance, someone successfully attacks this curve but there
> >   are other, strong curves available, then we'd be hosed.
> 
> Firstly, this isn't rigorous crypto, so the primitives here are in the
> enviable situation of being good enough if it's infeasible to break
> them in near-real time. If you want real security, use TLS.

Yeah, I'm not a big fan of inventing new things we know to be weaker
than the old things we already have, especially when the benefit
claimed by the newer thing seems marginal.

-Ekr

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm