Re: [TLS] Call for acceptance on multi-stapling

Nico Williams <nico@cryptonector.com> Thu, 19 April 2012 22:17 UTC

Return-Path: <nico@cryptonector.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D32DA11E80BB for <tls@ietfa.amsl.com>; Thu, 19 Apr 2012 15:17:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.949
X-Spam-Level:
X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MqwDQPGULQ5m for <tls@ietfa.amsl.com>; Thu, 19 Apr 2012 15:17:02 -0700 (PDT)
Received: from homiemail-a32.g.dreamhost.com (caiajhbdcbbj.dreamhost.com [208.97.132.119]) by ietfa.amsl.com (Postfix) with ESMTP id 0FADE11E80B8 for <tls@ietf.org>; Thu, 19 Apr 2012 15:17:02 -0700 (PDT)
Received: from homiemail-a32.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a32.g.dreamhost.com (Postfix) with ESMTP id B9DE8584059 for <tls@ietf.org>; Thu, 19 Apr 2012 15:17:01 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=cryptonector.com; h=mime-version :in-reply-to:references:date:message-id:subject:from:to:cc: content-type; q=dns; s=cryptonector.com; b=qgZicPvHUZDi0NIh0e+7y XonhKREaW1/JuzxvPcBNSbEXB795olkp4RjEO/xD957C0FqUFaPukQdtsFrrzDd8 XPtXQCOBVpX2H6nCFsBE8eamSKUC1/VwpXCkAkp4zjdTPcLnBSenKP2N8I+U5fn2 dkFLPQZFL14TnP0SASQK1c=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=30t8kP09wcP4ND0d2Yty 4I8Q7hs=; b=M+O5ImW2Wo/K6jtGv65yGmzWCzS2t6fEB83f5a11pCa9QD33CmnS dCDMfwehokeWcJLQRQmTQM68LJRCeIo8floviGOta6fvCmOls0E8RDkKiuJH7Bu2 ryG2BxJbIvhEpPgOKF47sXiLeZoTzlVuSPG9gnRiwIVVNsgotiMTuM8=
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a32.g.dreamhost.com (Postfix) with ESMTPSA id A13D5584057 for <tls@ietf.org>; Thu, 19 Apr 2012 15:17:01 -0700 (PDT)
Received: by pbbrp16 with SMTP id rp16so301335pbb.31 for <tls@ietf.org>; Thu, 19 Apr 2012 15:17:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.195.71 with SMTP id ic7mr7742972pbc.34.1334873821346; Thu, 19 Apr 2012 15:17:01 -0700 (PDT)
Received: by 10.68.28.6 with HTTP; Thu, 19 Apr 2012 15:17:01 -0700 (PDT)
In-Reply-To: <4F8FFCF5.9030202@extendedsubset.com>
References: <CAK3OfOi0DrCUs9DhgFgOGvTBr_nC93jGNkogpRsVZuQzsq1iRQ@mail.gmail.com> <201204191933.q3JJXbw4015580@fs4113.wdf.sap.corp> <CAK3OfOh_vgBmeRhZ=G4m52=3_2fgL+Scbru53SfP6=1EG5+2Wg@mail.gmail.com> <4F907B6E.3020704@pobox.com> <4F8FFCF5.9030202@extendedsubset.com>
Date: Thu, 19 Apr 2012 17:17:01 -0500
Message-ID: <CAK3OfOj=-Efx9tUCWVfBb2XUxc=navTaKqNiTGCDbnM=a17n1w@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Marsh Ray <marsh@extendedsubset.com>
Content-Type: text/plain; charset="UTF-8"
Cc: tls@ietf.org, aerowolf@gmail.com, Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: [TLS] Call for acceptance on multi-stapling
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.12
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/options/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: Thu, 19 Apr 2012 22:17:03 -0000

On Thu, Apr 19, 2012 at 6:54 AM, Marsh Ray <marsh@extendedsubset.com> wrote:
> Perhaps they didn't think the WG would adopt it and/or the servers would
> deploy support for it soon enough?

Dunno.  Suppose it'd worked?  Then it would have been wonderful that
it requires no server changes.  So that's my guess: Google was hoping
to have an optimization that works instantly with no changes required
on servers.

> I would love to support a revised version of the proposal
> http://tools.ietf.org/id/draft-bmoeller-tls-falsestart-00.txt
> that negotiated via a TLS extension.

Agreed.

Nico
--