Re: [Servercert-wg] [External Sender] Re: [EXTERNAL]- Subject attribute encoding order requirement (rationale for)

2024-03-21 Thread Clint Wilson via Servercert-wg
Hi Adriano, I haven’t looked through minutes and such yet, but as I recall this ordering was discussed a number of times on Validation Subcommittee calls during the creation of SC-062 (i.e. sometime in 2020-2023). The resultant ordering originated from the combination of 3 primary sources: 1.

Re: [Servercert-wg] [External Sender] Re: [EXTERNAL]- Subject attribute encoding order requirement (rationale for)

2024-03-21 Thread Adriano Santoni via Servercert-wg
Thank you Jaime , but I had already checked that. At that link I can only find the following very short exchange between chrisbn and sleevi: @chrisbn chrisbn May 13, 2022 Yes, I wonder about the order of fields not in this list. I understand the hierarchy to order logic, but is the order

Re: [Servercert-wg] [EXTERNAL]- Subject attribute encoding order requirement (rationale for)

2024-03-21 Thread Jaime Hablutzel via Servercert-wg
The discussion in https://github.com/sleevi/cabforum-docs/pull/36#discussion_r872103477 could help. > On 21 Mar 2024, at 09:39, Adriano Santoni via Servercert-wg > wrote: > > All, can anyone help me find the past email discussion, or at least the > rationale that someone wrote somewhere

[Servercert-wg] Subject attribute encoding order requirement (rationale for)

2024-03-21 Thread Adriano Santoni via Servercert-wg
All, can anyone help me find the past email discussion, or at least the rationale that someone wrote somewhere (e.g. on Github?), supporting the Subject attributes encoding relative order requirement that was introduced in BR 2.0.0 (Ballot SC-062) ? I am talking about §7.1.4.2 Subject