[oauth-ext-review] Request to register OAuth parameters

[Mike Jones <[e-mail]>]

Dear Designated Experts and IANA,

I am writing to you on behalf of the OpenID Connect Artifact Binding working group requesting to register the OAuth Dynamic Client Registration Metadata and OAuth Token Endpoint Authentication Methods parameters defined in http://openid.net/specs/openid-connect-registration-1_0-29.html#IANA.  The individual registration requests are repeated below.

These parameters were defined in the OpenID Dynamic Client Registration specification that became final in February, 2014.  Now that the OAuth Dynamic Client Registration Metadata registry and the OAuth Token Endpoint Authentication Methods registries have been established at http://www.iana.org/assignments/oauth-parameters/oauth-parameters.xhtml#client-metadata and http://www.iana.org/assignments/oauth-parameters/oauth-parameters.xhtml#token-endpoint-auth-method, those parameters not already registered by RFC 7591 are now being registered.

                                                            Thank you,
                                                            -- Mike

________________________________
 TOC <http://openid.net/specs/openid-connect-registration-1_0-29.html#toc>

10.1.  OAuth Dynamic Client Registration Metadata Registration

This specification registers the following client metadata definitions in the IANA "OAuth Dynamic Client Registration Metadata" registry [IANA.OAuth.Parameters]<http://openid.net/specs/openid-connect-registration-1_0-29.html#IANA.OAuth.Parameters> established by [RFC7591]<http://openid.net/specs/openid-connect-registration-1_0-29.html#RFC7591>:

________________________________
 TOC <http://openid.net/specs/openid-connect-registration-1_0-29.html#toc>

10.1.1.  Registry Contents
*        Client Metadata Name: application_type
*        Client Metadata Description: Kind of the application -- "native" or "web"
*        Change Controller: OpenID Foundation Artifact Binding Working Group - [e-mail]
*        Specification Document(s): Section 2 (Client Metadata)<http://openid.net/specs/openid-connect-registration-1_0-29.html#ClientMetadata> of this document
*        Client Metadata Name: sector_identifier_uri
*        Client Metadata Description: URL using the https scheme to be used in calculating Pseudonymous Identifiers by the OP
*        Change Controller: OpenID Foundation Artifact Binding Working Group - [e-mail]
*        Specification Document(s): Section 2 (Client Metadata)<http://openid.net/specs/openid-connect-registration-1_0-29.html#ClientMetadata> of this document
*        Client Metadata Name: subject_type
*        Client Metadata Description: subject_type requested for responses to this Client -- "pairwise" or "public"
*        Change Controller: OpenID Foundation Artifact Binding Working Group - [e-mail]
*        Specification Document(s): Section 2 (Client Metadata)<http://openid.net/specs/openid-connect-registration-1_0-29.html#ClientMetadata> of this document
*        Client Metadata Name: id_token_signed_response_alg
*        Client Metadata Description: JWS alg algorithm REQUIRED for signing the ID Token issued to this Client
*        Change Controller: OpenID Foundation Artifact Binding Working Group - [e-mail]
*        Specification Document(s): Section 2 (Client Metadata)<http://openid.net/specs/openid-connect-registration-1_0-29.html#ClientMetadata> of this document
*        Client Metadata Name: id_token_encrypted_response_alg
*        Client Metadata Description: JWE alg algorithm REQUIRED for encrypting the ID Token issued to this Client
*        Change Controller: OpenID Foundation Artifact Binding Working Group - [e-mail]
*        Specification Document(s): Section 2 (Client Metadata)<http://openid.net/specs/openid-connect-registration-1_0-29.html#ClientMetadata> of this document
*        Client Metadata Name: id_token_encrypted_response_enc
*        Client Metadata Description: JWE enc algorithm REQUIRED for encrypting the ID Token issued to this Client
*        Change Controller: OpenID Foundation Artifact Binding Working Group - [e-mail]
*        Specification Document(s): Section 2 (Client Metadata)<http://openid.net/specs/openid-connect-registration-1_0-29.html#ClientMetadata> of this document
*        Client Metadata Name: userinfo_signed_response_alg
*        Client Metadata Description: JWS alg algorithm REQUIRED for signing UserInfo Responses
*        Change Controller: OpenID Foundation Artifact Binding Working Group - [e-mail]
*        Specification Document(s): Section 2 (Client Metadata)<http://openid.net/specs/openid-connect-registration-1_0-29.html#ClientMetadata> of this document
*        Client Metadata Name: userinfo_encrypted_response_alg
*        Client Metadata Description: JWE alg algorithm REQUIRED for encrypting UserInfo Responses
*        Change Controller: OpenID Foundation Artifact Binding Working Group - [e-mail]
*        Specification Document(s): Section 2 (Client Metadata)<http://openid.net/specs/openid-connect-registration-1_0-29.html#ClientMetadata> of this document
*        Client Metadata Name: userinfo_encrypted_response_enc
*        Client Metadata Description: JWE enc algorithm REQUIRED for encrypting UserInfo Responses
*        Change Controller: OpenID Foundation Artifact Binding Working Group - [e-mail]
*        Specification Document(s): Section 2 (Client Metadata)<http://openid.net/specs/openid-connect-registration-1_0-29.html#ClientMetadata> of this document
*        Client Metadata Name: request_object_signing_alg
*        Client Metadata Description: JWS alg algorithm that MUST be used for signing Request Objects sent to the OP
*        Change Controller: OpenID Foundation Artifact Binding Working Group - [e-mail]
*        Specification Document(s): Section 2 (Client Metadata)<http://openid.net/specs/openid-connect-registration-1_0-29.html#ClientMetadata> of this document
*        Client Metadata Name: request_object_encryption_alg
*        Client Metadata Description: JWE alg algorithm the RP is declaring that it may use for encrypting Request Objects sent to the OP
*        Change Controller: OpenID Foundation Artifact Binding Working Group - [e-mail]
*        Specification Document(s): Section 2 (Client Metadata)<http://openid.net/specs/openid-connect-registration-1_0-29.html#ClientMetadata> of this document
*        Client Metadata Name: request_object_encryption_enc
*        Client Metadata Description: JWE enc algorithm the RP is declaring that it may use for encrypting Request Objects sent to the OP
*        Change Controller: OpenID Foundation Artifact Binding Working Group - [e-mail]
*        Specification Document(s): Section 2 (Client Metadata)<http://openid.net/specs/openid-connect-registration-1_0-29.html#ClientMetadata> of this document
*        Client Metadata Name: token_endpoint_auth_signing_alg
*        Client Metadata Description: JWS alg algorithm that MUST be used for signing the JWT used to authenticate the Client at the Token Endpoint for the private_key_jwt and client_secret_jwt authentication methods
*        Change Controller: OpenID Foundation Artifact Binding Working Group - [e-mail]
*        Specification Document(s): Section 2 (Client Metadata)<http://openid.net/specs/openid-connect-registration-1_0-29.html#ClientMetadata> of this document
*        Client Metadata Name: default_max_age
*        Client Metadata Description: Default Maximum Authentication Age
*        Change Controller: OpenID Foundation Artifact Binding Working Group - [e-mail]
*        Specification Document(s): Section 2 (Client Metadata)<http://openid.net/specs/openid-connect-registration-1_0-29.html#ClientMetadata> of this document
*        Client Metadata Name: require_auth_time
*        Client Metadata Description: Boolean value specifying whether the auth_time Claim in the ID Token is REQUIRED
*        Change Controller: OpenID Foundation Artifact Binding Working Group - [e-mail]
*        Specification Document(s): Section 2 (Client Metadata)<http://openid.net/specs/openid-connect-registration-1_0-29.html#ClientMetadata> of this document
*        Client Metadata Name: default_acr_values
*        Client Metadata Description: Default requested Authentication Context Class Reference values
*        Change Controller: OpenID Foundation Artifact Binding Working Group - [e-mail]
*        Specification Document(s): Section 2 (Client Metadata)<http://openid.net/specs/openid-connect-registration-1_0-29.html#ClientMetadata> of this document
*        Client Metadata Name: initiate_login_uri
*        Client Metadata Description: URI using the https scheme that a third party can use to initiate a login by the RP
*        Change Controller: OpenID Foundation Artifact Binding Working Group - [e-mail]
*        Specification Document(s): Section 2 (Client Metadata)<http://openid.net/specs/openid-connect-registration-1_0-29.html#ClientMetadata> of this document
*        Client Metadata Name: request_uris
*        Client Metadata Description: Array of request_uri values that are pre-registered by the RP for use at the OP
*        Change Controller: OpenID Foundation Artifact Binding Working Group - [e-mail]
*        Specification Document(s): Section 2 (Client Metadata)<http://openid.net/specs/openid-connect-registration-1_0-29.html#ClientMetadata> of this document

________________________________
 TOC <http://openid.net/specs/openid-connect-registration-1_0-29.html#toc>

10.2.  OAuth Token Endpoint Authentication Methods Registration

This specification registers the following token endpoint authentication methods in the IANA "OAuth Token Endpoint Authentication Methods" registry [IANA.OAuth.Parameters]<http://openid.net/specs/openid-connect-registration-1_0-29.html#IANA.OAuth.Parameters> established by [RFC7591]<http://openid.net/specs/openid-connect-registration-1_0-29.html#RFC7591>:

________________________________
 TOC <http://openid.net/specs/openid-connect-registration-1_0-29.html#toc>

10.2.1.  Registry Contents
*        Token Endpoint Authentication Method Name: client_secret_jwt
*        Change Controller: OpenID Foundation Artifact Binding Working Group - [e-mail]
*        Specification Document(s): Section 9 of OpenID Connect Core 1.0 [OpenID.Core] (Sakimura, N., Bradley, J., Jones, M., de Medeiros, B., and C. Mortimore, "OpenID Connect Core 1.0," August 2015.)<http://openid.net/specs/openid-connect-registration-1_0-29.html#OpenID.Core>
*        Token Endpoint Authentication Method Name: private_key_jwt
*        Change Controller: OpenID Foundation Artifact Binding Working Group - [e-mail]
*        Specification Document(s): Section 9 of OpenID Connect Core 1.0 [OpenID.Core] (Sakimura, N., Bradley, J., Jones, M., de Medeiros, B., and C. Mortimore, "OpenID Connect Core 1.0," August 2015.)<http://openid.net/specs/openid-connect-registration-1_0-29.html#OpenID.Core>