So, based off of the comments that have been made, please can Mozilla support 
such a change?

If not, what would Mozilla's objections be that are in scope to the 
question/issue? Presently, none appear to have been articulated.

The immediate benefit to Mozilla would be consistency and conformity among the 
OV certificates that get issued. This is because, as Jeremy mentions, they will 
be bound by the requirements that inclusion of the OID brings as it is an 
assertion of compliance.

As has been said but probably needs to be reiterated, we all need to be careful 
not to conflate, confuse and overload the issue with the entirely separate and 
distinct questions that surround handling of the certificate in code and what 
appropriate UX is. These are clearly far more contentious, perhaps political in 
nature, and should be considered and discussed independently to this.

Thanks!

Nick
_______________________________________________
dev-security-policy mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-security-policy

Reply via email to