Re: [oauth-ext-review] Registration of the new OAuth client registration parameter

[Michael Jones <[e-mail]>]

It’s possible to request preliminary registrations before a spec is final.  That process is in place exactly so that should the designated experts request changes to the registration, that it’s possible to make those changes.  Whereas, if changes are requested but the specification is final, the changes can’t be made, which isn’t a good situation.  So I’d suggest requesting preliminary registrations.

Dima, can you please add  links to the IANA Consideration sections requesting the desired registrations to this thread?

                                                                -- Mike

From: oauth-ext-review <[e-mail]> On Behalf Of Justin Richer
Sent: Thursday, April 11, 2024 3:00 PM
To: Rifaat Shekh-Yusef <[e-mail]>
Cc: Dima Postnikov <[e-mail]>; [e-mail]; Dave Tonge <[e-mail]>; Nat Sakimura <[e-mail]>
Subject: Re: [oauth-ext-review] Registration of the new OAuth client registration parameter

Hi Dima,

The process is to write to this email address which goes to the designated experts (of which I’m one), so you’ve done that part right. :)

OAuth chairs and IANA — I’ve looked at the registration, and I think it is sufficiently described to allow registration. However, the document is not yet final, and so the registration should not yet take place.

When the document is final, I believe IANA will be OK to add this value to the registry.


— Justin


On Apr 11, 2024, at 2:51 PM, Rifaat Shekh-Yusef <[e-mail]<mailto:[e-mail]>> wrote:

Hi Dima,

The process is described in the RFC7591 section 4.1:
https://datatracker.ietf.org/doc/html/rfc7591#section-4.1

The following is a link to the registry with the name of the designated expert:
https://www.iana.org/assignments/oauth-parameters/oauth-parameters.xhtml#client-metadata

Regards,
 Rifaat


On Thu, Apr 11, 2024 at 8:42 AM Dima Postnikov <[e-mail]<mailto:[e-mail]>> wrote:
Hi all

OIDF FAPI WG is planning to publish a final specification of FAPI 2 within a few weeks.

Per this specification, the following client metadata definition needs to be registered in the IANA "OAuth Dynamic Client Registration Metadata" registry established by RFC7591.



**Metadata Name**: `use_mtls_endpoint_aliases`

**Metadata Description**: Indicates the requirement for a client to use mutual TLS endpoint aliases defined by the AS where present.

**Change Controller**: OIDF FAPI WG

**Specification Document(s)**: Section 7 of FAPI 2 security profile

Could you please guide us through the process of what needs to be done.


Thanks for your assistance.


Best regards,


Dima Postnikov




_______________________________________________
oauth-ext-review mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/oauth-ext-review
_______________________________________________
oauth-ext-review mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/oauth-ext-review