Re: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS structure according to RFC 3647

[xiulei--- via Servercert-wg]

GDCA votes NO on Ballot SC-74.

Thanks.
 
From: Dimitris Zacharopoulos (HARICA) via Servercert-wg
Date: 2024-05-05 16:24
To: CA/B Forum Server Certificate WG Public Discussion List
Subject: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS 
structure according to RFC 3647
Voting begins for ballot SC-74.
SC-74 - Clarify CP/CPS structure according to RFC 3647
Summary
The TLS Baseline Requirements require in section 2.2 that:
"The Certificate Policy and/or Certification Practice Statement MUST be 
structured in accordance with RFC 3647 and MUST include all material required 
by RFC 3647."
The intent of this language was to ensure that all CAs' CP and/or CPS documents 
contain a similar structure, making it easier to review and compare against the 
BRs. However, there was some ambiguity as to the actual structure that CAs 
should follow. After several discussions in the SCWG Public Mailing List and 
F2F meetings, it was agreed that more clarity should be added to the existing 
requirement, pointing to the outline described in section 6 of RFC 3647.
The following motion has been proposed by Dimitris Zacharopoulos (HARICA) and 
endorsed by Aaron Poulsen (Amazon) and Tim Hollebeek (Digicert). 
You can view the github pull request representing this ballot here. 
Motion Begins
MODIFY the "Baseline Requirements for the Issuance and Management of 
Publicly-Trusted TLS Server Certificates" based on Version 2.0.4 as specified 
in the following redline:
https://github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae
 
Motion Ends
This ballot proposes a Final Maintenance Guideline. The procedure for approval 
of this ballot is as follows:
Discussion (at least 7 days)
Start time: 2024-04-25 16:30:00 UTC
End time: on or after 2024-05-02 16:30:00 UTC
Vote for approval (7 days)
Start time: 2024-05-05 8:30:00 UTC
End time: 2024-05-12 8:30:00 UTC

___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg

Re: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS structure according to RFC 3647

[BILGEM KSM]

Kamu SM votes "No" on Ballot SC-74. 




Tuğba ÖZCAN 

Head Of e-Signature Technologies Department 



TÜBİTAK/BİLGEM/Kamu SM 

Çamlıca Mahallesi 408. Cadde No: 136 

C Blok 5. Kat Yenimahalle/Ankara 

Dahili:8543 




tugba.oz...@tubitak.gov.tr 


Kimden: "CA"  
Kime: "Dimitris Zacharopoulos, HARICA" , "CA" 
 
Gönderilenler: 10 Mayıs Cuma 2024 9:50:25 
Konu: Re: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS 
structure according to RFC 3647 

JPRS votes NO to Ballot SC-74. 


On 2024/05/05 17:24, Dimitris Zacharopoulos (HARICA) via Servercert-wg wrote: 
> Voting begins for ballot SC-74. 
> 
> 
> SC-74 - Clarify CP/CPS structure according to RFC 3647 
> 
> 
> Summary 
> 
> The TLS Baseline Requirements require in section 2.2 that: 
> 
> /"The Certificate Policy and/or Certification Practice Statement MUST be 
> structured in accordance with RFC 3647 and MUST include all material required 
> by RFC 3647."/ 
> 
> The intent of this language was to ensure that all CAs' CP and/or CPS 
> documents contain a similar structure, making it easier to review and compare 
> against the BRs. However, there was some ambiguity as to the actual structure 
> that CAs should follow. After several discussions in the SCWG Public Mailing 
> List 
> <https://lists.cabforum.org/pipermail/servercert-wg/2023-November/004070.html>
>  and F2F meetings, it was agreed that more clarity should be added to the 
> existing requirement, pointing to the outline described in section 6 of RFC 
> 3647. 
> 
> The following motion has been proposed by Dimitris Zacharopoulos (HARICA) and 
> endorsed by Aaron Poulsen (Amazon) and Tim Hollebeek (Digicert). 
> 
> You can view the github pull request representing this ballot here 
> <https://github.com/cabforum/servercert/pull/503>. 
> 
> 
> Motion Begins 
> 
> MODIFY the "Baseline Requirements for the Issuance and Management of 
> Publicly-Trusted TLS Server Certificates" based on Version 2.0.4 as specified 
> in the following redline: 
> 
> * 
> https://github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae
>  
> 
> 
> Motion Ends 
> 
> This ballot proposes a Final Maintenance Guideline. The procedure for 
> approval of this ballot is as follows: 
> 
> 
> Discussion (at least 7 days) 
> 
> * Start time: 2024-04-25 16:30:00 UTC 
> * End time: on or after 2024-05-02 16:30:00 UTC 
> 
> 
> Vote for approval (7 days) 
> 
> * Start time: 2024-05-05 8:30:00 UTC 
> * End time: 2024-05-12 8:30:00 UTC 
> 
> 
> 
> ___ 
> Servercert-wg mailing list 
> Servercert-wg@cabforum.org 
> https://lists.cabforum.org/mailman/listinfo/servercert-wg 
___ 
Servercert-wg mailing list 
Servercert-wg@cabforum.org 
https://lists.cabforum.org/mailman/listinfo/servercert-wg 
___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg

Re: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS structure according to RFC 3647

[Yoshihiko Matsuo via Servercert-wg]

JPRS votes NO to Ballot SC-74.


On 2024/05/05 17:24, Dimitris Zacharopoulos (HARICA) via Servercert-wg wrote:

Voting begins for ballot SC-74.


  SC-74 - Clarify CP/CPS structure according to RFC 3647


Summary

The TLS Baseline Requirements require in section 2.2 that:

/"The Certificate Policy and/or Certification Practice Statement MUST be structured 
in accordance with RFC 3647 and MUST include all material required by RFC 3647."/

The intent of this language was to ensure that all CAs' CP and/or CPS documents 
contain a similar structure, making it easier to review and compare against the BRs. 
However, there was some ambiguity as to the actual structure that CAs should follow. 
After several discussions in the SCWG Public Mailing List 
 
and F2F meetings, it was agreed that more clarity should be added to the existing 
requirement, pointing to the outline described in section 6 of RFC 3647.

The following motion has been proposed by Dimitris Zacharopoulos (HARICA) and 
endorsed by Aaron Poulsen (Amazon) and Tim Hollebeek (Digicert).

You can view the github pull request representing this ballot here 
.


Motion Begins

MODIFY the "Baseline Requirements for the Issuance and Management of 
Publicly-Trusted TLS Server Certificates" based on Version 2.0.4 as specified in the 
following redline:

  * 
https://github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae


Motion Ends

This ballot proposes a Final Maintenance Guideline. The procedure for approval 
of this ballot is as follows:


Discussion (at least 7 days)

  * Start time: 2024-04-25 16:30:00 UTC
  * End time: on or after 2024-05-02 16:30:00 UTC


Vote for approval (7 days)

  * Start time: 2024-05-05 8:30:00 UTC
  * End time: 2024-05-12 8:30:00 UTC



___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg

___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg

Re: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS structure according to RFC 3647

[Mads Egil Henriksveen via Servercert-wg]

Buypass votes NO on ballot SC-74.

Regards
Mads

From: Servercert-wg  On Behalf Of Mads Egil 
Henriksveen via Servercert-wg
Sent: Thursday, May 9, 2024 4:50 PM
To: Dimitris Zacharopoulos (HARICA) ; CA/B Forum Server 
Certificate WG Public Discussion List 
Subject: Re: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS 
structure according to RFC 3647

Buypass votes YES on ballot SC-74.

Regards
Mads

From: Servercert-wg 
mailto:servercert-wg-boun...@cabforum.org>> 
On Behalf Of Dimitris Zacharopoulos (HARICA) via Servercert-wg
Sent: Sunday, May 5, 2024 10:25 AM
To: CA/B Forum Server Certificate WG Public Discussion List 
mailto:servercert-wg@cabforum.org>>
Subject: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS 
structure according to RFC 3647

Voting begins for ballot SC-74.
SC-74 - Clarify CP/CPS structure according to RFC 3647
Summary

The TLS Baseline Requirements require in section 2.2 that:

"The Certificate Policy and/or Certification Practice Statement MUST be 
structured in accordance with RFC 3647 and MUST include all material required 
by RFC 3647."

The intent of this language was to ensure that all CAs' CP and/or CPS documents 
contain a similar structure, making it easier to review and compare against the 
BRs. However, there was some ambiguity as to the actual structure that CAs 
should follow. After several discussions in the SCWG Public Mailing 
List<https://lists.cabforum.org/pipermail/servercert-wg/2023-November/004070.html>
 and F2F meetings, it was agreed that more clarity should be added to the 
existing requirement, pointing to the outline described in section 6 of RFC 
3647.

The following motion has been proposed by Dimitris Zacharopoulos (HARICA) and 
endorsed by Aaron Poulsen (Amazon) and Tim Hollebeek (Digicert).

You can view the github pull request representing this ballot 
here<https://github.com/cabforum/servercert/pull/503>.

Motion Begins

MODIFY the "Baseline Requirements for the Issuance and Management of 
Publicly-Trusted TLS Server Certificates" based on Version 2.0.4 as specified 
in the following redline:

  *   
https://github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae

Motion Ends

This ballot proposes a Final Maintenance Guideline. The procedure for approval 
of this ballot is as follows:

Discussion (at least 7 days)

  *   Start time: 2024-04-25 16:30:00 UTC
  *   End time: on or after 2024-05-02 16:30:00 UTC

Vote for approval (7 days)

  *   Start time: 2024-05-05 8:30:00 UTC
  *   End time: 2024-05-12 8:30:00 UTC

___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg

Re: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS structure according to RFC 3647

[Fernandez Ruperez, David Alvaro via Servercert-wg]

IZENPE votes NO on Ballot SC-74.




SC-74 - Clarify CP/CPS structure according to RFC 3647


Summary


The TLS Baseline Requirements require in section 2.2 that:

"The Certificate Policy and/or Certification Practice Statement MUST be 
structured in accordance with RFC 3647 and MUST include all material required 
by RFC 3647."

The intent of this language was to ensure that all CAs' CP and/or CPS documents 
contain a similar structure, making it easier to review and compare against the 
BRs. However, there was some ambiguity as to the actual structure that CAs 
should follow. After several discussions in the SCWG Public Mailing 
List
 and F2F meetings, it was agreed that more clarity should be added to the 
existing requirement, pointing to the outline described in section 6 of RFC 
3647.

The following motion has been proposed by Dimitris Zacharopoulos (HARICA) and 
endorsed by Aaron Poulsen (Amazon) and Tim Hollebeek (Digicert).

You can view the github pull request representing this ballot 
here.


Motion Begins


MODIFY the "Baseline Requirements for the Issuance and Management of 
Publicly-Trusted TLS Server Certificates" based on Version 2.0.4 as specified 
in the following redline:

*   
https://github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae


Motion Ends


This ballot proposes a Final Maintenance Guideline. The procedure for approval 
of this ballot is as follows:


Discussion (at least 7 days)


*   Start time: 2024-04-25 16:30:00 UTC
*   End time: on or after 2024-05-02 16:30:00 UTC


Vote for approval (7 days)


*   Start time: 2024-05-05 8:30:00 UTC
*   End time: 2024-05-12 8:30:00 UTC



___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg

Re: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS structure according to RFC 3647

[hcli]

TWCA changes its vote to “no” on ballot SC-74


Hao-Chun Li


From: Servercert-wg  On Behalf Of 
蔡家宏(chtsai) via Servercert-wg
Sent: Monday, May 6, 2024 4:21 PM
To: Dimitris Zacharopoulos (HARICA) ; CA/B Forum Server 
Certificate WG Public Discussion List 
Subject: Re: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS 
structure according to RFC 3647

TWCA votes "yes" to ballot SC-74.


From: Servercert-wg 
mailto:servercert-wg-boun...@cabforum.org>> 
On Behalf Of Dimitris Zacharopoulos (HARICA) via Servercert-wg
Sent: Sunday, May 5, 2024 4:25 PM
To: CA/B Forum Server Certificate WG Public Discussion List 
mailto:servercert-wg@cabforum.org>>
Subject: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS 
structure according to RFC 3647

Voting begins for ballot SC-74.
SC-74 - Clarify CP/CPS structure according to RFC 3647
Summary

The TLS Baseline Requirements require in section 2.2 that:

"The Certificate Policy and/or Certification Practice Statement MUST be 
structured in accordance with RFC 3647 and MUST include all material required 
by RFC 3647."

The intent of this language was to ensure that all CAs' CP and/or CPS documents 
contain a similar structure, making it easier to review and compare against the 
BRs. However, there was some ambiguity as to the actual structure that CAs 
should follow. After several discussions in the SCWG Public Mailing 
List<https://lists.cabforum.org/pipermail/servercert-wg/2023-November/004070.html>
 and F2F meetings, it was agreed that more clarity should be added to the 
existing requirement, pointing to the outline described in section 6 of RFC 
3647.

The following motion has been proposed by Dimitris Zacharopoulos (HARICA) and 
endorsed by Aaron Poulsen (Amazon) and Tim Hollebeek (Digicert).

You can view the github pull request representing this ballot 
here<https://github.com/cabforum/servercert/pull/503>.

Motion Begins

MODIFY the "Baseline Requirements for the Issuance and Management of 
Publicly-Trusted TLS Server Certificates" based on Version 2.0.4 as specified 
in the following redline:

  *   
https://github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae

Motion Ends

This ballot proposes a Final Maintenance Guideline. The procedure for approval 
of this ballot is as follows:

Discussion (at least 7 days)

  *   Start time: 2024-04-25 16:30:00 UTC
  *   End time: on or after 2024-05-02 16:30:00 UTC

Vote for approval (7 days)

  *   Start time: 2024-05-05 8:30:00 UTC
  *   End time: 2024-05-12 8:30:00 UTC

___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg

Re: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS structure according to RFC 3647

[陳立群 via Servercert-wg]

Chunghwa Telecom votes "No" to ballot SC-74.


Li-Chun Chen


-Original Message-
From: Servercert-wg  On Behalf Of
Dimitris Zacharopoulos (HARICA) via Servercert-wg
Sent: Friday, May 10, 2024 12:06 AM
To: servercert-wg@cabforum.org
Subject: [外部郵件]Re: [Servercert-wg] [Voting Begins] Ballot SC-74 -
Clarify CP/CPS structure according to RFC 3647

HARICA votes "no" to ballot SC-74.

Dimitris.


On 5/5/2024 12:06 μ.μ., Dimitris Zacharopoulos (HARICA) wrote:


HARICA votes "yes" to ballot SC-74.


On 5/5/2024 11:24 π.μ., Dimitris Zacharopoulos (HARICA) via
Servercert-wg wrote:


Voting begins for ballot SC-74.


SC-74 - Clarify CP/CPS structure according to RFC 3647


Summary


The TLS Baseline Requirements require in section 2.2 that:

"The Certificate Policy and/or Certification Practice
Statement MUST be structured in accordance with RFC 3647 and MUST include
all material required by RFC 3647."

The intent of this language was to ensure that all CAs' CP
and/or CPS documents contain a similar structure, making it easier to review
and compare against the BRs. However, there was some ambiguity as to the
actual structure that CAs should follow. After several discussions in the
SCWG Public Mailing List
<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.cab
forum.org%2Fpipermail%2Fservercert-wg%2F2023-November%2F004070.html=05%
7C02%7Crealsky%40cht.com.tw%7Cd05db8f105f940bae81b08dc70421522%7C54eb9440cf0
345fe835e61bd4ce515c8%7C0%7C0%7C638508676358101018%7CUnknown%7CTWFpbGZsb3d8e
yJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%
7C=0ArURxFBOKXx7idN%2Bhq8PfM%2Fno1gPS7%2F8UOyt1%2FhyuY%3D=0>
and F2F meetings, it was agreed that more clarity should be added to the
existing requirement, pointing to the outline described in section 6 of RFC
3647.

The following motion has been proposed by Dimitris
Zacharopoulos (HARICA) and endorsed by Aaron Poulsen (Amazon) and Tim
Hollebeek (Digicert). 


You can view the github pull request representing this
ballot here
<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co
m%2Fcabforum%2Fservercert%2Fpull%2F503=05%7C02%7Crealsky%40cht.com.tw%7
Cd05db8f105f940bae81b08dc70421522%7C54eb9440cf0345fe835e61bd4ce515c8%7C0%7C0
%7C638508676358111640%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2
luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=LhUovKWu6BVb%2Bgm0Gz
8vclynq360krmRL6YBiydLvhk%3D=0> . 



Motion Begins


MODIFY the "Baseline Requirements for the Issuance and
Management of Publicly-Trusted TLS Server Certificates" based on Version
2.0.4 as specified in the following redline:



*   https://github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba
66b5a85df75907ac2a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae
<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co
m%2Fcabforum%2Fservercert%2Fcompare%2Fc4a34fe2292022e0a04ba66b5a85df75907ac2
a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae=05%7C02%7Crealsky%40cht.c
om.tw%7Cd05db8f105f940bae81b08dc70421522%7C54eb9440cf0345fe835e61bd4ce515c8%
7C0%7C0%7C638508676358119054%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJ
QIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=YKGbmh48JeTJh
bWDykvV1QA7ijqjvV7ESll11g4m4uM%3D=0>  



Motion Ends


This ballot proposes a Final Maintenance Guideline. The
procedure for approval of this ballot is as follows:


Discussion (at least 7 days)


*   Start time: 2024-04-25 16:30:00 UTC
*   End time: on or after 2024-05-02 16:30:00 UTC


Vote for approval (7 days)


*   Start time: 2024-05-05 8:30:00 UTC
*   End time: 2024-05-12 8:30:00 UTC



 
___
Servercert-wg mailing list
Servercert-wg@cabforum.org
<mailto:Servercert-wg@cabforum.org> 
https://lists.cabforum.org/mailman/listinfo/servercert-wg
<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.cab
forum.org%2Fmailman%2Flistinfo%2Fservercert-wg=05%7C02%7Crealsky%40cht.
com.tw%7Cd05db8f105f940bae81b08dc70421522%7C54eb9440cf0345fe835e61bd4ce515c8
%7C0%7C0%7C638508676358125350%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLC
JQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=smvaIm69H5Kc
rU80UYVHOlC73%2BKYRuOo40%2Fu7Avr62E%3D=0> 





smime.p7s
Description: S/MIME cryptographic signature
___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg

Re: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS structure according to RFC 3647

[大野 文彰 via Servercert-wg]

SECOM Trust Systems changes its vote to NO on Ballot SC-74.

Best Regards,

ONO, Fumiaki
SECOM Trust Systems Co., Ltd.

From: 大野 文彰
Sent: Thursday, May 9, 2024 6:48 PM
To: 'Dimitris Zacharopoulos (HARICA)' ; 'CA/B Forum Server 
Certificate WG Public Discussion List' 
Subject: RE: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS 
structure according to RFC 3647

SECOM Trust Systems votes YES on Ballot SC-74.

Best Regards,

ONO, Fumiaki
SECOM Trust Systems Co., Ltd.

From: Servercert-wg [mailto:servercert-wg-boun...@cabforum.org] On Behalf Of 
Dimitris Zacharopoulos (HARICA) via Servercert-wg
Sent: Sunday, May 5, 2024 5:25 PM
To: CA/B Forum Server Certificate WG Public Discussion List 
mailto:servercert-wg@cabforum.org>>
Subject: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS 
structure according to RFC 3647

Voting begins for ballot SC-74.
SC-74 - Clarify CP/CPS structure according to RFC 3647
Summary

The TLS Baseline Requirements require in section 2.2 that:

"The Certificate Policy and/or Certification Practice Statement MUST be 
structured in accordance with RFC 3647 and MUST include all material required 
by RFC 3647."

The intent of this language was to ensure that all CAs' CP and/or CPS documents 
contain a similar structure, making it easier to review and compare against the 
BRs. However, there was some ambiguity as to the actual structure that CAs 
should follow. After several discussions in the SCWG Public Mailing 
List<https://lists.cabforum.org/pipermail/servercert-wg/2023-November/004070.html>
 and F2F meetings, it was agreed that more clarity should be added to the 
existing requirement, pointing to the outline described in section 6 of RFC 
3647.

The following motion has been proposed by Dimitris Zacharopoulos (HARICA) and 
endorsed by Aaron Poulsen (Amazon) and Tim Hollebeek (Digicert).

You can view the github pull request representing this ballot 
here<https://github.com/cabforum/servercert/pull/503>.

Motion Begins

MODIFY the "Baseline Requirements for the Issuance and Management of 
Publicly-Trusted TLS Server Certificates" based on Version 2.0.4 as specified 
in the following redline:

  *   
https://github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae

Motion Ends

This ballot proposes a Final Maintenance Guideline. The procedure for approval 
of this ballot is as follows:

Discussion (at least 7 days)

  *   Start time: 2024-04-25 16:30:00 UTC
  *   End time: on or after 2024-05-02 16:30:00 UTC

Vote for approval (7 days)

  *   Start time: 2024-05-05 8:30:00 UTC
  *   End time: 2024-05-12 8:30:00 UTC

___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg

Re: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS structure according to RFC 3647

[Brittany Randall via Servercert-wg]

GoDaddy votes "No" on SC-74 based on the discussion from the Server Certificate 
working group call on May 9. 2024.

Brittany

From: Servercert-wg  on behalf of Dimitris 
Zacharopoulos (HARICA) via Servercert-wg 
Sent: Sunday, May 5, 2024 1:24 AM
To: CA/B Forum Server Certificate WG Public Discussion List 

Subject: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS 
structure according to RFC 3647

Caution: This email is from an external sender. Please do not click links or 
open attachments unless you recognize the sender and know the content is safe. 
Forward suspicious emails to isitbad@.



Voting begins for ballot SC-74.
SC-74 - Clarify CP/CPS structure according to RFC 3647
Summary

The TLS Baseline Requirements require in section 2.2 that:

"The Certificate Policy and/or Certification Practice Statement MUST be 
structured in accordance with RFC 3647 and MUST include all material required 
by RFC 3647."

The intent of this language was to ensure that all CAs' CP and/or CPS documents 
contain a similar structure, making it easier to review and compare against the 
BRs. However, there was some ambiguity as to the actual structure that CAs 
should follow. After several discussions in the SCWG Public Mailing 
List<https://lists.cabforum.org/pipermail/servercert-wg/2023-November/004070.html>
 and F2F meetings, it was agreed that more clarity should be added to the 
existing requirement, pointing to the outline described in section 6 of RFC 
3647.

The following motion has been proposed by Dimitris Zacharopoulos (HARICA) and 
endorsed by Aaron Poulsen (Amazon) and Tim Hollebeek (Digicert).

You can view the github pull request representing this ballot 
here<https://github.com/cabforum/servercert/pull/503>.

Motion Begins

MODIFY the "Baseline Requirements for the Issuance and Management of 
Publicly-Trusted TLS Server Certificates" based on Version 2.0.4 as specified 
in the following redline:

  *   
https://github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae

Motion Ends

This ballot proposes a Final Maintenance Guideline. The procedure for approval 
of this ballot is as follows:

Discussion (at least 7 days)

  *   Start time: 2024-04-25 16:30:00 UTC
  *   End time: on or after 2024-05-02 16:30:00 UTC

Vote for approval (7 days)

  *   Start time: 2024-05-05 8:30:00 UTC
  *   End time: 2024-05-12 8:30:00 UTC

___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg

Re: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS structure according to RFC 3647

[Backman, Antti via Servercert-wg]

Telia changes its vote to ’no’ on Ballot SC-74

//Antti


Lähettäjä: Servercert-wg  käyttäjän 
Backman, Antti via Servercert-wg  puolesta
Lähetetty: tiistaina, toukokuuta 7, 2024 8:31 ip.
Vastaanottaja: Dimitris Zacharopoulos (HARICA) ; CA/B Forum 
Server Certificate WG Public Discussion List 
Aihe: Re: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS 
structure according to RFC 3647

Telia votes ’Yes’ on Ballot SC-074

//Antti


Lähettäjä: Servercert-wg  käyttäjän 
Dimitris Zacharopoulos (HARICA) via Servercert-wg  
puolesta
Lähetetty: sunnuntaina, toukokuuta 5, 2024 11:24 ap.
Vastaanottaja: CA/B Forum Server Certificate WG Public Discussion List 

Aihe: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS structure 
according to RFC 3647

Voting begins for ballot SC-74.
SC-74 - Clarify CP/CPS structure according to RFC 3647
Summary

The TLS Baseline Requirements require in section 2.2 that:

"The Certificate Policy and/or Certification Practice Statement MUST be 
structured in accordance with RFC 3647 and MUST include all material required 
by RFC 3647."

The intent of this language was to ensure that all CAs' CP and/or CPS documents 
contain a similar structure, making it easier to review and compare against the 
BRs. However, there was some ambiguity as to the actual structure that CAs 
should follow. After several discussions in the SCWG Public Mailing 
List<https://lists.cabforum.org/pipermail/servercert-wg/2023-November/004070.html>
 and F2F meetings, it was agreed that more clarity should be added to the 
existing requirement, pointing to the outline described in section 6 of RFC 
3647.

The following motion has been proposed by Dimitris Zacharopoulos (HARICA) and 
endorsed by Aaron Poulsen (Amazon) and Tim Hollebeek (Digicert).

You can view the github pull request representing this ballot 
here<https://github.com/cabforum/servercert/pull/503>.

Motion Begins

MODIFY the "Baseline Requirements for the Issuance and Management of 
Publicly-Trusted TLS Server Certificates" based on Version 2.0.4 as specified 
in the following redline:

  *   
https://github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae

Motion Ends

This ballot proposes a Final Maintenance Guideline. The procedure for approval 
of this ballot is as follows:

Discussion (at least 7 days)

  *   Start time: 2024-04-25 16:30:00 UTC
  *   End time: on or after 2024-05-02 16:30:00 UTC

Vote for approval (7 days)

  *   Start time: 2024-05-05 8:30:00 UTC
  *   End time: 2024-05-12 8:30:00 UTC


This email may contain information which is privileged or protected against 
unauthorized disclosure or communication. If you are not the intended 
recipient, please notify the sender and delete this message and any attachments 
from your system without producing, distributing or retaining copies thereof or 
disclosing its contents to any other person.

Telia Company processes emails and other files that may contain personal data 
in accordance with Telia Company’s Privacy 
Policy<https://www.teliacompany.com/en/about-the-company/privacy/>.


___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg

Re: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS structure according to RFC 3647

[Ben Wilson via Servercert-wg]

Mozilla changes its vote to "no" on Ballot SC-74 with the understanding
that additional edits are needed.

On Sun, May 5, 2024 at 1:05 PM Ben Wilson  wrote:

> Mozilla votes "yes" on Ballot SC-74.
>
> On Sun, May 5, 2024 at 3:06 AM Dimitris Zacharopoulos (HARICA) via
> Servercert-wg  wrote:
>
>> HARICA votes "yes" to ballot SC-74.
>>
>> On 5/5/2024 11:24 π.μ., Dimitris Zacharopoulos (HARICA) via Servercert-wg
>> wrote:
>>
>> Voting begins for ballot SC-74.
>> SC-74 - Clarify CP/CPS structure according to RFC 3647 Summary
>>
>> The TLS Baseline Requirements require in section 2.2 that:
>>
>> *"The Certificate Policy and/or Certification Practice Statement MUST be
>> structured in accordance with RFC 3647 and MUST include all material
>> required by RFC 3647."*
>>
>> The intent of this language was to ensure that all CAs' CP and/or CPS
>> documents contain a similar structure, making it easier to review and
>> compare against the BRs. However, there was some ambiguity as to the actual
>> structure that CAs should follow. After several discussions in the SCWG
>> Public Mailing List
>> 
>> and F2F meetings, it was agreed that more clarity should be added to the
>> existing requirement, pointing to the outline described in section 6 of RFC
>> 3647.
>>
>> The following motion has been proposed by Dimitris Zacharopoulos (HARICA)
>> and endorsed by Aaron Poulsen (Amazon) and Tim Hollebeek (Digicert).
>>
>> You can view the github pull request representing this ballot here
>> .
>> Motion Begins
>>
>> MODIFY the "Baseline Requirements for the Issuance and Management of
>> Publicly-Trusted TLS Server Certificates" based on Version 2.0.4 as
>> specified in the following redline:
>>
>>-
>>
>> https://github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae
>>
>> Motion Ends
>>
>> This ballot proposes a Final Maintenance Guideline. The procedure for
>> approval of this ballot is as follows:
>> Discussion (at least 7 days)
>>
>>- Start time: 2024-04-25 16:30:00 UTC
>>- End time: on or after 2024-05-02 16:30:00 UTC
>>
>> Vote for approval (7 days)
>>
>>- Start time: 2024-05-05 8:30:00 UTC
>>- End time: 2024-05-12 8:30:00 UTC
>>
>>
>>
>> ___
>> Servercert-wg mailing 
>> listServercert-wg@cabforum.orghttps://lists.cabforum.org/mailman/listinfo/servercert-wg
>>
>>
>> ___
>> Servercert-wg mailing list
>> Servercert-wg@cabforum.org
>> https://lists.cabforum.org/mailman/listinfo/servercert-wg
>>
>
___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg

Re: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS structure according to RFC 3647

[Marco Schambach via Servercert-wg]

IdenTrust also changes our vote to “No”  on Ballot SC-74 as the feedback from 
others make sense that this ballot requires further finetuning.

 

Marco S.

TrustID Program Manager 

 

From: Servercert-wg  On Behalf Of Marco 
Schambach via Servercert-wg
Sent: Tuesday, May 7, 2024 10:05 AM
To: Dimitris Zacharopoulos (HARICA) ; CA/B Forum Server 
Certificate WG Public Discussion List 
Subject: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS 
structure according to RFC 3647

 

IdenTrust votes “Yes” on Ballot SC-74

 

Marco S.

TrustID Program Manager 

 

From: Servercert-wg mailto:servercert-wg-boun...@cabforum.org> > On Behalf Of Dimitris 
Zacharopoulos (HARICA) via Servercert-wg
Sent: Sunday, May 5, 2024 4:25 AM
To: CA/B Forum Server Certificate WG Public Discussion List 
mailto:servercert-wg@cabforum.org> >
Subject: [External][Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify 
CP/CPS structure according to RFC 3647

 

Voting begins for ballot SC-74.


SC-74 - Clarify CP/CPS structure according to RFC 3647


Summary


The TLS Baseline Requirements require in section 2.2 that:

"The Certificate Policy and/or Certification Practice Statement MUST be 
structured in accordance with RFC 3647 and MUST include all material required 
by RFC 3647."

The intent of this language was to ensure that all CAs' CP and/or CPS documents 
contain a similar structure, making it easier to review and compare against the 
BRs. However, there was some ambiguity as to the actual structure that CAs 
should follow. After several discussions in the SCWG Public Mailing List 
<https://lists.cabforum.org/pipermail/servercert-wg/2023-November/004070.html>  
and F2F meetings, it was agreed that more clarity should be added to the 
existing requirement, pointing to the outline described in section 6 of RFC 
3647.

The following motion has been proposed by Dimitris Zacharopoulos (HARICA) and 
endorsed by Aaron Poulsen (Amazon) and Tim Hollebeek (Digicert). 

You can view the github pull request representing this ballot here 
<https://github.com/cabforum/servercert/pull/503> . 


Motion Begins


MODIFY the "Baseline Requirements for the Issuance and Management of 
Publicly-Trusted TLS Server Certificates" based on Version 2.0.4 as specified 
in the following redline:

*   
https://github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae
 


Motion Ends


This ballot proposes a Final Maintenance Guideline. The procedure for approval 
of this ballot is as follows:


Discussion (at least 7 days)


*   Start time: 2024-04-25 16:30:00 UTC
*   End time: on or after 2024-05-02 16:30:00 UTC


Vote for approval (7 days)


*   Start time: 2024-05-05 8:30:00 UTC
*   End time: 2024-05-12 8:30:00 UTC

 



smime.p7s
Description: S/MIME cryptographic signature
___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg

Re: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS structure according to RFC 3647

[Dimitris Zacharopoulos (HARICA) via Servercert-wg]

HARICA votes "no" to ballot SC-74.

Dimitris.

On 5/5/2024 12:06 μ.μ., Dimitris Zacharopoulos (HARICA) wrote:

HARICA votes "yes" to ballot SC-74.

On 5/5/2024 11:24 π.μ., Dimitris Zacharopoulos (HARICA) via 
Servercert-wg wrote:

Voting begins for ballot SC-74.


  SC-74 - Clarify CP/CPS structure according to RFC 3647


Summary

The TLS Baseline Requirements require in section 2.2 that:

/"The Certificate Policy and/or Certification Practice Statement MUST 
be structured in accordance with RFC 3647 and MUST include all 
material required by RFC 3647."/


The intent of this language was to ensure that all CAs' CP and/or CPS 
documents contain a similar structure, making it easier to review and 
compare against the BRs. However, there was some ambiguity as to the 
actual structure that CAs should follow. After several discussions in 
the SCWG Public Mailing List 
 
and F2F meetings, it was agreed that more clarity should be added to 
the existing requirement, pointing to the outline described in 
section 6 of RFC 3647.


The following motion has been proposed by Dimitris Zacharopoulos 
(HARICA) and endorsed by Aaron Poulsen (Amazon) and Tim Hollebeek 
(Digicert).


You can view the github pull request representing this ballot here 
.



Motion Begins

MODIFY the "Baseline Requirements for the Issuance and Management of 
Publicly-Trusted TLS Server Certificates" based on Version 2.0.4 as 
specified in the following redline:


  * 
https://github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae



Motion Ends

This ballot proposes a Final Maintenance Guideline. The procedure for 
approval of this ballot is as follows:



Discussion (at least 7 days)

  * Start time: 2024-04-25 16:30:00 UTC
  * End time: on or after 2024-05-02 16:30:00 UTC


Vote for approval (7 days)

  * Start time: 2024-05-05 8:30:00 UTC
  * End time: 2024-05-12 8:30:00 UTC



___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg


___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg

Re: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS structure according to RFC 3647

[Dimitris Zacharopoulos (HARICA) via Servercert-wg]

Based on comments received during -unfortunately- the voting period, it 
appears that more attention to detail like the case of the section 
headings, punctuation marks, etc need to be carefully reviewed before 
approving with this ballot.


I would like to recommend Members to change their vote to "no" so that 
the ballot fails and we can re-introduce it after we resolve these issues.



Thank you,
Dimitris.

On 5/5/2024 11:24 π.μ., Dimitris Zacharopoulos (HARICA) via 
Servercert-wg wrote:

Voting begins for ballot SC-74.


  SC-74 - Clarify CP/CPS structure according to RFC 3647


Summary

The TLS Baseline Requirements require in section 2.2 that:

/"The Certificate Policy and/or Certification Practice Statement MUST 
be structured in accordance with RFC 3647 and MUST include all 
material required by RFC 3647."/


The intent of this language was to ensure that all CAs' CP and/or CPS 
documents contain a similar structure, making it easier to review and 
compare against the BRs. However, there was some ambiguity as to the 
actual structure that CAs should follow. After several discussions in 
the SCWG Public Mailing List 
 
and F2F meetings, it was agreed that more clarity should be added to 
the existing requirement, pointing to the outline described in section 
6 of RFC 3647.


The following motion has been proposed by Dimitris Zacharopoulos 
(HARICA) and endorsed by Aaron Poulsen (Amazon) and Tim Hollebeek 
(Digicert).


You can view the github pull request representing this ballot here 
.



Motion Begins

MODIFY the "Baseline Requirements for the Issuance and Management of 
Publicly-Trusted TLS Server Certificates" based on Version 2.0.4 as 
specified in the following redline:


  * 
https://github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae



Motion Ends

This ballot proposes a Final Maintenance Guideline. The procedure for 
approval of this ballot is as follows:



Discussion (at least 7 days)

  * Start time: 2024-04-25 16:30:00 UTC
  * End time: on or after 2024-05-02 16:30:00 UTC


Vote for approval (7 days)

  * Start time: 2024-05-05 8:30:00 UTC
  * End time: 2024-05-12 8:30:00 UTC



___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg


___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg

Re: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS structure according to RFC 3647

[Rollin.Yu via Servercert-wg]

TrustAsia votes NO on Ballot SC-74.

Best regards,
Rollin Yu



> On May 5, 2024, at 16:24, Dimitris Zacharopoulos (HARICA) via Servercert-wg 
>  wrote:
> 
> Voting begins for ballot SC-74.
> SC-74 - Clarify CP/CPS structure according to RFC 3647
> 
> Summary
> 
> The TLS Baseline Requirements require in section 2.2 that:
> 
> "The Certificate Policy and/or Certification Practice Statement MUST be 
> structured in accordance with RFC 3647 and MUST include all material required 
> by RFC 3647."
> 
> The intent of this language was to ensure that all CAs' CP and/or CPS 
> documents contain a similar structure, making it easier to review and compare 
> against the BRs. However, there was some ambiguity as to the actual structure 
> that CAs should follow. After several discussions in the SCWG Public Mailing 
> List 
> 
>  and F2F meetings, it was agreed that more clarity should be added to the 
> existing requirement, pointing to the outline described in section 6 of RFC 
> 3647.
> 
> The following motion has been proposed by Dimitris Zacharopoulos (HARICA) and 
> endorsed by Aaron Poulsen (Amazon) and Tim Hollebeek (Digicert). 
> 
> You can view the github pull request representing this ballot here 
> . 
> 
> Motion Begins
> 
> MODIFY the "Baseline Requirements for the Issuance and Management of 
> Publicly-Trusted TLS Server Certificates" based on Version 2.0.4 as specified 
> in the following redline:
> 
> https://github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae
> Motion Ends
> 
> This ballot proposes a Final Maintenance Guideline. The procedure for 
> approval of this ballot is as follows:
> 
> Discussion (at least 7 days)
> 
> Start time: 2024-04-25 16:30:00 UTC
> End time: on or after 2024-05-02 16:30:00 UTC
> Vote for approval (7 days)
> 
> Start time: 2024-05-05 8:30:00 UTC
> End time: 2024-05-12 8:30:00 UTC
> 
> ___
> Servercert-wg mailing list
> Servercert-wg@cabforum.org
> https://lists.cabforum.org/mailman/listinfo/servercert-wg



smime.p7s
Description: S/MIME cryptographic signature
___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg

Re: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS structure according to RFC 3647

[Andrea Holland via Servercert-wg]

VikingCloud votes No on SC74.

Regards,
Andrea Holland

From: Servercert-wg  On Behalf Of Dimitris 
Zacharopoulos (HARICA) via Servercert-wg
Sent: Sunday, May 5, 2024 4:25 AM
To: CA/B Forum Server Certificate WG Public Discussion List 

Subject: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS 
structure according to RFC 3647


Caution: This email originated from outside of the organization. Do not click 
links or open attachments unless you recognize the sender and know the content 
is safe.

Voting begins for ballot SC-74.

SC-74 - Clarify CP/CPS structure according to RFC 3647
Summary

The TLS Baseline Requirements require in section 2.2 that:

"The Certificate Policy and/or Certification Practice Statement MUST be 
structured in accordance with RFC 3647 and MUST include all material required 
by RFC 3647."

The intent of this language was to ensure that all CAs' CP and/or CPS documents 
contain a similar structure, making it easier to review and compare against the 
BRs. However, there was some ambiguity as to the actual structure that CAs 
should follow. After several discussions in the SCWG Public Mailing 
List<https://lists.cabforum.org/pipermail/servercert-wg/2023-November/004070.html>
 and F2F meetings, it was agreed that more clarity should be added to the 
existing requirement, pointing to the outline described in section 6 of RFC 
3647.

The following motion has been proposed by Dimitris Zacharopoulos (HARICA) and 
endorsed by Aaron Poulsen (Amazon) and Tim Hollebeek (Digicert).

You can view the github pull request representing this ballot 
here<https://github.com/cabforum/servercert/pull/503>.

Motion Begins

MODIFY the "Baseline Requirements for the Issuance and Management of 
Publicly-Trusted TLS Server Certificates" based on Version 2.0.4 as specified 
in the following redline:

  *   
https://github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae

Motion Ends

This ballot proposes a Final Maintenance Guideline. The procedure for approval 
of this ballot is as follows:

Discussion (at least 7 days)

  *   Start time: 2024-04-25 16:30:00 UTC
  *   End time: on or after 2024-05-02 16:30:00 UTC

Vote for approval (7 days)

  *   Start time: 2024-05-05 8:30:00 UTC
  *   End time: 2024-05-12 8:30:00 UTC






Company Registration Details
VikingCloud is the registered business name of Sysxnet Limited. Sysxnet Limited 
is registered in Ireland under company registration number 147176 and its 
registered office is at 1st Floor, Block 71a, The Plaza, Park West Business 
Park, Dublin 12, Ireland.

Email Disclaimer
The information contained in this communication is intended solely for the use 
of the individual or entity to whom it is addressed and others authorized to 
receive it. It may contain confidential or legally privileged information. If 
you are not the intended recipient you are hereby notified that any disclosure, 
copying, distribution or taking any action in reliance on the contents of this 
information is strictly prohibited and may be unlawful. If you have received 
this communication in error, please notify us immediately by responding to this 
email and then delete it from your system. Sysxnet Limited is neither liable 
for the proper and complete transmission of the information contained in this 
communication nor for any delay in its receipt..
___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg

Re: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS structure according to RFC 3647

[Scott Rea via Servercert-wg]

eMudhra changes our vote to NO on Ballot SC-74

This is motivated by additional observations enumerated by DigiCert that this 
needs a little more work…

Regards,
_Scott


From: Servercert-wg  on behalf of Dimitris 
Zacharopoulos (HARICA) via Servercert-wg 
Date: Sunday, 5 May 2024 at 2:24 AM
To: CA/B Forum Server Certificate WG Public Discussion List 

Subject: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS 
structure according to RFC 3647
CAUTION: This email is originated from outside of the organization. Do not open 
the links or the attachments unless you recognize the sender and know the 
content is safe.

Voting begins for ballot SC-74.

SC-74 - Clarify CP/CPS structure according to RFC 3647
Summary

The TLS Baseline Requirements require in section 2.2 that:

"The Certificate Policy and/or Certification Practice Statement MUST be 
structured in accordance with RFC 3647 and MUST include all material required 
by RFC 3647."

The intent of this language was to ensure that all CAs' CP and/or CPS documents 
contain a similar structure, making it easier to review and compare against the 
BRs. However, there was some ambiguity as to the actual structure that CAs 
should follow. After several discussions in the SCWG Public Mailing 
List<https://lists.cabforum.org/pipermail/servercert-wg/2023-November/004070.html>
 and F2F meetings, it was agreed that more clarity should be added to the 
existing requirement, pointing to the outline described in section 6 of RFC 
3647.

The following motion has been proposed by Dimitris Zacharopoulos (HARICA) and 
endorsed by Aaron Poulsen (Amazon) and Tim Hollebeek (Digicert).

You can view the github pull request representing this ballot 
here<https://github.com/cabforum/servercert/pull/503>.

Motion Begins

MODIFY the "Baseline Requirements for the Issuance and Management of 
Publicly-Trusted TLS Server Certificates" based on Version 2.0.4 as specified 
in the following redline:

  *   
https://github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae

Motion Ends

This ballot proposes a Final Maintenance Guideline. The procedure for approval 
of this ballot is as follows:

Discussion (at least 7 days)

  *   Start time: 2024-04-25 16:30:00 UTC
  *   End time: on or after 2024-05-02 16:30:00 UTC

Vote for approval (7 days)

  *   Start time: 2024-05-05 8:30:00 UTC
  *   End time: 2024-05-12 8:30:00 UTC

Disclaimer: The email and its contents hold confidential information and are 
intended for the person or entity to which it is addressed. If you are not the 
intended recipient, please note that any distribution or copying of this email 
is strictly prohibited as per Company Policy, you are requested to notify the 
sender and delete the email and associated attachments with it from your system.
___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg

Re: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS structure according to RFC 3647

[Aaron Gable via Servercert-wg]

At the request of the authors, Let's Encrypt changes our vote on Ballot
SC-74 to No so that the ballot can be modified and resubmitted.

On Tue, May 7, 2024 at 3:21 PM Aaron Gable via Servercert-wg <
servercert-wg@cabforum.org> wrote:

> Let's Encrypt / ISRG votes Yes on Ballot SC-074.
>
> On Sun, May 5, 2024 at 1:24 AM Dimitris Zacharopoulos (HARICA) via
> Servercert-wg  wrote:
>
>> Voting begins for ballot SC-74.
>> SC-74 - Clarify CP/CPS structure according to RFC 3647 Summary
>>
>> The TLS Baseline Requirements require in section 2.2 that:
>>
>> *"The Certificate Policy and/or Certification Practice Statement MUST be
>> structured in accordance with RFC 3647 and MUST include all material
>> required by RFC 3647."*
>>
>> The intent of this language was to ensure that all CAs' CP and/or CPS
>> documents contain a similar structure, making it easier to review and
>> compare against the BRs. However, there was some ambiguity as to the actual
>> structure that CAs should follow. After several discussions in the SCWG
>> Public Mailing List
>> 
>> and F2F meetings, it was agreed that more clarity should be added to the
>> existing requirement, pointing to the outline described in section 6 of RFC
>> 3647.
>>
>> The following motion has been proposed by Dimitris Zacharopoulos (HARICA)
>> and endorsed by Aaron Poulsen (Amazon) and Tim Hollebeek (Digicert).
>>
>> You can view the github pull request representing this ballot here
>> .
>> Motion Begins
>>
>> MODIFY the "Baseline Requirements for the Issuance and Management of
>> Publicly-Trusted TLS Server Certificates" based on Version 2.0.4 as
>> specified in the following redline:
>>
>>-
>>
>> https://github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae
>>
>> Motion Ends
>>
>> This ballot proposes a Final Maintenance Guideline. The procedure for
>> approval of this ballot is as follows:
>> Discussion (at least 7 days)
>>
>>- Start time: 2024-04-25 16:30:00 UTC
>>- End time: on or after 2024-05-02 16:30:00 UTC
>>
>> Vote for approval (7 days)
>>
>>- Start time: 2024-05-05 8:30:00 UTC
>>- End time: 2024-05-12 8:30:00 UTC
>>
>>
>> ___
>> Servercert-wg mailing list
>> Servercert-wg@cabforum.org
>> https://lists.cabforum.org/mailman/listinfo/servercert-wg
>>
> ___
> Servercert-wg mailing list
> Servercert-wg@cabforum.org
> https://lists.cabforum.org/mailman/listinfo/servercert-wg
>
___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg

Re: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS structure according to RFC 3647

[Ponds-White, Trev via Servercert-wg]

Amazon Trust Services votes no based on the discussion in the Server Cert group 
call where it was determined we want to make an additional revision to this 
ballot.

From: Servercert-wg  On Behalf Of Dimitris 
Zacharopoulos (HARICA) via Servercert-wg
Sent: Sunday, May 5, 2024 1:24 AM
To: CA/B Forum Server Certificate WG Public Discussion List 

Subject: [EXTERNAL] [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify 
CP/CPS structure according to RFC 3647


CAUTION: This email originated from outside of the organization. Do not click 
links or open attachments unless you can confirm the sender and know the 
content is safe.


Voting begins for ballot SC-74.

SC-74 - Clarify CP/CPS structure according to RFC 3647
Summary

The TLS Baseline Requirements require in section 2.2 that:

"The Certificate Policy and/or Certification Practice Statement MUST be 
structured in accordance with RFC 3647 and MUST include all material required 
by RFC 3647."

The intent of this language was to ensure that all CAs' CP and/or CPS documents 
contain a similar structure, making it easier to review and compare against the 
BRs. However, there was some ambiguity as to the actual structure that CAs 
should follow. After several discussions in the SCWG Public Mailing 
List<https://lists.cabforum.org/pipermail/servercert-wg/2023-November/004070.html>
 and F2F meetings, it was agreed that more clarity should be added to the 
existing requirement, pointing to the outline described in section 6 of RFC 
3647.

The following motion has been proposed by Dimitris Zacharopoulos (HARICA) and 
endorsed by Aaron Poulsen (Amazon) and Tim Hollebeek (Digicert).

You can view the github pull request representing this ballot 
here<https://github.com/cabforum/servercert/pull/503>.

Motion Begins

MODIFY the "Baseline Requirements for the Issuance and Management of 
Publicly-Trusted TLS Server Certificates" based on Version 2.0.4 as specified 
in the following redline:

  *   
https://github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae

Motion Ends

This ballot proposes a Final Maintenance Guideline. The procedure for approval 
of this ballot is as follows:

Discussion (at least 7 days)

  *   Start time: 2024-04-25 16:30:00 UTC
  *   End time: on or after 2024-05-02 16:30:00 UTC

Vote for approval (7 days)

  *   Start time: 2024-05-05 8:30:00 UTC
  *   End time: 2024-05-12 8:30:00 UTC

___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg

Re: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS structure according to RFC 3647

[Doug Beattie via Servercert-wg]

GlobalSign changes our vote to NO on Ballot SC-74.

 

We agree with DigiCert’s observations that this needs a little more work:

The ballot is insufficiently clear about whether punctuation, capitalization, 
etc have to match exactly, and RFC 3647, which is Informative and was never 
intended to be used this way, is inconsistent itself in its use of 
capitalization and punctuation.

 

There needs to be additional clarity about exactly what the requirements are if 
we want to do this.

 

Doug

 

From: Servercert-wg  On Behalf Of Doug 
Beattie via Servercert-wg
Sent: Monday, May 6, 2024 6:41 AM
To: CA/B Forum Server Certificate WG Public Discussion List 

Subject: Re: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS 
structure according to RFC 3647

 

GlobalSign votes yes on SC-74.

 

Doug

 

From: Servercert-wg  On Behalf Of Dimitris 
Zacharopoulos (HARICA) via Servercert-wg
Sent: Sunday, May 5, 2024 4:25 AM
To: CA/B Forum Server Certificate WG Public Discussion List 

Subject: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS 
structure according to RFC 3647

 

Voting begins for ballot SC-74.


SC-74 - Clarify CP/CPS structure according to RFC 3647


Summary


The TLS Baseline Requirements require in section 2.2 that:

"The Certificate Policy and/or Certification Practice Statement MUST be 
structured in accordance with RFC 3647 and MUST include all material required 
by RFC 3647."

The intent of this language was to ensure that all CAs' CP and/or CPS documents 
contain a similar structure, making it easier to review and compare against the 
BRs. However, there was some ambiguity as to the actual structure that CAs 
should follow. After several discussions in the SCWG Public Mailing List 
<https://lists.cabforum.org/pipermail/servercert-wg/2023-November/004070.html>  
and F2F meetings, it was agreed that more clarity should be added to the 
existing requirement, pointing to the outline described in section 6 of RFC 
3647.

The following motion has been proposed by Dimitris Zacharopoulos (HARICA) and 
endorsed by Aaron Poulsen (Amazon) and Tim Hollebeek (Digicert). 

You can view the github pull request representing this ballot here 
<https://github.com/cabforum/servercert/pull/503> . 


Motion Begins


MODIFY the "Baseline Requirements for the Issuance and Management of 
Publicly-Trusted TLS Server Certificates" based on Version 2.0.4 as specified 
in the following redline:

*   
https://github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae
 


Motion Ends


This ballot proposes a Final Maintenance Guideline. The procedure for approval 
of this ballot is as follows:


Discussion (at least 7 days)


*   Start time: 2024-04-25 16:30:00 UTC
*   End time: on or after 2024-05-02 16:30:00 UTC


Vote for approval (7 days)


*   Start time: 2024-05-05 8:30:00 UTC
*   End time: 2024-05-12 8:30:00 UTC

 



smime.p7s
Description: S/MIME cryptographic signature
___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg

Re: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS structure according to RFC 3647

[Tim Hollebeek via Servercert-wg]

DigiCert votes NO on Ballot SC-74.



The ballot is insufficiently clear about whether punctuation, capitalization, 
etc have to match exactly, and RFC 3647, which is Informative and was never 
intended to be used this way, is inconsistent itself in its use of 
capitalization and punctuation.



There needs to be additional clarity about exactly what the requirements are 
if we want to do this.



-Tim



From: Servercert-wg  On Behalf Of Dimitris 
Zacharopoulos (HARICA) via Servercert-wg
Sent: Sunday, May 5, 2024 4:24 AM
To: CA/B Forum Server Certificate WG Public Discussion List 

Subject: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS 
structure according to RFC 3647



Voting begins for ballot SC-74.




SC-74 - Clarify CP/CPS structure according to RFC 3647


Summary


The TLS Baseline Requirements require in section 2.2 that:

"The Certificate Policy and/or Certification Practice Statement MUST be 
structured in accordance with RFC 3647 and MUST include all material required 
by RFC 3647."

The intent of this language was to ensure that all CAs' CP and/or CPS 
documents contain a similar structure, making it easier to review and compare 
against the BRs. However, there was some ambiguity as to the actual structure 
that CAs should follow. After several discussions in the SCWG Public Mailing 
List 
<https://url.avanan.click/v2/___https:/lists.cabforum.org/pipermail/servercert-wg/2023-November/004070.html___.YXAzOmRpZ2ljZXJ0OmE6bzozYzI2MWQxMjUxYTQyZjkzZjc5ZTc2YWM0MDc3NmJhNzo2OjBhNTk6YTQwZDgwNmE5Y2VkY2QwMTc1MTQyYTk2MTIyNTVmODBhNTM0YzIzOTI3MzE2ZDgwMDg3ZmVhMTAyMjcxZGQ2ODpoOkY>
 
and F2F meetings, it was agreed that more clarity should be added to the 
existing requirement, pointing to the outline described in section 6 of RFC 
3647.

The following motion has been proposed by Dimitris Zacharopoulos (HARICA) and 
endorsed by Aaron Poulsen (Amazon) and Tim Hollebeek (Digicert).

You can view the github pull request representing this ballot here 
<https://url.avanan.click/v2/___https:/github.com/cabforum/servercert/pull/503___.YXAzOmRpZ2ljZXJ0OmE6bzozYzI2MWQxMjUxYTQyZjkzZjc5ZTc2YWM0MDc3NmJhNzo2OmRmMzM6MDJlYjIwNGZmZjg3NjExOWMzM2IyODU3MjM3NGNjMWU0ZjBhYzExOTRhZmZmZjE5ZjY0OTZmNmU0YTljNmIyYjpoOkY>
 
.


Motion Begins


MODIFY the "Baseline Requirements for the Issuance and Management of 
Publicly-Trusted TLS Server Certificates" based on Version 2.0.4 as specified 
in the following redline:

* 
https://url.avanan.click/v2/___https://github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae___.YXAzOmRpZ2ljZXJ0OmE6bzozYzI2MWQxMjUxYTQyZjkzZjc5ZTc2YWM0MDc3NmJhNzo2OmIzOTE6ZDUwNjAwMjUzNmFmM2Y4YzAwNTc2NmVjODkwNWRkYjM4YWY5ODE3NmMzYWI5OTBmOTJkNGZmOWJmODc1MDA4NTp0OkY
 
<https://url.avanan.click/v2/___https:/github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae___.YXAzOmRpZ2ljZXJ0OmE6bzozYzI2MWQxMjUxYTQyZjkzZjc5ZTc2YWM0MDc3NmJhNzo2OjQzY2I6YjYyNzliYTI4Y2FlZWVmNjMyYjg3ZGRkZDVlMDg5NjNjZmY2ZjBlZjA0YzE5ZGM0NDllNmQxNGJlYTI0MDIzNzpoOkY>


Motion Ends


This ballot proposes a Final Maintenance Guideline. The procedure for approval 
of this ballot is as follows:


Discussion (at least 7 days)


*   Start time: 2024-04-25 16:30:00 UTC
*   End time: on or after 2024-05-02 16:30:00 UTC


Vote for approval (7 days)


*   Start time: 2024-05-05 8:30:00 UTC
*   End time: 2024-05-12 8:30:00 UTC





smime.p7s
Description: S/MIME cryptographic signature
___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg

Re: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS structure according to RFC 3647

[Mads Egil Henriksveen via Servercert-wg]

Buypass votes YES on ballot SC-74.

Regards
Mads

From: Servercert-wg  On Behalf Of Dimitris 
Zacharopoulos (HARICA) via Servercert-wg
Sent: Sunday, May 5, 2024 10:25 AM
To: CA/B Forum Server Certificate WG Public Discussion List 

Subject: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS 
structure according to RFC 3647

Voting begins for ballot SC-74.

SC-74 - Clarify CP/CPS structure according to RFC 3647
Summary

The TLS Baseline Requirements require in section 2.2 that:

"The Certificate Policy and/or Certification Practice Statement MUST be 
structured in accordance with RFC 3647 and MUST include all material required 
by RFC 3647."

The intent of this language was to ensure that all CAs' CP and/or CPS documents 
contain a similar structure, making it easier to review and compare against the 
BRs. However, there was some ambiguity as to the actual structure that CAs 
should follow. After several discussions in the SCWG Public Mailing 
List<https://lists.cabforum.org/pipermail/servercert-wg/2023-November/004070.html>
 and F2F meetings, it was agreed that more clarity should be added to the 
existing requirement, pointing to the outline described in section 6 of RFC 
3647.

The following motion has been proposed by Dimitris Zacharopoulos (HARICA) and 
endorsed by Aaron Poulsen (Amazon) and Tim Hollebeek (Digicert).

You can view the github pull request representing this ballot 
here<https://github.com/cabforum/servercert/pull/503>.

Motion Begins

MODIFY the "Baseline Requirements for the Issuance and Management of 
Publicly-Trusted TLS Server Certificates" based on Version 2.0.4 as specified 
in the following redline:

  *   
https://github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae

Motion Ends

This ballot proposes a Final Maintenance Guideline. The procedure for approval 
of this ballot is as follows:

Discussion (at least 7 days)

  *   Start time: 2024-04-25 16:30:00 UTC
  *   End time: on or after 2024-05-02 16:30:00 UTC

Vote for approval (7 days)

  *   Start time: 2024-05-05 8:30:00 UTC
  *   End time: 2024-05-12 8:30:00 UTC

___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg

Re: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS structure according to RFC 3647

[大野 文彰 via Servercert-wg]

SECOM Trust Systems votes YES on Ballot SC-74.

Best Regards,

ONO, Fumiaki
SECOM Trust Systems Co., Ltd.

From: Servercert-wg [mailto:servercert-wg-boun...@cabforum.org] On Behalf Of 
Dimitris Zacharopoulos (HARICA) via Servercert-wg
Sent: Sunday, May 5, 2024 5:25 PM
To: CA/B Forum Server Certificate WG Public Discussion List 

Subject: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS 
structure according to RFC 3647

Voting begins for ballot SC-74.

SC-74 - Clarify CP/CPS structure according to RFC 3647
Summary

The TLS Baseline Requirements require in section 2.2 that:

"The Certificate Policy and/or Certification Practice Statement MUST be 
structured in accordance with RFC 3647 and MUST include all material required 
by RFC 3647."

The intent of this language was to ensure that all CAs' CP and/or CPS documents 
contain a similar structure, making it easier to review and compare against the 
BRs. However, there was some ambiguity as to the actual structure that CAs 
should follow. After several discussions in the SCWG Public Mailing 
List<https://lists.cabforum.org/pipermail/servercert-wg/2023-November/004070.html>
 and F2F meetings, it was agreed that more clarity should be added to the 
existing requirement, pointing to the outline described in section 6 of RFC 
3647.

The following motion has been proposed by Dimitris Zacharopoulos (HARICA) and 
endorsed by Aaron Poulsen (Amazon) and Tim Hollebeek (Digicert).

You can view the github pull request representing this ballot 
here<https://github.com/cabforum/servercert/pull/503>.

Motion Begins

MODIFY the "Baseline Requirements for the Issuance and Management of 
Publicly-Trusted TLS Server Certificates" based on Version 2.0.4 as specified 
in the following redline:

  *   
https://github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae

Motion Ends

This ballot proposes a Final Maintenance Guideline. The procedure for approval 
of this ballot is as follows:

Discussion (at least 7 days)

  *   Start time: 2024-04-25 16:30:00 UTC
  *   End time: on or after 2024-05-02 16:30:00 UTC

Vote for approval (7 days)

  *   Start time: 2024-05-05 8:30:00 UTC
  *   End time: 2024-05-12 8:30:00 UTC

___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg

Re: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS structure according to RFC 3647

[Aaron Gable via Servercert-wg]

Let's Encrypt / ISRG votes Yes on Ballot SC-074.

On Sun, May 5, 2024 at 1:24 AM Dimitris Zacharopoulos (HARICA) via
Servercert-wg  wrote:

> Voting begins for ballot SC-74.
> SC-74 - Clarify CP/CPS structure according to RFC 3647 Summary
>
> The TLS Baseline Requirements require in section 2.2 that:
>
> *"The Certificate Policy and/or Certification Practice Statement MUST be
> structured in accordance with RFC 3647 and MUST include all material
> required by RFC 3647."*
>
> The intent of this language was to ensure that all CAs' CP and/or CPS
> documents contain a similar structure, making it easier to review and
> compare against the BRs. However, there was some ambiguity as to the actual
> structure that CAs should follow. After several discussions in the SCWG
> Public Mailing List
> 
> and F2F meetings, it was agreed that more clarity should be added to the
> existing requirement, pointing to the outline described in section 6 of RFC
> 3647.
>
> The following motion has been proposed by Dimitris Zacharopoulos (HARICA)
> and endorsed by Aaron Poulsen (Amazon) and Tim Hollebeek (Digicert).
>
> You can view the github pull request representing this ballot here
> .
> Motion Begins
>
> MODIFY the "Baseline Requirements for the Issuance and Management of
> Publicly-Trusted TLS Server Certificates" based on Version 2.0.4 as
> specified in the following redline:
>
>-
>
> https://github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae
>
> Motion Ends
>
> This ballot proposes a Final Maintenance Guideline. The procedure for
> approval of this ballot is as follows:
> Discussion (at least 7 days)
>
>- Start time: 2024-04-25 16:30:00 UTC
>- End time: on or after 2024-05-02 16:30:00 UTC
>
> Vote for approval (7 days)
>
>- Start time: 2024-05-05 8:30:00 UTC
>- End time: 2024-05-12 8:30:00 UTC
>
>
> ___
> Servercert-wg mailing list
> Servercert-wg@cabforum.org
> https://lists.cabforum.org/mailman/listinfo/servercert-wg
>
___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg

Re: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS structure according to RFC 3647

[Scott Rea via Servercert-wg]

eMudhra votes YES to ballot SC-74

From: Servercert-wg  on behalf of Dimitris 
Zacharopoulos (HARICA) via Servercert-wg 
Date: Sunday, 5 May 2024 at 2:24 AM
To: CA/B Forum Server Certificate WG Public Discussion List 

Subject: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS 
structure according to RFC 3647
CAUTION: This email is originated from outside of the organization. Do not open 
the links or the attachments unless you recognize the sender and know the 
content is safe.

Voting begins for ballot SC-74.

SC-74 - Clarify CP/CPS structure according to RFC 3647
Summary

The TLS Baseline Requirements require in section 2.2 that:

"The Certificate Policy and/or Certification Practice Statement MUST be 
structured in accordance with RFC 3647 and MUST include all material required 
by RFC 3647."

The intent of this language was to ensure that all CAs' CP and/or CPS documents 
contain a similar structure, making it easier to review and compare against the 
BRs. However, there was some ambiguity as to the actual structure that CAs 
should follow. After several discussions in the SCWG Public Mailing 
List<https://lists.cabforum.org/pipermail/servercert-wg/2023-November/004070.html>
 and F2F meetings, it was agreed that more clarity should be added to the 
existing requirement, pointing to the outline described in section 6 of RFC 
3647.

The following motion has been proposed by Dimitris Zacharopoulos (HARICA) and 
endorsed by Aaron Poulsen (Amazon) and Tim Hollebeek (Digicert).

You can view the github pull request representing this ballot 
here<https://github.com/cabforum/servercert/pull/503>.

Motion Begins

MODIFY the "Baseline Requirements for the Issuance and Management of 
Publicly-Trusted TLS Server Certificates" based on Version 2.0.4 as specified 
in the following redline:

  *   
https://github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae

Motion Ends

This ballot proposes a Final Maintenance Guideline. The procedure for approval 
of this ballot is as follows:

Discussion (at least 7 days)

  *   Start time: 2024-04-25 16:30:00 UTC
  *   End time: on or after 2024-05-02 16:30:00 UTC

Vote for approval (7 days)

  *   Start time: 2024-05-05 8:30:00 UTC
  *   End time: 2024-05-12 8:30:00 UTC

Disclaimer: The email and its contents hold confidential information and are 
intended for the person or entity to which it is addressed. If you are not the 
intended recipient, please note that any distribution or copying of this email 
is strictly prohibited as per Company Policy, you are requested to notify the 
sender and delete the email and associated attachments with it from your system.
___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg

Re: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS structure according to RFC 3647

[Backman, Antti via Servercert-wg]

Telia votes ’Yes’ on Ballot SC-074

//Antti


Lähettäjä: Servercert-wg  käyttäjän 
Dimitris Zacharopoulos (HARICA) via Servercert-wg  
puolesta
Lähetetty: sunnuntaina, toukokuuta 5, 2024 11:24 ap.
Vastaanottaja: CA/B Forum Server Certificate WG Public Discussion List 

Aihe: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS structure 
according to RFC 3647

Voting begins for ballot SC-74.
SC-74 - Clarify CP/CPS structure according to RFC 3647
Summary

The TLS Baseline Requirements require in section 2.2 that:

"The Certificate Policy and/or Certification Practice Statement MUST be 
structured in accordance with RFC 3647 and MUST include all material required 
by RFC 3647."

The intent of this language was to ensure that all CAs' CP and/or CPS documents 
contain a similar structure, making it easier to review and compare against the 
BRs. However, there was some ambiguity as to the actual structure that CAs 
should follow. After several discussions in the SCWG Public Mailing 
List<https://lists.cabforum.org/pipermail/servercert-wg/2023-November/004070.html>
 and F2F meetings, it was agreed that more clarity should be added to the 
existing requirement, pointing to the outline described in section 6 of RFC 
3647.

The following motion has been proposed by Dimitris Zacharopoulos (HARICA) and 
endorsed by Aaron Poulsen (Amazon) and Tim Hollebeek (Digicert).

You can view the github pull request representing this ballot 
here<https://github.com/cabforum/servercert/pull/503>.

Motion Begins

MODIFY the "Baseline Requirements for the Issuance and Management of 
Publicly-Trusted TLS Server Certificates" based on Version 2.0.4 as specified 
in the following redline:

  *   
https://github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae

Motion Ends

This ballot proposes a Final Maintenance Guideline. The procedure for approval 
of this ballot is as follows:

Discussion (at least 7 days)

  *   Start time: 2024-04-25 16:30:00 UTC
  *   End time: on or after 2024-05-02 16:30:00 UTC

Vote for approval (7 days)

  *   Start time: 2024-05-05 8:30:00 UTC
  *   End time: 2024-05-12 8:30:00 UTC


This email may contain information which is privileged or protected against 
unauthorized disclosure or communication. If you are not the intended 
recipient, please notify the sender and delete this message and any attachments 
from your system without producing, distributing or retaining copies thereof or 
disclosing its contents to any other person.

Telia Company processes emails and other files that may contain personal data 
in accordance with Telia Company’s Privacy 
Policy<https://www.teliacompany.com/en/about-the-company/privacy/>.


___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg

[Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS structure according to RFC 3647

[Marco Schambach via Servercert-wg]

IdenTrust votes “Yes” on Ballot SC-74

 

Marco S.

TrustID Program Manager 

 

From: Servercert-wg  On Behalf Of Dimitris 
Zacharopoulos (HARICA) via Servercert-wg
Sent: Sunday, May 5, 2024 4:25 AM
To: CA/B Forum Server Certificate WG Public Discussion List 

Subject: [External][Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify 
CP/CPS structure according to RFC 3647

 

Voting begins for ballot SC-74.




SC-74 - Clarify CP/CPS structure according to RFC 3647


Summary


The TLS Baseline Requirements require in section 2.2 that:

"The Certificate Policy and/or Certification Practice Statement MUST be 
structured in accordance with RFC 3647 and MUST include all material required 
by RFC 3647."

The intent of this language was to ensure that all CAs' CP and/or CPS documents 
contain a similar structure, making it easier to review and compare against the 
BRs. However, there was some ambiguity as to the actual structure that CAs 
should follow. After several discussions in the SCWG Public Mailing List 
<https://lists.cabforum.org/pipermail/servercert-wg/2023-November/004070.html>  
and F2F meetings, it was agreed that more clarity should be added to the 
existing requirement, pointing to the outline described in section 6 of RFC 
3647.

The following motion has been proposed by Dimitris Zacharopoulos (HARICA) and 
endorsed by Aaron Poulsen (Amazon) and Tim Hollebeek (Digicert). 

You can view the github pull request representing this ballot here 
<https://github.com/cabforum/servercert/pull/503> . 


Motion Begins


MODIFY the "Baseline Requirements for the Issuance and Management of 
Publicly-Trusted TLS Server Certificates" based on Version 2.0.4 as specified 
in the following redline:

*   
https://github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae
 


Motion Ends


This ballot proposes a Final Maintenance Guideline. The procedure for approval 
of this ballot is as follows:


Discussion (at least 7 days)


*   Start time: 2024-04-25 16:30:00 UTC
*   End time: on or after 2024-05-02 16:30:00 UTC


Vote for approval (7 days)


*   Start time: 2024-05-05 8:30:00 UTC
*   End time: 2024-05-12 8:30:00 UTC

 



smime.p7s
Description: S/MIME cryptographic signature
___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg

Re: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS structure according to RFC 3647

[lv_hui--- via Servercert-wg]

iTrusChina votes Yes to ballot SC-74



lv_...@itrus.cn
 
From: Dimitris Zacharopoulos (HARICA) via Servercert-wg
Date: 2024-05-05 16:24
To: CA/B Forum Server Certificate WG Public Discussion List
Subject: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS 
structure according to RFC 3647
Voting begins for ballot SC-74.
SC-74 - Clarify CP/CPS structure according to RFC 3647
Summary
The TLS Baseline Requirements require in section 2.2 that:
"The Certificate Policy and/or Certification Practice Statement MUST be 
structured in accordance with RFC 3647 and MUST include all material required 
by RFC 3647."
The intent of this language was to ensure that all CAs' CP and/or CPS documents 
contain a similar structure, making it easier to review and compare against the 
BRs. However, there was some ambiguity as to the actual structure that CAs 
should follow. After several discussions in the SCWG Public Mailing List and 
F2F meetings, it was agreed that more clarity should be added to the existing 
requirement, pointing to the outline described in section 6 of RFC 3647.
The following motion has been proposed by Dimitris Zacharopoulos (HARICA) and 
endorsed by Aaron Poulsen (Amazon) and Tim Hollebeek (Digicert). 
You can view the github pull request representing this ballot here. 
Motion Begins
MODIFY the "Baseline Requirements for the Issuance and Management of 
Publicly-Trusted TLS Server Certificates" based on Version 2.0.4 as specified 
in the following redline:
https://github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae
 
Motion Ends
This ballot proposes a Final Maintenance Guideline. The procedure for approval 
of this ballot is as follows:
Discussion (at least 7 days)
Start time: 2024-04-25 16:30:00 UTC
End time: on or after 2024-05-02 16:30:00 UTC
Vote for approval (7 days)
Start time: 2024-05-05 8:30:00 UTC
End time: 2024-05-12 8:30:00 UTC

___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg

Re: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS structure according to RFC 3647

[Brittany Randall via Servercert-wg]

GoDaddy votes Yes on SC-74

Best,

Brittany Randall


From: Servercert-wg  on behalf of Dimitris 
Zacharopoulos (HARICA) via Servercert-wg 
Sent: Sunday, May 5, 2024 1:24 AM
To: CA/B Forum Server Certificate WG Public Discussion List 

Subject: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS 
structure according to RFC 3647

Caution: This email is from an external sender. Please do not click links or 
open attachments unless you recognize the sender and know the content is safe. 
Forward suspicious emails to isitbad@.



Voting begins for ballot SC-74.
SC-74 - Clarify CP/CPS structure according to RFC 3647
Summary

The TLS Baseline Requirements require in section 2.2 that:

"The Certificate Policy and/or Certification Practice Statement MUST be 
structured in accordance with RFC 3647 and MUST include all material required 
by RFC 3647."

The intent of this language was to ensure that all CAs' CP and/or CPS documents 
contain a similar structure, making it easier to review and compare against the 
BRs. However, there was some ambiguity as to the actual structure that CAs 
should follow. After several discussions in the SCWG Public Mailing 
List<https://lists.cabforum.org/pipermail/servercert-wg/2023-November/004070.html>
 and F2F meetings, it was agreed that more clarity should be added to the 
existing requirement, pointing to the outline described in section 6 of RFC 
3647.

The following motion has been proposed by Dimitris Zacharopoulos (HARICA) and 
endorsed by Aaron Poulsen (Amazon) and Tim Hollebeek (Digicert).

You can view the github pull request representing this ballot 
here<https://github.com/cabforum/servercert/pull/503>.

Motion Begins

MODIFY the "Baseline Requirements for the Issuance and Management of 
Publicly-Trusted TLS Server Certificates" based on Version 2.0.4 as specified 
in the following redline:

  *   
https://github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae

Motion Ends

This ballot proposes a Final Maintenance Guideline. The procedure for approval 
of this ballot is as follows:

Discussion (at least 7 days)

  *   Start time: 2024-04-25 16:30:00 UTC
  *   End time: on or after 2024-05-02 16:30:00 UTC

Vote for approval (7 days)

  *   Start time: 2024-05-05 8:30:00 UTC
  *   End time: 2024-05-12 8:30:00 UTC

___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg

Re: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS structure according to RFC 3647

[Doug Beattie via Servercert-wg]

GlobalSign votes yes on SC-74.



Doug



From: Servercert-wg  On Behalf Of Dimitris 
Zacharopoulos (HARICA) via Servercert-wg
Sent: Sunday, May 5, 2024 4:25 AM
To: CA/B Forum Server Certificate WG Public Discussion List 

Subject: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS 
structure according to RFC 3647



Voting begins for ballot SC-74.




SC-74 - Clarify CP/CPS structure according to RFC 3647


Summary


The TLS Baseline Requirements require in section 2.2 that:

"The Certificate Policy and/or Certification Practice Statement MUST be 
structured in accordance with RFC 3647 and MUST include all material required 
by RFC 3647."

The intent of this language was to ensure that all CAs' CP and/or CPS 
documents contain a similar structure, making it easier to review and compare 
against the BRs. However, there was some ambiguity as to the actual structure 
that CAs should follow. After several discussions in the SCWG Public Mailing 
List 
<https://lists.cabforum.org/pipermail/servercert-wg/2023-November/004070.html> 
and F2F meetings, it was agreed that more clarity should be added to the 
existing requirement, pointing to the outline described in section 6 of RFC 
3647.

The following motion has been proposed by Dimitris Zacharopoulos (HARICA) and 
endorsed by Aaron Poulsen (Amazon) and Tim Hollebeek (Digicert).

You can view the github pull request representing this ballot here 
<https://github.com/cabforum/servercert/pull/503> .


Motion Begins


MODIFY the "Baseline Requirements for the Issuance and Management of 
Publicly-Trusted TLS Server Certificates" based on Version 2.0.4 as specified 
in the following redline:

* 
https://github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae


Motion Ends


This ballot proposes a Final Maintenance Guideline. The procedure for approval 
of this ballot is as follows:


Discussion (at least 7 days)


*   Start time: 2024-04-25 16:30:00 UTC
*   End time: on or after 2024-05-02 16:30:00 UTC


Vote for approval (7 days)


*   Start time: 2024-05-05 8:30:00 UTC
*   End time: 2024-05-12 8:30:00 UTC





smime.p7s
Description: S/MIME cryptographic signature
___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg

Re: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS structure according to RFC 3647

[chtsai]

TWCA votes "yes" to ballot SC-74.


From: Servercert-wg  On Behalf Of Dimitris 
Zacharopoulos (HARICA) via Servercert-wg
Sent: Sunday, May 5, 2024 4:25 PM
To: CA/B Forum Server Certificate WG Public Discussion List 

Subject: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS 
structure according to RFC 3647

Voting begins for ballot SC-74.

SC-74 - Clarify CP/CPS structure according to RFC 3647
Summary

The TLS Baseline Requirements require in section 2.2 that:

"The Certificate Policy and/or Certification Practice Statement MUST be 
structured in accordance with RFC 3647 and MUST include all material required 
by RFC 3647."

The intent of this language was to ensure that all CAs' CP and/or CPS documents 
contain a similar structure, making it easier to review and compare against the 
BRs. However, there was some ambiguity as to the actual structure that CAs 
should follow. After several discussions in the SCWG Public Mailing 
List<https://lists.cabforum.org/pipermail/servercert-wg/2023-November/004070.html>
 and F2F meetings, it was agreed that more clarity should be added to the 
existing requirement, pointing to the outline described in section 6 of RFC 
3647.

The following motion has been proposed by Dimitris Zacharopoulos (HARICA) and 
endorsed by Aaron Poulsen (Amazon) and Tim Hollebeek (Digicert).

You can view the github pull request representing this ballot 
here<https://github.com/cabforum/servercert/pull/503>.

Motion Begins

MODIFY the "Baseline Requirements for the Issuance and Management of 
Publicly-Trusted TLS Server Certificates" based on Version 2.0.4 as specified 
in the following redline:

  *   
https://github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae

Motion Ends

This ballot proposes a Final Maintenance Guideline. The procedure for approval 
of this ballot is as follows:

Discussion (at least 7 days)

  *   Start time: 2024-04-25 16:30:00 UTC
  *   End time: on or after 2024-05-02 16:30:00 UTC

Vote for approval (7 days)

  *   Start time: 2024-05-05 8:30:00 UTC
  *   End time: 2024-05-12 8:30:00 UTC

___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg

Re: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS structure according to RFC 3647

[BILGEM KSM]

Kamu SM votes "yes" on Ballot SC-74. 




Tuğba ÖZCAN 

Head Of e-Signature Technologies Department 



TÜBİTAK/BİLGEM/Kamu SM 

Çamlıca Mahallesi 408. Cadde No: 136 

C Blok 5. Kat Yenimahalle/Ankara 

Dahili:8543 




tugba.oz...@tubitak.gov.tr 


Kimden: "CA"  
Kime: "Dimitris Zacharopoulos, HARICA" , "CA" 
 
Gönderilenler: 5 Mayıs Pazar 2024 22:05:35 
Konu: Re: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS 
structure according to RFC 3647 

Mozilla votes "yes" on Ballot SC-74. 

On Sun, May 5, 2024 at 3:06 AM Dimitris Zacharopoulos (HARICA) via 
Servercert-wg < [ mailto:servercert-wg@cabforum.org | 
servercert-wg@cabforum.org ] > wrote: 



HARICA votes "yes" to ballot SC-74. 

On 5/5/2024 11:24 π.μ., Dimitris Zacharopoulos (HARICA) via Servercert-wg 
wrote: 

BQ_BEGIN
Voting begins for ballot SC-74. 
SC-74 - Clarify CP/CPS structure according to RFC 3647 
Summary 


The TLS Baseline Requirements require in section 2.2 that: 

"The Certificate Policy and/or Certification Practice Statement MUST be 
structured in accordance with RFC 3647 and MUST include all material required 
by RFC 3647." 

The intent of this language was to ensure that all CAs' CP and/or CPS documents 
contain a similar structure, making it easier to review and compare against the 
BRs. However, there was some ambiguity as to the actual structure that CAs 
should follow. After several discussions in the [ 
https://lists.cabforum.org/pipermail/servercert-wg/2023-November/004070.html | 
SCWG Public Mailing List ] and F2F meetings, it was agreed that more clarity 
should be added to the existing requirement, pointing to the outline described 
in section 6 of RFC 3647. 

The following motion has been proposed by Dimitris Zacharopoulos (HARICA) and 
endorsed by Aaron Poulsen (Amazon) and Tim Hollebeek (Digicert). 


You can view the github pull request representing this ballot [ 
https://github.com/cabforum/servercert/pull/503 | here ] . 
Motion Begins 


MODIFY the "Baseline Requirements for the Issuance and Management of 
Publicly-Trusted TLS Server Certificates" based on Version 2.0.4 as specified 
in the following redline: 


* [ 
https://github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae
 | 
https://github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae
 ] 
Motion Ends 


This ballot proposes a Final Maintenance Guideline. The procedure for approval 
of this ballot is as follows: Discussion (at least 7 days) 


* Start time: 2024-04-25 16:30:00 UTC 
* End time: on or after 2024-05-02 16:30:00 UTC 
Vote for approval (7 days) 


* Start time: 2024-05-05 8:30:00 UTC 
* End time: 2024-05-12 8:30:00 UTC 


___
Servercert-wg mailing list [ mailto:Servercert-wg@cabforum.org | 
Servercert-wg@cabforum.org ] [ 
https://lists.cabforum.org/mailman/listinfo/servercert-wg | 
https://lists.cabforum.org/mailman/listinfo/servercert-wg ] 



___ 
Servercert-wg mailing list 
[ mailto:Servercert-wg@cabforum.org | Servercert-wg@cabforum.org ] 
[ https://lists.cabforum.org/mailman/listinfo/servercert-wg | 
https://lists.cabforum.org/mailman/listinfo/servercert-wg ] 

BQ_END


___ 
Servercert-wg mailing list 
Servercert-wg@cabforum.org 
https://lists.cabforum.org/mailman/listinfo/servercert-wg 
___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg

Re: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS structure according to RFC 3647

[Ben Wilson via Servercert-wg]

Mozilla votes "yes" on Ballot SC-74.

On Sun, May 5, 2024 at 3:06 AM Dimitris Zacharopoulos (HARICA) via
Servercert-wg  wrote:

> HARICA votes "yes" to ballot SC-74.
>
> On 5/5/2024 11:24 π.μ., Dimitris Zacharopoulos (HARICA) via Servercert-wg
> wrote:
>
> Voting begins for ballot SC-74.
> SC-74 - Clarify CP/CPS structure according to RFC 3647 Summary
>
> The TLS Baseline Requirements require in section 2.2 that:
>
> *"The Certificate Policy and/or Certification Practice Statement MUST be
> structured in accordance with RFC 3647 and MUST include all material
> required by RFC 3647."*
>
> The intent of this language was to ensure that all CAs' CP and/or CPS
> documents contain a similar structure, making it easier to review and
> compare against the BRs. However, there was some ambiguity as to the actual
> structure that CAs should follow. After several discussions in the SCWG
> Public Mailing List
> 
> and F2F meetings, it was agreed that more clarity should be added to the
> existing requirement, pointing to the outline described in section 6 of RFC
> 3647.
>
> The following motion has been proposed by Dimitris Zacharopoulos (HARICA)
> and endorsed by Aaron Poulsen (Amazon) and Tim Hollebeek (Digicert).
>
> You can view the github pull request representing this ballot here
> .
> Motion Begins
>
> MODIFY the "Baseline Requirements for the Issuance and Management of
> Publicly-Trusted TLS Server Certificates" based on Version 2.0.4 as
> specified in the following redline:
>
>-
>
> https://github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae
>
> Motion Ends
>
> This ballot proposes a Final Maintenance Guideline. The procedure for
> approval of this ballot is as follows:
> Discussion (at least 7 days)
>
>- Start time: 2024-04-25 16:30:00 UTC
>- End time: on or after 2024-05-02 16:30:00 UTC
>
> Vote for approval (7 days)
>
>- Start time: 2024-05-05 8:30:00 UTC
>- End time: 2024-05-12 8:30:00 UTC
>
>
>
> ___
> Servercert-wg mailing 
> listServercert-wg@cabforum.orghttps://lists.cabforum.org/mailman/listinfo/servercert-wg
>
>
> ___
> Servercert-wg mailing list
> Servercert-wg@cabforum.org
> https://lists.cabforum.org/mailman/listinfo/servercert-wg
>
___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg

Re: [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS structure according to RFC 3647

[Dimitris Zacharopoulos (HARICA) via Servercert-wg]

HARICA votes "yes" to ballot SC-74.

On 5/5/2024 11:24 π.μ., Dimitris Zacharopoulos (HARICA) via 
Servercert-wg wrote:

Voting begins for ballot SC-74.


  SC-74 - Clarify CP/CPS structure according to RFC 3647


Summary

The TLS Baseline Requirements require in section 2.2 that:

/"The Certificate Policy and/or Certification Practice Statement MUST 
be structured in accordance with RFC 3647 and MUST include all 
material required by RFC 3647."/


The intent of this language was to ensure that all CAs' CP and/or CPS 
documents contain a similar structure, making it easier to review and 
compare against the BRs. However, there was some ambiguity as to the 
actual structure that CAs should follow. After several discussions in 
the SCWG Public Mailing List 
 
and F2F meetings, it was agreed that more clarity should be added to 
the existing requirement, pointing to the outline described in section 
6 of RFC 3647.


The following motion has been proposed by Dimitris Zacharopoulos 
(HARICA) and endorsed by Aaron Poulsen (Amazon) and Tim Hollebeek 
(Digicert).


You can view the github pull request representing this ballot here 
.



Motion Begins

MODIFY the "Baseline Requirements for the Issuance and Management of 
Publicly-Trusted TLS Server Certificates" based on Version 2.0.4 as 
specified in the following redline:


  * 
https://github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae



Motion Ends

This ballot proposes a Final Maintenance Guideline. The procedure for 
approval of this ballot is as follows:



Discussion (at least 7 days)

  * Start time: 2024-04-25 16:30:00 UTC
  * End time: on or after 2024-05-02 16:30:00 UTC


Vote for approval (7 days)

  * Start time: 2024-05-05 8:30:00 UTC
  * End time: 2024-05-12 8:30:00 UTC



___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg
___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg

[Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS structure according to RFC 3647

[Dimitris Zacharopoulos (HARICA) via Servercert-wg]

Voting begins for ballot SC-74.


 SC-74 - Clarify CP/CPS structure according to RFC 3647


   Summary

The TLS Baseline Requirements require in section 2.2 that:

/"The Certificate Policy and/or Certification Practice Statement MUST be 
structured in accordance with RFC 3647 and MUST include all material 
required by RFC 3647."/


The intent of this language was to ensure that all CAs' CP and/or CPS 
documents contain a similar structure, making it easier to review and 
compare against the BRs. However, there was some ambiguity as to the 
actual structure that CAs should follow. After several discussions in 
the SCWG Public Mailing List 
 
and F2F meetings, it was agreed that more clarity should be added to the 
existing requirement, pointing to the outline described in section 6 of 
RFC 3647.


The following motion has been proposed by Dimitris Zacharopoulos 
(HARICA) and endorsed by Aaron Poulsen (Amazon) and Tim Hollebeek 
(Digicert).


You can view the github pull request representing this ballot here 
.



   Motion Begins

MODIFY the "Baseline Requirements for the Issuance and Management of 
Publicly-Trusted TLS Server Certificates" based on Version 2.0.4 as 
specified in the following redline:


 * 
https://github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae



   Motion Ends

This ballot proposes a Final Maintenance Guideline. The procedure for 
approval of this ballot is as follows:



   Discussion (at least 7 days)

 * Start time: 2024-04-25 16:30:00 UTC
 * End time: on or after 2024-05-02 16:30:00 UTC


   Vote for approval (7 days)

 * Start time: 2024-05-05 8:30:00 UTC
 * End time: 2024-05-12 8:30:00 UTC

___
Servercert-wg mailing list
Servercert-wg@cabforum.org
https://lists.cabforum.org/mailman/listinfo/servercert-wg