RFC6962-bis: Should we flatten the MerkleTreeLeaf structure about certificate-transparency HOT 5 CLOSED

That is, eliminate

      MerkleLeafType leaf_type;
       select (leaf_type) {
           case timestamped_entry: TimestampedEntry;
       }

and include TimestampedEntry directly.

from certificate-transparency.

I'm in favour.

from certificate-transparency.

Out of curiosity, is the argument for flattening:
1. Greater confidence that there won't be need for new MerkleLeafTypes, or
2. If we ever did need new MerkleLeafType types (as mentioned in "Future revisions of this protocol version may add new MerkleLeafType types."), they could be added in a later version of MerkleTreeLeaf, by reintroducing this select.

from certificate-transparency.

No, its because the included structure already contains a type selector, so we expect that we could distinguish there instead.

from certificate-transparency.

Migrated to http://trac.tools.ietf.org/wg/trans/trac/ticket/6.

from certificate-transparency.