Greetings,

We are unable to verify this erratum that the submitter marked as editorial.  
Please note that we have changed the “Type” of the following errata 
report to “Technical”.  As Stream Approver, please review and set the 
Status and Type accordingly (see the definitions at 
https://www.rfc-editor.org/errata-definitions/).

You may review the report at: 
https://www.rfc-editor.org/errata/eid6909

Please see https://www.rfc-editor.org/how-to-verify/ for further 
information on how to verify errata reports.

Further information on errata can be found at: 
https://www.rfc-editor.org/errata.php.

Thank you.

RFC Editor/cs


> On Mar 31, 2022, at 6:48 AM, RFC Errata System <[email protected]> 
> wrote:
> 
> The following errata report has been submitted for RFC8152,
> "CBOR Object Signing and Encryption (COSE)".
> 
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid6909
> 
> --------------------------------------
> Type: Editorial
> Reported by: Thomas Fossati <[email protected]>
> 
> Section: 3.1
> 
> Original Text
> -------------
> Generic_Headers = (
>    ? 1 => int / tstr,  ; algorithm identifier
>    ? 2 => [+label],    ; criticality
>    ? 3 => tstr / int,  ; content type
>    ? 4 => bstr,        ; key identifier
>    ? 5 => bstr,        ; IV
>    ? 6 => bstr         ; Partial IV
> )
> 
> Corrected Text
> --------------
> Generic_Headers = (
>    ? 1 => int / tstr,  ; algorithm identifier
>    ? 2 => [+label],    ; criticality
>    ? 3 => tstr / int,  ; content type
>    ? 4 => bstr,        ; key identifier
>    ? ( 5 => bstr //    ; IV
>        6 => bstr )     ; Partial IV
> )
> 
> Notes
> -----
> Section 3.1 says: "The "Initialization Vector" and "Partial Initialization 
> Vector" header parameters MUST NOT both be present in the same security 
> layer."
> 
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party  
> can log in to change the status and edit the report, if necessary. 
> 
> --------------------------------------
> RFC8152 (draft-ietf-cose-msg-24)
> --------------------------------------
> Title               : CBOR Object Signing and Encryption (COSE)
> Publication Date    : July 2017
> Author(s)           : J. Schaad
> Category            : PROPOSED STANDARD
> Source              : CBOR Object Signing and Encryption
> Area                : Security
> Stream              : IETF
> Verifying Party     : IESG
> 

_______________________________________________
COSE mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/cose

Reply via email to