Hi all, Tobias Looker and Oliver Terbu have both served as co-chairs with me since the beginning of the working group. They have both needed to step down as co-chairs, and Steven McCowan has stepped u

I wanted to ask a question about key types. In our spec, we list a number of key types that must be supported. Keys for Edwards curves are an obvious and uncontroversial choice, but we also list ES256

FWIW, JsonWebKey2020 is an easy way to get any JWK based key from a did document. Given we're already using JWKs for the JOSE layer, I'm becoming more a fan of using JsonWebKey2020 over separate key t

Today on our call, I reacted to an idea about discontinuing support for attachments by saying it felt to me like crazy talk. I owe Kyle an apology for that. It was bad form in two ways: first, unfair

The Glossary Group has decided to focus on the meaning of service endpoints for DIDs. We are looking for community input on our current definitions of 5 different endpoints and would like your input.

I sent an email to this group a while back where I was discussing how to link PIURIs in DIDComm (the special URIs used to identify protocols and message types) with a URL namespace under http://didcom

Today we discussed whether we can use an initial-state matrix parameter on DIDs to pass info in a DIDComm message in the JSON field where a recipient is identified (where a simple DID would sometimes

Is there a meeting today?

Daniel Hardman has submitted our first content PR related to Routing. Here is the link to read the PR content: https://github.com/decentralized-identity/didcomm-messaging/blob/f642db1a09c79ba5db01b84b

Hi, I am looking into the transports section of the spec. For the case of transmitting the message using TLS based protocols, is the definition of DID-TLS part of this spec?

As discussed on today's call...

Daniel Hardman has written up a suggested outline, and we'll be discussing that on Monday's call. Please read it prior to the call: https://docs.google.com/document/d/1Hn4ofl7ubRy22Xv1Yj1g77OkJWlWkDh8

At the end of today's call, we had a mostly open question about the name of the repo to create to host our initial work. The two proposed names are did-messaging and didcomm-spec. did-messaging would

I'd like to offer this doc as a starting place for an outline for a DIDComm messaging spec. https://docs.google.com/document/d/1Hn4ofl7ubRy22Xv1Yj1g77OkJWlWkDh88O3Od-yp8Cg/edit I put sample content in

Dear all, Happy New Year! We are very close to set up everything and start to work properly. I am sending this email as a first step to make sure that DIDcomm has IPR protection. There is a separate m

Dear all, A convenient registration form for the DIDComm WG can be found here: https://forms.gle/mmCUgcQuguAAAhRKA After submitting the form, you will receive a calendar invite. Ideally, we can get th

I don't have Monday's meeting on my calendar. Where can I go to get an invitation that will put it on, in recurring form, correctly?

During our Working Group call today, we reached a consensus within the call participants about the scope section of the Working Group Charter. This email is a final request for comments on the Scope p

We are seeking input on the day and time for a weekly DIDComm Working Group Call. Please use the following link to indicate (by 'painting') the times you can regularly attend a meeting. http://whenisg

Dear all, I would like to move the final WG scope to LF and SC for sign-off, however, there are still outstanding comments on our working version in the "operating charter". May I ask everyone to take