IETF Logo Mail Archive

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

Adam Roach <adam@nostrum.com> Tue, 05 June 2018 19:07 UTC

Return-Path: <adam@nostrum.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 E9249130DC2; Tue, 5 Jun 2018 12:07:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.878
X-Spam-Level:
X-Spam-Status: No, score=-1.878 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=unavailable 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 g4PUgchollSn; Tue, 5 Jun 2018 12:07:49 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 CC233130DEE; Tue, 5 Jun 2018 12:07:49 -0700 (PDT)
Received: from Svantevit.local (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w55J7jgX074420 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 5 Jun 2018 14:07:46 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be Svantevit.local
To: Nick Harper <nharper@google.com>
Cc: Dirk Balfanz <balfanz@google.com>, The IESG <iesg@ietf.org>, John Bradley <ve7jtb@ve7jtb.com>, Tokbind WG <unbearable@ietf.org>, tokbind-chairs@ietf.org, draft-ietf-tokbind-https@ietf.org
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>
From: Adam Roach <adam@nostrum.com>
Message-ID: <69cb4854-912f-cc4f-1a61-d730ac53b89d@nostrum.com>
Date: Tue, 05 Jun 2018 14:07:40 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <CACdeXiLuNdafwooaADVqdk4xZQqG9GPjtM528JZR-Tfb3+TJ4Q@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------73847364591D96045D0457B1"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/unbearable/9i2KP0q_pU9vPXbbGM-6MlKKz5U>
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: Tue, 05 Jun 2018 19:07:52 -0000

On 6/5/18 2:01 PM, Nick Harper wrote:
> On Tue, Jun 5, 2018 at 11:50 AM, Adam Roach <adam@nostrum.com 
> <mailto: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

v2.23.0 | Report a Bug | By Email