EDC - Protocol compatibility of Decentralized Claims Protocol (aka IATP)

[lgblaumeiser]

Description

As Dataspace participant hosting an EDC instance, I want to get informed if a data transfer with another EDC is not possible due to a version incompatibility of the used distributed claims protocol (DCP formerly known as IATP). This requires the DCP to support a mechanism for protocol meta-information exchange between the communicating parties.

Impact

The DSP currently already supports the version negotiation, so that an EDC can stop the communication, if no common protocol version can be identified between the two parties. The claims protocol currently has in its initial form no such mechanism, so the communicating partners can only find out incompatibilities during the negotiation process. With this feature a more graceful handling of an incompatibility is enabled. It also supports multiple versions of the claims protocol to be offered, so that there is more flexibility on negotiating a protocol version supported by both communication partners.

Tractus-X activities

This issue is about tracking the upstream development. The feature depends on:

• Specification of the feature in the protocol
• Implementation of the upstream functionality

It is even unlikely, that this will be finished in 24/12

[jimmarino]

This probably needs to be submitted to the DCP specification group.

[stephanbcbauer]

Presented in the DRAFT Feature Freeze -> Committer is available

[stephanbcbauer]

Involved Expert Groups SSI and Dataspace Connectivity

[stephanbcbauer]

This requirements was created to discuss it in the EDWG (Specification Committee) @jimmarino -> depending on the results there will be implementation or not

[lgblaumeiser]

@jimmarino : Please raise the issue in the Eclipse Dataspace Working Group

[lgblaumeiser]

Close the issue with state "Not in release" as there was no development upstream on the DCP