[Ace] Martin Duke's No Objection on draft-ietf-ace-oauth-params-13: (with COMMENT)

Martin Duke via Datatracker <noreply@ietf.org> Thu, 18 March 2021 18:44 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 8A5EC3A31A5; Thu, 18 Mar 2021 11:44:53 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Martin Duke via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-ace-oauth-params@ietf.org, ace-chairs@ietf.org, ace@ietf.org, Jim Schaad <ietf@augustcellars.com>, ietf@augustcellars.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.27.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Martin Duke <martin.h.duke@gmail.com>
Message-ID: <161609309354.6073.6421666447862558561@ietfa.amsl.com>
Date: Thu, 18 Mar 2021 11:44:53 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ace/K3xxwHrWsNxEq82mGtUu4FEIMOQ>
Subject: [Ace] Martin Duke's No Objection on draft-ietf-ace-oauth-params-13: (with COMMENT)
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: Thu, 18 Mar 2021 18:44:54 -0000

Martin Duke has entered the following ballot position for
draft-ietf-ace-oauth-params-13: 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:


In sec 3.1 it says the AS SHOULD reject req_cnf if the key is symmetric. But in
Sec 5 it presents a totally reasonable use case where the C and RS hold a
previously established (symmetric?) key.  These observations are somewhat
contradictory. Should 3.1 include a qualifier. Would the AS know about this key
a priori so that it can ignore the recommendation? If not, how can this be done