Change:
Add in response for IANA review on all documents SecDir review by Nancy on -algs GenArt review on -struct

Discussion:
The term 'byte string' is used for sequences of bytes, while the term 'text string' is used for sequences of characters. <ins> The tables for algorithms contain the following columns: Additional columns may be present in the table depending on the algorithms. </ins> 1.4. At the time that RFC8152 was initially published, the CBOR Data

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 <del> 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 </del> <ins> 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 </ins> 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.

The algorithms defined in this document can be found in x-table-hmac. <del> 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. </del> <ins> 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. </ins> When using a COSE key for this algorithm, the following checks are made:

IANA is rquested to add a new row to the "COSE Algorithms" registry. <ins> The capabilities column for this registration is to be empty. </ins> 10.3. IANA is requested to modify the description to "Public Key" for the line with "Key Type" of 2 and the "Name" of "x".  See x-table- ec1-keys which has been modified with this change. <ins> IANA is requested to update the references in the table from RFC8152 to [[This Document]]. </ins> 11. There are a number of security considerations that need to be taken

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 <del> in and online protocol after having done some type of online key </del> <ins> in an online protocol after having done some type of online key </ins> 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