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

Toerless Eckert <tte@cs.fau.de> Mon, 28 June 2021 19:38 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
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 558283A0BC1 for <tools-discuss@ietfa.amsl.com>; Mon, 28 Jun 2021 12:38:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.65
X-Spam-Level:
X-Spam-Status: No, score=-1.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6yGrhLBbRznQ for <tools-discuss@ietfa.amsl.com>; Mon, 28 Jun 2021 12:38:23 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1AEB03A0BC2 for <tools-discuss@ietf.org>; Mon, 28 Jun 2021 12:38:22 -0700 (PDT)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [131.188.34.51]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id F258754804D; Mon, 28 Jun 2021 21:38:15 +0200 (CEST)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id EB6804E78C1; Mon, 28 Jun 2021 21:38:15 +0200 (CEST)
Date: Mon, 28 Jun 2021 21:38:15 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: John R Levine <johnl@taugh.com>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, tools-discuss@ietf.org
Message-ID: <20210628193815.GL5057@faui48e.informatik.uni-erlangen.de>
References: <20210627013258.1D30F188447C@ary.qy> <691b91b6-86d7-2a3d-b9dc-8c19cc507db4@gmail.com> <584d34d6-5630-bbb7-35cc-9459dabc80f0@taugh.com> <82887902-90d0-3616-656b-fc39e4febd47@gmail.com> <70fee53d-28b9-874a-6988-6c1234ca149@taugh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <70fee53d-28b9-874a-6988-6c1234ca149@taugh.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/uZZOfFwzkgiWok292MvHxFamDUE>
Subject: Re: [Tools-discuss] .txt? [I-D Action: draft-xxx.txt]
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
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, 28 Jun 2021 19:38:27 -0000

I only converted the last rfc i was editor for during the final revisions to go to rfc,
and i only did this so i could use the only one new feature of v3 that i felt i wanted
to use, name the Contributors tag. I still don't know what else i as an author
would benefit from in v3.

I did find the conversion sufficient for that last mile to RFC editor, but not persuasive to
suggest it to authors if/when they want to continue doing mayor edits to the document. This
is primarily beceause the v3 ended up with a tag-verbose XMLv3 than the v2 i had
edited for years. This specifically included inlining the rfc/draft references as opposed 
to keeping the references, but also several other tags that where written out more verbosely
and with a lot of default parameters (unnecessarily).  Hope i remember this all correctly.

This v2->v3 conversion process feels a bit like attempting to have a good idea but then
outsource the conversion cost.  Reminds me of linux. Great new SDK/Library, but now all
the third-party apps developed against an older version have to be rewritten. In comparison,
in Windows i can have 10 versions of the same core SDK co-installed and all the old but
still useful programs will still run. But no linux distributions do not support such slotting
or do not compile all old library versions, and library developers don't care about supporting
multi-slotting... *sigh*

Chers
    Toerless

On Sat, Jun 26, 2021 at 10:40:40PM -0400, John R Levine wrote:
> > > Among the many things on the to-do list is to redo the I-D submission page
> > > to make it clearer that you only need to submit one version of a draft,
> > > and that we'd appreciate the XML version if you have one.
> > 
> > Excellent. Is there any reason not to run the v2 to v3 converter automatically?
> 
> We really want people to stop using v2.  It's obsolete and missing some
> semantic features of v3.
> 
> Regards,
> John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
> Please consider the environment before reading this e-mail. https://jl.ly
> 
> ___________________________________________________________
> Tools-discuss mailing list - Tools-discuss@ietf.org
> This list is for discussion, not for action requests or bug reports.
> * Report datatracker and mailarchive bugs to: datatracker-project@ietf.org
> * Report tools.ietf.org bugs to: webmaster@tools.ietf.org
> * Report all other bugs or issues to: ietf-action@ietf.org
> List info (including how to Unsubscribe): https://www.ietf.org/mailman/listinfo/tools-discuss

-- 
---
tte@cs.fau.de