#157: Conflate Version and TransType
With TransItem support for v1 (RFC6962) disappearing in ticket #153, it
seems that having the type and version as separate fields just seems to
complicate matters unnecessarily. So let's conflate the two fields:
enum {
(0), x509_entry_v2(1), precert_entry_v2(2), x509_sct_v2(3),
precert_sct_v2(4), tree_head_v2(5), signed_tree_head_v2(6),
consistency_proof_v2(7), inclusion_proof_v2(8), (65535)
} TransTypeAndVersion;
The zero value is reserved to avoid confusion with a v1 SCT (which is
guaranteed to have zero as its first byte).
--
-------------------------------------+-------------------------------------
Reporter: | Owner: draft-ietf-trans-
[email protected] | [email protected]
Type: enhancement | Status: new
Priority: major | Milestone:
Component: rfc6962-bis | Version:
Severity: - | Keywords:
-------------------------------------+-------------------------------------
Ticket URL: <https://trac.tools.ietf.org/wg/trans/trac/ticket/157>
trans <https://tools.ietf.org/trans/>
_______________________________________________
Trans mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/trans
