Re: [oauth-ext-review] Request for registration of OAuth request parameter response_mode

Hannes?

On Fri, Jan 18, 2019 at 9:25 PM Mike Jones <Michael.Jones@microsoft.com>
wrote:

> Hannes, you’re the designated expert for this request.  Can you please
> approve it?
>
>
>
>                                                        Thanks,
>
>                                                        -- Mike
>
>
>
> *From:* Brian Campbell <bcampbell@pingidentity.com>
> *Sent:* Friday, January 18, 2019 8:40 AM
> *To:* Mike Jones <Michael.Jones@microsoft.com>
> *Cc:* oauth-ext-review@ietf.org
> *Subject:* Re: Request for registration of OAuth request parameter
> response_mode
>
>
>
> Following up on this to reiterate the request to designated expert(s) to
> request that IANA register the response_mode parameter in the IANA OAuth
> Parameters registry. According to
> https://tools.ietf.org/html/rfc6749?#section-11.2 IANA must only accept
> registry updates from the Designated Expert(s) and such requests are to be
> made through this list.
>
>
>
> The contents of the registration request are at
> https://openid.net/specs/oauth-v2-multiple-response-types-1_0.html#OAuthParametersRegistry
> and copied below for easy reference.
>
>
> 6.2.  OAuth Parameters Registration
>
> This specification registers the following parameter in the IANA OAuth
> Parameters registry defined in RFC 6749
> <https://openid.net/specs/oauth-v2-multiple-response-types-1_0.html#RFC6749>
> [RFC6749].
>
>
> ------------------------------
>
>  TOC
> <https://openid.net/specs/oauth-v2-multiple-response-types-1_0.html#toc>
> 6.2.1.  Registry Contents
>
> ·        Parameter name: response_mode
>
> ·        Parameter usage location: Authorization Request
>
> ·        Change controller: OpenID Foundation Artifact Binding Working
> Group - openid-specs-ab@lists.openid.net
>
> ·        Specification document(s): Section 2.1
> <https://openid.net/specs/oauth-v2-multiple-response-types-1_0.html#ResponseModes>
> of this document
>
> ·        Related information: None
>
>
>
>
>
>
>
> On Tue, Aug 7, 2018 at 1:46 PM Mike Jones <Michael.Jones@microsoft.com>
> wrote:
>
>
>
> -----Original Message-----
> From: Openid-specs-ab <openid-specs-ab-bounces@lists.openid.net> On
> Behalf Of Brian Campbell via Openid-specs-ab
> Sent: Tuesday, August 7, 2018 12:41 PM
> To: openid-specs-ab@lists.openid.net
> Cc: Brian Campbell <issues-reply@bitbucket.org>
> Subject: [Openid-specs-ab] Issue #1044: response_mode parameter
> registration missing (openid/connect)
>
>
>
> New issue 1044: response_mode parameter registration missing
> https://bitbucket.org/openid/connect/issues/1044/response_mode-parameter-registration
>
>
>
> Brian Campbell:
>
>
>
> OAuth 2.0 Multiple Response Type Encoding Practices defines the
> response_mode authorization parameter and even has a registration request
> for it at
> http://openid.net/specs/oauth-v2-multiple-response-types-1_0.html#OAuthParametersRegistry
> however the response_mode parameter is not in the OAuth Parameters registry
> https://www.iana.org/assignments/oauth-parameters/oauth-parameters.xhtml#parameters
>
>
>
> I imagine it's just something that got overlooked in the process of
> finalizing OAuth 2.0 Multiple Response Type Encoding Practices. But it
> should probably be fixed at some point. I guess/assume one could just
> follow up with IANA about it?
>
>
>
> _______________________________________________
>
> Openid-specs-ab mailing list
>
> Openid-specs-ab@lists.openid.net<mailto:Openid-specs-ab@lists.openid.net>
>
> http://lists.openid.net/mailman/listinfo/openid-specs-ab
>
>
> *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.*
>

-- 
_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._