[OAUTH-WG] Re: Roman Danyliw's No Objection on draft-ietf-oauth-selective-disclosure-jwt-20: (with COMMENT)
Brian Campbell <bcampbell@pingidentity.com> Wed, 28 May 2025 15:32 UTC
Return-Path: <bcampbell@pingidentity.com>
X-Original-To: oauth@mail2.ietf.org
Delivered-To: oauth@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 8F2D62DE75D0 for <oauth@mail2.ietf.org>; Wed, 28 May 2025 08:32:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=pingidentity.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QRcFSR5bBIix for <oauth@mail2.ietf.org>; Wed, 28 May 2025 08:32:00 -0700 (PDT)
Received: from mail-vk1-xa2e.google.com (mail-vk1-xa2e.google.com [IPv6:2607:f8b0:4864:20::a2e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 0C9072DE7566 for <oauth@ietf.org>; Wed, 28 May 2025 08:32:00 -0700 (PDT)
Received: by mail-vk1-xa2e.google.com with SMTP id 71dfb90a1353d-52934f4fb23so3003742e0c.1 for <oauth@ietf.org>; Wed, 28 May 2025 08:32:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pingidentity.com; s=google; t=1748446319; x=1749051119; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=DVZEBtJDNT1L6sBCH1ZUsy2+6+49KkKoeCe13YTP3C8=; b=KfLVfiwzWg5XNCJHxphkuwQi7QE1lIiBPx4LH5cOQULRlF4iqkKDSvnVYKosUmBC3M vpD+BU1HHTLVQOnPKVTVWZp40vJ31uvxuXfgNKJeQXaO94VwmSDQ7CXAHCZEb/td/j7E 7sNwmh5wF4MsiLgRzyCH00gmq5axgIPBGMJcMI4GLDu1lxM0a3VIMhI25qXhLys7E3CT /6UIwhfp2serHQQThO0FJWufExojynlIWTyz+cQ09tRyVVPeApsC7cpTh02m8W9chW7+ UW4u6XX6Ye3g+aOrBhZ40F9w3VFgbXQD08lU7Y66pJSWkAw590r54OJLkvmUmvfYAXcH H6XA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1748446319; x=1749051119; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=DVZEBtJDNT1L6sBCH1ZUsy2+6+49KkKoeCe13YTP3C8=; b=aSjLtLUVepgLrX2YZa6jA68fEIFwO4cqWwfsTqwQKTey6f+gbAJA7gN0/gZHJpK+mj lASBTFBaSObeWX6t1GDj0ccomGBcKiAEjbV3EC0H8V/r6jW5gihPvtlf2ratZgYbilhV YDjTRp5CJ4khfge26fsx+tW70GqaPx15MadpTraCKcnSO2K7W3eNQ9FqmMgkGv/FcKub EBiXF0GTMcvgdmfoS0KCWKX3fY+Pdbf5WWSIsgeguP7SC7xQXlZYyQzHkwECS5T/5RPT edAbN2deoNDJt0PyOArD0BUSeTwc1xtAMN6YFxb8OHYzYXfPwDlEgasx7MLz5nez7/aq cC8A==
X-Forwarded-Encrypted: i=1; AJvYcCWQnH2HKGYmo94D1JN0GTGItNdxnLJsDFtFmlhstIJ+7DJxn300n19A8n3+XIw/StklGjUQLg==@ietf.org
X-Gm-Message-State: AOJu0YydmMzmRGoTQXlcNJBmvn3u6c/77AH5jTw7HLx4f4GNyR5K8CYd 65J4PoJWxEEwsVFdzoaY5UCRoFjgdjwGw22iKxC3RWgpzVMCvvngdJttyAI56yS1gU6HSZEJ1FU U0bdV2Sk6Xpnqow3ugTgXzcYeYr52RNHJd5FyHNuKLtYR42r5A3WKHiR9q3abvL31dkl2MbS+Yu 7PBMEPmqzRm4nUYw==
X-Gm-Gg: ASbGncstdvKF5tCWy1AhsMSRBUZ3Q0vhUsYyKCCeiCfOyCswiivOOY/R5qBvbRRGpu+ P/vTUDNlm6lvQOQP8HBI+X1hfgJRuMvTwuuyV20I9MgflJqg8a3Uri15kioHKJrkGCNGk+wvesp j6S45yZYlQMR+Y7+SNp8gY0Seu6McC1As3bg==
X-Google-Smtp-Source: AGHT+IFGdYvd69L4BIoRnDTBxL1YcZ9sXrkd8qww/YKb6zew9pM5b+ocGXLGRneIguJ82fwKImv3pQaqu9CYjjaasdY=
X-Received: by 2002:a05:6122:6185:b0:52f:4624:35ef with SMTP id 71dfb90a1353d-52f46243757mr5295959e0c.6.1748446319265; Wed, 28 May 2025 08:31:59 -0700 (PDT)
MIME-Version: 1.0
References: <174837613200.1750595.14159105606635515789@dt-datatracker-59b84fc74f-84jsl>
In-Reply-To: <174837613200.1750595.14159105606635515789@dt-datatracker-59b84fc74f-84jsl>
From: Brian Campbell <bcampbell@pingidentity.com>
Date: Wed, 28 May 2025 09:31:32 -0600
X-Gm-Features: AX0GCFuoyvzWFCJ0nssFFaeAWIoeyduFTh8GbfWA4WVTd49s6iBGxn1SRgvpPbA
Message-ID: <CA+k3eCTjFnYAH=-5DNS1peRjoSnOMDRbzgaKgZ6Y8YQcjE8aKQ@mail.gmail.com>
To: Roman Danyliw <rdd@cert.org>
Content-Type: multipart/alternative; boundary="000000000000c4f0a0063633e12a"
Message-ID-Hash: IF4PFSQ2VG6XGWPZ26W4FS2QXMSIN4VO
X-Message-ID-Hash: IF4PFSQ2VG6XGWPZ26W4FS2QXMSIN4VO
X-MailFrom: bcampbell@pingidentity.com
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: The IESG <iesg@ietf.org>, 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
Precedence: list
Subject: [OAUTH-WG] Re: 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/MYGjVufBa2fOqhsG2oekxO4YpMU>
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>
Thanks for clearing the DISCUSS Roman, https://github.com/oauth-wg/oauth-selective-disclosure-jwt/pull/579/files has a few more updates aimed at your remaining comments. Please let me know if anything there looks amiss. I'll work with the co-authors and responsible AD to get a new draft out and moved forward in the process. On Tue, May 27, 2025 at 2:02 PM Roman Danyliw via Datatracker < noreply@ietf.org> wrote: > 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]. > > > > -- _CONFIDENTIALITY NOTICE: This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited. If you have received this communication in error, please notify the sender immediately by e-mail and delete the message and any file attachments from your computer. Thank you._
- [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