#107: Struct-ify STH For ticket #10 we need to be able to serialize each type of CT object into a list that can be embedded in TLS/certificate/OCSP extensions.
In RFC6962, TreeHeadSignature is a "digitally-signed struct" that doesn't contain the timestamp, tree_size and sha256_root_hash necessary to verify that signature. Hence why get-sth has to provide these as separate JSON outputs. To enable serialization using just TLS encoding rules (as we do for SCTs), let's create a new "struct" called SignedTreeHead that includes TreeHeadSignature, timestamp, tree_size and sha256_root_hash. -- -------------------------------------+------------------------------------- Reporter: | Owner: [email protected] | [email protected] Type: enhancement | Status: new Priority: major | Milestone: Component: rfc6962-bis | Version: Severity: - | Keywords: -------------------------------------+------------------------------------- Ticket URL: <http://trac.tools.ietf.org/wg/trans/trac/ticket/107> trans <http://tools.ietf.org/trans/> _______________________________________________ Trans mailing list [email protected] https://www.ietf.org/mailman/listinfo/trans
