[noise] Test vector format

Jonathan Rudenberg jonathan at titanous.com
Thu Apr 7 08:02:14 PDT 2016

> On Apr 7, 2016, at 01:38, Trevor Perrin <trevp at trevp.net> wrote:
> About JSON:  I worry about JSON files with large numbers of tests,
> since I think streaming APIs for JSON are less common than
> document-based APIs.  Also, I worry about someone developing for
> embedded systems, or smartcards, or IoT or something, who doesn't have
> JSON tools lying around.
> Would it be reasonable to make the format JSON-compatible but more
> restrictive, to make it easier to consume for dumb streaming parsers,
> but still allow consumers to use JSON?  This would make it harder for
> producing, but I think the tests will be consumed more than produced.
> Also, these restrictions could make the tests more human-readable.
> For example, what if every test block had the exact same sequence of
> fields prior to the "messages", one per line, with no sub-structures
> (unused psk or DH fields could have a special value "EMPTY"):

I’m fine with this. I think empty fields could just be an empty string? ("")


More information about the Noise mailing list