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

Hannes Tschofenig <Hannes.Tschofenig@arm.com> Wed, 27 March 2019 17:42 UTC

Return-Path: <Hannes.Tschofenig@arm.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 904CD120290 for <oauth-ext-review@ietfa.amsl.com>; Wed, 27 Mar 2019 10:42:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-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=armh.onmicrosoft.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 Nyl7DNWXW4dZ for <oauth-ext-review@ietfa.amsl.com>; Wed, 27 Mar 2019 10:41:58 -0700 (PDT)
Received: from EUR04-HE1-obe.outbound.protection.outlook.com (mail-eopbgr70052.outbound.protection.outlook.com [40.107.7.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D8B812030F for <oauth-ext-review@ietf.org>; Wed, 27 Mar 2019 10:41:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com; s=selector1-arm-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=E9hUvDJMbaLL57paDuWbS8HUp9HklsgArykzSg4j+QY=; b=bFea8HDU8qhrc8JW2rXFSEdWU4cbSKRs/LY4xfFLkBp2VBhHNVow5Rr9peEsmHeW5lMsoWzEsZuCO7lroUijSunsumfbHpjgaKlCY9h4FIMVWNxrN3jyOBe9Bm58/mR/ij8JIcRWC0kfQxsMhOgbHd4IliLaeOX0KGdcrNB6U34=
Received: from VI1PR0801MB2112.eurprd08.prod.outlook.com (10.173.75.16) by VI1PR0801MB2096.eurprd08.prod.outlook.com (10.173.75.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1730.18; Wed, 27 Mar 2019 17:41:54 +0000
Received: from VI1PR0801MB2112.eurprd08.prod.outlook.com ([fe80::dd0a:bfcc:b6ce:8d65]) by VI1PR0801MB2112.eurprd08.prod.outlook.com ([fe80::dd0a:bfcc:b6ce:8d65%11]) with mapi id 15.20.1730.019; Wed, 27 Mar 2019 17:41:54 +0000
From: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
To: Brian Campbell <bcampbell@pingidentity.com>, Mike Jones <Michael.Jones@microsoft.com>
CC: "oauth-ext-review@ietf.org" <oauth-ext-review@ietf.org>
Thread-Topic: Request for registration of OAuth request parameter response_mode
Thread-Index: AdQuh1/wGAO6OKOIQ62GMYH9QzlJIiAxSHSAAAfE8zAMEg2IgAAEuHyAADAP5IAABDkUAAEK6okw
Date: Wed, 27 Mar 2019 17:41:54 +0000
Message-ID: <VI1PR0801MB2112A77E8B51A096C2901CC4FA580@VI1PR0801MB2112.eurprd08.prod.outlook.com>
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> <CA+k3eCT2RCFkU_o6=ap1pF57LP2q7JaZhZENVzFZmaUiZLjt7Q@mail.gmail.com> <CA+k3eCR5yad5GsE-dFqgqT-5g5OfY3cCbF-wtSo2MH7F8UeFcQ@mail.gmail.com> <CA+k3eCRqnDQ_1XHefu=xR5nz6iQzoa67_BE=C4n3yjBZUV=eow@mail.gmail.com>
In-Reply-To: <CA+k3eCRqnDQ_1XHefu=xR5nz6iQzoa67_BE=C4n3yjBZUV=eow@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Hannes.Tschofenig@arm.com;
x-originating-ip: [31.133.146.81]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 304c51b7-a659-478e-8783-08d6b2db8095
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(4618075)(2017052603328)(7153060)(7193020); SRVR:VI1PR0801MB2096;
x-ms-traffictypediagnostic: VI1PR0801MB2096:
x-ms-exchange-purlcount: 9
x-microsoft-antispam-prvs: <VI1PR0801MB2096B72276CCC13938DC5613FA580@VI1PR0801MB2096.eurprd08.prod.outlook.com>
x-forefront-prvs: 0989A7979C
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(39860400002)(396003)(346002)(366004)(136003)(199004)(13464003)(40434004)(31014005)(189003)(5024004)(14444005)(97736004)(256004)(4326008)(25786009)(3846002)(7736002)(106356001)(790700001)(86362001)(74316002)(71190400001)(8676002)(6116002)(81166006)(81156014)(71200400001)(53376002)(229853002)(476003)(486006)(1511001)(14454004)(186003)(11346002)(66574012)(52536014)(446003)(72206003)(606006)(966005)(2906002)(53936002)(316002)(478600001)(66066001)(6246003)(8936002)(76176011)(110136005)(5660300002)(53546011)(55016002)(93886005)(6306002)(54896002)(26005)(6506007)(7696005)(68736007)(6436002)(9686003)(102836004)(236005)(33656002)(99286004)(45080400002)(105586002); DIR:OUT; SFP:1101; SCL:1; SRVR:VI1PR0801MB2096; H:VI1PR0801MB2112.eurprd08.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: arm.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: BDvHFWxM3ASm5ckNOjJo1qNp3jJUVomHDmJvN0sL4CqXxZfAXZT03OQbj015BbT3cmlf+Lb1hFEbwVh+9+Z0jTFJWWX1ChiRmTSYIYYXFcRE7QbPL/cup8DqTTYbZAW0txVGzRWgyhwMgv67HOZg6IOheOeV94qjmuZvJZAFCc5AEx8ILJ1oe40uJi7v876ziLSXcSUDSCoySEbM80K9kbdqaE1U/eTh+M8xGsyPliRKfaoBxY+3n41J3w09ag5sriau22+JWbiymWymSnRKC+YRUZzHbTjlw1JdGySt+fM/nNc5LdJFWMA8AHYTQR5m2T2qmkeyrKNGU7Ayu++ex8w0/u17nm8yeGaMqVhdFkQ0idlWxB7MaJVbqgjxh6UXFTlTuo4kx02JXl3WkbK5ojiOLRPuPzNNMSO6NIKziiQ=
Content-Type: multipart/alternative; boundary="_000_VI1PR0801MB2112A77E8B51A096C2901CC4FA580VI1PR0801MB2112_"
MIME-Version: 1.0
X-OriginatorOrg: arm.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 304c51b7-a659-478e-8783-08d6b2db8095
X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Mar 2019 17:41:54.3448 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: f34e5979-57d9-4aaa-ad4d-b122a662184d
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR0801MB2096
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth-ext-review/eY83YrGZE9z6acXYJ7wj8QsxAQI>
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: Wed, 27 Mar 2019 17:42:03 -0000

I just spoke with Mike about this request and I approve the registration of the response_mode parameter to the IANA OAuth Parameters registry.

IANA OAuth Parameters registry
•        Parameter name: response_mode
•        Parameter usage location: Authorization Request
•        Change controller: OpenID Foundation Artifact Binding Working Group - openid-specs-ab@lists.openid.net<mailto: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 at https://openid.net/specs/oauth-v2-multiple-response-types-1_0.html<https://openid.net/specs/oauth-v2-multiple-response-types-1_0.html#OAuthParametersRegistry>
•        Related information: None


From: Brian Campbell <bcampbell@pingidentity.com>
Sent: Freitag, 22. März 2019 11:13
To: Mike Jones <Michael.Jones@microsoft.com>
Cc: Hannes Tschofenig <Hannes.Tschofenig@arm.com>; oauth-ext-review@ietf.org
Subject: Re: Request for registration of OAuth request parameter response_mode

Further proof of the existence of Hannes. Q.E.D.

Would the gentlemen in the photo please approve the registration request?


On Fri, Mar 22, 2019, 9:12 AM Brian Campbell <bcampbell@pingidentity.com<mailto:bcampbell@pingidentity.com>> wrote:
And this morning, Hannes, I even had breakfast with you! You can't hide forever. Many months maybe but not forever.

On Thu, Mar 21, 2019, 10:15 AM Brian Campbell <bcampbell@pingidentity.com<mailto:bcampbell@pingidentity.com>> wrote:
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<mailto:bcampbell@pingidentity.com>> wrote:
Hannes?


On Fri, Jan 18, 2019 at 9:25 PM Mike Jones <Michael.Jones@microsoft.com<mailto: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<mailto:bcampbell@pingidentity.com>>
Sent: Friday, January 18, 2019 8:40 AM
To: Mike Jones <Michael.Jones@microsoft.com<mailto:Michael.Jones@microsoft.com>>
Cc: oauth-ext-review@ietf.org<mailto: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<mailto: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<mailto:Michael.Jones@microsoft.com>> wrote:


-----Original Message-----
From: Openid-specs-ab <openid-specs-ab-bounces@lists.openid.net<mailto: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<mailto:openid-specs-ab@lists.openid.net>
Cc: Brian Campbell <issues-reply@bitbucket.org<mailto: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><mailto: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.
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.