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

[Mike Jones <[e-mail]>]

All the existing OpenID Connect registrations at http://www.iana.org/assignments/oauth-parameters/oauth-parameters.xhtml already list the OpenID Foundation Artifact Binding Working Group as the change controller.  Consistency argues for all them being the same.

Given that the OpenID Foundation is listed, should the working group be closed, the foundation would be able to take over as the change controller anyway.

				-- Mike

-----Original Message-----
From: Hannes Tschofenig [mailto:[e-mail]] 
Sent: Tuesday, November 24, 2015 3:35 AM
To: Mike Jones <[e-mail]>; [e-mail]
Subject: Re: Request to register OAuth parameters

Hi Mike,

thanks for the request.

I have read through the list of items and I don't see a problem with the proposed entries to the two registries. Hence, I approve them.

I only have one minor question: Do you think that the change controller should be the 'OpenID Foundation Artifact Binding Working Group'? I would have rather said that it would better be the OpenID Foundation in general since that specific working group may not exist forever.

To IANA: Use the text from the original email since the text below seems to be garbled. Also note that the words 'Section 2 of this document'
refer to Section 2 of this specification:
http://openid.net/specs/openid-connect-registration-1_0-29.html

Ciao
Hannes


On 11/13/2015 08:47 PM, Mike Jones wrote:
> 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.xhtm
> l#client-metadata
> and
> http://www.iana.org/assignments/oauth-parameters/oauth-parameters.xhtm
> l#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#Clien
> tMetadata>
> of this document
> 
> *        Client Metadata Name: sector_identifier_uri
> 
> *        Client Metadata Description: URL using the httpsscheme 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#Clien
> tMetadata>
> of this document
> 
> *        Client Metadata Name: subject_type
> 
> *        Client Metadata Description: subject_typerequested 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#Clien
> tMetadata>
> of this document
> 
> *        Client Metadata Name: id_token_signed_response_alg
> 
> *        Client Metadata Description: JWS algalgorithm 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#Clien
> tMetadata>
> of this document
> 
> *        Client Metadata Name: id_token_encrypted_response_alg
> 
> *        Client Metadata Description: JWE algalgorithm 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#Clien
> tMetadata>
> of this document
> 
> *        Client Metadata Name: id_token_encrypted_response_enc
> 
> *        Client Metadata Description: JWE encalgorithm 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#Clien
> tMetadata>
> of this document
> 
> *        Client Metadata Name: userinfo_signed_response_alg
> 
> *        Client Metadata Description: JWS algalgorithm 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#Clien
> tMetadata>
> of this document
> 
> *        Client Metadata Name: userinfo_encrypted_response_alg
> 
> *        Client Metadata Description: JWE algalgorithm 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#Clien
> tMetadata>
> of this document
> 
> *        Client Metadata Name: userinfo_encrypted_response_enc
> 
> *        Client Metadata Description: JWE encalgorithm 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#Clien
> tMetadata>
> of this document
> 
> *        Client Metadata Name: request_object_signing_alg
> 
> *        Client Metadata Description: JWS algalgorithm 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#Clien
> tMetadata>
> of this document
> 
> *        Client Metadata Name: request_object_encryption_alg
> 
> *        Client Metadata Description: JWE algalgorithm 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#Clien
> tMetadata>
> of this document
> 
> *        Client Metadata Name: request_object_encryption_enc
> 
> *        Client Metadata Description: JWE encalgorithm 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#Clien
> tMetadata>
> of this document
> 
> *        Client Metadata Name: token_endpoint_auth_signing_alg
> 
> *        Client Metadata Description: JWS algalgorithm that MUST be used
> for signing the JWT used to authenticate the Client at the Token 
> Endpoint for the private_key_jwtand client_secret_jwtauthentication 
> 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#Clien
> tMetadata>
> 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#Clien
> tMetadata>
> of this document
> 
> *        Client Metadata Name: require_auth_time
> 
> *        Client Metadata Description: Boolean value specifying whether
> the auth_timeClaim 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#Clien
> tMetadata>
> 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#Clien
> tMetadata>
> of this document
> 
> *        Client Metadata Name: initiate_login_uri
> 
> *        Client Metadata Description: URI using the httpsscheme 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#Clien
> tMetadata>
> of this document
> 
> *        Client Metadata Name: request_uris
> 
> *        Client Metadata Description: Array of request_urivalues 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#Clien
> tMetadata>
> 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#OpenI
> D.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#OpenI
> D.Core>
> 
> 
>  
>