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

Show file tree
Hide file tree
Changes from 12 commits
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
15 changes: 13 additions & 2 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -224,15 +224,18 @@ <h2>Implementer Overview</h2>
<p>
A <dfn class="lint-ignore">conforming DID resolver</dfn> is any algorithm
realized as software and/or hardware that complies with the relevant normative
statements in <a href="#resolving"></a>.
statements in <a href="#resolving"></a> as well as implement <a>local binding</a>.
Copy link
Contributor

@wip-abramson wip-abramson Oct 9, 2025

Choose a reason for hiding this comment

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

I don't think this reads well. But also wondering why we need this addition?

Copy link
Member

@msporny msporny Oct 9, 2025

Choose a reason for hiding this comment

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

Complying with the "relevant normative statements" is equivalent to saying "implement" -- we don't need to re-state it.

</p>

<p>
A <dfn class="lint-ignore">conforming DID URL dereferencer</dfn> is any
algorithm realized as software and/or hardware that complies with the relevant
normative statements in <a href="#dereferencing"></a>.
</p>

<p>
A <dfn class="lint-ignore">https DID resolver</dfn> is a <a>conforming DID resolver</a> that also implements
Copy link
Contributor

@wip-abramson wip-abramson Oct 9, 2025

Choose a reason for hiding this comment

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

Suggested change
A <dfn class="lint-ignore">https DID resolver</dfn> is a <a>conforming DID resolver</a> that also implements
A <dfn class="lint-ignore">conforming HTTPS DID resolver</dfn> is a <a>conforming DID resolver</a> that also implements

I think for consistency we should capitalize https

<a href="#bindings-https">HTTP(S) Binding</a>.
</p>
</section>

<section class="informative">
Expand Down Expand Up @@ -2291,6 +2294,14 @@ <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 <a href="#dfn-https-did-resolver">HTTP(S) DID resolvers</a> MUST implement the GET version of the
<a href="#bindings-https">HTTPS binding</a> and MAY implement the POST version.
All <a href="#bindings-https">HTTPS bindings</a> MUST use TLS. Use of DNS names
in certificates is NOT REQUIRED; resolvers MAY use TLS certificates issued for IP addresses
(e.g., Let's Encrypt-style IP certificates).
Copy link
Member

@msporny msporny Oct 9, 2025

Choose a reason for hiding this comment

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

Naming specific brands/services in specs can be problematic because they often go out of business or stop operating. While the "Let's Encrypt" language is helpful, I suggest we don't add it.

</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
3 changes: 1 addition & 2 deletions terms.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -194,12 +194,11 @@

<dt><dfn data-lt="">local binding</dfn></dt>
<dd>A <a>binding</a> where the <a>client</a> invokes a <a>DID resolver</a> that runs on the same network host, e.g., via a local command line tool or library API.
In this case, the <a>DID resolver</a> is sometimes also called a "local <a>DID resolver</a>".
See Section <a href="#resolver-architectures"></a>.</dd>

<dt><dfn data-lt="">remote binding</dfn></dt>
<dd>A <a>binding</a> where the <a>client</a> invokes a <a>DID resolver</a> that runs on a different network host, e.g., via the <a href="#bindings-https">HTTP(S) binding</a>.
In this case, the <a>DID resolver</a> is sometimes also called a "remote <a>DID resolver</a>".
In this case, the <a>DID resolver</a> is sometimes also called a <a>https DID resolver</a>.
Copy link
Contributor

@wip-abramson wip-abramson Oct 9, 2025

Choose a reason for hiding this comment

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

Suggested change
In this case, the <a>DID resolver</a> is sometimes also called a <a>https DID resolver</a>.
In this case, the <a>DID resolver</a> is also called a <a>HTTPS DID resolver</a>.
``

See Section <a href="#resolver-architectures"></a>.</dd>

<dt><dfn data-lt="service">services</dfn></dt>
Expand Down