[Openid-specs-fapi] MODRNA Issue 206

[Brian Campbell]

Thanks Bjorn,

That covers the registration requests in sec 16.1
<https://openid.net/specs/openid-client-initiated-backchannel-authentication-core-1_0.html#rfc.section.16.1>,
however, there are also registration requests for OAuth Dynamic Client
Registration Metadata and OAuth Parameters in sections 16.2
<https://openid.net/specs/openid-client-initiated-backchannel-authentication-core-1_0.html#rfc.section.16.2>
and 16.3
<https://openid.net/specs/openid-client-initiated-backchannel-authentication-core-1_0.html#rfc.section.16.3>
respectively, which haven't been added.

It looks like Justin, the designated expert for the client metadata
registry, is asking for some changes
https://bitbucket.org/openid/mobile/issues/211/. They are minor and I
believe could be errata. However, I'm concerned that publishing a CIBA
errata could be a huge pain due mostly to changes in the xml2rfc tooling (I
think Mike has run into this on other specs so maybe he can ease the pain).

Furthermore, on looking at it again as a result of this, the OAuth
Parameters registration request doesn't look right to me. I don't know what
happened there. Maybe Dave knows and can tell me why I'm wrong here? But
unless I'm somehow confused, it should indicate "token request" rather than
"token response" for the "Parameter usage location:" and refer to Section
10.1 rather than 7.3. I believe that'd be errata qualifying change too,
which is good. But unfortunately would mean publishing a CIBA errata.






On Tue, Dec 6, 2022 at 8:32 AM Hjelm, Bjorn <bjorn.hjelm at verizonwireless.com>
wrote:

> All,
> For issue #206
> <https://bitbucket.org/openid/mobile/issues/206/ciba-iana-actions>, CIBA
> IANA actions, the CIBA entries in section 16
> <https://openid.net/specs/openid-client-initiated-backchannel-authentication-core-1_0.html#rfc.section.16>
> have been added to the OAuth Authorization Server Metadata
> <https://www.iana.org/assignments/oauth-parameters/oauth-parameters.xhtml#authorization-server-metadata>
> section of the IANA registry.
>
> The issue is now resolved and will be closed.
>
> BR,
> Bjorn
>

-- 
_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._
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-fapi/attachments/20221209/5e1e5224/attachment-0001.html>