Collect the full set of URLs for all CRLs used by SECOM Trust

This case is about collecting the full set of CRL URLs used by SECOM Trust Systems CO., LTD. for its EV certificates. The issue was triggered by a question about whether SECOM uses full or incremental CRLs for EV certificates. SECOM’s representative (via communication relayed in the thread) stated that SECOM does not employ incremental CRLs for EV certificates and that it uses a full CRL for EV certificates. The thread includes the EV certificate CRLDP information showing a CRL Distribution Point URL at http://repo1.secomtrust.net/spcpp/pfw/pfwevca/fullcrl.crl. The Mozilla CA Program participant indicated they understood this to mean SECOM uses a single complete CRL for EV certificates and that the data at that URL is small (< 2KB). The bug was resolved as FIXED, with the resolver noting they could not fully confirm the problem was fixed until dependent bugs (477244 and 474606) were resolved, but that SECOM had answered the questions for the moment.

1. 2009-02-06 Mozilla CA Program requested confirmation of the CRL URL set used for SECOM EV certificates and received CRLDP details indicating full CRL usage.
2. 2009-02-11 The reporter resolved the bug after receiving sufficient answers for the moment, while noting dependent bugs still needed resolution.

1. 2009-02-06 Johnath representative — Reported SECOM’s response: no incremental CRLs for EV; EV uses a full CRL at http://repo1.secomtrust.net/spcpp/pfw/pfwevca/fullcrl.crl, and the CRLDP indicates the full CRL.
2. 2009-02-06 Johnath representative — Noted they understood SECOM uses a single complete CRL for EV certificates and that other CRLDP data can be ignored if the full CRL is recognized.
3. 2009-02-09 Mozilla representative — Asked Johnathan to confirm that this is no longer an issue.
4. 2009-02-11 Johnath representative — Said they could not confirm the problem was fixed until bug 477244 (and really bug 474606) is resolved, but that SECOM had answered the questions and the reporter resolved this bug as a result.
5. 2009-03-04 Secom representative — Asked for the current status and when SECOM could expect to be arranged for EV.