Re: Worst case example of a proposed DID endpoint?

On Fri, Oct 18, 2024 at 3:01 PM Markus Sabadello <markus@danubetech.com>
wrote:

> DIDComm endpoints can be a bit complex, e.g.:
> https://identity.foundation/didcomm-messaging/spec/#service-endpoint
>
> The idea of having a DID (instead of HTTPS URL) as service endpoint has
> been proposed here:
> https://github.com/w3c/did-resolution/issues/7
>
> The idea of having non-correlatable endpoints have been discussed here:
> https://github.com/w3c/did-resolution/issues/35
>
> Hope this helps?
>

Thanks Markus!

The example in did:sov method is a good one for me to start with (
https://sovrin-foundation.github.io/sovrin/spec/did-method-spec-template.html
):

"service": [ { "type": "endpoint", "serviceEndpoint": "
https://example.com/endpoint" }, { "id":
"did:sov:HR6vs6GEZ8rHaVgjg2WodM#did-communication", "type":
"did-communication", "priority": 0, "recipientKeys": [
"did:sov:HR6vs6GEZ8rHaVgjg2WodM#key-agreement-1" ], "routingKeys": [],
"accept": [ "didcomm/aip2;env=rfc19" ], "serviceEndpoint": "
https://example.com/endpoint" } ]

I don't have an example of this from the real world (if someone has one, it
would be appreciated), but I suspect that in many real-world examples of
did:sov there might be a lot of correlatable data, as well as
quasi-correlatable data such as structures.

May goal is to have this subsumed into completely elided property, that
looks something like:

"service": [ { "type": "elidedEndpoints", "serviceEndpoint": "cbor:<base64
of a fully elided gordian envelope>" } ]

Fully elided it should be well under 100 bytes.

I also want show how someone could do a proof of inclusion for only the
portion:

"type": "endpoint", "serviceEndpoint": "https://example.com/endpoint
(plus the appropriate salts)

…that proves that the endpoint was committed to in the full did controller
document, without revealing any of other endpoint data.

We will be talking about Gordian Envelope at next Tuesday's CCG meeting,
and besides an overview, I'd like to show this as a practical example.

-- Christopher Allen

Received on Friday, 18 October 2024 22:52:52 UTC