[core] Comments on draft-ietf-ace-key-groupcomm-oscore
Jim Schaad <ietf@augustcellars.com> Thu, 24 January 2019 00:57 UTC
Return-Path: <ietf@augustcellars.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D5E7130F8B; Wed, 23 Jan 2019 16:57:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 uaRQg7Biu58w; Wed, 23 Jan 2019 16:57:33 -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 EC9D1129BBF; Wed, 23 Jan 2019 16:57:29 -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; Wed, 23 Jan 2019 16:57:24 -0800
From: Jim Schaad <ietf@augustcellars.com>
To: draft-ietf-ace-key-groupcomm-oscore@ietf.org
CC: core@ietf.org
Date: Wed, 23 Jan 2019 16:57:22 -0800
Message-ID: <08a001d4b37f$c55111b0$4ff33510$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-us
Thread-Index: AdSzdu0CKim28olUQnCJrTbZomSwpw==
X-Originating-IP: [73.180.8.170]
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/DYFkpmqZv2Xx0r6fA43e3GftFSU>
Subject: [core] Comments on draft-ietf-ace-key-groupcomm-oscore
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jan 2019 00:57:35 -0000
I am having a huge problem understanding this document because I am completely confused by the model that is being propagated here. This document has a model that every group is going to be on a different resource. It is not clear that this is the same model as is being used in the ACE group communication document. Probably one of these two documents should provide a more explicit module of how things work if this is what is going to be desired. I was under the impression that a single join point would be used for multiple groups at the same time. This may be acceptable with this document but if so then it is really not clear. This document appears to be pointed at dealing with multicast groups, but there does not seem to be any tie between multicast resources and join request points. The document should also deal with the same issue for pub-sub servers as that is of interest as well. This document appears to be missing the registration of the oscore-gp and oscore-gid attributes. I don't know but assume that there is (or should be) a registry for these types of things. Specifically do these items allow for multiple values or are they single valued? (I will assume that if they are multiple valued they should appear as multiple items just to make life easier.) Jim
- [core] Comments on draft-ietf-ace-key-groupcomm-o… Jim Schaad
- Re: [core] Comments on draft-tiloca-core-oscore-d… Marco Tiloca