[Ace] Secdir telechat review of draft-ietf-ace-oauth-authz-41

Phillip Hallam-Baker via Datatracker <noreply@ietf.org> Fri, 21 May 2021 23:41 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: ace@ietf.org
Delivered-To: ace@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B2D893A0CFB; Fri, 21 May 2021 16:41:19 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Phillip Hallam-Baker via Datatracker <noreply@ietf.org>
To: <secdir@ietf.org>
Cc: ace@ietf.org, draft-ietf-ace-oauth-authz.all@ietf.org, last-call@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.30.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <162164047967.4459.16040288658397288714@ietfa.amsl.com>
Reply-To: Phillip Hallam-Baker <hallam@gmail.com>
Date: Fri, 21 May 2021 16:41:19 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ace/cD1YzA2IuqeNZlJi7834CNimDtA>
Subject: [Ace] Secdir telechat review of draft-ietf-ace-oauth-authz-41
X-BeenThere: ace@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "Authentication and Authorization for Constrained Environments \(ace\)" <ace.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ace>, <mailto:ace-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ace/>
List-Post: <mailto:ace@ietf.org>
List-Help: <mailto:ace-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ace>, <mailto:ace-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 May 2021 23:41:20 -0000

Reviewer: Phillip Hallam-Baker
Review result: Ready

This draft was previously reviewed by Steve Kent for the -27 version. My review
therefore mostly consists of checking that the changes recommended have been
made and that no new issues have arisen. Note that contrary to the data in the
tracker, I was not given the assignment in 2019.

If you decide that you want to use OAUTH for authorization security for
Internet of Things, this is a reasonable approach to take. This is not a simple
proposition or for the fainthearted. OAuth is built around the various
constraints of the browser world to which the constraints of being a
constrained device are added.

The issues raised by Steve have all been addressed as far as I can see. It
looks good to go but since it is a security spec, ADs should still take note.