<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font face="Cambria">Hi Adriano,<br>
<br>
Like for other Subject attributes, primary source of "address" is
the official legal entity registry where content of the address is
country specific. Just curious, why are we creating new problems
(see "state", "locality" (that in some jurisdictions have
absolutely no meaning) related discussions)? Our vote for this
ballot will be No.<br>
<br>
Thanks,<br>
M.D.<br>
<br>
</font><br>
<div class="moz-cite-prefix">On 5/17/2017 1:08 PM, Adriano Santoni
via Public wrote:<br>
</div>
<blockquote
cite="mid:94c14cd4-7390-de1c-03c3-457cb1bdc1b2@staff.aruba.it"
type="cite">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<p><font face="Calibri">All, would like some opinions about the
following question:</font></p>
Can it be considered "okay" if the streetAddress component of an
OV (or EV) certificate Subject contains some more information than
it's strictly specified (or, more exactly, exemplified) in ITU-T
X.520 ?<br>
<br>
ITU-T X.520 (aka ISO/IEC 9594-6) reads: <br>
"The Street Address attribute type specifies a site for the local
distribution and physical delivery in a postal address,<br>
i.e., the street name, place, avenue and house number"<br>
<br>
For instance, how would you consider a street Address that, in
addition to street name and house number, also contains a country
name: compliant? non-compliant? of dubious compliance?<br>
<br>
Adriano<br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Public mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Public@cabforum.org">Public@cabforum.org</a>
<a class="moz-txt-link-freetext" href="https://cabforum.org/mailman/listinfo/public">https://cabforum.org/mailman/listinfo/public</a>
</pre>
</blockquote>
<br>
</body>
</html>