Skip to content
Open
Show file tree
Hide file tree
Changes from 8 commits
Commits
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
20 changes: 20 additions & 0 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -205,6 +205,18 @@ <h1>Introduction</h1>
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">remote DID resolver</dfn> is a resolver implementation that is permitted (and expected, if necessary)
to perform network calls, remote registry lookups, or external protocol interactions associated with
its resolution and de-referencing functions.
</p>
<p>
A <dfn class="lint-ignore">local DID resolver</dfn> is an implementation of a DID resolver and/or
DID URL dereferencer that never performs remote HTTP(s), DNS, blockchain, or other network‐based
lookups when executing the resolution or dereferencing functions. All operations are fulfilled by
local resources: e.g. embedded keys/methods, cached/packaged DID Documents, or local verifiable
registries or storage.
</p>

</section>

Expand Down Expand Up @@ -2223,6 +2235,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-remote-did-resolver">remote 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

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
4 changes: 2 additions & 2 deletions terms.html
Original file line number Diff line number Diff line change
Expand Up @@ -194,12 +194,12 @@

<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>".
In this case, the <a>DID resolver</a> is sometimes also called a <a>local 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>remote DID resolver</a>.
See Section <a href="#resolver-architectures"></a>.</dd>

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