Troy Ronda

DotNet Framework should be using the Aries RFC media types rather than application/ssi-agent-wire.

Ability to use big-endian variant of sgn0 in HashToCurve

1

The HashToCurve functions are currently hard-coded to use the little-endian variant (https://tools.ietf.org/html/draft-irtf-cfrg-hash-to-curve-06#section-4.1.2) of sgn0. It would be helpful if there was an additional option to use the big-endian variant (https://tools.ietf.org/html/draft-irtf-cfrg-hash-to-curve-06#section-4.1.1).

We would like to use the g1 package with the blake2b hash function. It would be helpful if you could expose a function that permits any hash function to be...

Mediated Holder Exchanges

8

Goal: VC HTTP APIs that enable the exchange of verifiable presentations between back-end services. This exchange should work for both scenarios that require a User UI and also for those...

use and accept updated media types

5

AcaPy should be using the Aries RFC media types rather than `application/ssi-agent-wire`.

use did-communication service type in DID Exchange

3

The service type should be `did-communication` rather than `IndyAgent` in DID Exchange.

Please use the https prefix for PIURI as the AcaPy default. We should be demonstrating the https prefix as the outgoing PIURI in the test harness.

Multilevel Nested JWM

5

Does the scope of the JWM spec include optimizing the payload encryption for a multi-level nested JWM? This topic was [raised](https://github.com/hyperledger/aries-rfcs/issues/341) in the Aries community. The idea of a detached...

Applicability of authenticated encryption?

4

I am curious about the applicability of authenticated encryption to this spec. E.g., ECDH-1PU [IETF draft](https://tools.ietf.org/html/draft-madden-jose-ecdh-1pu-02).

ECDH recommended curves

3

Section 6: Implementation Requirements The JWS paragraph lists RECOMMENDED curves but the JWE paragraph doesn't explicitly list the RECOMMENDED curves. I assume from the JWS paragraph (having P-256 and Ed25519)...