Opened 7 years ago
Closed 6 years ago
#97 closed defect (fixed)
Allocate an OID for CMS precertificates
Reported by: | rob.stradling@… | Owned by: | rob.stradling@… |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | rfc6962-bis | Version: | |
Severity: | - | Keywords: | |
Cc: |
Description
Section 3.1 currently says:
'A precertificate is a CMS [RFC5652] "signed-data" object that contains
a TBSCertificate [RFC5280] in its
"SignedData?.encapContentInfo.eContent" field, identified by the OID
<TBD> in the "SignedData?.encapContentInfo.eContentType" field.'
Ben, please allocate an OID under the Google arc (1.3.6.1.4.1.11129).
.2.4.8 seems to me to be the obvious candidate.
Thanks.
Change History (2)
comment:1 Changed 6 years ago by rob.stradling@…
- Owner changed from benl@… to rob.stradling@…
comment:2 Changed 6 years ago by melinda.shore@…
- Resolution set to fixed
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
Cancel that request.
Symantec have agreed to donate some OIDs under the thawte 1.3.101 OID arc. Let's use one of them here.