Skip to content

Commit b153ede

Browse files
authored
Tweak assignments table and add Google TrustAnchorIDs (#95)
1 parent ae24c09 commit b153ede

File tree

1 file changed

+21
-9
lines changed

1 file changed

+21
-9
lines changed

assignments.md

Lines changed: 21 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -4,18 +4,30 @@ To facilitate early experiments with Trust Anchor Identifiers, the following tab
44

55
## Steps to assign new IDs:
66
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.
88
3. Submit a pull request that adds a new row to the below table for each trust anchor ID assignment.
99

1010
### Notes:
1111
* 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:
14-
* `$ openssl x509 -in certificate.pem -noout -pubkey`
15-
* The following command can be used to easily extract subjectNames in the correct format:
16-
* `$ openssl x509 -in certificate.pem -noout -subject | sed -e "s/^subject= //"`
12+
* Subject and Public Key information for each CA can be obtained from the crt.sh CA ID links
13+
* The Subject column in this table is intended for human readability only.
14+
1715

1816
## List of assigned IDs
19-
|Trust Anchor ID|Subject Name|Public Key|
20-
|---------------|------------|----------|
21-
||||
17+
| Trust Anchor ID | Subject | Trust Anchor by crt.sh CA ID link |
18+
|-----------------|-------------------------------------------------|------------------------------|
19+
| 11129.9.1 | CN=GTS Root R1,O=Google Trust Services LLC,C=US | https://crt.sh/?caid=48269 |
20+
| 11129.9.2 | CN=GTS Root R2,O=Google Trust Services LLC,C=US | https://crt.sh/?caid=48271 |
21+
| 11129.9.3 | CN=GTS Root R3,O=Google Trust Services LLC,C=US | https://crt.sh/?caid=48268 |
22+
| 11129.9.4 | CN=GTS Root R4,O=Google Trust Services LLC,C=US | https://crt.sh/?caid=48274 |
23+
| 11129.9.5 | C=US, O=Google Trust Services, CN=WR1 | https://crt.sh/?caid=286242 |
24+
| 11129.9.6 | C=US, O=Google Trust Services, CN=WR2 | https://crt.sh/?caid=286243 |
25+
| 11129.9.7 | C=US, O=Google Trust Services, CN=WR3 | https://crt.sh/?caid=286244 |
26+
| 11129.9.8 | C=US, O=Google Trust Services, CN=WR4 | https://crt.sh/?caid=286245 |
27+
| 11129.9.9 | C=US, O=Google Trust Services, CN=WR5 | https://crt.sh/?caid=286246 |
28+
| 11129.9.10 | C=US, O=Google Trust Services, CN=WE1 | https://crt.sh/?caid=286236 |
29+
| 11129.9.11 | C=US, O=Google Trust Services, CN=WE2 | https://crt.sh/?caid=286237 |
30+
| 11129.9.12 | C=US, O=Google Trust Services, CN=WE3 | https://crt.sh/?caid=286239 |
31+
| 11129.9.13 | C=US, O=Google Trust Services, CN=WE4 | https://crt.sh/?caid=286240 |
32+
| 11129.9.14 | C=US, O=Google Trust Services, CN=WE5 | https://crt.sh/?caid=286241 |
33+
| 11129.9.15 | C=US, O=Google Trust Services, CN=AE1 | https://crt.sh/?caid=286234 |

0 commit comments

Comments
 (0)