[Openid-specs-ab] Fwd: Contributing OpenID Connect Relying Party Metadata Choices 1.0 spec to the working group

[Vladimir Dzhuvinov / Connect2id]

I support adoption of the metadata spec for Federation RPs.

Vladimir Dzhuvinov

On 22/10/2024 02:27, Nat Sakimura via Openid-specs-ab wrote:
> Dear AB/Connect WG:
>
> This email will start a one-week call for the adoption of the OpenID 
> Connect Relying Party Metadata Choices 1.0 spec.
> It was contributed on the last week of September and in discussion 
> since that, it was agreed that we need to clarify that multiple 
> choices are not to be used in DCR responses
> On the call last week, we discussed that it would be fine to do this 
> after adoption.
>
> As a reminder, adoption does not mean a document is finished, only 
> that it is an acceptable starting point.
>
> Best regards,
>
> Nat Sakimura
> Co-Chair, AB/Connect WG
>                                  
>
> ---------- Forwarded message ---------
> From: *Michael Jones via Openid-specs-ab* 
> <openid-specs-ab at lists.openid.net>
> Date: Wed, 9 Oct 2024 at 11:35
> Subject: [Openid-specs-ab] Contributing OpenID Connect Relying Party 
> Metadata Choices 1.0 spec to the working group
> To: openid-specs-ab at lists.openid.net <openid-specs-ab at lists.openid.net>
> Cc: Michael Jones <michael_b_jones at hotmail.com>
>
>
> The authors of the attached specification hereby contribute it to the 
> OpenID Connect working group.  It was created to address issues 
> https://bitbucket.org/openid/connect/issues/2158/metadata-parameter-value-arrays-for-rp 
> and https://github.com/openid/federation/issues/12.
>
> -- Mike
>
> *From:*Michael Jones
> *Sent:* Thursday, October 3, 2024 10:09 PM
> *To:* openid-specs-ab at lists.openid.net
> *Subject:* FW: OpenID Connect Relying Party Metadata Choices 1.0 spec
>
> On Monday’s working group call, we discussed that I should go through 
> the list of registered OAuth Client Metadata values 
> <https://www.iana.org/assignments/oauth-parameters/oauth-parameters.xhtml#client-metadata> 
> and see if there were any more that should be added to the list in 
> this specification.  My conclusion was that there were not.  I’ll 
> therefore plan to contribute it to the working group as-is so we can 
> start addressing the issues filed unless I hear feedback soon 
> requesting changes first.
>
> Thanks all,
>
> -- Mike
>
> *From:*Michael Jones
> *Sent:* Sunday, September 29, 2024 7:53 PM
> *To:* openid-specs-ab at lists.openid.net
> *Subject:* OpenID Connect Relying Party Metadata Choices 1.0 spec
>
> The attached spec (with source and HTML output) defines client 
> metadata parameters corresponding to all the single-valued OpenID 
> Connect Dynamic Client Registration metadata parameters, letting RPs 
> declare the sets of values for these parameters that they support.  
> This is intended to address both 
> https://bitbucket.org/openid/connect/issues/2158/metadata-parameter-value-arrays-for-rp 
> and https://github.com/openid/federation/issues/12.
>
> Reviews welcomed!
>
> -- Mike
>
> _______________________________________________
> Openid-specs-ab mailing list
> Openid-specs-ab at lists.openid.net
> https://lists.openid.net/mailman/listinfo/openid-specs-ab
>
> _______________________________________________
> Openid-specs-ab mailing list
> Openid-specs-ab at lists.openid.net
> https://lists.openid.net/mailman/listinfo/openid-specs-ab
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20241022/a00f20e6/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4007 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20241022/a00f20e6/attachment.p7s>