[CFRG] Re: Where should test vectors live?

[Orie Steele <[e-mail]>]

I like the idea of hosting machine readable test vectors.

The COSE WG has a collection of files under the working group GitHub
organization.

The is also
https://www.iana.org/assignments/yang-parameters/yang-parameters.xhtml

And...
https://www.iana.org/assignments/xml-registry/schema/location-type.xsd

So perhaps there is some possibility of hosting test vectors with IANA.

I would want to ensure that the references made in RFCs are not changed
after publication.

You could consider publishing the hash of the files along with the
references in an appendix.

Hosting the files in a version control system and referencing them that way
seems like the least effort.

OS


On Thu, Sep 19, 2024, 7:17 PM Christopher Patton <cpatton=
[e-mail]> wrote:

> Hi CFRG,
>
> It occurred to me today that our drafts often have human-friendly test
> vectors that look something like this:
> https://datatracker.ietf.org/doc/html/rfc9180#appendix-A.1.1
>
> These aren't super convenient for a machine. In theory you could write a
> script that downloads https://www.rfc-editor.org/rfc/rfc9180.txt and
> write a parser to pull out the test vectors, but does anyone really do
> this? Luckily for RFC 9180 we have a JSON version to work with instead:
>
> https://raw.githubusercontent.com/cfrg/draft-irtf-cfrg-hpke/refs/heads/master/test-vectors.json
>
> How do folks feel about pointing to machine readable test vectors from an
> RFC in lieu of producing human-friendly, but machine-unfriendly in the
> appendix? Suppose for example an RFC had a pointer to a JSON blob somewhere
> on datatracker. Is this feasible/desirable?
>
> Thanks,
> Chris P.
>
> _______________________________________________
> CFRG mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
>