157   TC 6.3.14 and TC 6.3.33 requires different security events to be raised by the DUT

Created: 06 Mar 2026

Status: Approval (Editoral)

Part: Part 100-3 (2020, Edition 1)

Links:

Page: 18 and 20

Clause: 6.3

Paragraph: "Action"

Issue

TC in 6.3.14 refers to Initial Handshake, while TC in 6.3.33 refers to the session renegotiation.
Nevertheless, both TCs refer to the same error condition, i.e. "the DUT (Server only) is NOT able to provide a certificate selected from the Certificate Chain specified in the Trusted CA Indication of the last ClientHello message received."

Nevertheless, different requirements are set out in the two TCs for the DUT in the term that different security events shall be raised:

- for TC 6.3.14: Raise the security event “Alarm: CA certificate not found”
- for TC 6.3.33: - Raise the security event “Alarm: certificate validation: CA certificate not available”.

Proposal

It should be clarified what should be the security event to be raised by the DUT for both TCs, considering that there should be no reason why different security events should be raised.

Discussion Created Status
Test cases 6.3.14 and 6.3.33 are already covered by test cases 6.3.11 and 6.3.30, respectively.

Test cases 6.3.14 and 6.3.33 shall be removed.
22 Jun 26 Approval (Editoral)
As stated in RFC 6066, Servers that receive a client hello containing the "trusted_ca_keys" extension MAY (or may not) use the information contained in the extension to guide their selection of an appropriate certificate chain to return to the client.

Test cases 6.3.14 and 6.3.33 are already covered by test cases 6.3.11 and 6.3.30, respectively.
22 Jun 26 Discussion (red)
Agreed to discuss this tissue with IEC TC57 WG15. 10 Jun 26 Accepted
Yes, I agree, it should be the same Alarm message. 16 Apr 26 Triage

 

Privacy | Contact | Disclaimer

Tissue DB v. 25.7.7.1