FR-01 Support Certificate Exchange with Unknown Pools

[danisoler-charin]

Description: The system shall enable a pool operator to retrieve certificates from other, previously unknown (to the requester) pool operators within the ecosystem.
Use Case: Any scenario where a certificate is needed from a pool not directly known to the requestor, but already part of the system
Already in OPNC 1?: This FR has been flagged as possible with current version through
"Broadcastflag" in

• getOemProvCert
• GenerateSignedContractData|createSignedContractData
• getSignedContractData

I have reviewed the code and come up with the following:

• getOemProvCert does not exist in opnc repo
• GenerateSignedContractData does not exist in opnc repo
• createSignedContractData does not exist in opnc repo
• getSignedContractData does not exist, however, getSignedContractDataResV1.json does, under Responses

There might be a confusion with the OPNC specific function names.

EVPKI Comments: There needs to be method to alert members of a new member, and there needs to be a single API to initiate connections.
E.g. A member is being introduced, and needs to connect to the other pool operators, or a member is already in the pool and a new member is introduced.

Please help clarify how is this FR already covered in OPNC 1.0 so we can conclude if there is any change needed or not

[steffenrhinow]

Unkwnon sources can not be connected automaticly as first the govenance body would need to audit that system and potentialy the PKI. OPNC relies on mutual trust and knowledge between the stakeholders

[danisoler-charin]

After discussion on 09/07/25:
Broadcastflag mechanism

• The confusion about the existing functions probably is a naming issue. @guillaumeFRANCOIS

Trust and governance challenges

• Pools cannot connect to completely unknown pools without prior onboarding due to security requirements, PKI trust validation, GDPR compliance for data sharing.
• Consensus that onboarding and trust establishment are prerequisites, highlighting ongoing European (STF) and NA (SAE) efforts to define common CTL governance models, which may take years (EU 2028).

Technical feasibility vs governance

• Technically, retrieving certificates between known pools is already possible in OPNC v1.
• The "previously unknown" aspect in the requirement description is not feasible because onboarding happening before this stage.
• The description will be rephrased to reflect this.

CONCLUDING:
✔️ Technically feasible: Certificate retrieval between pools is supported with current OPNC functionality once pools are onboarded and trusted.

[marvin-fastned]

Can we close this issue then?