Mihály Héder In the credential/wallet ecosystem there are an abundance of options between protocols and parameters, almost creating a combinatorical explosion of options implementers should support. Therefore the DIIP profile was developed: https://fidescommunity.github.io/DIIP/ 
Deep provides defaults as it "chooses standards for credential format, signature algorithm, identifying actors, and issuance and presentation protocols" so that an implementation can state that they are using DIIP. The task is to have our VC issueing IdPs (Ship, ssp) to support DIIP.

Stefan Liström: Revocation is not only a mandatory privacy enhancing feature for end-users, it is also a core security feature. Both use cases for revocation need to be implemented in a future EUDI wallet ecosystem. There is currently however no clear solution for interoperable, scalable revocation in the EUDI. This activity investigates and describes the possible approaches for scalable, interoperable ways to handle revocation. The activity should try to test at least two of the approaches with respect to requirements on scalability and interoperability as may needed for the EUDI.

In the world of OID4 wallets there is a large variety of different authentication flows, cryptographic methods, presentation formats and other parameters, meaning that even if two components are supporting OID4* it is far from certain that they can actually communicate. More interoperability is needed.

In this task, we
    • Attempt to implement the DIIP 4 profile for the Shibboleth / simpleSAMlphp IdP OID4VCI implementations (outcome of cycle 10) 
        ◦ Pass DIIP Conformance Test, against existing testbed
        ◦ Test with DIIP-compliant wallets
        ◦ engage DIIP/FIDES community
        ◦ specifically investigate DIIP revocation method IETF Token Status List, including scalability
        ◦ discover use cases (MMS from previous cycle)

Outcomes
    • proof-of-concept DIIP compliant Shib/SSP VC issuer or gap report on obstacles

The following parties will use the results of this activity: