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

Brian Campbell <bcampbell@pingidentity.com> Fri, 18 January 2019 16:40 UTC

Return-Path: <bcampbell@pingidentity.com>
X-Original-To: oauth-ext-review@ietfa.amsl.com
Delivered-To: oauth-ext-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27731130E7C for <oauth-ext-review@ietfa.amsl.com>; Fri, 18 Jan 2019 08:40:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=pingidentity.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NO1TdT-ndml7 for <oauth-ext-review@ietfa.amsl.com>; Fri, 18 Jan 2019 08:40:51 -0800 (PST)
Received: from mail-io1-xd33.google.com (mail-io1-xd33.google.com [IPv6:2607:f8b0:4864:20::d33]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 75E84129AB8 for <oauth-ext-review@ietf.org>; Fri, 18 Jan 2019 08:40:51 -0800 (PST)
Received: by mail-io1-xd33.google.com with SMTP id b16so11247519ior.1 for <oauth-ext-review@ietf.org>; Fri, 18 Jan 2019 08:40:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pingidentity.com; s=gmail; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=nqplxvr1viA+aWoJQ4MK61+RPJ04AMOcLvjl0KXp9Is=; b=ODA9EtLt+rrkmaKvgyYZKbNQ0ivPa+Nl1fXJWszqyQWNCPGKXwOgQh4+ApZVN7pIr0 foBktxZo+/F2Aydnb3jJoDJW8rVMtDMIuuqbb2WyOEokFkwnNVAymY0bXv2Bta/ISJGk 90xwOt+lwLoABQvmtE9w2ehana/jPTS+rJVUE=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=nqplxvr1viA+aWoJQ4MK61+RPJ04AMOcLvjl0KXp9Is=; b=D89v/8DdKiNXLLpSxn4jfxq3Pz3UzHbAklqwEqc8J4LSkELYOcsl0dAp9BVYeSWXf+ 8sVRxcXlCfx0LfPqZg5vfg959CpNYtdrkCD2xwlbQmgzabGhBWptv4j0NVWGQUoIkFkb PAG6j/yhxDvrm9nZa7QIV//ZcQoOVWkN3R/FoFmCjTPslepLKnwf/7//B7LbmUifV+2T ZdJtABkWUA0iZH5Q4dIT/DJEVWwegFNdZ+b9nomp0+IJ4/0zEN/+zdqmuxut3a07bzy8 HTR5yP2IyKB/+7uQ2WqZsbgAgnaFP6gHtByypAvuvOAjGp46TeemkDCIY0ENaxZEaZyf tihw==
X-Gm-Message-State: AJcUukcmMfaxgPFU6436q92Erxy9TGUQ3rmaJF4WMYuk2qK1nlTIPIRW stryqXbXgz3sRrPpL+nPOWjD1QgLMafDyBy+Q2osArxPj8eBp7aRw0kjcYVVRxSMM6ppLHakHcH hnwYiQ4pN8NsLYLEv1l4zUddQIp4i
X-Google-Smtp-Source: ALg8bN7sTqe0g6+Lx0bUfuaOwTPSCBKm6+QR/huL7leMftnW4YvUQ/krGNOIw00312x5NfRXSC0F70XQFdQh5gZ20kE=
X-Received: by 2002:a6b:b345:: with SMTP id c66mr10736290iof.59.1547829650508; Fri, 18 Jan 2019 08:40:50 -0800 (PST)
MIME-Version: 1.0
References: <SN6PR00MB030449F27812A7F2DA29779BF5270@SN6PR00MB0304.namprd00.prod.outlook.com>
In-Reply-To: <SN6PR00MB030449F27812A7F2DA29779BF5270@SN6PR00MB0304.namprd00.prod.outlook.com>
From: Brian Campbell <bcampbell@pingidentity.com>
Date: Fri, 18 Jan 2019 09:40:23 -0700
Message-ID: <CA+k3eCRH6XxpgLC56yBMYXe+v1tVi++v_ULpB=tu_Y=xZqONmg@mail.gmail.com>
To: Mike Jones <Michael.Jones@microsoft.com>
Cc: "oauth-ext-review@ietf.org" <oauth-ext-review@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007e0fc4057fbe2cd7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth-ext-review/ydjTOfZJ_dILvaGu0t6OhXT0wSg>
Subject: Re: [oauth-ext-review] Request for registration of OAuth request parameter response_mode
X-BeenThere: oauth-ext-review@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Review of proposed IANA registrations for OAuth." <oauth-ext-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth-ext-review>, <mailto:oauth-ext-review-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/oauth-ext-review/>
List-Post: <mailto:oauth-ext-review@ietf.org>
List-Help: <mailto:oauth-ext-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth-ext-review>, <mailto:oauth-ext-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Jan 2019 16:40:54 -0000

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