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 1BD1BC151998 for ; Thu, 19 Sep 2024 18:13:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.905 X-Spam-Level: X-Spam-Status: No, score=-1.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-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=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ipv-sx.20230601.gappssmtp.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 CdrzBDDZGBWJ for ; Thu, 19 Sep 2024 18:13:42 -0700 (PDT) Received: from mail-io1-xd2d.google.com (mail-io1-xd2d.google.com [IPv6:2607:f8b0:4864:20::d2d]) (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 E3E52C15199C for ; Thu, 19 Sep 2024 18:13:42 -0700 (PDT) Received: by mail-io1-xd2d.google.com with SMTP id ca18e2360f4ac-82a626d73efso65010639f.1 for ; Thu, 19 Sep 2024 18:13:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipv-sx.20230601.gappssmtp.com; s=20230601; t=1726794821; x=1727399621; 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=0SNN1TSqu5GyItVrzrBznxoDMX1Y6YQUofO9PVL8dTE=; b=q7vFR7mDb2SE4qpLvwT4KbQMSySpIJcqamARAFH3WLxWwj9ZhCRkmy/QxSfwbnK177 X+2VuHtQgVRvwNekZqryK9PLUDbgi/KS/h2rL+5tkFJt/rul6D8uO2P8fvt1kMUkOgXa ccdYVHrQB4ZaV5PbqZS30fWkTHNA17D5y9ze0xYwYcBR1FOEySSsrBF+F0M56UQkL7vc 1o5qTmzl4A+cKSyti419/FMI+ZsrB0/Jbh+4AvYrozlR5JiAcUd0E3CALALaZ8SXp4Js VLbiMCfMwrUNXEw7o3VT8IitV5cW8rGV7Nm7f2RDcidotPXeiVT7LMRu6+TfFHuGR31Z hLzw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1726794821; x=1727399621; 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=0SNN1TSqu5GyItVrzrBznxoDMX1Y6YQUofO9PVL8dTE=; b=L3m2Fn6X5Ge3MCVWjyomlmoQSua7D9E7ixwtikG+IGopnz190Dah2Q5ceY7a1FN3ZT AVfXNhEmQUThF6PaQf3t+jYLdxziJw8kDK+2PNtDqZEUb1MztcDawUogy+aPHE9JQLzT 3KnbGEMhvYj/BGhfYMzjcPb13KEaR8VzNBZrxZ6f7YpEDMg60Sqh0v9BSpBTUftjhz2Z sXW4a4Wdpshjmax9X/p/mn6XvEVRLE+ovbTVpw/TviIpDKwTi7HsjU3c2XEWqX1ZbEGN MZCHXjIrbYkUZsV5TgMm/+QemzttykpUPL/jf77oFo6TbTimKJb7iPCiK4SA1EvypJJn GcIw== X-Forwarded-Encrypted: i=1; AJvYcCWEXjJeInOIQW0Ey6v2181B+QWyc4MxEpepEYXYkGXM17O4Rip9FdgrbLdQtJv7RVcoR3xb@irtf.org X-Gm-Message-State: AOJu0YxlhabKVn7gAlZno/2pvubNeR2sKZujmCa7JS0YoUb+P6g2LdG8 flAVqxJZN5+lUq4Gq8nadqvssrfYBq/KoYgd+DIsjcM5Ac5vSgTe63wBq9SLYVm9p6xBPonu7ad X66y3OBxZXkNGKJottuC59JkhPDY9mjL+hc/G3A== X-Google-Smtp-Source: AGHT+IEySwKwedl4jBWJ8zaEpjHJ5E2Ck7PvwY7fMC3Aj/JpECzw9EG7M22g9+OUIr7U35mfl146BC30hhA/4y3Fjko= X-Received: by 2002:a92:ca0e:0:b0:3a0:beb4:e402 with SMTP id e9e14a558f8ab-3a0c9cd0c3emr9099085ab.1.1726794821583; Thu, 19 Sep 2024 18:13:41 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Richard Barnes Date: Thu, 19 Sep 2024 21:13:30 -0400 Message-ID: To: Watson Ladd Content-Type: multipart/alternative; boundary="000000000000f0eb82062282bf1e" Message-ID-Hash: LFBA4SQO3T2PUPRGLZD3ZB7GYSQIDW43 X-Message-ID-Hash: LFBA4SQO3T2PUPRGLZD3ZB7GYSQIDW43 X-MailFrom: rlb@ipv.sx 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: Christopher Patton , CFRG 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: --000000000000f0eb82062282bf1e Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable FWIW, RFC 6716 contains the source code of a reference implementation, and instructions for how to extract and build the code from the RFC: https://datatracker.ietf.org/doc/html/rfc6716#appendix-A.1 You could do a similar thing with test vectors. On Thu, Sep 19, 2024 at 9:10=E2=80=AFPM Watson Ladd = wrote: > > > On Thu, Sep 19, 2024, 5:18=E2=80=AFPM Christopher Patton 40cloudflare.com@dmarc.ietf.org> 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/m= aster/test-vectors.json >> >> How do folks feel about pointing to machine readable test vectors from a= n >> 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 somewh= ere >> on datatracker. Is this feasible/desirable? >> > > Why not in ignored elements (not sure how to do)in the XML source? This > might take some tools team input. > >> >> Thanks, >> Chris P. >> >> _______________________________________________ >> CFRG mailing list -- cfrg@irtf.org >> To unsubscribe send an email to cfrg-leave@irtf.org >> > _______________________________________________ > CFRG mailing list -- cfrg@irtf.org > To unsubscribe send an email to cfrg-leave@irtf.org > --000000000000f0eb82062282bf1e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
FWIW, RFC 6716 contains the source code of a referenc= e implementation, and instructions for how to extract and build the code fr= om the RFC:


You could do a similar th= ing with test vectors.

On Thu, Sep 19, 2024 at 9:10=E2=80=AFPM Wat= son Ladd <watsonbladd@gmail.com= > wrote:
=


On Thu, Sep 19, 2024, 5:18=E2=80=AFPM Christopher Patt= on <cpatton=3D40cloudflare.com@dmarc.ietf.org> wrote:
Hi CFRG,

It occurred to me today that our drafts often have = human-friendly test vectors that look something like this:

These aren't super convenie= nt for a machine. In theory you could write a script that downloads https://www.rfc-editor.org/rfc/rfc9180.txt and write a pars= er to pull out the test vectors, but does anyone really do this? Luckily fo= r RFC 9180 we have a JSON version to work with instead:

How do folks feel about pointing to m= achine readable test vectors from an RFC in lieu of producing human-friendl= y, but machine-unfriendly in the appendix? Suppose for example an RFC had a= pointer to a JSON blob somewhere on datatracker. Is this feasible/desirabl= e?

Why not in ignored elements (not sure how to do)in the XML source= ? This might take some tools team input.

Thanks,
Chris P.

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