Alex Turner

Here's a proposed format: ```jsonc [ { "not_before": "", "not_after": "", "keys": [ { "id": "", "key": "", }, // Optionally, additional keys ... ] }, // Optionally, additional keysets...

To better understand the processing cost differences, we ran a simple benchmark comparing CBOR and JSON for a sample report. We found similar serialization times for JSON and CBOR (both...

A concrete encoding that could be used would be tab-separated values in a pre-defined order using UTF-8 strings. This would avoid needing to encode reports using CBOR. It would also...

The delimiter-based encoding would require disallowing tabs in any string field, which might pose a risk for future extensions. Alternatives that avoid this issue include using Deterministically Encoded CBOR (https://www.rfc-editor.org/rfc/rfc8949.html#section-4.2)...

Another consideration is the communication between reporting origin and aggregation origin of the information needed to construct the authenticated data. For example, if this communication encodes each field separately, adding...

Thanks! Another (verbose) fix could be to add identical "Otherwise" branches for each if statement. For the naive implementation performance risk, I think the existing note probably covers us.