Open swcurran opened 3 years ago
Aries Framework .NET uses application/ssi-agent-wire
by default
This is why interoperability testing such as we are doing with Aries Agent Test Harness is so important. Despite what is said in the RFCs and the like, things can slip and if we haven't executed tests to demonstrate interop we're going to have to deal with these issues in the wild. And happily, when we do find these issues, we can define an execute a plan to keep interop going.
I'll put a community update RFC together.
@tmarkovski --- can you put a change into Aries Framework .NET so that both mime types are accepted, and then work in the community to get the change rolled out to all of those building on the framework?
Sure. This would be a fairly straightforward change with low impact.
The same issue is observed on Aries Javascript framework during the connection creation:
Unsupported content-type. Supported content-types are: application/ssi-agent-wire, application/didcomm-envelope-enc
This #571 changed the mime-type for DIDComm messages, and the feeling was that we didn't need to change the frameworks to make this happen.
We did an interop test in the https://github.com/hyperledger/aries-agent-test-harness between ACA-Py and AF-Go and we have a break on mime-type. AF-Go is using
application/didcomm-envelope-enc
and ACA-Py is usingapplication/ssi-agent-wire
and neither is handling the other. We can fix that, by changing both the accept both, but where does that leave Aries Framework .NET and other frameworks?Do we need to do a community update so that:
We can use Aries Agent Test Harness to find out what Aries Framework .NET is doing and I'll report back here.
@esplinr -- do you know what Evernym is doing?