MIME-Version: 1.0
References: 
 <CAG2Zi20N98cxpgjfRe6gWw1SQEoux+5P3NhLBFUfUHk_udYeFg@mail.gmail.com>
 <CAN8C-_KDTg2ZatR7tf0K9e19Xz24CrMF06_vB8fc0ZioqZ+oeA@mail.gmail.com>
 <BF349DA5-981E-4B06-83B7-8C6654D7F64B@pureftpd.org>
In-Reply-To: <BF349DA5-981E-4B06-83B7-8C6654D7F64B@pureftpd.org>
From: Christopher Patton <cpatton@cloudflare.com>
Date: Fri, 20 Sep 2024 10:31:07 -0700
Message-ID: 
 <CAG2Zi21Qq0ENbdXgdkmZ86xcLyHMgExfKqsAy2M9T4PMGYf8FQ@mail.gmail.com>
To: Frank Denis <cfrg=40pureftpd.org@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="00000000000020625c062290680f"
Message-ID-Hash: ZNSX3U6KUHXZ46MWAL7GZ3WSQUOH32G3
CC: CFRG <cfrg@irtf.org>
Precedence: list
Subject: =?utf-8?q?=5BCFRG=5D_Re=3A_Where_should_test_vectors_live=3F?=
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/cfrg/2Gr0lg6VyvDOlVfeHA2sVHznF6k>

--00000000000020625c062290680f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

+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

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/\
bb01e528dab1da66c3264347a7c020f2c3403494.tar.gz |\
tar -zxf - "*/test_vec/*.json"

Chris P.

On Fri, Sep 20, 2024 at 3:46=E2=80=AFAM Frank Denis <cfrg=3D
40pureftpd.org@dmarc.ietf.org> 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 <orie@transmute.industries>
> 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 -- cfrg@irtf.org
> To unsubscribe send an email to cfrg-leave@irtf.org
>

--00000000000020625c062290680f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">+1, this is my favorite idea on the thread so far. What do=
 folks think of this?<br><div><a href=3D"https://github.com/cfrg/draft-irtf=
-cfrg-vdaf/pull/430">https://github.com/cfrg/draft-irtf-cfrg-vdaf/pull/430<=
/a></div><div><br></div><div>Basically the RFC has a &quot;Test Vectors&quo=
t; section that tells where the test vectors are and how to consume them. A=
lso, point to a git commit so that the user can verify them:<br></div><div>=
<br></div><div>curl -L <a href=3D"https://github.com/cfrg/draft-irtf-cfrg-v=
daf/archive/\">https://github.com/cfrg/draft-irtf-cfrg-vdaf/archive/\</a><b=
r>bb01e528dab1da66c3264347a7c020f2c3403494.tar.gz |\<br>tar -zxf - &quot;*/=
test_vec/*.json&quot;</div><div><br></div><div>Chris P.<br></div></div><br>=
<div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Se=
p 20, 2024 at 3:46=E2=80=AFAM Frank Denis &lt;cfrg=3D<a href=3D"mailto:40pu=
reftpd.org@dmarc.ietf.org">40pureftpd.org@dmarc.ietf.org</a>&gt; wrote:<br>=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Ori,<br>
<br>
This is very good idea.<br>
<br>
And if files are hosted in Git, publishing the hash is not even necessary, =
as the URI can directly represent a specific revision.<br>
<br>
-Frank.<br>
<br>
&gt; On Sep 20, 2024, at 03:03, Orie Steele &lt;orie@transmute.industries&g=
t; wrote:<br>
&gt; <br>
&gt; I would want to ensure that the references made in RFCs are not change=
d after publication.<br>
&gt; <br>
&gt; You could consider publishing the hash of the files along with the ref=
erences in an appendix.<br>
&gt; <br>
&gt; Hosting the files in a version control system and referencing them tha=
t way seems like the least effort.<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
CFRG mailing list -- <a href=3D"mailto:cfrg@irtf.org" target=3D"_blank">cfr=
g@irtf.org</a><br>
To unsubscribe send an email to <a href=3D"mailto:cfrg-leave@irtf.org" targ=
et=3D"_blank">cfrg-leave@irtf.org</a><br>
</blockquote></div>

--00000000000020625c062290680f--