Skip to content

Make https binding mandatory #182

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 16 commits into
base: gh-pages
Choose a base branch
from
Open

Make https binding mandatory #182

Changes from 1 commit
Commits
Show all changes
16 commits
Select commit Hold shift + click to select a range
13a3679
Make https binding mandatory
ottomorac Sep 1, 2025
5d65ed3
correct wording to did methods
ottomorac Sep 1, 2025
4ed0039
Merge branch 'w3c:gh-pages' into ottomora-https-binding
ottomorac Sep 11, 2025
9f2c955
specify local vs. remote resolvers
ottomorac Sep 11, 2025
027e402
Update index.html
ottomorac Sep 12, 2025
8ec3f33
Update index.html
ottomorac Sep 24, 2025
e57a848
Merge branch 'w3c:gh-pages' into ottomora-https-binding
ottomorac Sep 24, 2025
55b3616
Add local and remote resolver classes
ottomorac Sep 24, 2025
b5ced4e
Update index.html
ottomorac Oct 2, 2025
c2968c0
Merge branch 'w3c:gh-pages' into ottomora-https-binding
ottomorac Oct 8, 2025
4fcabb7
Add https did resolver
ottomorac Oct 8, 2025
98520be
Add https did resolver
ottomorac Oct 9, 2025
049536e
Simplify change to make https binding mandatory
ottomorac Oct 9, 2025
e81362a
Simplify change to make https binding mandatory
ottomorac Oct 9, 2025
1933fd4
Simplify change to make https binding mandatory
ottomorac Oct 9, 2025
9d25698
Update index.html
ottomorac Oct 15, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2055,6 +2055,13 @@ <h1>Bindings</h1>
<p>This section defines bindings for the abstract algorithms in sections <a href="#resolving"></a> and
<a href="#dereferencing"></a>.</p>

<p>
All conformant <a>DID resolvers</a> MUST implement at least one implementation of a resolver
with <a href="#bindings-https">https binding</a>. Such implementations MUST use TLS. Use of DNS names
Copy link
Collaborator

@peacekeeper peacekeeper Sep 1, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't really understand this sentence.. If I implement a did:key resolver that only works as a library and doesn't include an HTTPS binding, does that mean it's not conformant?

Maybe this is supposed to say "All conformant DID methods" instead of "All conformant DID resolvers"?

Copy link
Contributor Author

@ottomorac ottomorac Sep 1, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks Markus. I changed it to say "All conformant DID methods".

I was unsure also about the second part, in this comment #93 (comment) Manu and Joe had indicated that there could be 2 classes of conformance "separate out libraries from resolver deployments that include HTTPS" but I am not sure how to word 2 classes of conformance in the spec. Apologies, this is new ground for me.

Copy link
Contributor Author

@ottomorac ottomorac Sep 2, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Adding this link that Will mentioned to me around what are conformance classes so we can discuss during the wg call: https://w3c.github.io/did-resolution/#conformance

in certificates is not required; resolvers MAY use certificates issued for IP addresses
(e.g., Let's Encrypt-style IP certificates). Additional bindings MAY also be provided.
</p>

<section id="bindings-https">
<h2>HTTP(S) Binding</h2>
<p>This section defines a <a>DID resolver</a> <a>binding</a> which exposes the
Expand Down
Loading