You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: assignments.md
+21-9Lines changed: 21 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,18 +4,30 @@ To facilitate early experiments with Trust Anchor Identifiers, the following tab
4
4
5
5
## Steps to assign new IDs:
6
6
1. If needed, obtain a Private Enterprise Number OID from IANA ([Request Form](https://www.iana.org/assignments/enterprise-numbers/assignment/apply/))
7
-
2. For each participating trust anchor, identified by their (subjectName, public key) tuple, assign a unique OID under the PEN.
7
+
2. For each participating trust anchor, identified by their {Subject, Public Key} tuple, assign a unique OID under the PEN. Assignments can be spot checked against crt.sh, which assigns unique CA IDs using the same fields.
8
8
3. Submit a pull request that adds a new row to the below table for each trust anchor ID assignment.
9
9
10
10
### Notes:
11
11
* Trust Anchor IDs should use the ASCII (dotted decimal) notation, e.g. `32473.1`.
12
-
* Public Keys should be PEM-encoded and include the `-----BEGIN PUBLIC KEY-----` and `-----END PUBLIC KEY-----` blocks.
13
-
* The following command can be used to easily extract public keys in the correct format:
0 commit comments