[cabfpub] **List of CABF Members, Associate Members, and Interested Parties who have declared their "participation" in the Server Certificate Working Group - please check for your name**
Moudrick M. Dadashov
md at ssc.lt
Wed Jul 4 21:16:28 UTC 2018
SSC declares its participation in the Server Certificate Working Group
(wiki updated).
Thanks,
M.D.
On 7/4/2018 2:23 AM, Kirk Hall via Public wrote:
>
> As noted in my prior emails, as of the Ballot 206 effective date of
> July 3, 2018, all Forum Members, Associate Members, and Interested
> Parties must do two things: (1) sign and return the IPR Agreement
> v1.3, and (2) declare their “participation” in a Chartered Working
> Group. There is only one Chartered Working Group at present – the
> Server Certificate Working Group (SCWG), which will take over most of
> the substantive discussion about server certificate requirements from
> the old CA/Browser Forum.
>
> *_I have listed below all the declarations of “participation” in the
> SCWG that we have received to date_.* (Note: it’s possible we missed
> some declarations – if you informed me or Ben of your “participation”
> in the SCWG and are not listed below, accept our apologies and _please
> inform us again_.)
>
> *_If you are a Forum Member or Associate Member and your name is not
> on the list_* – please add it via the wiki page here:
>
> https://www.cabforum.org/wiki/Server%20Certificate%20Working%20Group
>
> If you have any difficulties in posting to the wiki, please send your
> declaration of “participation” to me or to Ben, and we will add it.
>
> If you are an Interested Party and want to “participate”, you can’t
> post directly to the wiki, *_so please send an email to me or Ben and
> we will add it_*.
>
> Finally, please note that you will lose your status as a Member,
> Associate Member, or Interested Party if you fail to sign and return
> the IPR Agreement v1.3 – to remain in your current status, you must
> BOTH sign and return the IPRA v1.3, AND declare your “participation”
> in the Server Certificate Working Group. For Interested Parties - You
> can download the IPR Agreement v1.3 here – please sign and return to
> me. If you don’t return a signed IPRA v1.3, you will lose your right
> as an Interested Party to post to the Forum and Working Group list.
>
> https://cabforum.org/wp-content/uploads/CAB-Forum-Agreement-for-IPR-Policy_20FEB18.pdf
>
> https://cabforum.org/ipr-policy/
>
> https://cabforum.org/wp-content/uploads/CABF-IPR-Policy-v.1.3_4APR18.pdf
>
> ***
>
>
> *Server Certificate Working Group (as of July 3, 2018)*
>
> The following have formally declared their participation in the Server
> Certificate Working Group:
>
> Type 1 = Certificate Issuer 2 = Root Certificate Issuer 3 =
> Certificate Consumer 4 = Associate Member 5 = Interested Party
>
> *Root Certificate Issuer, Certificate Issuer*
>
> Name
>
>
>
> Date of Declaration
>
>
>
> Type
>
>
>
> Date of Withdrawal
>
> Actalis S.p.A.
>
>
>
> 2 July 2018
>
>
>
> Certificate Issuer
>
>
>
> Buypass AS
>
>
>
> 3 July 2018
>
>
>
> Root Certificate Issuer, Certificate Issuer
>
>
>
> Certigna
>
>
>
> 2 July 2018
>
>
>
> Certificate Issuer
>
>
>
> Digicert, Inc.
>
>
>
> 28 June 2018
>
>
>
> Root Certificate Issuer, Certificate Issuer
>
>
>
> Disig, a.s.
>
>
>
> 2 July 2018
>
>
>
> Certificate Issuer
>
>
>
> Entrust Datacard
>
>
>
> 29 June 2018
>
>
>
> Root Certificate Issuer, Certificate Issuer
>
>
>
> GlobalSign
>
>
>
> 29 June 2018
>
>
>
> Root Certificate Issuer, Certificate Issuer
>
>
>
> HARICA
>
>
>
> 2 July 2018
>
>
>
> Certificate Issuer
>
>
>
> KPN
>
>
>
> 3 July 2018
>
>
>
> Certificate Issuer
>
>
>
> Logius PKIoverheid
>
>
>
> 2 July 2018
>
>
>
> Root Certificate Issuer
>
>
>
> Trustwave
>
>
>
> 29 June 2018
>
>
>
> Root Certificate Issuer, Certificate Issuer
>
>
>
> TWCA
>
>
>
> 2 July 2018
>
>
>
> Certificate Issuer
>
>
>
> **
>
> *Certificate Consumer*
>
> Name
>
>
>
> Date of Declaration
>
>
>
> Type
>
>
>
> Date of Withdrawal
>
> Cisco Systems
>
>
>
> 28 June 2018
>
>
>
> Certificate Consumer
>
>
>
> Comodo Security Solutions
>
>
>
> 29 June 2018
>
>
>
> Certificate Consumer
>
>
>
> Google
>
>
>
> 3 July 2018
>
>
>
> Certificate Consumer
>
>
>
> Microsoft
>
>
>
> 29 June 2018
>
>
>
> Certificate Consumer
>
>
>
> **
>
> *Associate Member*
>
> Name
>
>
>
> Date of Declaration
>
>
>
> Type
>
>
>
> Date of Withdrawal
>
> CPA Canada
>
>
>
> 3 July 2018
>
>
>
> Associate Member
>
>
>
> **
>
> *Interested Party*
>
> Name
>
>
>
> Date of Declaration
>
>
>
> Type
>
>
>
> Date of Withdrawal
>
> Andrew Ayer
>
>
>
> 3 July 2018
>
>
>
> Interested Party
>
>
>
> Carl Mehner
>
>
>
> 3 July 2018
>
>
>
> Interested Party
>
>
>
> Dark Matter
>
>
>
> 3 July 2018
>
>
>
> Interested Party
>
>
>
> (1) Certificate Issuer: The member organization operates a
> certification authority that has a current and successful WebTrust for
> CAs audit, or ETSI TS 102042, ETSI 101456, or ETSI EN 319 411-1 audit
> report prepared by a properly-qualified auditor, and that actively
> issues certificates to Web servers that are openly accessible from the
> Internet, such certificates being treated as valid when using a
> browser created by a Certificate Consumer Member. Applicants that are
> not actively issuing certificates but otherwise meet membership
> criteria may be granted Associate Member status under Bylaw Sec. 3.1
> for a period of time to be designated by the Forum.
>
> (2) Root Certificate Issuer: The member organization operates a
> certification authority that has a current and successful WebTrust for
> CAs, or ETSI TS 102042, ETSI TS 101456, ETSI EN 319 411-1 audit report
> prepared by a properly-qualified auditor, and that actively issues
> certificates to subordinate CAs that, in turn, actively issue
> certificates to Web servers that are openly accessible from the
> Internet, such certificates being treated as valid when using a
> browser created by a Certificate Consumer Member. Applicants that are
> not actively issuing certificates but otherwise meet membership
> criteria may be granted Associate Member status under Bylaw Sec. 3.1
> for a period of time to be designated by the Forum.
>
> (3) A Certificate Consumer can participate in this Working Group if it
> produces a software product intended for use by the general public for
> browsing the Web securely.
>
>
>
> _______________________________________________
> Public mailing list
> Public at cabforum.org
> https://cabforum.org/mailman/listinfo/public
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cabforum.org/pipermail/public/attachments/20180705/d4fd9f9d/attachment-0003.html>
More information about the Public
mailing list