[Ace] AIF as a suggestion in key-groupcomm; AIF in MQTT

Carsten Bormann <cabo@tzi.org> Mon, 18 May 2020 15:21 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 EB2A33A0765 for <ace@ietfa.amsl.com>; Mon, 18 May 2020 08:21:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level:
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[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 EwuhltLrrErL for <ace@ietfa.amsl.com>; Mon, 18 May 2020 08:21:41 -0700 (PDT)
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 CB28B3A053E for <ace@ietf.org>; Mon, 18 May 2020 08:21:40 -0700 (PDT)
Received: from [192.168.217.119] (p548dc699.dip0.t-ipconnect.de [84.141.198.153]) (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 49QjR65d2YzybZ; Mon, 18 May 2020 17:21:38 +0200 (CEST)
From: Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mao-Original-Outgoing-Id: 611508098.2229871-50011e8fa52f5359aa98047e9ab2c652
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Date: Mon, 18 May 2020 17:21:38 +0200
Message-Id: <C6776FE8-B71C-4739-90EC-928D9D39604D@tzi.org>
To: Ace Wg <ace@ietf.org>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ace/4_SqHbPOCs88hRmEv6dk2VIUkMs>
Subject: [Ace] AIF as a suggestion in key-groupcomm; AIF in MQTT
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: Mon, 18 May 2020 15:21:43 -0000

As I said today, the role of AIF [1] in ACE documents can only be as a suggestion, or as a starting point, because it assumes that the (resource) names are static, and something application-specific has to be added for more dynamic names.

The current MQTT proposal [2] is different in three ways:
(1) it has different verbs (publish, subscribe)
(2) it uses topic filters instead of resource names
(3) it uses a text-based syntax.

I think that (3) has all the usual problems, so I would recommend against this.
(1) and (2) can be mapped to the structure of AIF without any pain, and I would recommend for this.

In summary, essence, AIF could be made useful as the base suggestion for MQTT as well as REST, with the refinement for verbs and filters retained in the current draft.

Grüße, Carsten



[1]: https://tools.ietf.org/html/draft-bormann-core-ace-aif
[2]: https://tools.ietf.org/html/draft-ietf-ace-mqtt-tls-profile-04#section-3