[cabfpub] BR Section 9.2.3 incompatability

Jeremy Rowley jeremy.rowley at digicert.com
Fri May 10 18:01:25 UTC 2013


It's come to my attention that section 9.2.3 has a potential incompatibility
with the requirements imposed by IGTF and other similar communities.  

 

Section 9.2.3:

9.2.3 Subject Domain Component Field 

Certificate Field: subject:domainComponent (OID 0.9.2342.19200300.100.1.25)

Required/Optional: Optional. 

Contents: If present, this field MUST contain all components of the
subject's Registered Domain Name in ordered sequence, with the most
significant component, closest to the root of the namespace, written last.

 

>From  OGF GFD.125 [http://www.ogf.org/documents/GFD.125.pdf] Section 2.3.2:

 

To ensure uniqueness and proper delegation, the use of domainComponent (DC)
naming corresponding to a registered DNS name owned by the authority at the
beginning of the issuer and subject name RDN sequence is strongly
encouraged. In that case, the ASN.1 SEQUENCE MUST start with the
domainComponent representing the top-level domain, for example "DC=org" or
"DC=eu".

 

The need for this comes from the fact that identification is based on the
subject DN only. From the IGTF Federation Document:

 

"3.1 Management and communication of identifiers

 

On accreditation, a specific subject name space or set of subject name
spaces is allocated to each authority. This name space must not overlap with
any existing name space already assigned to an existing authority for any
AP, assigned by any of the regional PMAs within the International Grid Trust
Federation."

 

Really, it boils down to the fact that the IGTF space and others expect to
use the DC field to indicate a responsible community or verifier.
Therefore, I propose we modify Section 9.2.3. to permit issue, community,
and RA information in the DC as well as subject information. 

 

My proposal:

9.2.3 Subject Domain Component Field 

Certificate Field: subject:domainComponent (OID 0.9.2342.19200300.100.1.25)

Required/Optional: Optional. 

Contents: If present, this field MUST contain all components of a verified
Domain Name (such as the Domain Name of the subject, issuer, or RA) in
ordered sequence, with the most significant component, closest to the root
of the namespace, written last.

 

Let me know if you are interested in endorsing.

 

Thanks,

 

Jeremy

 

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cabforum.org/pipermail/public/attachments/20130510/f347cd43/attachment-0002.html>


More information about the Public mailing list