[Unbearable] Warren Kumari's No Objection on draft-ietf-tokbind-https-14: (with COMMENT)

Warren Kumari <warren@kumari.net> Wed, 09 May 2018 15:17 UTC

Return-Path: <warren@kumari.net>
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 7F5271242F5; Wed, 9 May 2018 08:17:06 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Warren Kumari <warren@kumari.net>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-tokbind-https@ietf.org, John Bradley <ve7jtb@ve7jtb.com>, tokbind-chairs@ietf.org, ve7jtb@ve7jtb.com, unbearable@ietf.org, tim.chown@jisc.ac.uk
X-Test-IDTracker: no
X-IETF-IDTracker: 6.80.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152587902651.4047.12903143077082489214.idtracker@ietfa.amsl.com>
Date: Wed, 09 May 2018 08:17:06 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/unbearable/N7yuPdPIp9hdtLeLOkEl5KPXwB4>
Subject: [Unbearable] Warren Kumari's No Objection on draft-ietf-tokbind-https-14: (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: Wed, 09 May 2018 15:17:06 -0000

Warren Kumari has entered the following ballot position for
draft-ietf-tokbind-https-14: No Objection

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-https/



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

Thank you for a well written and easily understood document - it is unusual to
be able to cover like this in such an easily understood manner.

I'd suggest looking at Tim Chown's excellent OpsDir review:
https://datatracker.ietf.org/doc/review-ietf-tokbind-https-14-opsdir-lc-chown-2018-05-08/
, especially the bit about a "diagram of the relationship between the various
elements in a federated scenario"

Some text about what to do with a (hypothetical) status code 309 might be
helpful - this says it MUST be ignored; does this mean a -bis document if /
when it is released? Could the document describe how to decide if future 30x
codes are acceptible? Or it is clear that there will never be >308?.