[OAUTH-WG] Roman Danyliw's No Objection on draft-ietf-oauth-selective-disclosure-jwt-20: (with COMMENT)
Roman Danyliw via Datatracker <noreply@ietf.org> Tue, 27 May 2025 20:02 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: oauth@ietf.org
Delivered-To: oauth@mail2.ietf.org
Received: from [10.244.8.226] (unknown [104.131.183.230]) by mail2.ietf.org (Postfix) with ESMTP id 243ED2D85189; Tue, 27 May 2025 13:02:12 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Roman Danyliw via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 12.40.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <174837613200.1750595.14159105606635515789@dt-datatracker-59b84fc74f-84jsl>
Date: Tue, 27 May 2025 13:02:12 -0700
Message-ID-Hash: EOIYDYLQU7CPHMDSTDDOOOKUOCA7S6NV
X-Message-ID-Hash: EOIYDYLQU7CPHMDSTDDOOOKUOCA7S6NV
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-oauth.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-oauth-selective-disclosure-jwt@ietf.org, oauth-chairs@ietf.org, oauth@ietf.org, Hannes.Tschofenig@gmx.net
X-Mailman-Version: 3.3.9rc6
Reply-To: Roman Danyliw <rdd@cert.org>
Subject: [OAUTH-WG] Roman Danyliw's No Objection on draft-ietf-oauth-selective-disclosure-jwt-20: (with COMMENT)
List-Id: OAUTH WG <oauth.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/0O2GwvTbd1cmYn2oLigIhFqmk-c>
List-Archive: <https://mailarchive.ietf.org/arch/browse/oauth>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Owner: <mailto:oauth-owner@ietf.org>
List-Post: <mailto:oauth@ietf.org>
List-Subscribe: <mailto:oauth-join@ietf.org>
List-Unsubscribe: <mailto:oauth-leave@ietf.org>
Roman Danyliw has entered the following ballot position for draft-ietf-oauth-selective-disclosure-jwt-20: 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/about/groups/iesg/statements/handling-ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-oauth-selective-disclosure-jwt/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thank you to Thomas Fossati for the GENART review. Thanks for addressing my DISCUSS and COMMENT feedback with -20. Below is additional recommendations based on the DISCUSS feedback: ** Section 7.1 1. Decide which Disclosures to release to the Verifier, obtaining consent if necessary. Thanks for revising this text in -20. I would recommend making it clear that the means to get this “consent” is out of scope for this document. ** Section 9.1 Any of the JWS asymmetric digital signature algorithms registered in [IANA.JWS.Algorithms] that meet the security requirements described in the last paragraph of Section 5.2 of [RFC7515] can be used, including post-quantum algorithms, when they are ready. The last paragraph of Section 5.2 of RFC7515 says: Finally, note that it is an application decision which algorithms may be used in a given context. Even if a JWS can be successfully validated, unless the algorithm(s) used in the JWS are acceptable to the application, it SHOULD consider the JWS to be invalid. [on -19] -- This text from RFC7515 appears to be saying that the application decides and there aren’t any new security requirements. [response] Hard to disagree with that observation. Do you think some change is needed as a result? That bit in Section 9.1 was mostly (I think) intended to reassure readers that post-quantum algorithms showing up in the alg registry will be usable. [on -20] No comment on the phrase “… including post-quantum algorithms, when they are ready”. I’m reacting to the reference to RFC7515, as it seems misleading to me. Practically, it doesn’t impost any requirements, so why mention it? Would this be clearer: NEW (roughly) Per the last paragraph of Section 5.2 of [RFC7515], it is an application-specific decision to choose the appropriate JWS digital signature algorithm from [IANA.JWS.Algorithms].
- [OAUTH-WG] Roman Danyliw's No Objection on draft-… Roman Danyliw via Datatracker
- [OAUTH-WG] Re: Roman Danyliw's No Objection on dr… Brian Campbell
- [OAUTH-WG] Re: Roman Danyliw's No Objection on dr… Roman Danyliw