Re: [Ace] [media-types] ACE AIF media types

Carsten Bormann <cabo@tzi.org> Sat, 20 February 2021 21:35 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 A69013A0DAE; Sat, 20 Feb 2021 13:35:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 U8muzIqkXmhh; Sat, 20 Feb 2021 13:35:51 -0800 (PST)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BAF2B3A0DAD; Sat, 20 Feb 2021 13:35:50 -0800 (PST)
Received: from [192.168.217.118] (p5089a828.dip0.t-ipconnect.de [80.137.168.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4DjhZV0KRrzybx; Sat, 20 Feb 2021 22:35:46 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <2a4c85fb-b743-1fd3-1556-39c175ef2cfb@isode.com>
Date: Sat, 20 Feb 2021 22:35:45 +0100
Cc: media-types@ietf.org, Ace Wg <ace@ietf.org>
X-Mao-Original-Outgoing-Id: 635549745.419328-d0d58741df38bc0166cc0579869a1edb
Content-Transfer-Encoding: quoted-printable
Message-Id: <3DDF5FBC-74E8-480D-851C-8C625D3E97A7@tzi.org>
References: <4C0883A8-C309-480D-AA7F-0B889F04F34B@tzi.org> <2a4c85fb-b743-1fd3-1556-39c175ef2cfb@isode.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ace/8siDRcdoICiVjUHwdzMYxErRTe8>
Subject: Re: [Ace] [media-types] ACE AIF media types
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, 20 Feb 2021 21:35:56 -0000

Hi Alexey,

On 2021-02-13, at 16:16, Alexey Melnikov <alexey.melnikov@isode.com> wrote:
> 
> This mostly looks fine, but the registration templates are missing some required and recommended fields from the template. Please review and update.

Thank you.
I seem to have missed pointing to the update.

https://www.ietf.org/archive/id/draft-ietf-ace-aif-02.html#name-iana-considerations

Relevant parts copied below.
(Obviously, the Tperm definitions need to say
+    A value from the subregistry for `Tperm`.
for Tperm, as it analogously already does for Toid.
In the editor’s copy.)

Grüße, Carsten



5.1.  Media Types

   IANA is requested to add the following Media-Types to the "Media
   Types" registry.

   +==========+======================+=====================+
   | Name     | Template             | Reference           |
   +==========+======================+=====================+
   | aif+cbor | application/aif+cbor | RFC XXXX, Section 4 |
   +----------+----------------------+---------------------+
   | aif+json | application/aif+json | RFC XXXX, Section 4 |
   +----------+----------------------+---------------------+

                            Table 3

   // RFC Ed.: please replace RFC XXXX with this RFC number and remove
   this note.

   For "application/aif+cbor":

   Type name:  application
   Subtype name:  aif+cbor
   Required parameters:
      *  "Toid": the identifier for the object for which permissions are
         supplied.  A value from the subregistry for "Toid".  Default
         value: "local-uri" (RFC XXXX).

      *  "Tperm": the data type of a permission set for the the object
         identified via a "Toid".  Default value: "REST-method-set" (RFC
         XXXX).
   Optional parameters:  none
   Encoding considerations:  binary (CBOR)
   Security considerations:  Section 6 of RFC XXXX



Bormann                  Expires 21 August 2021                 [Page 8]
Internet-Draft                   ACE AIF                   February 2021


   Interoperability considerations:  none
   Published specification:  Section 4 of RFC XXXX
   Applications that use this media type:  No known applications
      currently use this media type.
   Fragment identifier considerations:  The syntax and semantics of
      fragment identifiers is as specified for "application/cbor".  (At
      publication of RFC XXXX, there is no fragment identification
      syntax defined for "application/cbor".)
   Person & email address to contact for further information:  ACE WG
      mailing list (ace@ietf.org), or IETF Applications and Real-Time
      Area (art@ietf.org)
   Intended usage:  COMMON
   Restrictions on usage:  none
   Author/Change controller:  IETF
   Provisional registration:  no

   For "application/aif+json":

   Type name:  application
   Subtype name:  aif+json
   Required parameters:
      *  "Toid": the identifier for the object for which permissions are
         supplied.  A value from the subregistry for "Toid".  Default
         value: "local-uri" (RFC XXXX).

      *  "Tperm": the data type of a permission set for the the object
         identified via a "Toid".  Default value: "REST-method-set" (RFC
         XXXX).
   Optional parameters:  none
   Encoding considerations:  binary (JSON is UTF-8-encoded text)
   Security considerations:  Section 6 of RFC XXXX
   Interoperability considerations:  none
   Published specification:  Section 4 of RFC XXXX
   Applications that use this media type:  No known applications
      currently use this media type.
   Fragment identifier considerations:  The syntax and semantics of
      fragment identifiers is as specified for "application/json".  (At
      publication of RFC XXXX, there is no fragment identification
      syntax defined for "application/json".)
   Person & email address to contact for further information:  ACE WG
      mailing list (ace@ietf.org), or IETF Applications and Real-Time
      Area (art@ietf.org)
   Intended usage:  COMMON
   Restrictions on usage:  none
   Author/Change controller:  IETF
   Provisional registration:  no





Bormann                  Expires 21 August 2021                 [Page 9]
Internet-Draft                   ACE AIF                   February 2021


5.2.  Registries

   IANA is requested to create a registry for AIF with two sub-
   registries for "Toid" and "Tperm", populated with:

    +=============+=================+=================================+
    | Subregistry | name            | Description/Specification       |
    +=============+=================+=================================+
    | Toid        | local-part      | local-part of URI as specified  |
    |             |                 | in RFC XXXX                     |
    +-------------+-----------------+---------------------------------+
    | Tperm       | REST-method-set | set of REST methods represented |
    |             |                 | as specified in RFC XXXX        |
    +-------------+-----------------+---------------------------------+

                                  Table 4

   The registration policy is Specification required [RFC8126].  The
   designated expert will engage with the submitter to ascertain the
   requirements of this document are addressed.

   // RFC Ed.: please replace RFC XXXX with this RFC number and remove
   this note.