mirror of
https://codeberg.org/openpgp/notes.git
synced 2024-11-27 01:52:06 +01:00
ch4: elaborate on user id conventions
This commit is contained in:
parent
2df7aa779d
commit
3ed3d5ed6a
1 changed files with 6 additions and 2 deletions
|
@ -143,13 +143,17 @@ Identity components in an OpenPGP certificate are used by the certificate holder
|
||||||
|
|
||||||
An OpenPGP certificate can contain any number of [User IDs](https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-10.html#name-user-id-packet-tag-13). Each User ID associates the certificate with an identity.
|
An OpenPGP certificate can contain any number of [User IDs](https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-10.html#name-user-id-packet-tag-13). Each User ID associates the certificate with an identity.
|
||||||
|
|
||||||
Often, identities in a User ID consist of a string that is composed of a name and an email address (this string must be UTF-8 encoded).
|
|
||||||
|
|
||||||
```{figure} diag/user_id.png
|
```{figure} diag/user_id.png
|
||||||
|
|
||||||
OpenPGP certificates can contain any number of User IDs
|
OpenPGP certificates can contain any number of User IDs
|
||||||
```
|
```
|
||||||
|
|
||||||
|
Often, identities in a User ID consist of a UTF-8 encoded string that is composed of a name and an email address. By convention, User IDs typically consist of an [RFC2822](https://www.rfc-editor.org/rfc/rfc2822) *name-addr*.
|
||||||
|
|
||||||
|
Also see [draft-dkg-openpgp-userid-conventions-00](https://datatracker.ietf.org/doc/draft-dkg-openpgp-userid-conventions/), 25 August 2023.
|
||||||
|
|
||||||
|
One proposed variant for encoding identities in User ID is to use ["split User IDs"](https://dkg.fifthhorseman.net/blog/2021-dkg-openpgp-transition.html#split-user-ids).
|
||||||
|
|
||||||
(primary_user_id)=
|
(primary_user_id)=
|
||||||
#### Primary User ID and its implications
|
#### Primary User ID and its implications
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue