Skip to content
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.

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

Add security consideration around Multiformat choice. #107

Merged
merged 2 commits into from
Oct 19, 2024
Merged
Changes from all 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
32 changes: 32 additions & 0 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -2878,6 +2878,38 @@ <h3>Revocation Semantics</h3>
</section>
</section>

<section>
<h2>Choosing a Multiformat</h2>

<p>
<dfn class="external lint-ignore">Multiformats</dfn> enable self-describing
data; if data is known to be a Multiformat, its exact type can be determined by
reading a few compact header bytes that are expressed at the beginning of the
data. <a href="#multibase-0">Multibase</a>, <a href="#multihash">Multihash</a>,
and <a href="#Multikey">Multikey</a> are types of Multiformats that are defined
by this specification.
</p>

<p>
The Multiformats specifications exist because application developers
appropriately choose different base-encoding functions, cryptographic
hashing functions, and cryptographic key formats, among other things,
based on different use cases and their requirements. No single
base-encoding function, cryptographic hashing function, or cryptographic
key format in the world has ever satisfied all requirement sets.
Multiformats provides an alternative means by which to encode and/or
detect any base-encoding, cryptographic hash, or cryptographic key
format in self-documenting data and documents.
</p>

<p>
To increase interoperability, specification authors are urged to minimize
the number of Multiformats &mdash; optimally, choosing only one &mdash; to
be used for any particular application or ecosystem.
</p>

</section>

<section>
<h2>Encrypted Data in Controller Documents</h2>
<p>
Expand Down