]> RISE AB

Isafjordsgatan 22 Kista 16440 Stockholm Sweden marco.tiloca@ri.se

Hollandstr. 12/4 Vienna 1020 Austria christian@amsuess.com

Consultant

+31-492474673 (Netherlands), +33-966015248 (France) stokcons@bbhmail.nl

Applications CoRE Working Group Internet-Draft Group communication over the Constrained Application Protocol (CoAP) can be secured by means of Group Object Security for Constrained RESTful Environments (Group OSCORE). At deployment time, devices may not know the exact security groups to join, the respective Group Manager, or other information required to perform the joining process. This document describes how a CoAP endpoint can use descriptions and links of resources registered at the CoRE Resource Directory to discover security groups and to acquire information for joining them through the respective Group Manager. A given security group may protect multiple application groups, which are separately announced in the Resource Directory as sets of endpoints sharing a pool of resources. This approach is consistent with, but not limited to, the joining of security groups based on the ACE framework for Authentication and Authorization in constrained environments. Discussion Venues Discussion of this document takes place on the Constrained RESTful Environments Working Group mailing list (core@ietf.org), which is archived at . Source for this draft and an issue tracker can be found at .

Introduction The Constrained Application Protocol (CoAP) supports group communication over IP multicast to improve efficiency and latency of communication and reduce bandwidth requirements. A set of CoAP endpoints constitutes an application group by sharing a common pool of resources, that can be efficiently accessed through group communication. The members of an application group may be members of a security group, thus sharing a common set of keying material to secure group communication. The security protocol Group Object Security for Constrained RESTful Environments (Group OSCORE) builds on OSCORE and protects CoAP messages end-to-end in group communication contexts through CBOR Object Signing and Encryption (COSE) . An application group may rely on one or more security groups, and a same security group may be used by multiple application groups at the same time. A CoAP endpoint relies on a Group Manager (GM) to join a security group and get the group keying material. The joining process in is based on the ACE framework for Authentication and Authorization in constrained environments , with the joining endpoint and the GM acting as ACE Client and Resource Server, respectively. That is, the joining endpoint accesses the group-membership resource exported by the GM and associated with the security group to join. Typically, devices store a static X509 IDevID certificate installed at manufacturing time . This is used at deployment time during an enrollment process that provides the devices with an Operational Certificate, possibly updated during the device lifetime. Operational Certificates may specify information to join security groups, especially a reference to the group-membership resources to access at the respective GMs. However, it is usually impossible to provide such precise information to freshly deployed devices, as part of their (early) Operational Certificate. This can be due to a number of reasons: (1) the security group(s) to join and the responsible GM(s) are generally unknown at manufacturing time; (2) a security group of interest is created, or the responsible GM is deployed, only after the device is enrolled and fully operative in the network; (3) information related to existing security groups or to their GMs has changed. This requires a method for CoAP endpoints to dynamically discover security groups and their GM, and to retrieve relevant information about deployed groups. To this end, CoAP endpoints can use descriptions and links of group-membership resources at GMs, to discover security groups and retrieve the information required for joining them. With the discovery process of security groups expressed in terms of links to resources, the remaining problem is the discovery of those links. The CoRE Resource Directory (RD) allows such discovery in an efficient way, and it is expected to be used in many setups that would benefit of security group discovery. This specification builds on this approach and describes how CoAP endpoints can use the RD to perform the link discovery steps, in order to discover security groups and retrieve the information required to join them through their GM. In short, the GM registers as an endpoint with the RD. The resulting registration resource includes one link per security group under that GM, specifying the path to the related group-membership resource to access for joining that group. Additional descriptive information about the security group is stored with the registered link. In a RD based on Link Format as defined in , this information is specified as target attributes of the registered link, and includes the identifiers of the application groups which use that security group. This enables a lookup of those application groups at the RD, where they are separately announced by a Commissioning Tool (see Appendix A of ). When querying the RD for security groups, a CoAP endpoint can use CoAP observation . This results in automatic notifications on the creation of new security groups or the update of existing groups. Thus, it facilitates the early deployment of CoAP endpoints, i.e., even before the GM is deployed and security groups are created. Interaction examples are provided in Link Format, as well as in the Constrained RESTful Application Language CoRAL with reference to a CoRAL-based RD . While all the CoRAL examples show the CoRAL textual serialization format, its binary serialization format is used on the wire. [ NOTE: The reported CoRAL examples are based on the textual representation used until version -03 of . These will be revised to use the CBOR diagnostic notation instead. ] The approach in this document is consistent with, but not limited to, the joining of security groups defined in .

Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here. This specification requires readers to be familiar with the terms and concepts discussed in and , as well as in . Readers should also be familiar with the terms and concepts discussed in , and . Terminology for constrained environments, such as "constrained device" and "constrained-node network", is defined in . Consistently with the definitions from , this document also refers to the following terminology.

• CoAP group: a set of CoAP endpoints all configured to receive CoAP multicast messages sent to the group's associated IP multicast address and UDP port. An endpoint may be a member of multiple CoAP groups by subscribing to multiple IP multicast addresses.
• Security group: a set of CoAP endpoints that share the same security material, and use it to protect and verify exchanged messages. A CoAP endpoint may be a member of multiple security groups. There can be a one-to-one or a one-to-many relation between security groups and CoAP groups. This document especially considers a security group to be an OSCORE group, where all members share one OSCORE Security Context to protect group communication with Group OSCORE . However, the approach defined in this document can be used to support the discovery of different security groups than OSCORE groups.
• Application group: a set of CoAP endpoints that share a common set of resources. An endpoint may be a member of multiple application groups. An application group can be associated with one or more security groups, and multiple application groups can use the same security group. Application groups are announced in the RD by a Commissioning Tool, according to the RD-Groups usage pattern (see Appendix A of ).

Like , this document also uses the following term.

• Authentication credential: set of information associated with an entity, including that entity's public key and parameters associated with the public key. Examples of authentication credentials are CBOR Web Tokens (CWTs) and CWT Claims Sets (CCSs) , X.509 certificates and C509 certificates .

Registration of Group Manager Endpoints During deployment, a Group Manager (GM) can find the CoRE Resource Directory (RD) as described in . Afterwards, the GM registers as an endpoint with the RD, as described in . The GM SHOULD NOT use the Simple Registration approach described in . When registering with the RD, the GM also registers the links to all the group-membership resources it has at that point in time, i.e., one for each of its security groups. In the registration request, each link to a group-membership resource has as target the URI of that resource at the GM. Also, it specifies a number of descriptive parameters as defined in . Furthermore, the GM MAY additionally register the link to its resource implementing the ACE authorization information endpoint (see ). A joining node can provide the GM with its own access token by sending it in a request targeting that resource, thus proving to be authorized to join certain security groups (see ). In such a case, the link MUST include the parameter 'rt' with value "ace.ai", defined in .

Parameters For each registered link to a group-membership resource at a GM, the following parameters are specified together with the link. In the RD defined in and based on Link Format, each parameter is specified in a target attribute with the same name. In a RD based on CoRAL, such as the one defined in , each parameter is specified in a nested element with the same name.

• 'ct', specifying the content format used with the group-membership resource at the Group Manager, with value "application/ace-groupcomm+cbor" registered in . Note: The examples in this document use the provisional value 65000 from the range "Reserved for Experimental Use" of the "CoAP Content-Formats" registry, within the "CoRE Parameters" registry.
• 'rt', specifying the resource type of the group-membership resource at the Group Manager, with value "core.osc.gm" registered in .
• 'if', specifying the interface description for accessing the group-membership resource at the Group Manager, with value "ace.group" registered in .
• 'sec-gp', specifying the name of the security group of interest, as a stable and invariant identifier, such as the group name used in . This parameter MUST specify a single value.
• 'app-gp', specifying the name(s) of the application group(s) associated with the security group of interest indicated by 'sec-gp'. This parameter MUST occur once for each application group, and MUST specify only a single application group. When a security group is created at the GM, the names of the application groups using it are also specified as part of the security group configuration (see ). Thus, when registering the links to its group-membership resource, the GM is aware of the application groups and their names. If a different entity than the GM registers the security groups to the RD, e.g., a Commissioning Tool, this entity has to also be aware of the application groups and their names to specify. To this end, it can obtain them from the GM or from the Administator that created the security groups at the GM (see ).

Optionally, the following parameters can also be specified. If Link Format is used, the value of each of these parameters is encoded as a text string.

• 'hkdf', specifying the HKDF Algorithm used in the security group. If present, this parameter MUST specify a single value, which is taken from the 'Value' column of the "COSE Algorithms" Registry .
• 'cred_fmt', specifying the format of the authentication credentials used in the security group. If present, this parameter MUST specify a single value, which is taken from the 'Label' column of the "COSE Header Parameters" Registry . Acceptable values denote a format that MUST explicitly provide the public key as well as the comprehensive set of information related to the public key algorithm, including, e.g., the used elliptic curve (when applicable). At the time of writing this specification, acceptable formats of authentication credentials are CBOR Web Tokens (CWTs) and CWT Claim Sets (CCSs) , X.509 certificates and C509 certificates . Further formats may be available in the future, and would be acceptable to use as long as they comply with the criteria defined above. [ As to CWTs and unprotected CWT claim sets, there is a pending registration requested by draft-ietf-lake-edhoc. ] [ As to C509 certificates, there is a pending registration requested by draft-ietf-cose-cbor-encoded-cert. ]
• 'sign_enc_alg', specifying the encryption algorithm used to encrypt messages in the security group, when these are also signed, e.g., as in the group mode of Group OSCORE (see ). If present, this parameter MUST specify a single value, which is taken from the 'Value' column of the "COSE Algorithms" Registry .
• 'sign_alg', specifying the algorithm used to sign messages in the security group. If present, this parameter MUST specify a single value, which is taken from the 'Value' column of the "COSE Algorithms" Registry .
• 'sign_alg_crv', specifying the elliptic curve (if applicable) for the algorithm used to sign messages in the security group. If present, this parameter MUST specify a single value, which is taken from the 'Value' column of the "COSE Elliptic Curves" Registry .
• 'sign_key_kty', specifying the key type of countersignature keys used to sign messages in the security group. If present, this parameter MUST specify a single value, which is taken from the 'Value' column of the "COSE Key Types" Registry .
• 'sign_key_crv', specifying the elliptic curve (if applicable) of countersignature keys used to sign messages in the security group. If present, this parameter MUST specify a single value, which is taken from the 'Value' column of the "COSE Elliptic Curves" Registry .
• 'alg', specifying the encryption algorithm used to encrypt messages in the security group, when these are encrypted with pairwise encryption keys, e.g., as in the pairwise mode of Group OSCORE (see ). If present, this parameter MUST specify a single value, which is taken from the 'Value' column of the "COSE Algorithms" Registry .
• 'ecdh_alg', specifying the ECDH algorithm used to derive pairwise encryption keys in the security group, e.g., as for the pairwise mode of Group OSCORE (see ). If present, this parameter MUST specify a single value, which is taken from the 'Value' column of the "COSE Algorithms" Registry .
• 'ecdh_alg_crv', specifying the elliptic curve for the ECDH algorithm used to derive pairwise encryption keys in the security group. If present, this parameter MUST specify a single value, which is taken from the 'Value' column of the "COSE Elliptic Curves" Registry .
• 'ecdh_key_kty', specifying the key type of keys used with an ECDH algorithm to derive pairwise encryption keys in the security group. If present, this parameter MUST specify a single value, which is taken from the 'Value' column of the "COSE Key Types" Registry .
• 'ecdh_key_crv', specifying the elliptic curve of keys used with an ECDH algorithm to derive pairwise encryption keys in the security group. If present, this parameter MUST specify a single value, which is taken from the 'Value' column of the "COSE Elliptic Curves" Registry .
• 'det_hash_alg', specifying the hash algorithm used in the security group when producing deterministic requests, as defined in . If present, this parameter MUST specify a single value, which is taken from the 'Value' column of the "COSE Algorithms" Registry . This parameter MUST NOT be present if the security group does not use deterministic requests.
• 'rekeying_scheme', specifying the rekeying scheme used in the security group for distributing new group keying meterial to the group members. If present, this parameter MUST specify a single value, which is taken from the 'Value' column of the "ACE Groupcomm Rekeying Schemes" registry defined in .

If the security group does not recur to message signing, then the parameters 'sign_enc_alg', 'sign_alg', 'sign_alg_crv', 'sign_key_kty' and 'sign_key_crv' MUST NOT be present. For instance, this is the case for a security group that uses Group OSCORE and uses only the pairwise mode (see ). If the security group does not recur to message encryption through pairwise encryption keys, then the parameters 'alg', 'ecdh_alg', 'ecdh_alg_crv', 'ecdh_key_kty' and 'ecdh_key_crv' MUST NOT be present. For instance, this is the case for a security group that uses Group OSCORE and uses only the group mode see ). Note that the values registered in the COSE Registries are strongly typed. On the contrary, Link Format is weakly typed and thus does not distinguish between, for instance, the string value "-10" and the integer value -10. Thus, in RDs that return responses in Link Format, string values which look like an integer are not supported. Therefore, such values MUST NOT be advertised through the corresponding parameters above. A CoAP endpoint that queries the RD to discover security groups and their group-membership resource to access (see ) would benefit from the information above as follows.

• The values of 'cred_fmt', 'sign_alg', 'sign_alg_crv', 'sign_key_kty', 'sign_key_crv', 'ecdh_alg', 'ecdh_alg_crv', 'ecdh_key_kty' and 'ecdh_key_crv' related to a group-membership resource provide an early knowledge of the format of authentication credentials as well as of the type of public keys used in the security group. Thus, the CoAP endpoint does not need to ask the GM for this information as a preliminary step before the joining process, or to perform a trial-and-error joining exchange with the GM. Hence, at the very first step of the joining process, the CoAP endpoint is able to provide the GM with its own authentication credential in the correct expected format and including a public key of the correct expected type.
• The values of 'hkdf', 'sign_enc_alg', 'sign_alg', 'alg' and 'ecdh_alg' related to a group-membership resource provide an early knowledge of the algorithms used in the security group. Thus, the CoAP endpoint is able to decide whether to actually proceed with the joining process, depending on its support for the indicated algorithms.

Relation Link to Authorization Server For each registered link to a group-membership resource, the GM MAY additionally specify the link to the ACE Authorization Server (AS) associated with the GM, and issuing authorization credentials to join the security group as described in . The link to the AS has as target the URI of the resource where to send an authorization request to. In the RD defined in and based on Link Format, the link to the AS is separately registered with the RD, and includes the following parameters as target attributes.

• 'rel', with value "authorization_server".
• 'anchor', with value the target of the link to the group-membership resource at the GM.

In a RD based on CoRAL, such as the one defined in , this is mapped (as describe there) to a link from the registration resource to the AS, using the <http://www.iana.org/assignments/relation/authorization_server> link relation type.

Registration Example The example below shows a GM with endpoint name "gm1" and address 2001:db8::ab that registers with the RD. The GM specifies the value of the 'sec-gp' parameter for accessing the security group with name "feedca570000", and used by the application group with name "group1" specified with the value of the 'app-gp' parameter. The countersignature algorithm used in the security group is EdDSA (-8), with elliptic curve Ed25519 (6). Authentication credentials used in the security group are X.509 certificates , which is signaled through the COSE Header Parameter "x5chain" (33). The ECDH algorithm used in the security group is ECDH-SS + HKDF-256 (-27), with elliptic curve X25519 (4). In addition, the GM specifies the link to the ACE Authorization Server associated with the GM, to which a CoAP endpoint should send an Authorization Request for joining the corresponding security group (see ).

Example in Link Format Request: GM -> RD ;ct=65000;rt="core.osc.gm";if="ace.group"; sec-gp="feedca570000";app-gp="group1"; cred_fmt="33";sign_enc_alg="10"; sign_alg="-8";sign_alg_crv="6"; alg="10";ecdh_alg="-27";ecdh_alg_crv="4", ;rel="authorization-server"; anchor="coap://[2001:db8::ab]/ace-group/feedca570000" ]]> Response: RD -> GM

Example in CoRAL Request: GM -> RD #using reef = #using iana = #base reef:rd-item { reef:ct 65000 reef:rt "core.osc.gm" reef:if "ace.group" sec-gp "feedca570000" app-gp "group1" cred_fmt 33 sign_enc_alg 10 sign_alg -8 sign_alg_crv 6 alg 10 ecdh_alg -27 ecdh_alg_crv 4 iana:authorization-server } ]]> Response: RD -> GM

Addition and Update of Security Groups The GM is responsible to refresh the registration of all its group-membership resources in the RD. This means that the GM has to update the registration within its lifetime as per , and has to change the content of the registration when a group-membership resource is added/removed, or if its parameters have to be changed, such as in the following cases.

• The GM creates a new security group and starts exporting the related group-membership resource.
• The GM dismisses a security group and stops exporting the related group-membership resource.
• Information related to an existing security group changes, e.g., the list of associated application groups.

To perform an update of its registrations, the GM can re-register with the RD and fully specify all links to its group-membership resources. Alternatively, the GM can perform a PATCH/iPATCH request to the RD, as per . This requires new media-types to be defined in future standards, to apply a new document as a patch to an existing stored document.

Addition Example The example below shows how the GM from re-registers with the RD. When doing so, it specifies:

• The same previous group-membership resource associated with the security group with name "feedca570000".
• An additional group-membership resource associated with the security group with name "ech0ech00000" and used by the application group "group2".
• A third group-membership resource associated with the security group with name "abcdef120000" and used by two application groups, namely "group3" and "group4".

Furthermore, the GM relates the same Authorization Server also to the security groups "ech0ech00000" and "abcdef120000".

Example in Link Format Request: GM -> RD ;ct=65000;rt="core.osc.gm";if="ace.group"; sec-gp="feedca570000";app-gp="group1"; cred_fmt="33";sign_enc_alg="10"; sign_alg="-8";sign_alg_crv="6"; alg="10";ecdh_alg="-27";ecdh_alg_crv="4", ;ct=65000;rt="core.osc.gm";if="ace.group"; sec-gp="ech0ech00000";app-gp="group2"; cred_fmt="33";sign_enc_alg="10"; sign_alg="-8";sign_alg_crv="6"; alg="10";ecdh_alg="-27";ecdh_alg_crv="4", ;ct=65000;rt="core.osc.gm";if="ace.group"; sec-gp="abcdef120000";app-gp="group3"; app-gp="group4";cred_fmt="33"; sign_enc_alg="10";sign_alg="-8"; sign_alg_crv="6";alg="10";ecdh_alg="-27"; ecdh_alg_crv="4", ;rel="authorization-server"; anchor="coap://[2001:db8::ab]/ace-group/feedca570000", ;rel="authorization-server"; anchor="coap://[2001:db8::ab]/ace-group/ech0ech00000", ;rel="authorization-server"; anchor="coap://[2001:db8::ab]/ace-group/abcdef120000" ]]> Response: RD -> GM

Example in CoRAL Request: GM -> RD #using reef = #using iana = #base reef:rd-item { reef:ct 65000 reef:rt "core.osc.gm" reef:if "ace.group" sec-gp "feedca570000" app-gp "group1" cred_fmt 33 sign_enc_alg 10 sign_alg -8 sign_alg_crv 6 alg 10 ecdh_alg -27 ecdh_alg_crv 4 iana:authorization-server } reef:rd-item { reef:ct 65000 reef:rt "core.osc.gm" reef:if "ace.group" sec-gp "ech0ech00000" app-gp "group2" cred_fmt 33 sign_enc_alg 10 sign_alg -8 sign_alg_crv 6 alg 10 ecdh_alg -27 ecdh_alg_crv 4 iana:authorization-server } reef:rd-item { reef:ct 65000 reef:rt "core.osc.gm" reef:if "ace.group" sec-gp "abcdef120000" app-gp "group3" app-gp "group4" cred_fmt 33 sign_enc_alg 10 sign_alg -8 sign_alg_crv 6 alg 10 ecdh_alg -27 ecdh_alg_crv 4 iana:authorization-server } ]]> Response: RD -> GM

Discovery of Security Groups A CoAP endpoint that wants to join a security group, hereafter called the joining node, might not have all the necessary information at deployment time. Also, it might want to know about possible new security groups created afterwards by the respective Group Managers. To this end, the joining node can perform a resource lookup at the RD as per , to retrieve the missing pieces of information needed to join the security group(s) of interest. The joining node can find the RD as described in . The joining node uses the following parameter value for the lookup filtering.

• 'rt' = "core.osc.gm", specifying the resource type of the group-membership resource at the Group Manager, with value "core.osc.gm" registered in .

The joining node may additionally consider the following parameters for the lookup filtering, depending on the information it has already available.

• 'sec-gp', specifying the name of the security group of interest. This parameter MUST specify a single value.
• 'ep', specifying the registered endpoint of the GM.
• 'app-gp', specifying the name(s) of the application group(s) associated with the security group of interest. This parameter MAY be included multiple times, and each occurrence MUST specify the name of one application group.
• 'if', specifying the interface description for accessing the group-membership resource at the Group Manager, with value "ace.group" registered in .

The response from the RD may include links to a group-membership resource specifying multiple application groups, as all using the same security group. In this case, the joining node is already expected to know the exact application group of interest. Furthermore, the response from the RD may include the links to different group-membership resources, all specifying a same application group of interest for the joining node, if the corresponding security groups are all used by that application group. In this case, application policies on the joining node should define how to determine the exact security group to join (see ). For example, different security groups can reflect different security algorithms to use. Hence, a client application can take into account what the joining node supports and prefers, when selecting one particular security group among the indicated ones, while a server application would need to join all of them. Later on, the joining node will be anyway able to join only security groups for which it is actually authorized to be a member (see ). Note that, with RD-based discovery, including the 'app-gp' parameter multiple times would result in finding only the group-membership resource that serves all the specified application groups, i.e., not any group-membership resource that serves either. Therefore, a joining node needs to perform N separate queries with different values for 'app-gp', in order to safely discover the (different) group-membership resource(s) serving the N application groups. The discovery of security groups as defined in this document is applicable and useful to other CoAP endpoints than the actual joining nodes. In particular, other entities can be interested to discover and interact with the group-membership resource at the Group Manager. These include entities acting as signature checkers, e.g., intermediary gateways, that do not join a security group, but can retrieve authentication credentials of group members from the Group Manager, in order to verify counter signatures of group messages (see ).

Discovery Example #1 Consistently with the examples in and , the examples below consider a joining node that wants to join the security group associated with the application group "group1", but that does not know the name of the security group, the responsible GM and the group-membership resource to access.

Example in Link Format Request: Joining node -> RD Response: RD -> Joining node ;ct=65000; rt="core.osc.gm";if="ace.group";sec-gp="feedca570000"; app-gp="group1";cred_fmt="33";sign_enc_alg="10"; sign_alg="-8";sign_alg_crv="6";alg="10"; ecdh_alg="-27";ecdh_alg_crv="4" ]]> By performing the separate resource lookup below, the joining node can retrieve the link to the ACE Authorization Server associated with the GM, where to send an Authorization Request for joining the corresponding security group (see ). Request: Joining node -> RD Response: RD -> Joining node ;rel=authorization-server; anchor="coap://[2001:db8::ab]/ace-group/feedca570000" ]]> To retrieve the multicast IP address of the CoAP group used by the application group "group1", the joining node performs an endpoint lookup as shown below. The following assumes that the application group "group1" had been previously registered as per Appendix A of , with ff35:30:2001:db8::23 as multicast IP address of the associated CoAP group. Request: Joining node -> RD Response: RD -> Joining node ;ep="group1";et="core.rd-group"; base="coap://[ff35:30:2001:db8::23]";rt="core.rd-ep" ]]>

Example in CoRAL Request: Joining node -> RD Response: RD -> Joining node #using reef = #using iana = #base reef:rd-item { reef:ct 65000 reef:rt "core.osc.gm" reef:if "ace.group" sec-gp "feedca570000" app-gp "group1" cred_fmt 33 sign_enc_alg 10 sign_alg -8 sign_alg_crv 6 alg 10 ecdh_alg -27 ecdh_alg_crv 4 iana:authorization-server } ]]> To retrieve the multicast IP address of the CoAP group used by the application group "group1", the joining node performs an endpoint lookup as shown below. The following assumes that the application group "group1" had been previously registered, with ff35:30:2001:db8::23 as multicast IP address of the associated CoAP group. Request: Joining node -> RD Response: RD -> Joining node #using reef = reef:rd-unit <./rd/501> { reef:ep "group1" reef:et "core.rd-group" reef:base reef:rt "core.rd-ep" } ]]>

Discovery Example #2 Consistently with the examples in and , the examples below consider a joining node that wants to join the security group with name "feedca570000", but that does not know the responsible GM, the group-membership resource to access, and the associated application groups. The examples also show how the joining node uses CoAP observation , in order to be notified of possible changes to the parameters of the group-membership resource. This is also useful to handle the case where the security group of interest has not been created yet, so that the joining node can receive the requested information when it becomes available.

Example in Link Format Request: Joining node -> RD Response: RD -> Joining node ;ct=65000; rt="core.osc.gm";if="ace.group";sec-gp="feedca570000"; app-gp="group1";cred_fmt="33";sign_enc_alg="10"; sign_alg="-8";sign_alg_crv="6";alg="10"; ecdh_alg="-27";ecdh_alg_crv="4" ]]> Depending on the search criteria, the joining node performing the resource lookup can get large responses. This can happen, for instance, when the lookup request targets all the group-membership resources at a specified GM, or all the group-membership resources of all the registered GMs, as in the example below. Request: Joining node -> RD Response: RD -> Joining node ;ct=65000; rt="core.osc.gm";if="ace.group";sec-gp="feedca570000"; app-gp="group1";cred_fmt="33";sign_enc_alg="10"; sign_alg="-8";sign_alg_crv="6";alg="10";ecdh_alg="-27"; ecdh_alg_crv="4", ;ct=65000; rt="core.osc.gm";if="ace.group";sec-gp="ech0ech00000"; app-gp="group2";cred_fmt="33";sign_enc_alg="10"; sign_alg="-8";sign_alg_crv="6";alg="10";ecdh_alg="-27"; ecdh_alg_crv="4", ;ct=65000; rt="core.osc.gm";if="ace.group";sec-gp="abcdef120000"; app-gp="group3";app-gp="group4";cred_fmt="33"; sign_enc_alg="10";sign_alg="-8";sign_alg_crv="6";alg="10"; ecdh_alg="-27";ecdh_alg_crv="4" ]]> Therefore, it is RECOMMENDED that a joining node which performs a resource lookup with the CoAP Observe option specifies the value of the parameter 'sec-gp' in its GET request sent to the RD.

Example in CoRAL Request: Joining node -> RD Response: RD -> Joining node #using reef = #using iana = #base reef:rd-item { reef:ct 65000 reef:rt "core.osc.gm" reef:if "ace.group" sec-gp "feedca570000" app-gp "group1" cred_fmt 33 sign_enc_alg 10 sign_alg -8 sign_alg_crv 6 alg 10 ecdh_alg -27 ecdh_alg_crv 4 iana:authorization-server } ]]>

Use Case Example With Full Discovery In this section, the discovery of security groups is described to support the installation process of a lighting installation in an office building. The described process is a simplified version of one of many processes. The process described in this section is intended as an example and does not have any particular ambition to serve as recommendation or best practice to adopt. That is, it shows a possible workflow involving a Commissioning Tool (CT) used in a certain way, while it is not meant to prescribe how the workflow should necessarily be. Assume the existence of four luminaires that are members of two application groups. In the first application group, the four luminaires receive presence messages and light intensity messages from sensors or their proxy. In the second application group, the four luminaires and several other pieces of equipment receive building state schedules. Each of the two application groups is associated with a different security group and to a different CoAP group with its own dedicated multicast IP address. The Fairhair Alliance describes how a new device is accepted and commissioned in the network , by means of its certificate stored during the manufacturing process. When commissioning the new device in the installation network, the new device gets a new identity defined by a newly allocated certificate, following the BRSKI specification. describes how the CT assigns an endpoint name based on the CN field, (CN=ACME) and the serial number of the certificate (serial number = 123x, with 3 < x < 8). Corresponding ep-names ACME-1234, ACME-1235, ACME-1236 and ACME-1237 are also assumed. It is common practice that locations in the building are specified according to a coordinate system. After the acceptance of the luminaires into the installation network, the coordinate of each device is communicated to the CT. This can be done manually or automatically. The mapping between location and ep-name is calculated by the CT. For instance, on the basis of grouping criteria, the CT assigns: i) application group "grp_R2-4-015" to the four luminaires; and ii) application group "grp_schedule" to all schedule requiring devices. Also, the device with ep name ACME-123x has been assigned IP address: [2001:db8:4::x]. The RD is assigned IP address: [2001:db8:4:ff]. The used multicast addresses are: [ff05::5:1] and [ff05::5:2]. The following assumes that each device is pre-configured with the name of the two application groups it belongs to. Additional mechanisms can be defined in the RD, for supporting devices to discover the application groups they belong to. provides this same use case example in CoRAL. The CT defines the application group "grp_R2-4-015", with resource /light and base address [ff05::5:1], as follows. Request: CT -> RD ;rt="oic.d.light" ]]> Response: RD -> CT Also, the CT defines a second application group "grp_schedule", with resource /schedule and base address [ff05::5:2], as follows. Request: CT -> RD ;rt="oic.r.time.period" ]]> Response: RD -> CT Finally, the CT defines the corresponding security groups. In particular, assuming a Group Manager responsible for both security groups and with address [2001:db8::ab], the CT specifies: Request: CT -> RD ;ct=65000;rt="core.osc.gm";if="ace.group"; sec-gp="feedca570000"; app-gp="grp_R2-4-015", ;ct=65000;rt="core.osc.gm";if="ace.group"; sec-gp="feedsc590000"; app-gp="grp_schedule" ]]> Response: RD -> CT The device with IP address [2001:db8:4::x] can retrieve the multicast IP address of the CoAP group used by the application group "grp_R2-4-015", by performing an endpoint lookup as shown below. Request: Joining node -> RD Response: RD -> Joining node ;ep="grp_R2-4-015";et="core.rd-group"; base="coap://[ff05::5:1]";rt="core.rd-ep" ]]> Similarly, to retrieve the multicast IP address of the CoAP group used by the application group "grp_schedule", the device performs an endpoint lookup as shown below. Request: Joining node -> RD Response: RD -> Joining node ;ep="grp_schedule";et="core.rd-group"; base="coap://[ff05::5:2]";rt="core.rd-ep" ]]> Consequently, the device learns the security groups it has to join. In particular, it does the following for app-gp="grp_R2-4-015". Request: Joining node -> RD Response: RD -> Joining Node ;ct=65000; rt="core.osc.gm";if="ace.group";sec-gp="feedca570000"; app-gp="grp_R2-4-015" ]]> Similarly, the device does the following for app-gp="grp_schedule". Response: RD -> Joining Node ;ct=65000; rt="core.osc.gm";if="ace.group";sec-gp="feedsc590000"; app-gp="grp_schedule" ]]> After this last discovery step, the device can ask permission to join the security groups, and effectively join them through the Group Manager, e.g., according to .

Security Considerations The security considerations as described in apply here as well.

IANA Considerations This document has no actions for IANA.

References Normative References RISE AB Ericsson AB Ericsson AB Ericsson AB Universitaet Duisburg-Essen This document defines Group Object Security for Constrained RESTful Environments (Group OSCORE), providing end-to-end security of CoAP messages exchanged between members of a group, e.g., sent over IP multicast. In particular, the described approach defines how OSCORE is used in a group communication setting to provide source authentication for CoAP group requests, sent by a client to multiple servers, and for protection of the corresponding CoAP responses. Group OSCORE also defines a pairwise mode where each member of the group can efficiently derive a symmetric pairwise key with any other member of the group for pairwise OSCORE communication. ARM The Constrained RESTful Application Language (CoRAL) defines a data model and interaction model as well as a compact serialization formats for the description of typed connections between resources on the Web ("links"), possible operations on such resources ("forms"), and simple resource metadata. IoTconsultancy.nl InterDigital RISE AB This document specifies the use of the Constrained Application Protocol (CoAP) for group communication, including the use of UDP/IP multicast as the default underlying data transport. Both unsecured and secured CoAP group communication are specified. Security is achieved by use of the Group Object Security for Constrained RESTful Environments (Group OSCORE) protocol. The target application area of this specification is any group communication use cases that involve resource-constrained devices or networks that support CoAP. This document replaces RFC 7390, while it updates RFC 7252 and RFC 7641. In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. This specification defines Web Linking using a link format for use by constrained web servers to describe hosted resources, their attributes, and other relationships between links. Based on the HTTP Link Header field defined in RFC 5988, the Constrained RESTful Environments (CoRE) Link Format is carried as a payload and is assigned an Internet media type. "RESTful" refers to the Representational State Transfer (REST) architecture. A well-known URI is defined as a default entry point for requesting the links hosted by a server. [STANDARDS-TRACK] The Constrained Application Protocol (CoAP) is a specialized web transfer protocol for use with constrained nodes and constrained (e.g., low-power, lossy) networks. The nodes often have 8-bit microcontrollers with small amounts of ROM and RAM, while constrained networks such as IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs) often have high packet error rates and a typical throughput of 10s of kbit/s. The protocol is designed for machine- to-machine (M2M) applications such as smart energy and building automation. CoAP provides a request/response interaction model between application endpoints, supports built-in discovery of services and resources, and includes key concepts of the Web such as URIs and Internet media types. CoAP is designed to easily interface with HTTP for integration with the Web while meeting specialized requirements such as multicast support, very low overhead, and simplicity for constrained environments. RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. Concise Binary Object Representation (CBOR) is a data format designed for small code size and small message size. There is a need to be able to define basic security services for this data format. This document defines the CBOR Object Signing and Encryption (COSE) protocol. This specification describes how to create and process signatures, message authentication codes, and encryption using CBOR for serialization. This specification additionally describes how to represent cryptographic keys using CBOR. This document, along with RFC 9053, obsoletes RFC 8152. Concise Binary Object Representation (CBOR) is a data format designed for small code size and small message size. There is a need to be able to define basic security services for this data format. This document defines a set of algorithms that can be used with the CBOR Object Signing and Encryption (COSE) protocol (RFC 9052). This document, along with RFC 9052, obsoletes RFC 8152. In many Internet of Things (IoT) applications, direct discovery of resources is not practical due to sleeping nodes or networks where multicast traffic is inefficient. These problems can be solved by employing an entity called a Resource Directory (RD), which contains information about resources held on other servers, allowing lookups to be performed for those resources. The input to an RD is composed of links, and the output is composed of links constructed from the information stored in the RD. This document specifies the web interfaces that an RD supports for web servers to discover the RD and to register, maintain, look up, and remove information on resources. Furthermore, new target attributes useful in conjunction with an RD are defined. IANA IANA IANA IANA Informative References RISE AB Universitaet Duisburg-Essen Ericsson AB This document defines an application profile of the ACE framework for Authentication and Authorization, to request and provision keying material in group communication scenarios that are based on CoAP and are secured with Group Object Security for Constrained RESTful Environments (Group OSCORE). This application profile delegates the authentication and authorization of Clients, that join an OSCORE group through a Resource Server acting as Group Manager for that group. This application profile leverages protocol-specific transport profiles of ACE to achieve communication security, server authentication and proof-of-possession for a key owned by the Client and bound to an OAuth 2.0 Access Token. Ericsson AB RISE AB This document defines how to use the Authentication and Authorization for Constrained Environments (ACE) framework to distribute keying material and configuration parameters for secure group communication. Candidate group members acting as Clients and authorized to join a group can do so by interacting with a Key Distribution Center (KDC) acting as Resource Server, from which they obtain the keying material to communicate with other group members. While defining general message formats as well as the interface and operations available at the KDC, this document supports different approaches and protocols for secure group communication. Therefore, details are delegated to separate application profiles of this document, as specialized instances that target a particular group communication approach and define how communications in the group are protected. Compliance requirements for such application profiles are also specified. RISE AB RISE AB Consultant Ericsson AB Group communication for CoAP can be secured using Group Object Security for Constrained RESTful Environments (Group OSCORE). A Group Manager is responsible to handle the joining of new group members, as well as to manage and distribute the group keying material. This document defines a RESTful admin interface at the Group Manager, that allows an Administrator entity to create and delete OSCORE groups, as well as to retrieve and update their configuration. The ACE framework for Authentication and Authorization is used to enforce authentication and authorization of the Administrator at the Group Manager. Protocol-specific transport profiles of ACE are used to achieve communication security, proof-of- possession and server authentication. Ericsson This document explores how the Constrained RESTful Application Language (CoRAL) might be used for two use cases in Constrained RESTful Environments (CoRE): CoRE Resource Discovery, which allows a client to discover the resources of a server given a host name or IP address, and CoRE Resource Directory, which provides a directory of resources on many servers. Ericsson AB Ericsson AB RISE AB RISE AB Nexus Group This document specifies a CBOR encoding of X.509 certificates. The resulting certificates are called C509 Certificates. The CBOR encoding supports a large subset of RFC 5280 and all certificates compatible with the RFC 7925, IEEE 802.1AR (DevID), CNSA, RPKI, GSMA eUICC, and CA/Browser Forum Baseline Requirements profiles. When used to re-encode DER encoded X.509 certificates, the CBOR encoding can in many cases reduce the size of RFC 7925 profiled certificates with over 50%. The CBOR encoded structure can alternatively be signed directly ("natively signed"), which does not require re- encoding for the signature to be verified. The document also specifies C509 COSE headers, a C509 TLS certificate type, and a C509 file format. RISE AB Group communication with the Constrained Application Protocol (CoAP) can be secured end-to-end using Group Object Security for Constrained RESTful Environments (Group OSCORE), also across untrusted intermediary proxies. However, this sidesteps the proxies' abilities to cache responses from the origin server(s). This specification restores cacheability of protected responses at proxies, by introducing consensus requests which any client in a group can send to one server or multiple servers in the same group. The Internet Protocol Suite is increasingly used on small devices with severe constraints on power, memory, and processing resources, creating constrained-node networks. This document provides a number of basic terms that have been useful in the standardization work for constrained-node networks. The Constrained Application Protocol (CoAP) is a RESTful application protocol for constrained nodes and networks. The state of a resource on a CoAP server can change over time. This document specifies a simple protocol extension for CoAP that enables CoAP clients to "observe" resources, i.e., to retrieve a representation of a resource and keep this representation updated by the server over a period of time. The protocol follows a best-effort approach for sending new representations to clients and provides eventual consistency between the state observed by each client and the actual resource state at the server. A common design pattern in Internet of Things (IoT) deployments is the use of a constrained device that collects data via sensors or controls actuators for use in home automation, industrial control systems, smart cities, and other IoT deployments. This document defines a Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) 1.2 profile that offers communications security for this data exchange thereby preventing eavesdropping, tampering, and message forgery. The lack of communication security is a common vulnerability in IoT products that can easily be solved by using these well-researched and widely deployed Internet security protocols. The methods defined in RFC 7252 for the Constrained Application Protocol (CoAP) only allow access to a complete resource, not to parts of a resource. In case of resources with larger or complex data, or in situations where resource continuity is required, replacing or requesting the whole resource is undesirable. Several applications using CoAP need to access parts of the resources. This specification defines the new CoAP methods, FETCH, PATCH, and iPATCH, which are used to access and update parts of a resource. CBOR Web Token (CWT) is a compact means of representing claims to be transferred between two parties. The claims in a CWT are encoded in the Concise Binary Object Representation (CBOR), and CBOR Object Signing and Encryption (COSE) is used for added application-layer security protection. A claim is a piece of information asserted about a subject and is represented as a name/value pair consisting of a claim name and a claim value. CWT is derived from JSON Web Token (JWT) but uses CBOR rather than JSON. This document defines Object Security for Constrained RESTful Environments (OSCORE), a method for application-layer protection of the Constrained Application Protocol (CoAP), using CBOR Object Signing and Encryption (COSE). OSCORE provides end-to-end protection between endpoints communicating using CoAP or CoAP-mappable HTTP. OSCORE is designed for constrained nodes and networks supporting a range of proxy operations, including translation between different transport protocols. Although an optional functionality of CoAP, OSCORE alters CoAP options processing and IANA registration. Therefore, this document updates RFC 7252. This document specifies automated bootstrapping of an Autonomic Control Plane. To do this, a Secure Key Infrastructure is bootstrapped. This is done using manufacturer-installed X.509 certificates, in combination with a manufacturer's authorizing service, both online and offline. We call this process the Bootstrapping Remote Secure Key Infrastructure (BRSKI) protocol. Bootstrapping a new device can occur when using a routable address and a cloud service, only link-local connectivity, or limited/disconnected networks. Support for deployment models with less stringent security requirements is included. Bootstrapping is complete when the cryptographic identity of the new key infrastructure is successfully deployed to the device. The established secure connection can be used to deploy a locally issued certificate to the device as well. This specification defines a framework for authentication and authorization in Internet of Things (IoT) environments called ACE-OAuth. The framework is based on a set of building blocks including OAuth 2.0 and the Constrained Application Protocol (CoAP), thus transforming a well-known and widely used authorization solution into a form suitable for IoT devices. Existing specifications are used where possible, but extensions are added and profiles are defined to better serve the IoT use cases. FairHair Alliance

Use Case Example With Full Discovery (CoRAL) This section provides the same use case example of , but specified in CoRAL . The CT defines the application group "grp_R2-4-015", with resource /light and base address [ff05::5:1], as follows. Request: CT -> RD #base reef:ep "grp_R2-4-015" reef:et "core.rd-group" reef:rd-item { reef:rt "oic.d.light" } ]]> Response: RD -> CT Also, the CT defines a second application group "grp_schedule", with resource /schedule and base address [ff05::5:2], as follows. Request: CT -> RD #base reef:rd-item { reef:rt "oic.r.time.period" } ]]> Response: RD -> CT Finally, the CT defines the corresponding security groups. In particular, assuming a Group Manager responsible for both security groups and with address [2001:db8::ab], the CT specifies: Request: CT -> RD #using reef = #base reef:rd-item { reef:ct 65000 reef:ct 41 reef:rt "core.osc.gm" reef:if "ace.group" sec-gp "feedca570000" app-gp "grp_R2-4-015" } reef:rd-item { reef:ct 65000 reef:ct 41 reef:rt "core.osc.gm" reef:if "ace.group" sec-gp "feedsc590000" app-gp "grp_schedule" } ]]> Response: RD -> CT The device with IP address [2001:db8:4::x] can retrieve the multicast IP address of the CoAP group used by the application group "grp_R2-4-015", by performing an endpoint lookup as shown below. Request: Joining node -> RD Response: RD -> Joining node #base reef:rd-unit <501> { reef:ep "grp_R2-4-015" reef:et "core.rd-group" reef:base reef:rt "core.rd-ep" } ]]> Similarly, to retrieve the multicast IP address of the CoAP group used by the application group "grp_schedule", the device performs an endpoint lookup as shown below. Request: Joining node -> RD Response: RD -> Joining node #base reef:rd-unit <502> { reef:ep "grp_schedule" reef:et "core.rd-group" reef:base reef:rt "core.rd-ep" } ]]> Consequently, the device learns the security groups it has to join. In particular, it does the following for app-gp="grp_R2-4-015". Request: Joining node -> RD Response: RD -> Joining Node #using reef = #base reef:rd-item { reef:ct 65000 reef:rt "core.osc.gm" reef:if "ace.group" sec-gp "feedca570000" app-gp "grp_R2-4-015" } ]]> Similarly, the device does the following for app-gp="grp_schedule". Response: RD -> Joining Node #using reef = #base reef:rd-item { reef:ct 65000 reef:rt "core.osc.gm" reef:if "ace.group" sec-gp "feedsc590000" app-gp "grp_schedule" } ]]> After this last discovery step, the device can ask permission to join the security groups, and effectively join them through the Group Manager, e.g., according to .

Acknowledgments The authors sincerely thank Carsten Bormann, Klaus Hartke, Jaime Jimenez, Francesca Palombini, Dave Robin and Jim Schaad for their comments and feedback. The work on this document has been partly supported by VINNOVA and the Celtic-Next project CRITISEC; by the H2020 project SIFIS-Home (Grant agreement 952652); and by the EIT-Digital High Impact Initiative ACTIVE.