aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJames Bottomley <James.Bottomley@HansenPartnership.com>2023-03-17 17:05:08 +0000
committerJames Bottomley <James.Bottomley@HansenPartnership.com>2023-03-17 17:05:08 +0000
commitcf6bcb0dc82612815e16fad08d7af52bf5303870 (patch)
tree9979f96db4483de4042aefdf89251b94786e838b
parent07344a654c2bb17bfabbdbbd7422ba8864818493 (diff)
downloadopenssl_tpm2_engine-cf6bcb0dc82612815e16fad08d7af52bf5303870.tar.gz
doc: update the OID in the RFC to match reality
Gary Lin noticed that the OID in the RFC is missing a digit compared to what's already in use. This appears to be an oversight from when the negotiations with the TCG were onging and the code got updated but not the RFC. Update the OID base to 2.23.133.10.1 to reflect what everyone is actually using. Cc: Gary Lin <glin@suse.com> Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com>
-rw-r--r--doc/draft-bottomley-tpm2-keys.xml4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/draft-bottomley-tpm2-keys.xml b/doc/draft-bottomley-tpm2-keys.xml
index dac4c0e..0173c70 100644
--- a/doc/draft-bottomley-tpm2-keys.xml
+++ b/doc/draft-bottomley-tpm2-keys.xml
@@ -23,7 +23,7 @@ An alternate method (rfc include) is described in the references.
<email>James.Bottomley@HansenPartnership.com</email>
</address>
</author>
- <date month="December" year="2022"/>
+ <date month="March" year="2023"/>
<area>Security</area>
<keyword>I-D</keyword>
<keyword>Internet-Draft</keyword>
@@ -129,7 +129,7 @@ An alternate method (rfc include) is described in the references.
</t>
<figure><artwork>
id-tpmkey OBJECT IDENTIFIER ::=
- {joint-iso-itu-t(2) international-organizations(23) 133 10}
+ {joint-iso-itu-t(2) international-organizations(23) 133 10 1}
</artwork></figure>
<t>
And the three key types are: