IETF Logo Mail Archive

Re: [xml2rfc] [Tools-discuss] [Rfc-markdown] New xml2rfc release: v3.16.0

Carsten Bormann <cabo@tzi.org> Fri, 20 January 2023 14:20 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3582C1526FF; Fri, 20 Jan 2023 06:20:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 sKqJWXNuEGbs; Fri, 20 Jan 2023 06:20:17 -0800 (PST)
Received: from smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (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 117A9C15270B; Fri, 20 Jan 2023 06:20:16 -0800 (PST)
Received: from [192.168.217.124] (p548dc9a4.dip0.t-ipconnect.de [84.141.201.164]) (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 4Nz1qJ63lbzDCd9; Fri, 20 Jan 2023 15:20:12 +0100 (CET)
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: <4e6509a8-4eab-8280-103a-02ab58caafb1@petit-huguenin.org>
Date: Fri, 20 Jan 2023 15:20:12 +0100
Cc: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>, xml2rfc@ietf.org, tools-discuss <tools-discuss@ietf.org>
X-Mao-Original-Outgoing-Id: 695917212.293834-bca5df99d962d510c1a029f9ff6af946
Content-Transfer-Encoding: quoted-printable
Message-Id: <E50F7D52-3EC7-4D7F-B061-E5B43F7543A8@tzi.org>
References: <CAD2=Z87EMetcpv66YY_b2+X1-yFy4cTpKMjPoJL=cH99c7P_Uw@mail.gmail.com> <9d719176-a4eb-7cce-e706-10325700531c@petit-huguenin.org> <F1A5624B-16D0-4463-AC5F-B0A03F3B94B6@ietf.org> <8f5a497e-4135-7c0c-46cb-c3fe4791e9f3@petit-huguenin.org> <c3b3064f-e505-f504-f258-06f0d824ed4b@it.aoyama.ac.jp> <147fb362-e522-8ad4-51e2-2363a6e0eeb8@petit-huguenin.org> <5EFC7B9D-05B7-4B33-8BC6-760E080E0B4F@tzi.org> <4e6509a8-4eab-8280-103a-02ab58caafb1@petit-huguenin.org>
To: Marc Petit-Huguenin <marc@petit-huguenin.org>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/aKJMomj1B1rYNXqi9_Al-5JB5UM>
Subject: Re: [xml2rfc] [Tools-discuss] [Rfc-markdown] New xml2rfc release: v3.16.0
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: XML2RFC discussion list <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jan 2023 14:20:19 -0000

> What I see is a bunch of preschooler asking the teacher to remove the lines because it is too hard to color inside them.

Most IETF contributors aren’t preschoolers.

What I see is a teacher handing out tools that can only draw square lines while what needs to be drawn has curves.

I think we have exhausted this discussion; no more light will be created.

The experiment to have xml2rfc mechanically chaperone RFC 7997 has failed, and we need to recover from that experiment — v3.16.0 is a start, but just a start.
(This is compounded by the fact that RFC 7997 is misguided as the way forward for RFCs, but that is a different discussion where I can imagine there could be reasonably different opinions.)

I’d rather spend the time discussing what we need to do to support the efforts of the authors, the reviewers, and the RPC editors in creating high-quality documents.

Grüße, Carsten

v2.29.0 | Report a Bug | By Email | System Status