Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: 
 <CAG2Zi20N98cxpgjfRe6gWw1SQEoux+5P3NhLBFUfUHk_udYeFg@mail.gmail.com>
Date: Fri, 20 Sep 2024 03:24:25 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <282D3E19-B25D-4E1A-B13E-778A9B5A9A4E@tzi.org>
References: 
 <CAG2Zi20N98cxpgjfRe6gWw1SQEoux+5P3NhLBFUfUHk_udYeFg@mail.gmail.com>
To: Christopher Patton <cpatton=40cloudflare.com@dmarc.ietf.org>
Message-ID-Hash: BG3C7UWDO55VPDUHA4IEEZWUL6O2UTLE
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/E8Q_gBN4rzx39BoHJNZOzu0Tupk>

On 20. Sep 2024, at 02:17, Christopher Patton =
<cpatton=3D40cloudflare.com@dmarc.ietf.org> wrote:
>=20
> 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?

It is actually much better to download =
https://www.rfc-editor.org/rfc/rfc9180.xml and use a tool such as =
kramdown-rfc-extract-sourcecode [1] to extract the <sourcecode snippets =
in the document.
If the document authors have used the type=3D and name=3D attributes, =
the extraction result can go right into CI scripts and other processing.
(In RFC 9180, the type attribute is used wisely, but the name attributes =
are all empty, so kramdown-rfc-extract-sourcecode will guess file names =
from the context.)

Maintaining your own test vector blob of course gives you more ways to =
evolve the test vectors (and to handle those pesky errata), but I wanted =
to point out that it is easy to get at the actual test vectors in the =
RFCXML document without writing fragile heuristic text file parsers.

Gr=C3=BC=C3=9Fe, Carsten

[1]: https://github.com/cabo/kramdown-rfc/wiki/Extracting-sourcecode