Re: [Ace] draft-ietf-ace-key-groupcomm-oscore

Francesca Palombini <> Mon, 03 June 2019 09:01 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id EF5E71200D8; Mon, 3 Jun 2019 02:01:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 9sdrqnYxcpfm; Mon, 3 Jun 2019 02:00:57 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E4985120020; Mon, 3 Jun 2019 02:00:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=M1+heryMo0PhVLYe1w3R3p/PWgTH6ZCePYsIiG0mCEk=; b=MhxUkTxnv/4Nprf3TuhVJLMPMB+pSp2KcBj7jAWvNoZ/1Le+KWIkhLuaRPAxv3yQai4cOxQn7cFPydx0hkzn2s2I+4T8eyr4UEhhza8gfkipukq9YUqJSxB5djJJBpvzA866MVb/r7hHk13U3HL70Df9rVEQClHMOoxqCBb9r/U=
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1965.12; Mon, 3 Jun 2019 09:00:53 +0000
Received: from ([fe80::8a9:a4d6:303b:45f0]) by ([fe80::8a9:a4d6:303b:45f0%5]) with mapi id 15.20.1965.011; Mon, 3 Jun 2019 09:00:53 +0000
From: Francesca Palombini <>
To: Jim Schaad <>, "" <>
CC: "" <>
Thread-Topic: draft-ietf-ace-key-groupcomm-oscore
Thread-Index: AQHVFTfYPpErjgyNn0iE0xOyD54uCaaBKWWAgAijYwA=
Date: Mon, 3 Jun 2019 09:00:53 +0000
Message-ID: <>
References: <> <018501d515a9$ed26d8a0$c77489e0$>
In-Reply-To: <018501d515a9$ed26d8a0$c77489e0$>
Accept-Language: en-GB, en-US
Content-Language: en-US
authentication-results: spf=none (sender IP is );
x-originating-ip: []
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 2c6d56d1-9c88-4848-2ade-08d6e801fb9a
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600148)(711020)(4605104)(1401327)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:HE1PR0701MB2972;
x-ms-traffictypediagnostic: HE1PR0701MB2972:
x-microsoft-antispam-prvs: <>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0057EE387C
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(366004)(346002)(136003)(376002)(39860400002)(396003)(199004)(189003)(51914003)(51444003)(229853002)(5660300002)(25786009)(561944003)(53936002)(4326008)(486006)(76176011)(33656002)(82746002)(68736007)(44832011)(256004)(54896002)(6486002)(83716004)(6512007)(476003)(6436002)(71190400001)(71200400001)(6306002)(14444005)(6246003)(73956011)(36756003)(66946007)(478600001)(86362001)(7736002)(66556008)(64756008)(102836004)(66446008)(66476007)(76116006)(186003)(26005)(446003)(11346002)(2616005)(6506007)(81166006)(81156014)(8676002)(316002)(2906002)(66066001)(99286004)(110136005)(14454004)(3846002)(6116002)(2501003)(8936002)(4743002)(9326002); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR0701MB2972;; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None ( does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: wZkpzVoHZ6ZIP4jgdgvMe5h7tsGBx16XA5stqJrRUnRlwWvvHjLXuI9YX1C6HHJoQGbZgmcMgpDHeetMLl6+OuH/gnvqNyi5uZrPGPWWsFpbsp1h6lGa6Ogcp+JhnS/B/hUmP58eSTjhrB01tPEbSP95dfsYlS0rkNzom/d6cEuEr8h/yaIF7GFPTAjtG5JE94IToAKnUsqbbV6RpaNrfNm5BHoF0TXXWp6NrQGBJcQ2UmtdXYNh5xbGVIpQIlp5gnetM8T2O7dAf0vRl5zEse4lhpBWe98HhTIsR5QPWtIrDuuAyqA2E5ftRmjNg9ScWnRS9p1d0PLSb3V1m0t4Ro032Jhhq2pH3KruWheMwywFW9OgKdZ4LJzYJh+2W6SXDx9i8tptBpgnykxXBdM/Orqx7X6NGiHBFKmdl7WB940=
Content-Type: multipart/alternative; boundary="_000_671FEB26C25D4AB0BF9F3E6FAD38ADDDericssoncom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 2c6d56d1-9c88-4848-2ade-08d6e801fb9a
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Jun 2019 09:00:53.1648 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0701MB2972
Archived-At: <>
Subject: Re: [Ace] draft-ietf-ace-key-groupcomm-oscore
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Authentication and Authorization for Constrained Environments \(ace\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 03 Jun 2019 09:01:01 -0000

Hi Jim,
We have now added your review comments to the github issues, and we’ll get to it. Below, the couple of comments that needed additional clarification (and consequent APs).
Thank you again for the thorough review!
Francesca and Marco
2.  Section 3.1 - "requester" seems to be an odd name for "sender" or
[*] This particular document does not consider the concept of publisher. Requester was chosen to identify a client in a group communication setting, i.e. stressing that it sends (group) requests and receives (unicast) responses. Sender would not be correct, as both clients and servers are senders at some point during the message exchange.
[JLS] I will probably complain again at a later date.  My problem is that requester is not the opposite of listener.  A different set might be “requester”, “responder”, “monitor”
[FP] Ok, thanks for the proposal. We will switch to these terms. (AP8)

3. Section 3.1 - I am trying to figure out why a Gid would be a reasonable
value for the scope.  This means that the AS is going to be the one to
assign the Gid value in many cases as it needs to check the scope value
there.  Is that going to be a common case?  I.e. Are Gids going to be
assigned by administrators?
[*] The Gid of the Authorization Request would be a reasonable scope because the join resource is associated to it (at the GM). The GM receiving a Join Request must be able to retrieve the correct Gid following the access to the join resource. No, the AS does not assign the Gid value (if that is used as scope in the Authorization Request). The AS only needs to check that the client is authorized to get an access token for that scope, regardless that it is a join resource. The Gid is assigned by the resource owner of the join resource at the GM, that is an administrator.
[JLS] Ok – so the answer to my question is yes.  I wanted to be sure it was not a registration process on the KDC (I think).
[FP] Right, it is not a registration process.

4. Section 3.1 - Is the form in Appendix C of the Gid in some respect
mandatory?  If it is not, then how does a receiver of a message distinguish
between two different groups that are using the same multicast address?  Is
that going to be a non-supported case?  The most common case of this would
be having two different groups on the default CoAP multicast address talking
to RDs with different permissions at the RD to see things.
[*] As of now, that is just an example, we might reconsider and make this at least mandatory to implement, so it would be good with more feedback on this. The requirements anyway are that in a GM all the Gids are unique, and that a Gid is changed after a group rekeying. The format in appendix C guarantees both. If your second question refers to one node in 2 groups (managed by 2 different GMs), where these 2 Gids collide, then that is up to the application to decide how to deal with it (discard, try both contexts…). We briefly discuss sec cons about it in section 8.5 of core-oscore-groupcomm. However, that is independent from the format of the Gid, as long as the requirements are met.
[JLS] My question dealt with having two different KDCs each of which has a Gid and that Gid collides for some reason.  The groups of the two KDCs are distinct and the resources accessible by those different KDCs are distinct and are quite possibly two different applications.
[FP] Ok, that’s what we thought. So we will add sec cons that this is up to the application to decide (AP9)

7.  Section 4.2 - for 'client_cred', I am unsure what the client is supposed
to do if the joining node does not know the countersignature algorithm.  Can
the include public key not be in a consistent format?  What does consistent
format even mean?
[*] Consistent format refers to the key type based on the countersignature algorithm used. If the joining node does not know the countersignature algorithm, it might just omit this parameter, or send a public key as a guess. If the guess is incorrect, the GM will reply as specified in 4.3 (see point 8).
[JLS] I don’t know what point 8 is – There are 6 points for the outer list and the inner point 8 defines a field and does not define a response.
[FP] I meant point 8. of your review comments: the one just below this one.

8. Section 4.3 - I don't understand why the GM is accepting the join request
if the client_cred passed in was not in the correct format.  Is this a typo?
[*] The reason for responding with a non-error response code is to be able to use the payload to provide the key info in a CBOR map. With a 4.XX response, that would not be possible since the payload is supposed to be a diagnostic human readable text string. We are willing to change that if the WG/CoAP experts can confirm that would be ok.
[JLS] So I return a 2.01 in both cases, and based on the content the client needs to determine what is happening?   We are breaking the 4.xx response already in the OAuth framework by returning an error response.  I would think that it would make more sense to continue that trend.
[FP] Ok, we will change this to error code. We will bring this up in CoRE as well. (AP10)

10.  Section 6 - What is the POP method for the fourth bullet method?
[*] We address this as well in point 9 of your review comments, to which we say: “Until now, we kept that out of the scope of this and dependent documents (see section 8 of ace-key-groupcomm-oscore), but we are looking to include it.
One possibility we are considering is to sign the key distribution request together with a nonce that was sent from the KDC (for the sake of freshness),  using the private key paired to the public key sent in ‘client_cred’.“
You seemed ok with this, so we will implement it here. (AP5)
[JLS] This is a problem that is going to need to be solved at some point for the OAuth framework as well at some point in the future.  But may be more of a problem here.  You might want to talk to Ludwig about the solution space.
[FP] We will do that.

12.  Section 7 - This text implies to me that all users of a group key need
to be able to act as servers and have a fixed port number which was supplied
some how to the GM so that it can be notified.   This could be done by
keeping up the DTLS session, but that is still a little bit tricky and would
not work for OSCORE based messages.  This text might want to point to the
section in the ietf-ace-key-groupcomm that deals with this and require that
the query or subscribe methods be supported.  Although both of those suffer
from the lack of hard break on the part of publishers.
[*] Yes, that is correct, group members would need to act as servers. The port number could be either default or part of the Join Request (in a new field “rekeying uri”?), with the group member assuming that the rekeying is done with this (unicast) default algorithm. The GM could then either confirm, or communicate to the joining node a different group rekeying scheme (in “group_policies”) and port and resource (in the new field “rekeying uri”) in the Join Response. However, that is quite heavy on the group member, which is a reason to use RD instead to discover in advance the rekeying scheme and rekeying uri as linked target attributes of the join resource. Would that work? Also why do you say that it would not work for OSCORE based messages? We could easily specify that when using the OSCORE profile between group member and GM, the nodes need to have both roles, so configure their keying material accordingly (for example: the group member’s recipient context need to contain a replay window). (AP7)
[JLS] I think that this may need to have a design session to figure out all of the ramifications and problems.
[FP] Ok, we will start drafting this on a separate branch to have a starting point. We could have this design session in Montreal or during an interim.