[cabfpub] Naming rules

Moudrick M. Dadashov md at ssc.lt
Fri Mar 3 05:40:30 UTC 2017


Hi Peter,

In Europe we also use  Subject Names specified in ETSI EN 319 412-1, 
ETSI EN 319 412-2 and ETSI EN 319 412-3.

Thanks,
M.D.

On 3/3/2017 5:29 AM, Peter Bowen via Public wrote:
> We have had a number of discussions over the last few months about the content of Subject Names in Certificates.  I promised on a recent call to try to summarize one of the issues, including the issue that Li-Chun has raised.
>
> The Baseline Requirements specify how Names are to be constructed.  There are rules about which attributes must appear in names and what the content of the attributes must be.
>
> There are other existing PKIs with different naming rules.  Another PKI could forbid an attribute required by the BRs.  Alternatively another PKI could require that the full Name be taken verbatim from some other source, such as an existing Directory Information Tree; these Names many not include attributes required by the BRs.
>
> I believe the government on Taiwan falls into the latter case.  They have a PKI which has the policy that names must be taken from an existing Directory Information Tree operated by the government.  Many of the Names in the existing DIT don’t include attributes that are required by the BRs.  Therefore the question is whether we should make an exception to allow this existing PKI to be declared BR-compliant by adding some language like “ If a Government CA is required by its Certificate Policy to use Subject Names from a Directory Information Tree operated by a Government Entity, then section 7.1.4.2.2 shall not apply.”
>
> Li-Chun: Did I get this right?
>
> Others: Does this make the issue clearer?
>
> Thanks,
> Peter
> _______________________________________________
> Public mailing list
> Public at cabforum.org
> https://cabforum.org/mailman/listinfo/public

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cabforum.org/pipermail/public/attachments/20170303/7e6cb5de/attachment-0003.html>


More information about the Public mailing list