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.

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

clarify language on kid handling #122

Merged
merged 2 commits into from
Feb 7, 2024
Merged

clarify language on kid handling #122

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2139b58
clarify language on kid handling
Feb 6, 2024
6a19e46
Merge branch 'main' into issue-118
decentralgabe Feb 7, 2024
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
14 changes: 12 additions & 2 deletions spec/spec.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -246,7 +246,7 @@ An example is given as follows:

#### Verification Methods

- Each Verification Method **name** is represented as a `_kN._did` record where `N` is the zero-indexed positional index of
- Method **name** is represented as a `_kN._did` record where `N` is the zero-indexed positional index of
a given [Verification Method](https://www.w3.org/TR/did-core/#verification-methods) (e.g. `_k0`, `_k1`).

- Each [Verification Method](https://www.w3.org/TR/did-core/#verification-methods) **rdata** is represented with the form
Expand Down Expand Up @@ -778,14 +778,24 @@ encoding format, we recommend additional considerations to keep payload sizes mi

#### Representing Keys

The following representations of keys and their identifiers using `JsonWebKey` (JWK) are ****REQUIRED****:
Apart from the encoding of the cryptographic key itself, which cannot be further minimized in size, it is
****REQUIRED**** to follow the following guidance on representations of keys and their identifiers
using the `JsonWebKey` type:

- The [[ref:Identity Key]]'s identifier ****MUST**** always be `0`.

- Key identifiers (`kid`s) ****MAY**** be omitted. If omitted, upon reconstruction of a DID Document, the JWK `kid`
and its corresponding Verification Method `id` is to be set to the key's JWK Thumbprint [[spec:RFC7638]].

- A Verification Method's `id` ****MUST**** always match the corresponding JWK's `kid` property.

- DID Document representations ****SHOULD**** always use fully qualified identifiers (e.g.
is set to its JWK Thumbprint [[spec:RFC7638]].

- [[ref:DID Document]] representations of elliptic curve (EC) keys ****MUST**** include the x- and y-coordinate pair.
To conserve space in the DNS packet representation, compressed point encoding ****MUST**** be used to transmit the
x-coordinate and a sign bit for the y-coordinate. This practice reduces each public key's size from 65 to 33 bytes.

- [[ref:DID Document]] representations ****SHOULD**** always use fully qualified identifiers (e.g.
`did:dht:uodqi99wuzxsz6yx445zxkp8ddwj9q54ocbcg8yifsqru45x63kj#0` as opposed to `0` or `#0`)

Expand Down
Loading