[CFRG] Re: Where should test vectors live?

[Christopher Patton <[e-mail]>]

Sofi,

Good point. From this perspective, I think the ideal place to host test
vectors would be on datatracker, since presumably datatracker outlives any
RFC! Does anyone know if this is an option? Can an RFC have a link to
datatracker?

On Fri, Sep 20, 2024 at 10:47 AM Sofia Celi <[e-mail]> wrote:

> This is a nice idea, Chris!
>
> At the risk of being ''too academic'' here, there is some way that
> conferences handle artifacts, for example, the CCS one:
> https://www.sigsac.org/ccs/CCS2024/call-for/call-for-artifacts.html Some
> of the tools (Zenodo, FigShare, Dryad, or Software Heritage) suggested
> there allow for versions, citations, DOI, and have a declared plan to
> enable permanent accessibility (which I think Github/Gitlab do not have).
>
> Thank you,
>
> On 20/09/2024 18:31, Christopher Patton wrote:
> > +1, this is my favorite idea on the thread so far. What do folks think
> > of this?
> > https://github.com/cfrg/draft-irtf-cfrg-vdaf/pull/430 <https://
> > github.com/cfrg/draft-irtf-cfrg-vdaf/pull/430>
> >
> > Basically the RFC has a "Test Vectors" section that tells where the test
> > vectors are and how to consume them. Also, point to a git commit so that
> > the user can verify them:
> >
> > curl -L https://github.com/cfrg/draft-irtf-cfrg-vdaf/archive/\ <https://
> > github.com/cfrg/draft-irtf-cfrg-vdaf/archive/\
> <http://github.com/cfrg/draft-irtf-cfrg-vdaf/archive/%5C>>
> > bb01e528dab1da66c3264347a7c020f2c3403494.tar.gz |\
> > tar -zxf - "*/test_vec/*.json"
> >
> > Chris P.
> >
> > On Fri, Sep 20, 2024 at 3:46 AM Frank Denis
> > <cfrg=[e-mail]
> > <mailto:[e-mail]>> wrote:
> >
> >     Hi Ori,
> >
> >     This is very good idea.
> >
> >     And if files are hosted in Git, publishing the hash is not even
> >     necessary, as the URI can directly represent a specific revision.
> >
> >     -Frank.
> >
> >      > On Sep 20, 2024, at 03:03, Orie Steele
> >     <[e-mail]> wrote:
> >      >
> >      > 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.
> >
> >
> >
> >
> >     _______________________________________________
> >     CFRG mailing list -- [e-mail] <mailto:[e-mail]>
> >     To unsubscribe send an email to [e-mail] <mailto:cfrg-
> >     [e-mail]>
> >
> >
> > _______________________________________________
> > CFRG mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
>
> --
> Sofía Celi
> @claucece
> Cryptographic research and implementation at many places.
> Reach me out at: [e-mail]
> Website: https://sofiaceli.com/
>
> _______________________________________________
> CFRG mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
>