Not clear how to carry PKI based key materials in YY-1

[Essien-Ge]

Contact Details

essien.ge@philips.com

Section Number

2:3.YY1.4.1.2 Message Semantics

What is wrong

According to the name, YY1 is targeting to support PKI material not just the self generated key pairs.
From the description in Use Case #1: WHO Global Digital Health Certification Network, it says "Trust in the GDHCN is established through a Public Key Infrastructure (PKI). Each participating jurisdiction submits its PKI material — including Signing Certificate Authority (SCA) certificates and Document Signer Certificates (DSCs) — to the WHO Trust Anchor through a formal onboarding process. The Trust Anchor publishes this key material in trust lists that other participants can retrieve and use to verify the digital signatures on health certificates."
However, currently in 2:3.YY1.4.1.2 Message Semantics only says submitter to generate key pairs, without mentioning the case that CA is enrolled and signing certificate for the submitter, and in that case how the certificate chain are summitted. This case should be more practical and more secure.
The example also only have the condition that key is directly included, not that the key is in the certificate chain.

Describe the solution you'd like

Suggest to include the condition on how PKI certificate used, including:

1. how certificate chain is carried in the transaction, maybe also CRL/OCSP if needed. Update example to include such case.
2. in the description of 2:3.YY1.4.1.1 Trigger Events, clearly include the case that CA exists (in which case the key may not be generated by the summitted)
3. In 2:3.YY1.4.1.3 Expected Actions, how verification should be done if there's a CA. This may include that check if the CA certificate is trusted by trust anchor, verify the certificate chain till the root certificate through signature, check CRL/OCSP if exist, and check the subject is submitter certificate is valid according to the identity of the submitted authenticated.

Relevant log output

Priority

{"High" => "Important issue where there is major issue to be resolved. Requires discussion and debate."}

Code of Conduct

• I agree to follow the IHE Code of Conduct