Re: [Technical Errata Reported] RFC6277 (5892)
Russ Housley <[email protected]>
| Newsgroups | gmane.ietf.x509 |
|---|---|
| Message-ID | <[email protected]> |
Ben: > > On Fri, Nov 01, 2019 at 06:26:13PM -0700, RFC Errata System wrote: >> The following errata report has been submitted for RFC6277, >> "Online Certificate Status Protocol Algorithm Agility". >> >> -------------------------------------- >> You may review the report below and at: >> https://www.rfc-editor.org/errata/eid5892 >> >> -------------------------------------- >> Type: Technical >> Reported by: Russ Housley <[email protected]> >> >> Section: Appendix A.1 >> >> Original Text >> ------------- >> PreferredSignatureAlgorithm ::= SEQUENCE { >> sigIdentifier AlgorithmIdentifier{SIGNATURE-ALGORITHM, {...}}, >> pubKeyAlgIdentifier SMIMECapability{PUBLIC-KEY, {...}} OPTIONAL } >> >> >> Corrected Text >> -------------- >> PreferredSignatureAlgorithm ::= SEQUENCE { >> sigIdentifier AlgorithmIdentifier{SIGNATURE-ALGORITHM, {...}}, >> pubKeyAlgIdentifier AlgorithmIdentifier{PUBLIC-KEY, {...}} OPTIONAL} > > Is this going to encode in the same way as the 1988-syntax version (from > Appendix A.2): > > PreferredSignatureAlgorithm ::= SEQUENCE { > sigIdentifier AlgorithmIdentifier, > pubKeyAlgIdentifier SMIMECapability OPTIONAL > } Yes, this will produce the same "bits on the wire". Russ _______________________________________________ pkix mailing list [email protected] https://www.ietf.org/mailman/listinfo/pkix