Return-Path: X-Original-To: cfrg@ietfa.amsl.com Delivered-To: cfrg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FE40C14F6A6 for ; Fri, 20 Sep 2024 10:57:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.106 X-Spam-Level: X-Spam-Status: No, score=-2.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cloudflare.com Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d8UcXpP9J3MI for ; Fri, 20 Sep 2024 10:57:48 -0700 (PDT) Received: from mail-qt1-x831.google.com (mail-qt1-x831.google.com [IPv6:2607:f8b0:4864:20::831]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F19BC14F6A7 for ; Fri, 20 Sep 2024 10:57:48 -0700 (PDT) Received: by mail-qt1-x831.google.com with SMTP id d75a77b69052e-45821ebb4e6so16873771cf.2 for ; Fri, 20 Sep 2024 10:57:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudflare.com; s=google09082023; t=1726855067; x=1727459867; darn=irtf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=4giMTApkHajQHgf94dSAT+9ntr2muxs/2R4dnjuu01c=; b=TUHS544PYjkem1qnmDDIWVNPGbAAL67V/BJEeyzLwX6KV6g1TfRct6+vlzsD3a76wI 9DqRG06af4JAEai4biSIklTX0QaXEfO+bokSpQsBabC1LXJrdOQ4ACnixYb9pIkEMu3X nWI1W3pFcmbfVsuwVcnxh56rgUBknJG9pUuMg3nwGUW0J+xRICprRCMEVqZv8HhbneG3 ovWLZ0QEyAkj5T1dphNzip491C36Q3MxixNuqT5YBGl6PCn/CsPxgmiG575DM6FYZqIX r7jH/lvzjCPI45KO2wOL7GNh9ZBdOY0qjRYskq72Vd90cQQ1RNKnV117jFdu9E+A5NV/ sHbw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1726855067; x=1727459867; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=4giMTApkHajQHgf94dSAT+9ntr2muxs/2R4dnjuu01c=; b=GxUWhB1gj2YSx85DP/rpv4UkarFfJBB4addL3tBNOXA3AD6AbDY7dewXYoa1uNcuxq jy+PGrgBjiuO7qUzkg9MrCyB74yz63SvE0Thn4gjWdPnG1iMS6SI2tdIBLx69Zs/JqR7 rXtn/A+KzANREtU9pkXzfKHVct/j7XxPNgFf+0m/xsH4Bgfih4TvZJknNf63I4ITofBf U6ZhZ6Wvx+G7V8Eg7694Nyqo+j+6FyeOfKR2loD3du5MLVp/EQrZG4jcqstCLYkGv/T0 Rdta+rgtuhU9Mn3ZjQJT9LwsB1xxyQ6RoEfTqt/vXZN0lmSODVYakOi5CCovGAbcJ621 flSQ== X-Gm-Message-State: AOJu0YzWm9rzgWgl+XUOnYTEmT+XA/8aSXzChaQWCCdi7RyMnFg+D520 /xRxELCyEw00GaBoXoR1ys+n1LMFGpzjQ26DZF6JNKtA8/mzXd7Hz9IB9OZuretvkoU/B0QNiOx z8XM6ARY3sooxj8QPiOnrbES+cLE3dzoN80NxYw== X-Google-Smtp-Source: AGHT+IGrj3+aosMYBOWoc+FLK3oJMO+qUjoRskCacVaOLggrTxHFAF9owQjvQeS7Ja2lKaiKmebLnp1jxp3tuwvcvDk= X-Received: by 2002:a05:622a:50c:b0:458:3207:4a13 with SMTP id d75a77b69052e-45b2291ee81mr41770431cf.50.1726855067092; Fri, 20 Sep 2024 10:57:47 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Christopher Patton Date: Fri, 20 Sep 2024 10:57:36 -0700 Message-ID: To: Sofia Celi Content-Type: multipart/alternative; boundary="000000000000da84d3062290c63f" Message-ID-Hash: 25RTZNFE65UWGJ4NZSPGIJPBBQYB5KXX X-Message-ID-Hash: 25RTZNFE65UWGJ4NZSPGIJPBBQYB5KXX X-MailFrom: cpatton@cloudflare.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-cfrg.irtf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: cfrg@irtf.org X-Mailman-Version: 3.3.9rc4 Precedence: list Subject: =?utf-8?q?=5BCFRG=5D_Re=3A_Where_should_test_vectors_live=3F?= List-Id: Crypto Forum Research Group Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --000000000000da84d3062290c63f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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=E2=80=AFAM Sofia Celi = 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 > github.com/cfrg/draft-irtf-cfrg-vdaf/pull/430> > > > > Basically the RFC has a "Test Vectors" section that tells where the tes= t > > vectors are and how to consume them. Also, point to a git commit so tha= t > > the user can verify them: > > > > curl -L https://github.com/cfrg/draft-irtf-cfrg-vdaf/archive/\ > 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 > > > > 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 > > 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 > leave@irtf.org> > > > > > > _______________________________________________ > > CFRG mailing list -- cfrg@irtf.org > > To unsubscribe send an email to cfrg-leave@irtf.org > > -- > Sof=C3=ADa Celi > @claucece > Cryptographic research and implementation at many places. > Reach me out at: cherenkov@riseup.net > Website: https://sofiaceli.com/ > > _______________________________________________ > CFRG mailing list -- cfrg@irtf.org > To unsubscribe send an email to cfrg-leave@irtf.org > --000000000000da84d3062290c63f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Sofi,

Good point. From this = perspective, I think the ideal place to host test vectors would be on datat= racker, 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=E2=80=AFAM Sofia Celi <cherenkov@riseup.net> wrote:
This is a nice idea, Chris!

At the risk of being ''too academic'' here, there is some w= ay that
conferences handle artifacts, for example, the CCS one:
https://www.sigsac.org/ccs/CCS202= 4/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-v= daf/pull/430 <https://
> github.com/cfrg/draft-irtf-cfrg-vdaf/pull= /430>
>
> Basically the RFC has a "Test Vectors" section that tells wh= ere the test
> vectors are and how to consume them. Also, point to a git commit so th= at
> the user can verify them:
>
> curl -L https://github.com/cfrg/draft-i= rtf-cfrg-vdaf/archive/\ <https://
> github.com/cfrg/draft-irtf-cfrg-vdaf/arc= hive/\>
> bb01e528dab1da66c3264347a7c020f2c3403494.tar.gz |\
> tar -zxf - "*/test_vec/*.json"
>
> Chris P.
>
> On Fri, Sep 20, 2024 at 3:46=E2=80=AFAM Frank Denis
> <cfrg=3D40pureftpd.org@dmarc.ietf.org
> <mailto:40pureftpd.org@dmarc.ietf.org>> wrote:
>
>=C2=A0 =C2=A0 =C2=A0Hi Ori,
>
>=C2=A0 =C2=A0 =C2=A0This is very good idea.
>
>=C2=A0 =C2=A0 =C2=A0And if files are hosted in Git, publishing the hash= is not even
>=C2=A0 =C2=A0 =C2=A0necessary, as the URI can directly represent a spec= ific revision.
>
>=C2=A0 =C2=A0 =C2=A0-Frank.
>
>=C2=A0 =C2=A0 =C2=A0 > On Sep 20, 2024, at 03:03, Orie Steele
>=C2=A0 =C2=A0 =C2=A0<orie@transmute.industries> wrote:
>=C2=A0 =C2=A0 =C2=A0 >
>=C2=A0 =C2=A0 =C2=A0 > I would want to ensure that the references ma= de in RFCs are not
>=C2=A0 =C2=A0 =C2=A0changed after publication.
>=C2=A0 =C2=A0 =C2=A0 >
>=C2=A0 =C2=A0 =C2=A0 > You could consider publishing the hash of the= files along with
>=C2=A0 =C2=A0 =C2=A0the references in an appendix.
>=C2=A0 =C2=A0 =C2=A0 >
>=C2=A0 =C2=A0 =C2=A0 > Hosting the files in a version control system= and referencing
>=C2=A0 =C2=A0 =C2=A0them that way seems like the least effort.
>
>
>
>
>=C2=A0 =C2=A0 =C2=A0_______________________________________________
>=C2=A0 =C2=A0 =C2=A0CFRG mailing list -- cfrg@irtf.org <mailto:cfrg@irtf.org>
>=C2=A0 =C2=A0 =C2=A0To unsubscribe send an email to cfrg-leave@irtf.org <mailto:cfrg-
>=C2=A0 =C2=A0 =C2=A0leave@irtf.org>
>
>
> _______________________________________________
> CFRG mailing list -- cfrg@irtf.org
> To unsubscribe send an email to cfrg-leave@irtf.org

--
Sof=C3=ADa Celi
@claucece
Cryptographic research and implementation at many places.
Reach me out at: = cherenkov@riseup.net
Website: https://sofiaceli.com/

_______________________________________________
CFRG mailing list -- cfr= g@irtf.org
To unsubscribe send an email to cfrg-leave@irtf.org
--000000000000da84d3062290c63f--