IETF Logo Mail Archive

Re: [OAUTH-WG] WGLC for OAuth 2.0 Protected Resource Metadata

Vladimir Dzhuvinov <vladimir@connect2id.com> Thu, 28 March 2024 20:57 UTC

Return-Path: <vladimir@connect2id.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D72FEC169410 for <oauth@ietfa.amsl.com>; Thu, 28 Mar 2024 13:57:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=connect2id.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jGRCBsXP0lnK for <oauth@ietfa.amsl.com>; Thu, 28 Mar 2024 13:57:04 -0700 (PDT)
Received: from mout-b-110.mailbox.org (mout-b-110.mailbox.org [195.10.208.55]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D01FC14F6A7 for <oauth@ietf.org>; Thu, 28 Mar 2024 13:57:02 -0700 (PDT)
Received: from smtp1.mailbox.org (smtp1.mailbox.org [10.196.197.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-b-110.mailbox.org (Postfix) with ESMTPS id 4V5G7G1Sr9z9vhd for <oauth@ietf.org>; Thu, 28 Mar 2024 21:56:58 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=connect2id.com; s=MBO0001; t=1711659418; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=q9pa+1B5Vvlum1uJX3XYgmqZmTSfkJAs1Sa1TeI4MZ0=; b=IBmEbVm8nOLgW9rjiMm1/0NdiC4vYV+Q8wtWrZ17wDrSzAY6EmzYhFuIY8OHS2+ny7cl5g Pt7wrU3TQCkkId2ZQpN2dmtgNGB4uoIprsBaMCKWf+Y6+8wZMRHtXp47nfEBKi4N0kqjDW lHsC4W4jmC9Ig0dTrMvtz/0nIsz/T6uJkkibD2nCKsgTOqwGFnAzZQsfkdswwwguobbVTC /nyZWSqIUkNmkC22ObCaLXyKrYnlrvankDpyTlJ1Ri5t1PYdQbeIS0I/LKqM8jhyt/odcL RlFHjEgVdBlVAxeSwF3LU4rWwUQrAtpjVCfM/jgRYIXhOZHT0N1I5vAqvJw95g==
Message-ID: <bb6c0d9f-5156-4b2b-b102-883ee913dfd5@connect2id.com>
Date: Thu, 28 Mar 2024 22:56:28 +0200
MIME-Version: 1.0
Content-Language: en-US
To: oauth@ietf.org
References: <CADNypP9QRjmgs5Si4Fj+hSmScwx+4ihQmxfznCCVE4+8F2UFkw@mail.gmail.com>
From: Vladimir Dzhuvinov <vladimir@connect2id.com>
Organization: Connect2id Ltd.
In-Reply-To: <CADNypP9QRjmgs5Si4Fj+hSmScwx+4ihQmxfznCCVE4+8F2UFkw@mail.gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms050901030204000801020609"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/jt6qQonFAkuuQqXTsL2pxB2ayaM>
Subject: Re: [OAUTH-WG] WGLC for OAuth 2.0 Protected Resource Metadata
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/oauth/>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Mar 2024 20:57:08 -0000

I have a question about the parameters: 
resource_signing_alg_values_supported, 
resource_encryption_alg_values_supported, 
resource_encryption_enc_values_supported.

I'm not sure how to interpret "content". Where the algorithms, if 
advertised, get to apply. Is this something that resources / 
applications will define, depending on the resource characteristics? If 
we take JWE for instance, it could be used for 3 things at least. To 
encrypt bearer JWTs to access the resource, in addition to encrypting 
request and response payloads.

Vladimir

On 27/03/2024 14:53, Rifaat Shekh-Yusef wrote:
> All,
>
> This is a *WG Last Call* for the *OAuth 2.0 Protected Resource 
> Metadata* document.
> https://www.ietf.org/archive/id/draft-ietf-oauth-resource-metadata-03.html
>
> Please, review this document and reply on the mailing list if you have 
> any comments or concerns, by *April 12*.
>
> Regards,
>   Rifaat & Hannes
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth

v2.23.0 | Report a Bug | By Email