The document says:
/* Managed by IANA */
enum {
X509(0),
RawPublicKey(2),
1609Dot2(?), /* Number 3 will be requested for 1609.2 */
(255)
103097(?), /* Number 4 will be requested for 103097 */
(255)
} CertificateType;
Two
Hi Ilari,
>> - The construction looks like it mixes different kinds of structures:
1609.2 Data of type signed versus TLS 1.3 signature. I do not think
this is cryptographically kosher. In fact, I think the call for
"extreme care" for certain kinds of modifications from TLS 1.3
specificatio
[CC'd back to the TLS list because this affects other TLS work as well]
Benjamin Kaduk writes:
>Having looked a bit harder, it seems that perhaps I need to point out that,
>if you want IANA to allocate a value, you need to *ask IANA for it*. The
>tls-reg-rev...@ietf.org list is not a supported
