Re: [Unbearable] Adam Roach's Yes on draft-ietf-tokbind-https-14: (with COMMENT)

Dirk Balfanz <balfanz@google.com> Wed, 06 June 2018 05:11 UTC

Return-Path: <balfanz@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 43B89130E96 for <unbearable@ietfa.amsl.com>; Tue, 5 Jun 2018 22:11:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.51
X-Spam-Level:
X-Spam-Status: No, score=-17.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=unavailable 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 kXmmUUYmkj9P for <unbearable@ietfa.amsl.com>; Tue, 5 Jun 2018 22:11:44 -0700 (PDT)
Received: from mail-wr0-x22e.google.com (mail-wr0-x22e.google.com [IPv6:2a00:1450:400c:c0c::22e]) (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 65F03130E37 for <unbearable@ietf.org>; Tue, 5 Jun 2018 22:11:41 -0700 (PDT)
Received: by mail-wr0-x22e.google.com with SMTP id w10-v6so4721738wrk.9 for <unbearable@ietf.org>; Tue, 05 Jun 2018 22:11:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=m5ca3KygPKCDi5mjgeT7rhsbm+zw4TvsgtLLv7m96Xs=; b=I029BsdWlJjFPxBieaLPRycqPQdH/+XMSWjq+J2aAnXqPI1Dtoip6QI8j78MwpVW9M annE4sCurjaKQlVlvrh5QOqR3k1pgD7J8XF/CT9TBrzB0WgpYQWs8prq0mhQyXLzpNEh yt0EJp06yczyhpjjafgwwoXg0B05ap2Y0enPe5Z9GKNjb/jE11Oa2OAcloliaK6yj2ai +L5H4aFMPncw2fC8nZIDe+qG0S/1D+08zVSnUxuieMKyC1rez4i6z8xBT7fdpygKxcq6 mBPRpV2Gxom7YCERZniLSpTjS6dl75bZgsr2rqLXGfa/D3tu6y4lvNUSGOV//IDHfqqN Y+9A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=m5ca3KygPKCDi5mjgeT7rhsbm+zw4TvsgtLLv7m96Xs=; b=cJo6OkVfRaMmR0dBVPlezH09+sscpCIn2/4cXVIDAVRUPxXIEuNcpjqeP/+yT2c+9O 5qCrRk3CB0DBuTlq+lNRCQyZaE6NOoEE5cEvSMjP2giVGBhrzbFmsYDeeznvBDBdaZFm fuLDsiE9E2OHPEFMYXxrwEOvWo4VMkGWb2PQQUESva2sPQy0IKPG8xX0kCqjLaxUwf4u l7eOBoOXGG5WCL1mkUn/BWb0Esa0LRLFk31debKTjaawrzX0AQJpspgnUpY1Hs09wK9B kSIsEOJrG3gxoo6XWGgRkv93ssoXdLWWt7wDkCetKthEhmb3c3+KAzvxhm+ZskyQZK6J tA3Q==
X-Gm-Message-State: APt69E1tDXTODRhnKHRmmwmnK5zqC4WsUu1a/rQtFSguGkrf0PaI44m8 TgUFI1o7IeWVlxUcViaMw8Da6zfm8dncPh+gXj5E+g==
X-Google-Smtp-Source: ADUXVKJ8877+JUuXGPQRUtlJW9QOGTW9LLPwOTBaVshBo94qh5C+R46LsVhuQzvRbdoEmbxrMpZ+IM6y6QwSk3SgkRI=
X-Received: by 2002:adf:eccd:: with SMTP id s13-v6mr1078147wro.160.1528261899477; Tue, 05 Jun 2018 22:11:39 -0700 (PDT)
MIME-Version: 1.0
References: <152575956787.20253.13180458622500226833.idtracker@ietfa.amsl.com> <CADHfa2DPni78gNNZyQr6Tbt6DTzVWY+md7L4220NPTDprUCp6A@mail.gmail.com> <c103c5d7-3508-23b5-aae0-165dcd81db17@nostrum.com> <CACdeXiKnuLxR5ZVn9D9p9CHk+SBqFMOJGeziKjVNAw9AifvmMQ@mail.gmail.com> <b9cc789a-6b18-38d1-e693-479071c70f16@nostrum.com> <CACdeXiLuNdafwooaADVqdk4xZQqG9GPjtM528JZR-Tfb3+TJ4Q@mail.gmail.com> <69cb4854-912f-cc4f-1a61-d730ac53b89d@nostrum.com> <CAANoGh+4G73ZD0FrHLqj1Jrb4SpfEt=SO33zmHmVeD2M0pDkuw@mail.gmail.com>
In-Reply-To: <CAANoGh+4G73ZD0FrHLqj1Jrb4SpfEt=SO33zmHmVeD2M0pDkuw@mail.gmail.com>
From: Dirk Balfanz <balfanz@google.com>
Date: Tue, 5 Jun 2018 22:11:27 -0700
Message-ID: <CADHfa2BomchYmQWOBzS0_GVhkS33C9atTvQy-VYujwvLUYoJuQ@mail.gmail.com>
To: John Bradley <ve7jtb@ve7jtb.com>
Cc: Adam Roach <adam@nostrum.com>, Nick Harper <nharper@google.com>, The IESG <iesg@ietf.org>, Tokbind WG <unbearable@ietf.org>, tokbind-chairs@ietf.org, draft-ietf-tokbind-https@ietf.org
Content-Type: multipart/alternative; boundary="000000000000a4d0ec056df23312"
Archived-At: <https://mailarchive.ietf.org/arch/msg/unbearable/b8AtTUooZRXOxlY-Yo8gmzoolMg>
Subject: Re: [Unbearable] Adam Roach's Yes on draft-ietf-tokbind-https-14: (with COMMENT)
X-BeenThere: unbearable@ietf.org
X-Mailman-Version: 2.1.26
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: Wed, 06 Jun 2018 05:11:47 -0000

I uploaded a new draft (
https://tools.ietf.org/html/draft-ietf-tokbind-https-17) that includes a
non-normative reference to tokbind-tls13, and some clarifying language
around redirects.

Dirk.

On Tue, Jun 5, 2018 at 12:28 PM John Bradley <ve7jtb@ve7jtb.com> wrote:

> I think adding a non normative reference to the current draft of tls13 is
> fine.  The data tracker will have the forward reference to the final spec
> if someone follows it.
>
> John B.
>
> On Tue, Jun 5, 2018, 9:07 PM Adam Roach <adam@nostrum.com> wrote:
>
>> On 6/5/18 2:01 PM, Nick Harper wrote:
>>
>> On Tue, Jun 5, 2018 at 11:50 AM, Adam Roach <adam@nostrum.com> wrote:
>>
>>> Then please add an informative reference to draft-ietf-tokbind-tls13.
>>>
>>> /a
>>>
>> The reason for splitting off draft-ietf-tokbind-tls13 into a separate
>> draft was so that publication of draft-ietf-tls-tls13 doesn't delay
>> publication of the 3 core tokbind drafts (draft-ietf-tokbind-protocol,
>> draft-ietf-tokbind-negotiation, and draft-ietf-tokbind-https). It sounds
>> like adding a reference to draft-ietf-tokbind-tls13 would result in
>> postponing publication of at least this draft until both
>> draft-ietf-tls-tls13 and draft-ietf-tokbind-tls13 get published.
>>
>>
>> It would if the reference were normative. This is why I said "informative
>> reference" above.
>>
>> /a
>>
>