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

Brian Campbell <bcampbell@pingidentity.com> Thu, 21 March 2019 09:16 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 77148130F62 for <oauth-ext-review@ietfa.amsl.com>; Thu, 21 Mar 2019 02:16:11 -0700 (PDT)
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 7IJtPXCcH8WU for <oauth-ext-review@ietfa.amsl.com>; Thu, 21 Mar 2019 02:16:07 -0700 (PDT)
Received: from mail-io1-xd2c.google.com (mail-io1-xd2c.google.com [IPv6:2607:f8b0:4864:20::d2c]) (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 915AB12B001 for <oauth-ext-review@ietf.org>; Thu, 21 Mar 2019 02:16:05 -0700 (PDT)
Received: by mail-io1-xd2c.google.com with SMTP id e13so4645108ioq.6 for <oauth-ext-review@ietf.org>; Thu, 21 Mar 2019 02:16:05 -0700 (PDT)
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=Xi92QcrLEMAmkAklnnZwkHIJTYH9iXZJnUtMVkK0B/g=; b=Yo2WTWOnPQCXspM+E0Wmms6Ohfb09AuKllYkceLH+jZpofeOc0X8YYJlMWZVOmJZgD +JJvPgVp97MI77llGsYstFcpGJsOnhXrR+pRZtAy+zSiA0sV7uD+pnQ0qzEscjIcF20c pEbYwiqmwUeWAJFgyPHM0+Jecb6Ne/F4VfXs4=
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=Xi92QcrLEMAmkAklnnZwkHIJTYH9iXZJnUtMVkK0B/g=; b=ugORqmLswAT8svJYsEde4n4AjJVHzlRSg2qpJuiDZjYKah998iLIOrDfQ2JFQoY9ou fGPqhJepWTP7j+qNuqRAaMhq9FWHqAPQ6ekKtvf2LxeCMHLjXcDQ/2CHvdONNgZMb4JA yrf5PuM0C780G3rp+OQ0v+gy4XtzWvxrUqbDD/72p7fcyIcfeB/SfXBgx4Rq3sUUTiDe bFTQ2O5th8VlDhVzw5JgL05ARDmUMphA1SUdLFN6VSGc0U15T+rBE8f1T5f/7Gvm8egr iFF1SnQdzkDw+Md5/Kda9N8nGp0y1CS4fsrIjoCaqQQHDv1FV2ePRurT/J956f5w3E/8 NV1A==
X-Gm-Message-State: APjAAAXuCzNVoPHN1q925IFHcCmjgqY6Zml0QMTR8TSYWwXYk1tKiHML P8u+KOO7LO+prl8v6YMCqKqidxgbqFYHO+CeaMLVTihtE7ztaKur3znQ9jo3X+4rapPw47IPTtZ Nx4tyORPJJIuiY6VE5HusD9di8WNeA6+yOw==
X-Google-Smtp-Source: APXvYqyMbu59PW808rBAw2cH0vXHtIJPxHRhbxjB+0m4C4/7K4OY1+X8ym63YOc/zz6YDq7pRFNFBP3Z+yXYobX+3Ds=
X-Received: by 2002:a6b:510f:: with SMTP id f15mr1868702iob.59.1553159763322; Thu, 21 Mar 2019 02:16:03 -0700 (PDT)
MIME-Version: 1.0
References: <SN6PR00MB030449F27812A7F2DA29779BF5270@SN6PR00MB0304.namprd00.prod.outlook.com> <CA+k3eCRH6XxpgLC56yBMYXe+v1tVi++v_ULpB=tu_Y=xZqONmg@mail.gmail.com> <BL0PR00MB0292EBB50A36B1846B1EEEDBF59C0@BL0PR00MB0292.namprd00.prod.outlook.com> <CA+k3eCTz6+nZciC3aMCerpKBpvPdztdyDwvo7OirtcHrVKfXEw@mail.gmail.com>
In-Reply-To: <CA+k3eCTz6+nZciC3aMCerpKBpvPdztdyDwvo7OirtcHrVKfXEw@mail.gmail.com>
From: Brian Campbell <bcampbell@pingidentity.com>
Date: Thu, 21 Mar 2019 10:15:51 +0100
Message-ID: <CA+k3eCT2RCFkU_o6=ap1pF57LP2q7JaZhZENVzFZmaUiZLjt7Q@mail.gmail.com>
To: Mike Jones <Michael.Jones@microsoft.com>
Cc: Hannes Tschofenig <Hannes.Tschofenig@arm.com>, oauth-ext-review@ietf.org
Content-Type: multipart/mixed; boundary="000000000000f998c90584972f35"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth-ext-review/S6Dkzy9xLmAwYKZuHTraN8CGQbg>
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: Thu, 21 Mar 2019 09:16:15 -0000

Hannes, I know you exist and are still alive because I'm sitting behind you
and have the attached photo to prove it. Please acknowledge this request

On Thu, Mar 21, 2019, 8:00 AM Brian Campbell <bcampbell@pingidentity.com>
wrote:

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