Re: [Tools-discuss] .txt? [I-D Action: draft-xxx.txt]

Carsten Bormann <> Tue, 29 June 2021 16:05 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6E29E3A38C6 for <>; Tue, 29 Jun 2021 09:05:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id W6im2-ahxFyC for <>; Tue, 29 Jun 2021 09:05:38 -0700 (PDT)
Received: from ( [IPv6:2001:638:708:32::19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D86613A38C5 for <>; Tue, 29 Jun 2021 09:05:37 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPSA id 4GDq7p371rz2xHV; Tue, 29 Jun 2021 18:05:25 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.\))
From: Carsten Bormann <>
In-Reply-To: <>
Date: Tue, 29 Jun 2021 18:05:14 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <20210627013258.1D30F188447C@ary.qy> <> <> <> <> <> <> <> <> <> <>
To: Julian Reschke <>
X-Mailer: Apple Mail (2.3654.
Archived-At: <>
Subject: Re: [Tools-discuss] .txt? [I-D Action: draft-xxx.txt]
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 29 Jun 2021 16:05:43 -0000

>> As a format for authoring, making the input vastly more complicated in the name of some lofty goal (here: standards conformance) is exactly the leading symptom of the v3 development process.  Offering a bespoke, efficient(*) way of keyboarding IETF document references is exactly the right way to handle this, at least for people still authoring in XML.
> It is not "vastly more complicated". It's a different syntax (with the
> benefit of it not being PI-based which is yet another XML complication
> for most authors). (*)

Yes.  Not using PIs means that this feature now comes under the strict eyes of the chaperone, the RNG validation.
So we all have to fix up the RFCXML RNC to make this feature available in various environments.
This is not progress.

Also, the fact that there now need to be full URIs instead of more reasonable document identifiers is confusing people.
(Not that the old ones were particularly good, but they should have been simplified, not pessimized.)

Yes, PIs are unclean in some universe.  They are also useful for adding features where being clean gets in the way.

> IFIUC, you miss the feature of not having to specify the complete URL of
> the reference? (Or is there something else I'm not aware of?).

Typing full URLs is not a good use of author time.

> (*) And, BTW the *other* way to include stuff as explained in
> <>
> continues to work, as it's just a basic XML feature.

Which is, of course the one I used during the first 10 years of using RFCXML; I wasn’t even aware about the PI form before I moved away from keyboarding XML.
But others were (and some still use XML), and I’m trying to be their advocate here.

Grüße, Carsten