Re: Transforming a trade name into ASCII in the O field of an OV cert

On 4/24/18 2:47 PM, Henri Sivonen via dev-security-policy wrote: > On Tue, Apr 24, 2018 at 11:03 PM, cbonnell--- via dev-security-policy > wrote: >> On Tuesday, April 24, 2018 at 4:33:24 PM UTC-4, Henri Sivonen wrote: >>> On Tue, Apr 24, 2018 at 10:18 PM,

Re: Transforming a trade name into ASCII in the O field of an OV cert

On Tue, Apr 24, 2018 at 11:03 PM, cbonnell--- via dev-security-policy wrote: > On Tuesday, April 24, 2018 at 4:33:24 PM UTC-4, Henri Sivonen wrote: >> On Tue, Apr 24, 2018 at 10:18 PM, Jeremy Rowley via >> dev-security-policy

Re: Transforming a trade name into ASCII in the O field of an OV cert

On Tuesday, April 24, 2018 at 4:33:24 PM UTC-4, Henri Sivonen wrote: > On Tue, Apr 24, 2018 at 10:18 PM, Jeremy Rowley via > dev-security-policy wrote: > > That is correct. We use transliteration of non-latin names through a system > > recognized by ISO per

Re: Transforming a trade name into ASCII in the O field of an OV cert

On Tue, Apr 24, 2018 at 10:32 PM, Henri Sivonen wrote: > On Tue, Apr 24, 2018 at 10:18 PM, Jeremy Rowley via > dev-security-policy wrote: >> That is correct. We use transliteration of non-latin names through a system >> recognized by

RE: Transforming a trade name into ASCII in the O field of an OV cert

That is correct. We use transliteration of non-latin names through a system recognized by ISO per Appendix D(1)(3) -Original Message- From: dev-security-policy On Behalf Of cbonnell--- via dev-security-policy Sent:

Re: Transforming a trade name into ASCII in the O field of an OV cert

On Monday, April 23, 2018 at 3:34:38 PM UTC-4, Wayne Thayer wrote: > Section 9.2.1 of the EVGLs is stricter, only permitting abbreviations. If > this were an EV cert I would argue that it was misissued. > > On Mon, Apr 23, 2018 at 12:13 PM, Ryan Sleevi via dev-security-policy < >

Re: Transforming a trade name into ASCII in the O field of an OV cert

Section 9.2.1 of the EVGLs is stricter, only permitting abbreviations. If this were an EV cert I would argue that it was misissued. On Mon, Apr 23, 2018 at 12:13 PM, Ryan Sleevi via dev-security-policy < dev-security-policy@lists.mozilla.org> wrote: > On Mon, Apr 23, 2018 at 1:11 PM, Henri

Re: Transforming a trade name into ASCII in the O field of an OV cert

On Mon, Apr 23, 2018 at 1:11 PM, Henri Sivonen via dev-security-policy < dev-security-policy@lists.mozilla.org> wrote: > First, it seems to me that the Baseline Requirements allow > transformations of the organization's name only if the CA documents > such transformations. I am unable to find

Re: Transforming a trade name into ASCII in the O field of an OV cert

On Sun, Apr 15, 2018 at 6:47 PM, Ryan Sleevi wrote: > > On Sun, Apr 15, 2018 at 9:13 AM Henri Sivonen via dev-security-policy > wrote: >> >> (Mozilla hat off.) >> >> After reading about the California versus Delaware thing when it comes >>

Re: Transforming a trade name into ASCII in the O field of an OV cert

On Sun, Apr 15, 2018 at 9:13 AM Henri Sivonen via dev-security-policy < dev-security-policy@lists.mozilla.org> wrote: > (Mozilla hat off.) > > After reading about the California versus Delaware thing when it comes > to the certificate for stripe.com, out of curiosity, I took a fresh > look at the

Transforming a trade name into ASCII in the O field of an OV cert

(Mozilla hat off.) After reading about the California versus Delaware thing when it comes to the certificate for stripe.com, out of curiosity, I took a fresh look at the ISO 3166-1 code in the EV certificates of some of the banks that operate in Finland. (Result: https://www.nordea.fi/ is SE,