Fix incompatibility/deprecation issue between issuance, wallet and EDC

[lgblaumeiser]

Description

Details to be found here:
eclipse-tractusx/ssi-credential-issuer#224 Finding 3

Issue in EDC is here: eclipse-edc/Connector#4357

Basic issue is that there are different formats for the revocation list:

• StatusList2021, which is deprecated
• BitStringStatusList

EDC implements only StatusList2021 as of now
MIW is planned to support BitStringStatusList
Intention is to get rid of the deprecated format.

Impact

The planned procedure is to support BitStringStatusList in all relevant components first but stick in the operation to StatusList2021. Have a clear communication on when BitStringStatusList will be used. This will render older EDC versions to be not compliant with the mechanism anymore. So switching to BitStringStatusList is a breaking network change that must be coordinated.

Goal is to do the change prior to 2026 which would violate the 1 + 1 Release Schedule.

Additional information

• I'm willing to contribute to this feature

[lgblaumeiser]

@jjeroch : Does this summarize the issue we discussed this morning, can you add missing details or forward the issue to people who can?

@stephanbcbauer : This is a feature that we should add to the 24/12 release and coordinate between the teams. It is about ensuring that all relevant components support BitStringStatusList and StatusList2021 for now. This enables us to switch at any time convenient in the future.

[stephanbcbauer]

I added the milestone 24.12, because we need it on the board. Let's discuss this feature tomorrow in our meeting

[Phil91]

I've added a ticket for the portal team to support the BitString Status List: see #404

[paullatzelsperger]

Just as a small and admittedly detailed comment from the EDC side: yes, we will support BitStringStatusList in future versions (tx-edc probably 0.8.x), but so far we have limited it to support only statusSize = 1, i.e the only valid states are "set" and "not-set".

This is permitted by the spec and still satisfies conformance.

There are also two other implementation issues on which all involved parties should have alignment:

• agreeing on a minimum bitstring length: by default and unless stated otherwise it is 16KB (132.072 bits). this is important because the spec mandates a length check.
• agreeing on how to handle expiry of the statuslist credential itself: VC DataModel 2.0 defines validUntil, but BitStringStatusList also defines ttl which is a conflict. Suggestion: do not use ttl

[lgblaumeiser]

We should have a look into this during the planning of 25/03.

[lgblaumeiser]

Hi @MaximilianHauer, I have created this feature in the past as a consequence of a discussion that was done late in the planning of 24/12. We could never properly discuss the topic with all stakeholders as MIW died away shortly after this item was created. As you can see from Pauls comment, the EDC is somehow prepared with a unilateral implementation which makes some assumption on how the ButString status list is implemented. As the item is labeled with SSI, I co-assign you and kindly ask you to bring this to the SSI expert group for coordination.

[stephanbcbauer]

@MaximilianHauer if this feature is still valid, and we want to have it in the planning for 25.03, we should definitely "rerefine" it and also upgrade it to the new feature template
=> in this case, the milestone 24.12 needs to be deleted. Thanks