Re: [Ace] I-D Action: draft-ietf-ace-aif-04.txt

Carsten Bormann <cabo@tzi.org> Fri, 28 January 2022 14:57 UTC

Return-Path: <cabo@tzi.org>
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 E77633A1711 for <ace@ietfa.amsl.com>; Fri, 28 Jan 2022 06:57:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 VysehHUcDG8Q for <ace@ietfa.amsl.com>; Fri, 28 Jan 2022 06:57:21 -0800 (PST)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 04A7C3A1727 for <ace@ietf.org>; Fri, 28 Jan 2022 06:57:20 -0800 (PST)
Received: from [192.168.217.118] (p5089a6b7.dip0.t-ipconnect.de [80.137.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4JlgXr6M9YzDCcS; Fri, 28 Jan 2022 15:57:16 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <164338017009.17061.4460362194218791141@ietfa.amsl.com>
Date: Fri, 28 Jan 2022 15:57:16 +0100
X-Mao-Original-Outgoing-Id: 665074636.509406-ddf3f6c497993778b4ec55c8cf378f95
Content-Transfer-Encoding: quoted-printable
Message-Id: <9A313B41-ADF1-4C73-BF19-1814EB6A8D97@tzi.org>
References: <164338017009.17061.4460362194218791141@ietfa.amsl.com>
To: Ace Wg <ace@ietf.org>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ace/N3lrGrIBNvoYei0uWLxBe61TXwQ>
Subject: Re: [Ace] I-D Action: draft-ietf-ace-aif-04.txt
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: Fri, 28 Jan 2022 14:57:32 -0000

This version is pretty much identical to the previous one, with one significant change:

After discussion with the WG chairs, and a look at 

https://datatracker.ietf.org/doc/draft-ietf-ace-aif/referencedby/

it seemed more natural to put this on the standards track right away instead of going through the downref procedure three times...

I’m sure the WG chairs will post soon how we are going to handle this change; officially, of course, the document has left the WG already and is now in the hands of the AD.

(I also fixed two typos and added the venue boilerplate.
You will see a lot more changes because the last version was submitted before the <tt> flag day semantic change in xml2rfc.)

Grüße, Carsten


> On 2022-01-28, at 15:29, internet-drafts@ietf.org wrote:
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Authentication and Authorization for Constrained Environments WG of the IETF.
> 
>        Title           : An Authorization Information Format (AIF) for ACE
>        Author          : Carsten Bormann
> 	Filename        : draft-ietf-ace-aif-04.txt
> 	Pages           : 14
> 	Date            : 2022-01-28
> 
> Abstract:
>   Constrained Devices as they are used in the "Internet of Things" need
>   security.  One important element of this security is that devices in
>   the Internet of Things need to be able to decide which operations
>   requested of them should be considered authorized, need to ascertain
>   that the authorization to request the operation does apply to the
>   actual requester, and need to ascertain that other devices they place
>   requests on are the ones they intended.
> 
>   To transfer detailed authorization information from an authorization
>   manager (such as an ACE-OAuth Authorization Server) to a device, a
>   compact representation format is needed.  This document provides a
>   suggestion for such a format, the Authorization Information Format
>   (AIF).  AIF is defined both as a general structure that can be used
>   for many different applications and as a specific refinement that
>   describes REST resources (potentially dynamically created) and the
>   permissions on them.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-ace-aif/
> 
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-ace-aif-04.html
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-ace-aif-04