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 62ED8C180B43 for ; Fri, 20 Sep 2024 00:27:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.907 X-Spam-Level: X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=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 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 Tji909J32GwC for ; Fri, 20 Sep 2024 00:27:36 -0700 (PDT) Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [134.102.50.21]) (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 6E09AC16941D for ; Fri, 20 Sep 2024 00:27:35 -0700 (PDT) Received: from smtpclient.apple (p5dc5d074.dip0.t-ipconnect.de [93.197.208.116]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4X93r52jDjzDCdH; Fri, 20 Sep 2024 09:27:33 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51.11.1\)) From: Carsten Bormann In-Reply-To: Date: Fri, 20 Sep 2024 09:27:22 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <4A43A49C-443C-4B8C-8795-021ADEEF733E@tzi.org> References: To: =?utf-8?Q?Bj=C3=B6rn_Haase?= X-Mailer: Apple Mail (2.3776.700.51.11.1) Message-ID-Hash: TQ57WQVQGFP6CE34A2M5EDLT2M2A5TDY X-Message-ID-Hash: TQ57WQVQGFP6CE34A2M5EDLT2M2A5TDY X-MailFrom: cabo@tzi.org 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: On 20. Sep 2024, at 08:49, Bj=C3=B6rn Haase = wrote: >=20 > So far we have integrated ANSI-C test vectors in the draft. I did try = to do similarly for JSON, however it seems that for JSON we will not be = able to follow the =E2=80=9Cmax number of characters per line=E2=80=9D = requirement > for I-D and RFC. You can use RFC 8792 to handle that requirement. (kramdown-rfc-extract-sourcecode automatically reverses that processing, = and kramdown-rfc has several ways to automatically apply the processing = where needed only.) Gr=C3=BC=C3=9Fe, Carsten [1]: https://www.rfc-editor.org/rfc/rfc8792=20 "RFC 8792: Handling Long Lines in Content of Internet-Drafts and RFCs=E2=80= =9D