IETF Logo Mail Archive

[CFRG] Re: Where should test vectors live?

Sofia Celi <cherenkov@riseup.net> Fri, 20 September 2024 17:47 UTC

Return-Path: <cherenkov@riseup.net>
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 A0EB0C14F6A1 for <cfrg@ietfa.amsl.com>; Fri, 20 Sep 2024 10:47:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.108
X-Spam-Level:
X-Spam-Status: No, score=-7.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-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 (1024-bit key) header.d=riseup.net
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 XezVAHZ8EjLs for <cfrg@ietfa.amsl.com>; Fri, 20 Sep 2024 10:47:01 -0700 (PDT)
Received: from mx0.riseup.net (mx0.riseup.net [198.252.153.6]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40900C14F5EA for <cfrg@irtf.org>; Fri, 20 Sep 2024 10:47:01 -0700 (PDT)
Received: from fews02-sea.riseup.net (fews02-sea-pn.riseup.net [10.0.1.112]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx0.riseup.net (Postfix) with ESMTPS id 4X9KZr5JK5z9x84 for <cfrg@irtf.org>; Fri, 20 Sep 2024 17:47:00 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1726854420; bh=SUOE1jff2TRHeWuqjbzoZlSX9JQcAcaScNhgOkQjfLk=; h=Date:Subject:To:References:From:In-Reply-To:From; b=mvBTJUAIG4lNqm5+hoWhExztldVWKzi0w5NOcPEHUEfxytKn1LSjF7ExU512deWEZ J/Kz0uvphVa/2Bz9K66f3MX7YI+RKLUfjrs9s2c0spdVHj+FDPE7qoUO4vvyXSkoMj pOkl2qe1Cd+JZa2+U5nMiBqXXHEt6KGvAsiJpAtQ=
X-Riseup-User-ID: A8997A877C6C0CFF7BB1716B670B6FDD6A9A4AA70F9F5D595E333E549BE8D44E
Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews02-sea.riseup.net (Postfix) with ESMTPSA id 4X9KZr2HJPzFw3p for <cfrg@irtf.org>; Fri, 20 Sep 2024 17:47:00 +0000 (UTC)
Message-ID: <ed017073-0627-4c01-bcf4-a64cef743ed2@riseup.net>
Date: Fri, 20 Sep 2024 18:46:58 +0100
MIME-Version: 1.0
To: cfrg@irtf.org
References: <CAG2Zi20N98cxpgjfRe6gWw1SQEoux+5P3NhLBFUfUHk_udYeFg@mail.gmail.com> <CAN8C-_KDTg2ZatR7tf0K9e19Xz24CrMF06_vB8fc0ZioqZ+oeA@mail.gmail.com> <BF349DA5-981E-4B06-83B7-8C6654D7F64B@pureftpd.org> <CAG2Zi21Qq0ENbdXgdkmZ86xcLyHMgExfKqsAy2M9T4PMGYf8FQ@mail.gmail.com>
Content-Language: en-GB
From: Sofia Celi <cherenkov@riseup.net>
In-Reply-To: <CAG2Zi21Qq0ENbdXgdkmZ86xcLyHMgExfKqsAy2M9T4PMGYf8FQ@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Message-ID-Hash: XTTC32XHO4QFVFAV5WGRN6PRJ3RXJYL6
X-Message-ID-Hash: XTTC32XHO4QFVFAV5WGRN6PRJ3RXJYL6
X-MailFrom: cherenkov@riseup.net
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
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [CFRG] Re: Where should test vectors live?
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cfrg/7rDdMWizT6jZd5ZRf37eqma9L6Y>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cfrg>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Owner: <mailto:cfrg-owner@irtf.org>
List-Post: <mailto:cfrg@irtf.org>
List-Subscribe: <mailto:cfrg-join@irtf.org>
List-Unsubscribe: <mailto:cfrg-leave@irtf.org>

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/\>
> bb01e528dab1da66c3264347a7c020f2c3403494.tar.gz |\
> tar -zxf - "*/test_vec/*.json"
> 
> Chris P.
> 
> On Fri, Sep 20, 2024 at 3:46 AM Frank Denis 
> <cfrg=40pureftpd.org@dmarc.ietf.org 
> <mailto: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 <mailto:cfrg@irtf.org>
>     To unsubscribe send an email to cfrg-leave@irtf.org <mailto:cfrg-
>     leave@irtf.org>
> 
> 
> _______________________________________________
> CFRG mailing list -- cfrg@irtf.org
> To unsubscribe send an email to cfrg-leave@irtf.org

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

v2.39.1 | Report a Bug | By Email | System Status