[cabfpub] rfc822Names and otherNames

Ryan Sleevi sleevi at google.com
Wed Dec 14 16:13:38 UTC 2016

On Tue, Dec 13, 2016 at 10:13 PM, Jeremy Rowley via Public <
public at cabforum.org> wrote:

> Therefore, I’d like to modify the baseline requirements to permit other
> name types. Does anyone else see a need for this? Are there risks in
> permitting the additional names that I’m not aware of?

In general, permitting specific name types, with specific documentation on
the information they contain, should be an OK thing.

However, letting CAs decide entirely will forever salt the earth there for
being able to use those name types, and may result in additional security
risk - much like the issues with validation and "any equivalent method"

So, to the extent possible, I'd like to treat it as a validation method -
that is, there's (generally) no harm in adding additional name types
(provided they don't cause compat issues), so long as the industry can
agree on the nature and structure of the data. Or make sure they're not
technically capable of being used as TLS certs due to their issuing
intermediate being technically restricted via EKU :)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cabforum.org/pipermail/public/attachments/20161214/11f9b245/attachment-0003.html>

More information about the Public mailing list