IETF Logo Mail Archive

[CFRG] Re: Where should test vectors live?

Watson Ladd <watsonbladd@gmail.com> Fri, 20 September 2024 01:09 UTC

Return-Path: <watsonbladd@gmail.com>
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 93AD3C15198F for <cfrg@ietfa.amsl.com>; Thu, 19 Sep 2024 18:09:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, 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=gmail.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 wh65UZkMCJpy for <cfrg@ietfa.amsl.com>; Thu, 19 Sep 2024 18:09:43 -0700 (PDT)
Received: from mail-wm1-x32d.google.com (mail-wm1-x32d.google.com [IPv6:2a00:1450:4864:20::32d]) (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 6A26DC151980 for <cfrg@irtf.org>; Thu, 19 Sep 2024 18:09:43 -0700 (PDT)
Received: by mail-wm1-x32d.google.com with SMTP id 5b1f17b1804b1-42cb806623eso12266935e9.2 for <cfrg@irtf.org>; Thu, 19 Sep 2024 18:09:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1726794582; x=1727399382; 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=VTi3zOv8hPA8FjbdT960ZX2nsURSXsvm5BP6e83QeYQ=; b=YkJJaJ1wleVM0wUuQJO3lfD0DenFMP+DV0fcuAwmoNAC73479ppN6Cnt7kb1dH9jsF vhvJPkfialcV0GaqUiSqjU0HQKQNFN66+rb9DpEgPFEDGl6XPVXlQEYqF17KcPa5aFkM n4hA6flPm/VcszHhf2HI2eDLupVoDkV4Isapc3adWHuxgtjmvBpEd/WYinS7mrsQb/fI KrDLq7cmIy1v/eLXDVcnFXefgISsPtpYUqfeoy10uPUmE7qHqZsTHsJssNb85So+9AoL aYLVncIi1KzAZy8+iyv8/um/6GpIrc1V71k2myI3odfeCuEDbAahSdKXEfSuQtmAI34x dHTQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1726794582; x=1727399382; 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=VTi3zOv8hPA8FjbdT960ZX2nsURSXsvm5BP6e83QeYQ=; b=Lxjs0PgNiBHgoFTlcZtGmDjDRikBbHqq1k7ScVMgzw7KSU8gnL3hff0BlQOIRg3NEZ D1nDovfr4uk2yt4z77Bvt+3RMFk1VPATVeoHjM1K26sVIJKyyooVUz/Lx8orGiw1GNzs hTpzHMX5wvZyQnegeX1V9tcVPdBERGTYqyn7+/KZYC03acvVNqUpSHEMksV81wJpeNK5 lPzqjnUo4vXVmZD9RdXumLgv2R4CVR1KtxJ6uPmLH92XwngHimyT+dYxZ9C8jufYFpdR 9kVMglGVQz1HcqLRtWyLtnDvjnEBNlbDJAgP7ilyd8T/c6NCHhN89gl36uWfws4KNZf9 HwrQ==
X-Gm-Message-State: AOJu0YzfD9bvSukCsw4o077QGp0yMOu4ptMnIp3bzL0QbE5mYqQqLa0W YUuzIhSoyea+iaWEsYPIq2IswjwuI5txd2nq+XNfRVa/yj8A/AFhNnoy/oghuSIautYw/pQAP0X qKQFCby61pZsvlJEt+FPfyBQA0pcPyw==
X-Google-Smtp-Source: AGHT+IHwY+kzkDaiCHFBTflkA/jDqpGgIYNE0AYA81MMIDu43yu0jP4iTMfOhoFHg06SNRgB/V6J/AB5aaihpl5DdWo=
X-Received: by 2002:a05:600c:154d:b0:42c:acfa:9cae with SMTP id 5b1f17b1804b1-42e7adc0d9dmr6323305e9.35.1726794581537; Thu, 19 Sep 2024 18:09:41 -0700 (PDT)
MIME-Version: 1.0
References: <CAG2Zi20N98cxpgjfRe6gWw1SQEoux+5P3NhLBFUfUHk_udYeFg@mail.gmail.com>
In-Reply-To: <CAG2Zi20N98cxpgjfRe6gWw1SQEoux+5P3NhLBFUfUHk_udYeFg@mail.gmail.com>
From: Watson Ladd <watsonbladd@gmail.com>
Date: Thu, 19 Sep 2024 18:09:30 -0700
Message-ID: <CACsn0cmLjjyxcKsiHio-Vu-8jo80FQ=aFtoO3GD69jC5kUig9A@mail.gmail.com>
To: Christopher Patton <cpatton=40cloudflare.com@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a1fc54062282b10a"
Message-ID-Hash: BSUTLDSDYZDE2PNK2M4JZMI4KALZ5IAE
X-Message-ID-Hash: BSUTLDSDYZDE2PNK2M4JZMI4KALZ5IAE
X-MailFrom: watsonbladd@gmail.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 <cfrg@irtf.org>
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/B8l3WmgXMiqq1yGe2-jcq5-6H_Q>
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>

On Thu, Sep 19, 2024, 5:18 PM Christopher Patton <cpatton=
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/master/test-vectors.json
>
> How do folks feel about pointing to machine readable test vectors from an
> 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 somewhere
> 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
>

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