[Unbearable] Adam Roach's Yes on draft-ietf-tokbind-protocol-17: (with COMMENT)

Adam Roach <adam@nostrum.com> Tue, 08 May 2018 03:48 UTC

Return-Path: <adam@nostrum.com>
X-Original-To: unbearable@ietf.org
Delivered-To: unbearable@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EB39F12D878; Mon, 7 May 2018 20:48:52 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Adam Roach <adam@nostrum.com>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-tokbind-protocol@ietf.org, John Bradley <ve7jtb@ve7jtb.com>, tokbind-chairs@ietf.org, ve7jtb@ve7jtb.com, unbearable@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.79.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152575133296.20185.13357598694255506687.idtracker@ietfa.amsl.com>
Date: Mon, 07 May 2018 20:48:52 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/unbearable/npAPoH9Uwcyev9DjxDO2U3Tq0WM>
Subject: [Unbearable] Adam Roach's Yes on draft-ietf-tokbind-protocol-17: (with COMMENT)
X-BeenThere: unbearable@ietf.org
X-Mailman-Version: 2.1.22
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, 08 May 2018 03:48:53 -0000

Adam Roach has entered the following ballot position for
draft-ietf-tokbind-protocol-17: Yes

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-tokbind-protocol/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thanks for a well-written document. I have only one very small nit to
incorporate if a new version of the document is produced prior to RFC editor
hand-off:

§1:

>  A Token Binding is established by a user agent generating a private-
>  public key pair (possibly, within a secure hardware module, such as
>  TPM)

Nit: remove comma after "possibly"