SG Trust Services root inclusion request for email trust bit

This case is a Mozilla root inclusion request for SG Trust Services’ "SG TRUST SERVICES RACINE" root certificate. The request was opened by Sylvain Rossi on behalf of SG Trust Services and initially asked for inclusion of the root with the email trust bit enabled. Mozilla reviewed the CA’s organization, certificate policies, verification practices, CRL access, and audit evidence over multiple rounds of questions and document updates. During the review, SG Trust Services clarified that it was only asking for the S/MIME/email trust bit, and Mozilla later summarized the request as meeting the stated requirements. On 2013-04-11, Mozilla approved inclusion of the "SG TRUST SERVICES RACINE" root certificate with email trust enabled and filed the corresponding NSS bug #860929. The bug was later resolved as FIXED.

1. 2011-06-06 SG Trust Services requested Mozilla root inclusion for the "SG TRUST SERVICES RACINE" root certificate.
2. 2011-09-05 SG Trust Services provided updated CRL endpoints for the hierarchy.
3. 2012-03-23 Concerns were raised about example certificate chaining, policy OIDs, and a CRL revocation reason.
4. 2013-03-13 SG Trust Services clarified that it was only requesting the email (S/MIME) trust bit.
5. 2013-04-11 Mozilla approved inclusion of the "SG TRUST SERVICES RACINE" root certificate with email trust enabled.

1. 2011-06-06 Sealweb representative — Opened the bug and provided the initial inclusion request, CP/CPS links, and root certificate attachment.
2. 2011-06-20 Mozilla representative — Accepted the bug and began review of the submitted information.
3. 2011-07-21 Mozilla representative — Asked that Joël Dupont be added to the CC list as the authorized ongoing point of contact.
4. 2011-09-20 Mozilla representative — Asked SG Trust Services to respond to the CA Communication action items.
5. 2012-05-03 Docusign representative — Raised technical questions about certificatePolicies constraints and a CRL revocation reason, and later said his questions were sufficiently addressed.
6. 2012-11-15 Mozilla representative — Opened the first public discussion period for the request.
7. 2013-03-13 Sealweb representative — Confirmed that SG Trust Services only wanted the email trust bit enabled.
8. 2013-04-08 Mozilla representative — Summarized the assessment and stated intent to approve the request.
9. 2013-04-11 Mozilla representative — Approved inclusion of the root certificate with email trust enabled and filed NSS bug 860929.