| pr paths node_dis_index pr_dis para commentary commit_s commit_e draft para_hash block_hash url AB paragraph |
| 7 {} {} {} |
| make up the Internet of Things (IoT). One of the standards that has |
| come out of this process is ""Concise Binary Object Representation |
| (CBOR)"" I-D.ietf-cbor-7049bis. CBOR extended the data model of the |
| JavaScript Object Notation (JSON) STD90 by allowing for binary data, |
| among other changes. CBOR has been adopted by several of the IETF |
| working groups dealing with the IoT world as their encoding of data |
| structures. CBOR was designed specifically both to be small in terms |
| of messages transported and implementation size and to be a schema- |
| free decoder. A need exists to provide message security services for |
| IoT, and using CBOR as the message-encoding format makes sense." These all looks like straightforward and necessary changes . a5e38d950e35310736731d31591298acef6e7593 a5e38d950e35310736731d31591298acef6e7593 draft-ietf-cose-countersign 62a35d89fd81e0989feead6e913c2d6571dc41bf46bc661bfc41a07d201400bf ['62a35d89fd81e0989feead6e913c2d6571dc41bf46bc661bfc41a07d201400bf', '21da057efabcf67ae32fe40be6a1b6c04441024cd76e35eecdcbd53b80b04610'] A "there has been an increased focus on small, constrained devices that |
| make up the internet of things (iot). one of the standards that has |
| come out of this process is ""concise binary object representation |
| (cbor)"" i-d.ietf-cbor-7049bis. cbor extended the data model of the |
| javascript object notation (json) std90 by allowing for binary data, |
| among other changes. cbor has been adopted by several of the ietf |
| working groups dealing with the iot world as their encoding of data |
| structures. cbor was designed specifically both to be small in terms |
| of messages transported and implementation size and to be a schema- |
| free decoder. a need exists to provide message security services for |
| iot, and using cbor as the message-encoding format makes sense. |
| 7 {} {} {} |
| make up the Internet of Things (IoT). One of the standards that has |
| come out of this process is ""Concise Binary Object Representation |
| (CBOR)"" RFC8949. CBOR extended the data model of the JavaScript |
| Object Notation (JSON) STD90 by allowing for binary data, among other |
| changes. CBOR has been adopted by several of the IETF working groups |
| dealing with the IoT world as their encoding of data structures. |
| CBOR was designed specifically both to be small in terms of messages |
| transported and implementation size and to be a schema-free decoder. |
| A need exists to provide message security services for IoT, and using |
| CBOR as the message-encoding format makes sense." These all looks like straightforward and necessary changes . a5e38d950e35310736731d31591298acef6e7593 a5e38d950e35310736731d31591298acef6e7593 draft-ietf-cose-countersign 21da057efabcf67ae32fe40be6a1b6c04441024cd76e35eecdcbd53b80b04610 ['62a35d89fd81e0989feead6e913c2d6571dc41bf46bc661bfc41a07d201400bf', '21da057efabcf67ae32fe40be6a1b6c04441024cd76e35eecdcbd53b80b04610'] B "there has been an increased focus on small, constrained devices that |
| make up the internet of things (iot). one of the standards that has |
| come out of this process is ""concise binary object representation |
| (cbor)"" rfc8949. cbor extended the data model of the javascript |
| object notation (json) std90 by allowing for binary data, among other |
| changes. cbor has been adopted by several of the ietf working groups |
| dealing with the iot world as their encoding of data structures. |
| cbor was designed specifically both to be small in terms of messages |
| transported and implementation size and to be a schema-free decoder. |
| a need exists to provide message security services for iot, and using |
| cbor as the message-encoding format makes sense. |
| 7 {} {} {} in I-D.ietf-core-groupcomm-bis. These all looks like straightforward and necessary changes . a5e38d950e35310736731d31591298acef6e7593 a5e38d950e35310736731d31591298acef6e7593 draft-ietf-cose-countersign 3aa87ba28574afabe40122ab42adda1b8f42c68d59ba6f412cde019388bb99dd ['3aa87ba28574afabe40122ab42adda1b8f42c68d59ba6f412cde019388bb99dd', 'ca7cfb498edc537de6268a3c70794231c33443a5595e4697e4953d24267edb0d'] A in i-d.ietf-core-groupcomm-bis. |
| 7 {} {} {} in I-D.ietf-core-oscore-groupcomm. These all looks like straightforward and necessary changes . a5e38d950e35310736731d31591298acef6e7593 a5e38d950e35310736731d31591298acef6e7593 draft-ietf-cose-countersign ca7cfb498edc537de6268a3c70794231c33443a5595e4697e4953d24267edb0d ['3aa87ba28574afabe40122ab42adda1b8f42c68d59ba6f412cde019388bb99dd', 'ca7cfb498edc537de6268a3c70794231c33443a5595e4697e4953d24267edb0d'] B in i-d.ietf-core-oscore-groupcomm. |
| 7 {} {} {} "In order to always regenerate the same byte string for the " |
| signed"" value, the deterministic encoding rules defined in I-D.ietf- |
| cbor-7049bis. These rules match the ones laid out in I-D.ietf-cose- |
| rfc8152bis-struct." These all looks like straightforward and necessary changes . a5e38d950e35310736731d31591298acef6e7593 a5e38d950e35310736731d31591298acef6e7593 draft-ietf-cose-countersign ad27de44a8e20d7f090f4cad629c15f37a4d3c9fa969777782a7f55f8e265806 ['ad27de44a8e20d7f090f4cad629c15f37a4d3c9fa969777782a7f55f8e265806', '1cd4cce56ccb42bf1ac9857d8457c0baab6727d0a26b7b27a94365ed0ae4d3aa'] A "in order to always regenerate the same byte string for the ""to be |
| signed"" value, the deterministic encoding rules defined in i-d.ietf- |
| cbor-7049bis. these rules match the ones laid out in i-d.ietf-cose- |
| rfc8152bis-struct. |
| 7 {} {} {} "In order to always regenerate the same byte string for the " |
| signed"" value, the deterministic encoding rules defined in RFC8949. |
| These rules match the ones laid out in I-D.ietf-cose-rfc8152bis- |
| struct." These all looks like straightforward and necessary changes . a5e38d950e35310736731d31591298acef6e7593 a5e38d950e35310736731d31591298acef6e7593 draft-ietf-cose-countersign 1cd4cce56ccb42bf1ac9857d8457c0baab6727d0a26b7b27a94365ed0ae4d3aa ['ad27de44a8e20d7f090f4cad629c15f37a4d3c9fa969777782a7f55f8e265806', '1cd4cce56ccb42bf1ac9857d8457c0baab6727d0a26b7b27a94365ed0ae4d3aa'] B "in order to always regenerate the same byte string for the ""to be |
| signed"" value, the deterministic encoding rules defined in rfc8949. |
| these rules match the ones laid out in i-d.ietf-cose-rfc8152bis- |
| struct. |
| 6 {} {} {} |
| parties share the key, data origin authentication is not provided. |
| Any party that knows the message-authentication key can compute a |
| valid authentication tag; therefore, the contents could originate |
| from any one of the parties that share the key." < tWhen either COSEEncrypt and COSEMac is used and more than two parties share the key , data origin authentication is not provided . Any party that knows the message - authentication key can compute a valid authentication tag ; therefore , the contents could originate from any one of the parties that share the key.</t < tCountersignatures of COSEEncrypt and COSEMac with short authentication tags do not provide the security properties associated with the same algorithm used in COSESign . To provide 128 - bit security against collision attacks , the tag length MUST be at least 256 - bits . A countersignature of a COSEMac with AES - MAC 256/128 provides at most 64 bits of integrity protection . Similarly , a countersignature of a COSE_Encrypt with AES - CCM-16 - 64 - 128 provides at most 32 bits bits of integrity protection.</t 16f600b4f061f469801a808c9b4b79021328b031 16f600b4f061f469801a808c9b4b79021328b031 draft-ietf-cose-countersign aabcf2641b2d6238e8b9eb83a94f72cb39a9d4fad7feecf408d47b126b1674f3 ['aabcf2641b2d6238e8b9eb83a94f72cb39a9d4fad7feecf408d47b126b1674f3', 'e545e886e1ad54dfff42c3e2ae036d9324dadc06cf138cef2230c5abc6844aff'] B "when either cose_encrypt and cose_mac is used and more than two |
| parties share the key, data origin authentication is not provided. |
| any party that knows the message-authentication key can compute a |
| valid authentication tag; therefore, the contents could originate |
| from any one of the parties that share the key. |
| 6 {} {} {} |
| authentication tags do not provide the security properties associated |
| with the same algorithm used in COSE_Sign. To provide 128-bit |
| security against collision attacks, the tag length MUST be at least |
| 256-bits. A countersignature of a COSE_Mac with AES-MAC 256/128 |
| provides at most 64 bits of integrity protection. Similarly, a |
| countersignature of a COSE_Encrypt with AES-CCM-16-64-128 provides at |
| most 32 bits bits of integrity protection." < tWhen either COSEEncrypt and COSEMac is used and more than two parties share the key , data origin authentication is not provided . Any party that knows the message - authentication key can compute a valid authentication tag ; therefore , the contents could originate from any one of the parties that share the key.</t < tCountersignatures of COSEEncrypt and COSEMac with short authentication tags do not provide the security properties associated with the same algorithm used in COSESign . To provide 128 - bit security against collision attacks , the tag length MUST be at least 256 - bits . A countersignature of a COSEMac with AES - MAC 256/128 provides at most 64 bits of integrity protection . Similarly , a countersignature of a COSE_Encrypt with AES - CCM-16 - 64 - 128 provides at most 32 bits bits of integrity protection.</t 16f600b4f061f469801a808c9b4b79021328b031 16f600b4f061f469801a808c9b4b79021328b031 draft-ietf-cose-countersign e545e886e1ad54dfff42c3e2ae036d9324dadc06cf138cef2230c5abc6844aff ['aabcf2641b2d6238e8b9eb83a94f72cb39a9d4fad7feecf408d47b126b1674f3', 'e545e886e1ad54dfff42c3e2ae036d9324dadc06cf138cef2230c5abc6844aff'] B "countersignatures of cose_encrypt and cose_mac with short |
| authentication tags do not provide the security properties associated |
| with the same algorithm used in cose_sign. to provide 128-bit |
| security against collision attacks, the tag length must be at least |
| 256-bits. a countersignature of a cose_mac with aes-mac 256/128 |
| provides at most 64 bits of integrity protection. similarly, a |
| countersignature of a cose_encrypt with aes-ccm-16-64-128 provides at |
| most 32 bits bits of integrity protection. |
| 2 {} {} {} |
| Appendix_B_1_3. An example of a countersignature in an encryption |
| object can be found in Appendix_B_3_3." "Remove the sections from the Examples Applenix that were blank , clean up the Security Considerations , and narrow the table in the IANA considerations . |
| Looks good to me ! Thanks ! Let us know if you want us to merge it or you plan to do that yourself ." ebe510e4808b2623576577844f6dce45a96e1c2c ebe510e4808b2623576577844f6dce45a96e1c2c draft-ietf-cose-countersign e49f554dc74b2192077e16a2405e095febd9d83e7e1a11b18468fc8c3fb0362e ['e49f554dc74b2192077e16a2405e095febd9d83e7e1a11b18468fc8c3fb0362e', 'fd7685778abd6a32a5e8f2c5ce990acbae40a06982a75278ab3aec0c2ebee4fc'] A "an example of a countersignature on a signature can be found in |
| appendix_b_1_3. an example of a countersignature in an encryption |
| object can be found in appendix_b_3_3. |
| 2 {} {} {} |
| Appendix_A_1_1. An example of a countersignature in an encryption |
| object can be found in Appendix_A_2_1." "Remove the sections from the Examples Applenix that were blank , clean up the Security Considerations , and narrow the table in the IANA considerations . |
| Looks good to me ! Thanks ! Let us know if you want us to merge it or you plan to do that yourself ." ebe510e4808b2623576577844f6dce45a96e1c2c ebe510e4808b2623576577844f6dce45a96e1c2c draft-ietf-cose-countersign fd7685778abd6a32a5e8f2c5ce990acbae40a06982a75278ab3aec0c2ebee4fc ['e49f554dc74b2192077e16a2405e095febd9d83e7e1a11b18468fc8c3fb0362e', 'fd7685778abd6a32a5e8f2c5ce990acbae40a06982a75278ab3aec0c2ebee4fc'] B "an example of a countersignature on a signature can be found in |
| appendix_a_1_1. an example of a countersignature in an encryption |
| object can be found in appendix_a_2_1. |
| 2 {} {} {} |
| registry." "Remove the sections from the Examples Applenix that were blank , clean up the Security Considerations , and narrow the table in the IANA considerations . |
| Looks good to me ! Thanks ! Let us know if you want us to merge it or you plan to do that yourself ." ebe510e4808b2623576577844f6dce45a96e1c2c ebe510e4808b2623576577844f6dce45a96e1c2c draft-ietf-cose-countersign 659510bb7ad5a3f7155e6afe2ab25efea78030f51e6303daf9573bba9b10e7e2 ['659510bb7ad5a3f7155e6afe2ab25efea78030f51e6303daf9573bba9b10e7e2', 'dc996f5288d257a9d1840d15fe602855e13ce42383b10458d8a0ee558e492242'] A "iana is requested to register the following new items in the |
| registry. |
| 2 {} {} {} |
| registry. For these entries, the Value Registry column will be blank |
| and the Reference column will be ." "Remove the sections from the Examples Applenix that were blank , clean up the Security Considerations , and narrow the table in the IANA considerations . |
| Looks good to me ! Thanks ! Let us know if you want us to merge it or you plan to do that yourself ." ebe510e4808b2623576577844f6dce45a96e1c2c ebe510e4808b2623576577844f6dce45a96e1c2c draft-ietf-cose-countersign dc996f5288d257a9d1840d15fe602855e13ce42383b10458d8a0ee558e492242 ['659510bb7ad5a3f7155e6afe2ab25efea78030f51e6303daf9573bba9b10e7e2', 'dc996f5288d257a9d1840d15fe602855e13ce42383b10458d8a0ee558e492242'] B "iana is requested to register the following new items in the |
| registry. for these entries, the value registry column will be blank |
| and the reference column will be . |
| 2 {} {} {} TODO - review and trim as needed. |
| Looks good to me ! Thanks ! Let us know if you want us to merge it or you plan to do that yourself . |
| 2 {} {} {} |
| multiple algorithms has been demonstrated in some cases to leak |
| information about that key, provide the opportunity for attackers to |
| forge integrity tags, or gain information about encrypted content. |
| Binding a key to a single algorithm prevents these problems. Key |
| creators and key consumers are strongly encouraged not only to create |
| new keys for each different algorithm, but to include that selection |
| of algorithm in any distribution of key material and strictly enforce |
| the matching of algorithms in the key structure to algorithms in the |
| message structure. In addition to checking that algorithms are |
| correct, the key form needs to be checked as well. Do not use an |
| 'EC2' key where an 'OKP' key is expected." "Remove the sections from the Examples Applenix that were blank , clean up the Security Considerations , and narrow the table in the IANA considerations . |
| Looks good to me ! Thanks ! Let us know if you want us to merge it or you plan to do that yourself ." ebe510e4808b2623576577844f6dce45a96e1c2c ebe510e4808b2623576577844f6dce45a96e1c2c draft-ietf-cose-countersign 791550beeccf2e4842ae935dd72caae3f241e62feda660dd6213960f4fcb4f86 ['791550beeccf2e4842ae935dd72caae3f241e62feda660dd6213960f4fcb4f86', 'a1d37d6e03c5a4432371997da3297cfa9c595d60ea9166ca5ac33d36265d91b8', 'bb5ea9de609c567b83b0c1d6d26d72609c909b76f1401c53c4d630cb221fa36a'] A "although it has been mentioned before, the use of a single key for |
| multiple algorithms has been demonstrated in some cases to leak |
| information about that key, provide the opportunity for attackers to |
| forge integrity tags, or gain information about encrypted content. |
| binding a key to a single algorithm prevents these problems. key |
| creators and key consumers are strongly encouraged not only to create |
| new keys for each different algorithm, but to include that selection |
| of algorithm in any distribution of key material and strictly enforce |
| the matching of algorithms in the key structure to algorithms in the |
| message structure. in addition to checking that algorithms are |
| correct, the key form needs to be checked as well. do not use an |
| 'ec2' key where an 'okp' key is expected. |
| 2 {} {} {} |
| multiple algorithms has been demonstrated in some cases to leak |
| information about that key, provide the opportunity for attackers to |
| forge integrity tags, or gain information about encrypted content. |
| Binding a key to a single algorithm prevents these problems." "Remove the sections from the Examples Applenix that were blank , clean up the Security Considerations , and narrow the table in the IANA considerations . |
| Looks good to me ! Thanks ! Let us know if you want us to merge it or you plan to do that yourself ." ebe510e4808b2623576577844f6dce45a96e1c2c ebe510e4808b2623576577844f6dce45a96e1c2c draft-ietf-cose-countersign a1d37d6e03c5a4432371997da3297cfa9c595d60ea9166ca5ac33d36265d91b8 ['791550beeccf2e4842ae935dd72caae3f241e62feda660dd6213960f4fcb4f86', 'a1d37d6e03c5a4432371997da3297cfa9c595d60ea9166ca5ac33d36265d91b8', 'bb5ea9de609c567b83b0c1d6d26d72609c909b76f1401c53c4d630cb221fa36a'] B "although it has been mentioned before, the use of a single key for |
| multiple algorithms has been demonstrated in some cases to leak |
| information about that key, provide the opportunity for attackers to |
| forge integrity tags, or gain information about encrypted content. |
| binding a key to a single algorithm prevents these problems. |
| 2 {} {} {} |
| create new keys for each different algorithm, but to include that |
| selection of algorithm in any distribution of key material and |
| strictly enforce the matching of algorithms in the key structure to |
| algorithms in the message structure. In addition to checking that |
| algorithms are correct, the key form needs to be checked as well. Do |
| not use an 'EC2' key where an 'OKP' key is expected." "Remove the sections from the Examples Applenix that were blank , clean up the Security Considerations , and narrow the table in the IANA considerations . |
| Looks good to me ! Thanks ! Let us know if you want us to merge it or you plan to do that yourself ." ebe510e4808b2623576577844f6dce45a96e1c2c ebe510e4808b2623576577844f6dce45a96e1c2c draft-ietf-cose-countersign bb5ea9de609c567b83b0c1d6d26d72609c909b76f1401c53c4d630cb221fa36a ['791550beeccf2e4842ae935dd72caae3f241e62feda660dd6213960f4fcb4f86', 'a1d37d6e03c5a4432371997da3297cfa9c595d60ea9166ca5ac33d36265d91b8', 'bb5ea9de609c567b83b0c1d6d26d72609c909b76f1401c53c4d630cb221fa36a'] B "key creators and key consumers are strongly encouraged not only to |
| create new keys for each different algorithm, but to include that |
| selection of algorithm in any distribution of key material and |
| strictly enforce the matching of algorithms in the key structure to |
| algorithms in the message structure. in addition to checking that |
| algorithms are correct, the key form needs to be checked as well. do |
| not use an 'ec2' key where an 'okp' key is expected. |
| 1 {} {} {} |
| changes should be submitted as pull requests at <https://github.com/ |
| cose-wg/cose-rfc8152bis>. Instructions are on that page as well. |
| Editorial changes can be managed in GitHub, but any substantial |
| issues need to be discussed on the COSE mailing list." Add as a document editor . No changes to the body of the document . a83d32177b26acac684baf31a778028ae7a17f7d a83d32177b26acac684baf31a778028ae7a17f7d draft-ietf-cose-countersign d3c78c0a06c87b2297c5abb82682d359b2531db9058769f823910e1d3fe7d89b ['d3c78c0a06c87b2297c5abb82682d359b2531db9058769f823910e1d3fe7d89b', '39ddc5a898293c847d846b49c92ee84da69300d298a0f7d31919d66ac8f715c0'] A "the source for this draft is being maintained in github. suggested |
| changes should be submitted as pull requests at <https://github.com/ |
| cose-wg/cose-rfc8152bis>. instructions are on that page as well. |
| editorial changes can be managed in github, but any substantial |
| issues need to be discussed on the cose mailing list. |
| 1 {} {} {} |
| changes should be submitted as pull requests at <https://github.com/ |
| cose-wg/countersign>. Instructions are on that page as well. |
| Editorial changes can be managed in GitHub, but any substantial |
| issues need to be discussed on the COSE mailing list." Add as a document editor . No changes to the body of the document . a83d32177b26acac684baf31a778028ae7a17f7d a83d32177b26acac684baf31a778028ae7a17f7d draft-ietf-cose-countersign 39ddc5a898293c847d846b49c92ee84da69300d298a0f7d31919d66ac8f715c0 ['d3c78c0a06c87b2297c5abb82682d359b2531db9058769f823910e1d3fe7d89b', '39ddc5a898293c847d846b49c92ee84da69300d298a0f7d31919d66ac8f715c0'] B "the source for this draft is being maintained in github. suggested |
| changes should be submitted as pull requests at <https://github.com/ |
| cose-wg/countersign>. instructions are on that page as well. |
| editorial changes can be managed in github, but any substantial |
| issues need to be discussed on the cose mailing list. |
|
|
