Skip to content

Commit 3659eab

Browse files
committed
Override issuer encoding used in early implementations
RELATIVE-OID isn't yet widely implemented. For example, see <golang/go#75260>. To unblock early deployments, we'll go with UTF8String instead.
1 parent 29f4e79 commit 3659eab

1 file changed

Lines changed: 11 additions & 1 deletion

File tree

draft-davidben-tls-merkle-tree-certs.md

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -645,7 +645,17 @@ The attribute's value is a RELATIVE-OID containing the trust anchor ID's ASN.1 r
645645
1.3.6.1.5.5.7.25.TBD=#0d0481fd5901
646646
~~~
647647

648-
For initial experimentation, early implementations of this design will use the OID 1.3.6.1.4.1.44363.47.1 instead of `id-rdna-trustAnchorID`.
648+
For initial experimentation, early implementations of this design will:
649+
650+
1. Use UTF8String to represent the attribute's value rather than RELATIVE-OID. The UTF8String contains trust anchor ID's ASCII representation, e.g. `324731.1`.
651+
652+
1. Use the OID 1.3.6.1.4.1.44363.47.1 instead of `id-rdna-trustAnchorID`.
653+
654+
For example, the distinguished name for a log named `32473.1` would be represented in syntax of {{?RFC4514}} as:
655+
656+
~~~
657+
1.3.6.1.4.1.44363.47.1=#0c0733323437332e31
658+
~~~
649659

650660
## Log Entries
651661

0 commit comments

Comments
 (0)