Re: [Tools-discuss] [Rswg] Is there a reason to allow prepped content in rfcxml Internet-Draft submissions

Carsten Bormann <cabo@tzi.org> Mon, 05 June 2023 19:57 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEFBEC151524 for <tools-discuss@ietfa.amsl.com>; Mon, 5 Jun 2023 12:57:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 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] 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 P0Nuk_rJeuP6 for <tools-discuss@ietfa.amsl.com>; Mon, 5 Jun 2023 12:57:19 -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 RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EEB02C151085 for <tools-discuss@ietf.org>; Mon, 5 Jun 2023 12:57:18 -0700 (PDT)
Received: from smtpclient.apple (p548dc15c.dip0.t-ipconnect.de [84.141.193.92]) (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 4QZksS6YlGzDCbP; Mon, 5 Jun 2023 21:57:16 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.600.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <69781036-0c86-fd20-8e3b-6b44bc395921@nostrum.com>
Date: Mon, 05 Jun 2023 21:57:05 +0200
Cc: "rswg@rfc-editor.org" <rswg@rfc-editor.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <2A8B6DDE-8527-4EAC-8A9C-36CC91933485@tzi.org>
References: <69781036-0c86-fd20-8e3b-6b44bc395921@nostrum.com>
To: tools-discuss <tools-discuss@ietf.org>
X-Mailer: Apple Mail (2.3731.600.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/aLBD-kGLJ3OSFD5mPMMd9UTdzcQ>
Subject: Re: [Tools-discuss] [Rswg] Is there a reason to allow prepped content in rfcxml Internet-Draft submissions
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Jun 2023 19:57:21 -0000

[Rswg] Is there a reason to allow prepped content in rfcxml Internet-Draft submissions

Yes, there is a reason. Running the preptool makes sure all external includes are resolved.

But of course there are better ways to achieve this.

> Should the submission interface for Internet-Drafts allow any prepped content at all?

Probably not.

> Where would it be problematic if the submission checks rejected any submission containing that content?

Not from my point of view.
Of course, the error message must be useful, so the submitter knows what they actually need to change.

Grüße, Carsten