[oauth-ext-review] [IANA #1175814] expert review for draft-ietf-oauth-jwsreq-26 (OAuth Parameters - oauth-parameters)

Amanda Baber via RT <drafts-expert-review-comment@iana.org> Tue, 08 September 2020 21:44 UTC

Return-Path: <iana-shared@icann.org>
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 3D40A3A1519 for <oauth-ext-review@ietfa.amsl.com>; Tue, 8 Sep 2020 14:44:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.627
X-Spam-Level:
X-Spam-Status: No, score=-0.627 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, MISSING_HEADERS=1.021, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 YnMC7RYwR1B4 for <oauth-ext-review@ietfa.amsl.com>; Tue, 8 Sep 2020 14:44:16 -0700 (PDT)
Received: from smtp01.icann.org (smtp01.icann.org [192.0.33.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18E863A1518 for <oauth-ext-review@ietf.org>; Tue, 8 Sep 2020 14:44:16 -0700 (PDT)
Received: from request4.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by smtp01.icann.org (Postfix) with ESMTP id EF129E066A; Tue, 8 Sep 2020 21:44:15 +0000 (UTC)
Received: by request4.lax.icann.org (Postfix, from userid 48) id ECF52203B7; Tue, 8 Sep 2020 21:44:15 +0000 (UTC)
RT-Owner: amanda.baber
From: "Amanda Baber via RT" <drafts-expert-review-comment@iana.org>
Reply-To: drafts-expert-review-comment@iana.org
In-Reply-To: <rt-4.4.3-17288-1599510542-1459.1175814-9-0@icann.org>
References: <RT-Ticket-1175814@icann.org> <rt-4.4.3-8481-1597261983-295.1175814-9-0@icann.org> <rt-4.4.3-8480-1597266242-1095.1175814-9-0@icann.org> <rt-4.4.3-27209-1598029692-1867.1175814-9-0@icann.org> <CAJcjuE+PqWJ4-ofeDRk7ZrQnX6HvGKTLCmWq7Xr0VgCN+zjE3g@mail.gmail.com> <AM0PR08MB3716CE981E7B194344EB677DFA510@AM0PR08MB3716.eurprd08.prod.outlook.com> <AM0PR08MB3716E890676E0BCBC55AC951FA280@AM0PR08MB3716.eurprd08.prod.outlook.com> <MN2PR00MB0686E4E403497B538D5292BAF5281@MN2PR00MB0686.namprd00.prod.outlook.com> <rt-4.4.3-17288-1599510542-1459.1175814-9-0@icann.org>
Message-ID: <rt-4.4.3-22744-1599601455-681.1175814-9-0@icann.org>
X-RT-Loop-Prevention: IANA
X-RT-Ticket: IANA #1175814
X-Managed-BY: RT 4.4.3 (http://www.bestpractical.com/rt/)
X-RT-Originator: amanda.baber@icann.org
CC: rdd@cert.org, oauth-ext-review@ietf.org, nat@nat.consulting, michael.jones@microsoft.com, hannes.tschofenig@arm.com
Content-Type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
Precedence: bulk
Date: Tue, 08 Sep 2020 21:44:15 +0000
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth-ext-review/lBcQI1BvUpVOYpAPtL9DB5odi2I>
Subject: [oauth-ext-review] [IANA #1175814] expert review for draft-ietf-oauth-jwsreq-26 (OAuth Parameters - oauth-parameters)
X-BeenThere: oauth-ext-review@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 08 Sep 2020 21:44:18 -0000

Hi Mike, Roman, all,

We've had confirmation from Barry that "IETF" is preferred.

I'll move ahead with the registry actions and use "IETF." If there's a reason to prefer "IESG," let me know.

Best regards,
Amanda

On Mon Sep 07 20:29:02 2020, Michael.Jones@microsoft.com wrote:
> Thanks for reviewing the submissions, Hannes.  We can update the draft
> to consistently use either IETF or IESG.  Roman, the IESG seems to
> have gone back and forth between these two.  Is “IETF” the current
> Change Controller of preference?
> 
> Thanks,
> -- Mike
> 
> From: oauth-ext-review <oauth-ext-review-bounces@ietf.org> On Behalf
> Of Hannes Tschofenig
> Sent: Monday, September 7, 2020 8:13 AM
> To: Hannes Tschofenig <Hannes.Tschofenig@arm.com>om>; Nat Sakimura
> <nat@nat.consulting>ng>; drafts-expert-review-comment@iana.org
> Cc: oauth-ext-review@ietf.org
> Subject: Re: [oauth-ext-review] [IANA #1175814] expert review for
> draft-ietf-oauth-jwsreq-26 (OAuth Parameters - oauth-parameters)
> 
> Hi all,
> 
> I reviewed Section 9.1 of https://tools.ietf.org/html/draft-ietf-
> oauth-jwsreq-28 and I am OK with registering the listed parameters.
> Note that these parameters are not meant to be used in practice, as
> the draft says.
> 
> FWIW I noticed that some of the parameters indicate that the IESG is
> the change controller while other parameters say IETF as the change
> controller. I noticed that the IANA registry itself is inconsistent in
> that regard. Ultimately, it does not matter but at least within a
> single document the change controller should either be listed as IETF
> or IESG but not both.
> 
> Ciao
> Hannes
> 
> From: oauth-ext-review <oauth-ext-review-
> bounces@ietf.org<mailto:oauth-ext-review-bounces@ietf.org>> On Behalf
> Of Hannes Tschofenig
> Sent: Monday, August 31, 2020 9:05 AM
> To: Nat Sakimura <nat@nat.consulting<mailto:nat@nat.consulting>>;
> drafts-expert-review-comment@iana.org<mailto:drafts-expert-review-
> comment@iana.org>
> Cc: oauth-ext-review@ietf.org<mailto:oauth-ext-review@ietf.org>
> Subject: Re: [oauth-ext-review] [IANA #1175814] expert review for
> draft-ietf-oauth-jwsreq-26 (OAuth Parameters - oauth-parameters)
> 
> Hi Nat, Hi all,
> 
> I am back from my sabbatical leave tomorrow and will take a look at it
> tomorrow. Sorry for the delay.
> 
> Ciao
> Hannes
> 
> From: Nat Sakimura <nat@nat.consulting<mailto:nat@nat.consulting>>
> Sent: Sunday, August 30, 2020 10:08 PM
> To: drafts-expert-review-comment@iana.org<mailto:drafts-expert-review-
> comment@iana.org>
> Cc: oauth-ext-review@ietf.org<mailto:oauth-ext-review@ietf.org>;
> Hannes Tschofenig
> <Hannes.Tschofenig@arm.com<mailto:Hannes.Tschofenig@arm.com>>
> Subject: Re: [oauth-ext-review] [IANA #1175814] expert review for
> draft-ietf-oauth-jwsreq-26 (OAuth Parameters - oauth-parameters)
> 
> Hannes? Could you do the review, please?
> 
> On Sat, Aug 22, 2020 at 2:08 AM Amanda Baber via RT <drafts-expert-
> review-comment@iana.org<mailto:drafts-expert-review-comment@iana.org>>
> wrote:
> Hi Hannes,
> 
> This is a reminder for IANA's OAuth Parameters review request for
> draft-ietf-oauth-jwsreq. The document has been approved, but we need
> your review before we can make the registrations.
> 
> thanks,
> Amanda
> 
> On Wed Aug 12 21:04:02 2020, amanda.baber wrote:
> > Dear Hannes,
> >
> > As the designated expert for the OAuth Parameters registry, can you
> > review the registrations in Section 9.1 of this document?
> >
> > https://tools.ietf.org/html/draft-ietf-oauth-jwsreq
> >
> > The two-week review period would end on August 26th.
> >
> > This document is on tomorrow's IESG telechat agenda, but we're
> > notifying the ADs that it still requires IANA review. (When this
> > document was last sent to IANA, there were no registry actions.)
> >
> > Best regards,
> >
> > Amanda Baber
> > Lead IANA Services Specialist
> 
> _______________________________________________
> oauth-ext-review mailing list
> oauth-ext-review@ietf.org<mailto:oauth-ext-review@ietf.org>
> https://www.ietf.org/mailman/listinfo/oauth-ext-review
> 
> 
> --
> Nat Sakimura
> NAT.Consulting LLC
> 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.
> 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.