SwissSign preliminary incident report on stateOrProvinceName formatting

SwissSign opened this bug as a preliminary incident report after a third party asked about unexpected stateOrProvinceName attribute formatting in OV and EV certificates. SwissSign said its certificates use state shortcodes without the ISO 3166-1 country-code prefix, and it started an investigation. In its conclusion, SwissSign stated that using either the state name or the shortcode is compliant with the relevant TLS Baseline Requirements, EV Guidelines, and SwissSign CP/CPS. CCADB Support asked whether the bug should be closed as INVALID, and SwissSign agreed that it could be closed as INVALID if there were no further questions. CCADB then issued a final call for comments and said the bug would be closed as INVALID on or about 2026-09-01 if no further discussion occurred.

1. 2026-08-20 SwissSign opened a preliminary incident report about OV and EV certificates using state shortcodes without the ISO country-code prefix.
2. 2026-08-21 SwissSign concluded that the formatting was compliant with the TLS BR, EV Guidelines, and SwissSign CP/CPS.
3. 2026-08-25 CCADB issued a final call for comments and said the bug would be closed as INVALID if no further questions were raised.

1. 2026-08-20 SwissSign AG — Roman Fischer reported the issue as a third-party inquiry about unexpected certificate attribute combinations and said SwissSign had started an investigation.
2. 2026-08-21 SwissSign AG — Roman Fischer explained SwissSign's lookup-table approach and concluded the use of the state shortcode without the country-code prefix was compliant.
3. 2026-08-21 CCADB representative — CCADB Support said it would continue monitoring the bug and consider additional information when deciding next action.
4. 2026-08-25 CCADB representative — CCADB Support asked whether the bug should be closed as INVALID.
5. 2026-08-25 SwissSign AG — Roman Fischer agreed the bug could be closed as INVALID if there were no questions or discussion.
6. 2026-08-25 CCADB representative — CCADB Support gave a final call for comments and said the bug would be closed as INVALID on approximately 2026-09-01.