<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><font face="Calibri">I fully agree with Dimitris.</font></p>
<p><font face="Calibri">Thanks,</font></p>
<p><font face="Calibri">Adriano</font></p>
<p><font face="Calibri"></font><br>
</p>
<div class="moz-cite-prefix">Il 05/08/2021 09:55, Dimitris
Zacharopoulos (HARICA) via Smcwg-public ha scritto:<br>
</div>
<blockquote type="cite"
cite="mid:0100017b154f2a2c-fc4a829b-dbca-4191-82c6-852965981f4f-000000@email.amazonses.com"><br>
<br>
On 5/8/2021 10:39 π.μ., Wiedenhorst, Matthias via Smcwg-public
wrote:
<br>
<blockquote type="cite">- Natural person associated with a legal
person ("Sponsored")
<br>
These unsurprisingly already match with the typical subject
types and for example also with the definition of possible
subject as given in ETSI EN 319 411-1.
<br>
In my opinion it should be up to the CA whether they want to
sell all of these profiles on a retail basis or if some are only
available through Enterprise RAs. But maybe in that case,
"Sponsored" is not the very best name for that profile
anymore...
<br>
</blockquote>
<br>
I shared that same observation at yesterday's call.
<br>
<br>
One could request a certificate that contains an organization name
and individual information in the subject, including a validated
email address. This doesn't need to be "sponsored".
<br>
<br>
Stephen mentioned that this would fit under the "individual"
profile, but with a "corporate" flavor.
<br>
<br>
The responsibility of the CA is to "bind" a key with attributes of
a specific natural person or legal entity. If the subject of the
certificate is a "natural person, associated with a legal entity",
after the CA validates control of a specific email address, the CA
would need to bind the organization attributes (countryName,
organizationName, etc) and personal attributes (givenName,
surname) with the same Applicant.
<br>
<br>
I had reservations about the "sponsored" title early in our
discussions because whether it is "sponsored" or not, from a
certificate profile perspective, is irrelevant. As Matthias
pointed out, the "sponsored" flavor is more of a "delegation of
validation duties" issue rather than a certificate profile issue.
<br>
<br>
The word "Corporate" instead of "Sponsored" and a detailed
description that it is related to an "Individual associated with
an Organization" seems preferable.
<br>
<br>
<br>
Thanks,
<br>
Dimitris.
<br>
_______________________________________________
<br>
Smcwg-public mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Smcwg-public@cabforum.org">Smcwg-public@cabforum.org</a>
<br>
<a class="moz-txt-link-freetext" href="https://lists.cabforum.org/mailman/listinfo/smcwg-public">https://lists.cabforum.org/mailman/listinfo/smcwg-public</a>
<br>
</blockquote>
</body>
</html>