Re: [smime] [Technical Errata Reported] RFC3125 (5901)

Option B is to import CommitmentTypeIdentifier from FROM PKIXTSP, but these seems like the easier approach.

I reviewed this and believe this errata is correct and should be approved. 

spt

> On Nov 13, 2019, at 00:05, RFC Errata System <rfc-editor@rfc-editor.org> wrote:
> 
> The following errata report has been submitted for RFC3125,
> "Electronic Signature Policies".
> 
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid5901
> 
> --------------------------------------
> Type: Technical
> Reported by: Russ Housley <housley@vigilsec.com>
> 
> Section: Appendix A.1
> 
> Original Text
> -------------
> CommitmentType ::= SEQUENCE {
>        identifier                      CommitmentTypeIdentifier,
>        fieldOfApplication      [0] FieldOfApplication OPTIONAL,
>        semantics                       [1] DirectoryString OPTIONAL }
> 
> Corrected Text
> --------------
> CommitmentType ::= SEQUENCE {
>        identifier                      CommitmentTypeIdentifier,
>        fieldOfApplication      [0] FieldOfApplication OPTIONAL,
>        semantics                       [1] DirectoryString OPTIONAL }
> 
> CommitmentTypeIdentifier ::= OBJECT IDENTIFIER
> 
> Notes
> -----
> The definition of CommitmentTypeIdentifier is missing from the ASN.1 module.  RFC 3126 shows that it is an object identifier.
> 
> 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. 
> 
> --------------------------------------
> RFC3125 (draft-ietf-smime-espolicies-00)
> --------------------------------------
> Title               : Electronic Signature Policies
> Publication Date    : September 2001
> Author(s)           : J. Ross, D. Pinkas, N. Pope
> Category            : EXPERIMENTAL
> Source              : S/MIME Mail Security
> Area                : Security
> Stream              : IETF
> Verifying Party     : IESG
> 
> _______________________________________________
> smime mailing list
> smime@ietf.org
> https://www.ietf.org/mailman/listinfo/smime