IETF Logo Mail Archive

Re: [Unbearable] Switching exporters for 0-RTT Token Binding

Bill Cox <waywardgeek@google.com> Sun, 07 May 2017 04:06 UTC

Return-Path: <waywardgeek@google.com>
X-Original-To: unbearable@ietfa.amsl.com
Delivered-To: unbearable@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83D781242EA for <unbearable@ietfa.amsl.com>; Sat, 6 May 2017 21:06:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
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 PHH4ILiDO-L4 for <unbearable@ietfa.amsl.com>; Sat, 6 May 2017 21:06:42 -0700 (PDT)
Received: from mail-yw0-x22c.google.com (mail-yw0-x22c.google.com [IPv6:2607:f8b0:4002:c05::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8E7D91205F0 for <unbearable@ietf.org>; Sat, 6 May 2017 21:06:42 -0700 (PDT)
Received: by mail-yw0-x22c.google.com with SMTP id b68so17495547ywe.3 for <unbearable@ietf.org>; Sat, 06 May 2017 21:06:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=+0J33aYGxQ5S4G5JnoBaNxkD97H6YvtdxYHsCNS12kU=; b=Tb+OvXqQtcm4v68LKmpbj6mHUinWwB7BLXS2Z4d6ozFWqKqIitHDhztqk5UGIT7c+g oFShactVv0JX/tO6KgsQrZwO0n8MEPsQ6bskq2LFenL6xoGTziJZ7TtBUDif0a5zmlJg GJNmrF5esk/J7PdXXewC0BcHf51BemLZU2OsEUZYjL+ivs2JN9ku+yK6EdE+UdErVW0f BaOeKhdfRRsYM7x3ghaH2JJzgT/3e0HrRfPjXt+rT469Pcz0M+wxbvkyYBVAZlGSBsdO 2/3znoJnM39cG4oP9NXIi6/1+Kc3cJlOabCDG+fI3zT1zfCjqy49u7iQmJuZkYuntTR7 dJtg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=+0J33aYGxQ5S4G5JnoBaNxkD97H6YvtdxYHsCNS12kU=; b=uflCfKa9bEnoVjK4xeXrBQVaAlseH5A89rf+xER96TvFk742k9t5kH3Pr77D4G7Udm KzD28cxEpbUP/dtbmWiOFzzuXQECJJ+tdbyaOFrHsbVdf3IarqRt826OZMTL2lrCspe8 fnsM/ay4M0RQ3TGrlecPYXseUayrSjVmGYdz/bdrRLCQU8wveAbyHgzgPK+sHaUpBsav DiDKq8Iq11yBnVTjA33wtXDo3VuXZxuRxRU/j1je8x8UQTaiXCJnDYXx1c95iF4OqIeM AzesfOyhhJ23Z2Dpl4KCSbIDXvpS9MktoTBNK94Vmt4WeNZ1HyRJ476oU+Isr0v2EJSE 9yTg==
X-Gm-Message-State: AN3rC/52hecydDcVwrHcUN8I58Wvq7vgA/mOKv402aovAcpWWkJEWBhG vb1pHMdFLa8aJUWxMAG5f004myrPWf+t
X-Received: by 10.129.93.65 with SMTP id r62mr44815158ywb.95.1494130001492; Sat, 06 May 2017 21:06:41 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.13.222.70 with HTTP; Sat, 6 May 2017 21:06:41 -0700 (PDT)
In-Reply-To: <20170506180431.GY30306@kduck.kaduk.org>
References: <CACdeXiLF3G8tBO5z5L2mfe5N-kYMv_4TNFS2_0YdecquMM_kuw@mail.gmail.com> <20170420020846.GY30306@kduck.kaduk.org> <CACdeXiLPb-QwLhG89ahV_q8q3n16jA+WEnsTzKTAyMtYcVF4Pw@mail.gmail.com> <SN1PR21MB0096D78DF3E9C07B23DC76078C100@SN1PR21MB0096.namprd21.prod.outlook.com> <20170428021355.GY30306@kduck.kaduk.org> <CACdeXiLGL7ejX00xkHPDwd1gTEaxD++QEisH9v_R=hSHJA9KJw@mail.gmail.com> <20170506180431.GY30306@kduck.kaduk.org>
From: Bill Cox <waywardgeek@google.com>
Date: Sat, 06 May 2017 21:06:41 -0700
Message-ID: <CAH9QtQF9kC5a2Fp0WbfV3+UcmpOjA1DA=QGquBKHhxi-CizGFQ@mail.gmail.com>
To: Benjamin Kaduk <kaduk@mit.edu>
Cc: Nick Harper <nharper@google.com>, Andrei Popov <Andrei.Popov@microsoft.com>, IETF Tokbind WG <unbearable@ietf.org>
Content-Type: multipart/alternative; boundary="001a114d9c7afd11f4054ee73f34"
Archived-At: <https://mailarchive.ietf.org/arch/msg/unbearable/NtSDxyPz4s8Tr0YdXDewSkjxQEo>
Subject: Re: [Unbearable] Switching exporters for 0-RTT Token Binding
X-BeenThere: unbearable@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "\"This list is for discussion of proposals for doing better than bearer tokens \(e.g. HTTP cookies, OAuth tokens etc.\) for web applications. The specific goal is chartering a WG focused on preventing security token export and replay attacks.\"" <unbearable.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/unbearable>, <mailto:unbearable-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/unbearable/>
List-Post: <mailto:unbearable@ietf.org>
List-Help: <mailto:unbearable-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/unbearable>, <mailto:unbearable-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 May 2017 04:06:44 -0000

Sticking with the original EKM makes a lot of sense to me.  Is anyone
proposing sending 0-RTT data that is poorly protected, and then later
sending 1-RTT data that is better protected?  Does anyone feel that is a
good idea?  I hope not, in which case, sticking with the original EMK makes
sense.

+1 for sticking with the original EKM value.

Bill

On Sat, May 6, 2017 at 11:04 AM, Benjamin Kaduk <kaduk@mit.edu> wrote:

> On Fri, May 05, 2017 at 01:25:15PM -0700, Nick Harper wrote:
> > It sounds like the consensus on this thread is that 0-RTT TB should
> > use the 0-RTT exporter for the whole connection - switching exporters
> > adds complexity, and no use cases have been identified where it
> > provides extra value. I will update the draft to have it not switch
> > exporters. Once I make the language change around switching exporters
> > and also resolve the 4 issues currently open on
> > https://github.com/nharper/0-rtt-token-binding/issues, I'll upload a
> > new I-D.
>
> This is not the list for the WG of which I'm chair, so it is not my
> call to make, but I would worry that there was insufficient input in
> the thread from which to make a claim of consensus.
>
> Chairs, am I in the woods?
>
> -Ben
>
> _______________________________________________
> Unbearable mailing list
> Unbearable@ietf.org
> https://www.ietf.org/mailman/listinfo/unbearable
>

v2.23.0 | Report a Bug | By Email