Draft: draft-ietf-cose-rfc8152bis-algs

Commentary: Add in response for IANA review on all documents SecDir review by  on -algs GenArt review on -struct
Additional columns may be present in the table depending on the
algorithms.
A GitHub project has been created at <https://github.com/cose-wg/
Examples> that contains a set of testing examples as well.  Each
example is found in a JSON file that contains the inputs used to
create the example, some of the intermediate values that can be used
in debugging the example and the output of the example presented in
both a hex and a CBOR diagnostic notation format.  Some of the
examples at the site are designed failure testing cases; these are
clearly marked as such in the JSON file.  If errors in the examples
in this document are found, the examples on GitHub will be updated,
and a note to that effect will be placed in the JSON file.
A GitHub project has been created at <https://github.com/cose-wg/
Examples> that contains a set of testing examples as well.  Each
example is found in a JSON file that contains the inputs used to
create the example, some of the intermediate values that can be used
for debugging, and the output of the example.  The results are
encoded using both hexadecimal and CBOR diagnostic notation format.
Some of the examples are designed to test failure case; these are
clearly marked as such in the JSON file.  If errors in the examples
in this document are found, the examples on GitHub will be updated,
and a note to that effect will be placed in the JSON file.
Some recipient algorithms carry the key while others derive a key
from secret data.  For those algorithms that carry the key (such as
AES Key Wrap), the size of the HMAC key SHOULD be the same size as
the underlying hash function.  For those algorithms that derive the
key (such as ECDH), the derived key MUST be the same size as the
underlying hash function.
Some recipient algorithms transport the key, while others derive a
key from secret data.  For those algorithms that transport the key
(such as AES Key Wrap), the size of the HMAC key SHOULD be the same
size as the underlying hash function.  For those algorithms that
derive the key (such as ECDH), the derived key MUST be the same size
as the underlying hash function.
The capabilities column for this registration is to be empty.
IANA is requested to update the references in the table from RFC8152
to .
COSE was initially designed as part of a solution to provide security
to Constrained RESTful Environments (CoRE), and this is done using
RFC8613 and I-D.ietf-core-groupcomm-bis.  However, COSE is not
restricted to just these cases and can be used in any place where one
would consider either JOSE or CMS RFC5652 for the purpose of
providing security services.  The use of COSE, like JOSE and CMS, is
only in store and forward or offline protocols, different solutions
would be appropriate for online protocols although one can use COSE
in and online protocol after having done some type of online key
establishment process.  Any application which uses COSE for security
services first needs to determine what security services are required
and then select the appropriate COSE structures and cryptographic
algorithms based on those needs.  app-considerations provides
additional information on what applications need to specify when
using COSE.
COSE was initially designed as part of a solution to provide security
to Constrained RESTful Environments (CoRE), and this is done using
RFC8613 and I-D.ietf-core-groupcomm-bis.  However, COSE is not
restricted to just these cases and can be used in any place where one
would consider either JOSE or CMS RFC5652 for the purpose of
providing security services.  The use of COSE, like JOSE and CMS, is
only in store and forward or offline protocols, different solutions
would be appropriate for online protocols although one can use COSE
in an online protocol after having done some type of online key
establishment process.  Any application which uses COSE for security
services first needs to determine what security services are required
and then select the appropriate COSE structures and cryptographic
algorithms based on those needs.  app-considerations provides
additional information on what applications need to specify when
using COSE.