Re: [TLS] Fwd: New Version Notification for draft-thomson-http-replay-00.txt

Willy Tarreau <w@1wt.eu> Mon, 26 June 2017 08:01 UTC

Return-Path: <w@1wt.eu>
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 C0E19126C23 for <tls@ietfa.amsl.com>; Mon, 26 Jun 2017 01:01:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LM2nrCWff0Qs for <tls@ietfa.amsl.com>; Mon, 26 Jun 2017 01:01:41 -0700 (PDT)
Received: from 1wt.eu (wtarreau.pck.nerim.net [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id 75EA0127B5A for <tls@ietf.org>; Mon, 26 Jun 2017 01:01:36 -0700 (PDT)
Received: (from willy@localhost) by pcw.home.local (8.15.2/8.15.2/Submit) id v5Q81VNb003927; Mon, 26 Jun 2017 10:01:31 +0200
Date: Mon, 26 Jun 2017 10:01:31 +0200
From: Willy Tarreau <w@1wt.eu>
To: Kazuho Oku <kazuhooku@gmail.com>
Cc: Martin Thomson <martin.thomson@gmail.com>, "tls@ietf.org" <tls@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <20170626080131.GC3730@1wt.eu>
References: <149811425736.30341.16596521802774811431.idtracker@ietfa.amsl.com> <CABkgnnU4E0AH5=_xSoQVq49J8fHxPHBchVAMmD57KO2Y5WjVCw@mail.gmail.com> <CANatvzx8rPPQ-gpPyYAPuvZ4NBFxwSZZHVTEOuAbU0hbAG1Wwg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CANatvzx8rPPQ-gpPyYAPuvZ4NBFxwSZZHVTEOuAbU0hbAG1Wwg@mail.gmail.com>
User-Agent: Mutt/1.6.1 (2016-04-27)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/RcXh5C7bdCmtjynhh2r8xCplCqU>
Subject: Re: [TLS] Fwd: New Version Notification for draft-thomson-http-replay-00.txt
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 26 Jun 2017 08:01:42 -0000

Hi Kazuho,

On Mon, Jun 26, 2017 at 04:03:24PM +0900, Kazuho Oku wrote:
> One question: is the name `early-data` a good choice?
> 
> The reason I raise the concern is because what the header suggest is
> if the endpoint has not yet seen a proof (i.e. ClientFinished). The
> name "early-data" might be confusing since it may seem to imply _when_
> the request has been received rather than the current state of the
> connection.

You mean that you'd prefer something indicating that there were unsafe
(ie not yet validated) early data in fact, that's it ?

Willy