[cabfpub] OIDs for DV and OV

Robin Alden robin at comodo.com
Mon Oct 6 14:36:12 UTC 2014

Hi Dean,

                Comodo already use the DV and OV policy OIDs defined at

We have no objection to other CAs following suit.


I am of the opinion that if a CA has policy OIDs which identify which of
the two defined options in the BRs you followed for subject information
then it would be better that we all use the same OIDs.


Ryan's objection is religious, not technical.







From: public-bounces at cabforum.org [mailto:public-bounces at cabforum.org]
On Behalf Of Dean Coclin
Sent: 02 October 2014 18:34
To: public at cabforum.org
Subject: [cabfpub] OIDs for DV and OV


Further to today's discussion on our call, I'd like to get more feedback
on a proposal to make a unique standardized OID mandatory for DV and OV
certificates in the Baseline Requirements. Currently we have a mandatory
OID for EV certificates but optional for OV and DV.  This makes things
difficult for at least two groups of constituents:


1.       Relying parties that would like to distinguish between these

2.       Analysts that report on SSL certificate data who have had to
issue revised reports because of cert misclassification


My proposal is for CAs to put in OID X if it's a DV certificate and OID
Y if it's an OV certificate.


As Rick reminded me on the call, we currently have something like this
for EV certificates (except that CAs are free to use the standard OID or
define one of their own).


I'd like to hear pros/cons of this. Ryan S indicated that Google would
not support such a proposal but we didn't have time to discuss the


I'm sure there are both technical and policy reasons. Personally I'd
like to focus on the latter but remarks on both are welcome. This
proposal doesn't require anyone to do anything with this data (i.e
relying parties can choose whether or not to utilize it).





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cabforum.org/pipermail/public/attachments/20141006/51ba7f8d/attachment-0003.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5857 bytes
Desc: not available
URL: <http://lists.cabforum.org/pipermail/public/attachments/20141006/51ba7f8d/attachment-0001.p7s>

More information about the Public mailing list