IETF Logo Mail Archive

Re: [Ace] FW: [IANA #1157486] Last Call: <draft-ietf-ace-oauth-authz-27.txt> (Authentication and Authorization for Constrained Environments (ACE) using the OAuth 2.0 Framework (ACE-OAuth)) to Proposed Standard

Jim Schaad <ietf@augustcellars.com> Sat, 21 December 2019 19:07 UTC

Return-Path: <ietf@augustcellars.com>
X-Original-To: ace@ietfa.amsl.com
Delivered-To: ace@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CF2A120059 for <ace@ietfa.amsl.com>; Sat, 21 Dec 2019 11:07:44 -0800 (PST)
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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 Lsz--HfI6LBZ for <ace@ietfa.amsl.com>; Sat, 21 Dec 2019 11:07:42 -0800 (PST)
Received: from mail2.augustcellars.com (augustcellars.com [50.45.239.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C81A12004F for <ace@ietf.org>; Sat, 21 Dec 2019 11:07:42 -0800 (PST)
Received: from Jude (73.180.8.170) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Sat, 21 Dec 2019 11:07:36 -0800
From: Jim Schaad <ietf@augustcellars.com>
To: 'Ludwig Seitz' <ludwig_seitz@gmx.de>, 'Daniel Migault' <daniel.migault@ericsson.com>
CC: ace@ietf.org, 'Benjamin Kaduk' <kaduk@mit.edu>, 'Roman Danyliw' <rdd@cert.org>
References: <RT-Ticket-1157486@icann.org> <157508633572.4770.7120325133415529789.idtracker@ietfa.amsl.com> <rt-4.4.3-30491-1576273382-1996.1157486-37-0@icann.org> <000901d5b201$0ff47c90$2fdd75b0$@augustcellars.com> <42f75b3b-9d85-5483-401b-d23b167dd038@gmx.de>
In-Reply-To: <42f75b3b-9d85-5483-401b-d23b167dd038@gmx.de>
Date: Sat, 21 Dec 2019 11:07:34 -0800
Message-ID: <008301d5b831$e91ba8f0$bb52fad0$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQHhbZrA39yrlgk7GZbeDpCgEddqRwIbSyNFAgMixioBz+/VpgHr1TCip2617vA=
Content-Language: en-us
X-Originating-IP: [73.180.8.170]
Archived-At: <https://mailarchive.ietf.org/arch/msg/ace/sj4Lm_B6mPkTBIQYfsSRnDReZPE>
Subject: Re: [Ace] FW: [IANA #1157486] Last Call: <draft-ietf-ace-oauth-authz-27.txt> (Authentication and Authorization for Constrained Environments (ACE) using the OAuth 2.0 Framework (ACE-OAuth)) to Proposed Standard
X-BeenThere: ace@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Authentication and Authorization for Constrained Environments \(ace\)" <ace.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ace>, <mailto:ace-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ace/>
List-Post: <mailto:ace@ietf.org>
List-Help: <mailto:ace-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ace>, <mailto:ace-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Dec 2019 19:07:45 -0000

Personal opinion,

I think that we should be requesting a separate page.  I think we are going to have enough different registries that keeping them separate from OAuth is going to be useful in preventing confusion.  For the mapping registries, it might be useful to see if IANA can give us a link from the mapping registry to the OAuth registry.

Jim


-----Original Message-----
From: Ludwig Seitz <ludwig_seitz@gmx.de> 
Sent: Saturday, December 21, 2019 3:26 AM
To: Jim Schaad <ietf@augustcellars.com>; 'Daniel Migault' <daniel.migault@ericsson.com>
Cc: ace@ietf.org; Benjamin Kaduk <kaduk@mit.edu>; 'Roman Danyliw' <rdd@cert.org>
Subject: Re: FW: [IANA #1157486] Last Call: <draft-ietf-ace-oauth-authz-27.txt> (Authentication and Authorization for Constrained Environments (ACE) using the OAuth 2.0 Framework (ACE-OAuth)) to Proposed Standard

> From: Sabrina Tanamal via RT <drafts-lastcall@iana.org>
> Subject: [IANA #1157486] Last Call: 
> <draft-ietf-ace-oauth-authz-27.txt> (Authentication and Authorization 
> for Constrained Environments (ACE) using the OAuth 2.0 Framework 
> (ACE-OAuth)) to Proposed Standard
>
> (BEGIN IANA COMMENTS)
>
> IESG/Authors/WG Chairs:
>
> The IANA Functions Operator has completed its review of draft-ietf-ace-oauth-authz-27. If any part of this review is inaccurate, please let us know.
>
> The IANA Functions Operator has a question about one of the actions requested in the IANA Considerations section of this document.
>
> The IANA Functions Operator understands that, upon approval of this document, there are fifteen actions which we must complete.
>
> NOTE: We’re asking the ADs how to handle the registrations for which Hannes is the only reviewer.
>
> IANA Question --> Several sections of the current draft propose to create new registries (Sections 8.1, 8.3, 8.4, 8.6, 8.7, 8.9, and 8.11). For each of these requests, IANA asks the authors where the new registries are to be located. Should they be added to an existing registry page? If not, do they belong in an existing category at http://www.iana.org/protocols? For each of the new registries, it is not clear from the context of the request where the new registries should be established.
>
Hello WG chairs (WG and ADs in cc),

I am in need of some guidance here due to my lack of experience in IANA matters.

Do we want to establish a new protocol page for ACE in the IANA registries?

Alternatively we could add them to the OAuth pages under a specific ACE section.

Regards,
Ludwig

v2.23.0 | Report a Bug | By Email