Hi,

Speaking to Warren offline, he suggests (as an author) that this errata should 
be verified.

Please let me know this week if anyone feels differently, otherwise I'll verify 
this at the end of the week.

Thanks,
Rob


> -----Original Message-----
> From: RFC Errata System <[email protected]>
> Sent: 05 October 2020 20:21
> To: [email protected]; [email protected]; [email protected]; Rob Wilton
> (rwilton) <[email protected]>; [email protected]; Joe Clarke
> (jclarke) <[email protected]>; [email protected]
> Cc: [email protected]; [email protected]; [email protected]
> Subject: [Technical Errata Reported] RFC8886 (6298)
> 
> The following errata report has been submitted for RFC8886,
> "Secure Device Install".
> 
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid6298
> 
> --------------------------------------
> Type: Technical
> Reported by: Stéphane Bortzmeyer <[email protected]>
> 
> Section: A.1.1
> 
> Original Text
> -------------
> openssl ecparam -out privatekey.key -name prime256v1 -genkey
> 
> Corrected Text
> --------------
> openssl ecparam -out key.pem -name prime256v1 -genkey
> 
> Notes
> -----
> The rest of the appendix expects the name key.pem.
> 
> 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.
> 
> --------------------------------------
> RFC8886 (draft-ietf-opsawg-sdi-13)
> --------------------------------------
> Title               : Secure Device Install
> Publication Date    : September 2020
> Author(s)           : W. Kumari, C. Doyle
> Category            : INFORMATIONAL
> Source              : Operations and Management Area Working Group
> Area                : Operations and Management
> Stream              : IETF
> Verifying Party     : IESG
_______________________________________________
OPSAWG mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/opsawg

Reply via email to