Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: 
 <DU0PR05MB9720A330F827931CE6FCFCE2836C2@DU0PR05MB9720.eurprd05.prod.outlook.com>
Date: Fri, 20 Sep 2024 18:47:44 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <6BC090CE-7F48-47EC-B100-D5867DCF72A5@tzi.org>
References: 
 <CAG2Zi20N98cxpgjfRe6gWw1SQEoux+5P3NhLBFUfUHk_udYeFg@mail.gmail.com>
 <CACsn0cmLjjyxcKsiHio-Vu-8jo80FQ=aFtoO3GD69jC5kUig9A@mail.gmail.com>
 <DU0PR05MB9720F36FCE38A9477411FB9B836C2@DU0PR05MB9720.eurprd05.prod.outlook.com>
 <4A43A49C-443C-4B8C-8795-021ADEEF733E@tzi.org>
 <DU0PR05MB9720A88DCA9BC057068D64F3836C2@DU0PR05MB9720.eurprd05.prod.outlook.com>
 <DDE188BA-342E-48D0-9EF0-F1B108414FD9@tzi.org>
 <DU0PR05MB9720A330F827931CE6FCFCE2836C2@DU0PR05MB9720.eurprd05.prod.outlook.com>
To: =?utf-8?Q?Bj=C3=B6rn_Haase?= <bjoern.haase=40endress.com@dmarc.ietf.org>
Message-ID-Hash: PYGA3UHKEWLHI3YENZED4HR37Q23YU35
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/-ITUcO9ecAyNJ-9N8I77xlXk0xA>

On 2024-09-20, at 13:47, Bj=C3=B6rn Haase =
<bjoern.haase=3D40endress.com@dmarc.ietf.org> wrote:
>=20
> I did not find off-the-shelf tools for decoding that don't rely on the =
specific bash script.=20

Hi Bj=C3=B6rn,

this is useful information.

I believe this is best addressed by adding a web page that allows access =
to extracted <sourcecode snippets (after any RFC 8792 decoding, if that =
happens to apply) from existing RFC and I-D documents (specifically =
their XML form, as extracting from the plain text form cannot ever be =
fully reliable).

It may also be useful to provide a CLI tool (*) that does exactly RFC =
8792 decoding and nothing else.  I didn=E2=80=99t see a use case because =
the need for that decoding only ever arises in the context of extracting =
<sourcecode snippets from a document, so I made it part of that, but =
maybe people feel more comfortable with integrating a =E2=80=9Cdo one =
thing well=E2=80=9D tool into their workflows.

Gr=C3=BC=C3=9Fe, Carsten

(*) FYI the actual decoding is approximately 29 LOC in my =
implementation; need to add CLI parsing and file handling.