2024-10-09

This meeting is part of the quarterly CAB meeting schedule.

The next CAB meeting will be held at October 9, 2024 at 15:00 CET. If you would like to be invited for this meeting, or if you would like to add a topic to the agenda, please reach out to us through available channels.

Agenda

1. Welcome + introduce new participants

2. Updated framework release process and structure - Asynchronous release of documentation and supporting IT components -> to be included in RFC048 - Introduction of optional features (per role)

3. Update on the implementation of RFCs on the RFC board We expect a next release of the framework in December 2024, which is expected to include following RFCs: - RFC031: Introduce iSHARE-ID and allow multiple identifiers using DID - RFC045: Introduce zero-trust network - RFC042: Harmonise terminology - RFC052: Applicability of service levels under Adhering parties contract should be applicable only to parties providing services - RFC036: Decommision of PKIOverheid certificates - RFC034: Define standard policy creation endpoint for AR (implement as optional feature) - RFC047: Respecification of the capabilities endpoint Please note that release of the framework documentation precedes releases of supporting IT components such as the CTT and the iSHARE Satellite reference implementation. The final scope of the release will be determine shortly before the release and shared through the usual channels.

4. Advice on the implementation of RFCs - RFC055: Allow conditions in delegations (implement as optional feature for AR) - RFC051: Revert to standard OAuth authentication flows - RFC053: Allow Service Consumers without PKI certificate

5. Input/review required

   Any of the above RFCs if not concluded, then Input/Review is required for the same.

6. Advice on newly incoming RFCs - Evaluate if eIDAS 2.0 affects the Assessment Framework - Publish OpenAPI (Swagger) definitions under MIT license - Introduce optional features in Framework

7. RFC prioritisation: discuss priority on the RFC board

8. Wrap up and outlook to next quarter - Next CAB session on December 4, we suggest to host it at our office and request members to plan it in their agenda to visit our office.

Meeting results

1. About the asynchronous release of documentation. After questions from CAB it is clarified that within six months of the framework release, the IT components will be updated, unless there are reasons or circumstances to deviate from this. This is to be included in RFC048. iSHARE Foundation will update RFC048. About the introduction of optional features (per roles). CAB suggests to refrain from using optional features too much, so the consistency throughout the framework is affected as less as possible. It should be a balance between impact on participants and consistency / interoperability across participants and data spaces. These things must be detailed out in the RFC impact analysis of introducing optional features.

2. CAB was provided insight into the expected scope of the next release.

3. Advice on the implementation of the RFCs: - RFC055 was discussed in depth. Although it is recognised that the RFC increases complexity, it is also recognised that it brings a relevant extension to the framework. It was decided that implementation as an optional feature, allowing for both scenario's (scenario C) is the preferred implementation scenario. The optional part of it will be part of the dataspace definition (whether to use it or not). CAB advices to start implementation. - RFC051 was discussed. CAB advices to clarify more clearly what implementation scenario is selected and then to start implementation. It will not affect the formal specifications, but will lead to the creation of supporting documents. - RFC053 was explained and CAB advices to start implementation.

4. --

5. - Evaluate if eIDAS 2.0 affects the Assessment Framework -> OK to take on as RFC. CAB advices to also look at eHerkenning's updated assessment framework (which is probably in line with eIDAS 2.0) and DSGO's assessment framework. - Publish OpenAPI (Swagger) definitions under MIT license -> CAB agrees to develop this as an RFC and would like to see progress on this on a short term. - Introduce optional features in Framework -> as discussed earlier, OK to create.

6. RFCs we re-prioritised on the board

7. All are invited to come to the iSHARE Rotterdam office for the next CAB, scheduled on December 4, 2024. We will organise a meeting on the open source projects that iSHARE is involved in, or add it to the agenda of next CAB.