The following errata report has been verified for RFC3125,
"Electronic Signature Policies".
--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid5901
--------------------------------------
Status: Verified
Type: Technical
Reported by: Russ Housley <housley(_at_)vigilsec(_dot_)com>
Date Reported: 2019-11-12
Verified by: Roman Danyliw (IESG)
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.
--------------------------------------
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(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/smime