Re: [rfc-i] Evolving document sources over a long time (Re: Comments on draft-roach-bis-documents-00)

Julian Reschke <julian.reschke@gmx.de> Sun, 12 May 2019 16:41 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCD32120235 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Sun, 12 May 2019 09:41:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.749
X-Spam-Level:
X-Spam-Status: No, score=-4.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=gmx.net
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 fSjvTIi6wBfS for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Sun, 12 May 2019 09:41:26 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 00A7A12021F for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Sun, 12 May 2019 09:41:25 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 21370B80A6C; Sun, 12 May 2019 09:41:16 -0700 (PDT)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 38F93B80A6C for <rfc-interest@rfc-editor.org>; Sun, 12 May 2019 09:41:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K0OlIDHAzlHf for <rfc-interest@rfc-editor.org>; Sun, 12 May 2019 09:41:13 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) by rfc-editor.org (Postfix) with ESMTPS id 6CE36B80A6B for <rfc-interest@rfc-editor.org>; Sun, 12 May 2019 09:41:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1557679269; bh=iCtDWkKQrXiOHGBPGIrdJOZH6IILTxIKRWwB9xziK/U=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=XdeF2ifZbwPooXPKXgXlSxsYKnBZ/d2PZN0ueoXQpA/G7o7kvu9WqpFdQWNBuSy9b uKvctP8GhN4dCkThDzPfsOqkpOeyeJRYh1bHoh5XRv+WLQvYwQXWe7fscz8butMMvL mkEPymd4zldKHRuW4cYL8iCaxqpl6fl7zmxGx7D0=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.124] ([91.61.61.108]) by mail.gmx.com (mrgmx104 [212.227.17.168]) with ESMTPSA (Nemesis) id 1N49lJ-1giFC142Wv-010362; Sun, 12 May 2019 18:41:09 +0200
To: RFC Interest <rfc-interest@rfc-editor.org>, Carsten Bormann <cabo@tzi.org>, David Noveck <davenoveck@gmail.com>
References: <CADaq8jdRMUZAN3rRXoActXqvGpkgx_-kW67uwzGLtVPoh7LfAQ@mail.gmail.com> <6E787E2A-18F2-4EFE-BFBA-61B1B4300930@tzi.org> <CADaq8jc1KJwC=Ypoo9a+-=Me=GP5tgX=2kcfUd56o53Mcu05kw@mail.gmail.com> <9179590B-C513-44DC-906C-16534DA8EC51@tzi.org>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <1852d84b-48cc-0129-3564-6ec9b92c4315@gmx.de>
Date: Sun, 12 May 2019 18:41:08 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <9179590B-C513-44DC-906C-16534DA8EC51@tzi.org>
Content-Language: en-US
X-Provags-ID: V03:K1:POSDF49PfOfL6BAEt2YPPC8KGfUS0aCDxqlaVkJh1dh9HB/34gU 3FgUC2SaC19TjoJLBpn5FrfvDDNqlcZa0lsYqpZo/n/fzEMxG+uKX7JzCiCVx9uOOwKuE2b yQR9VkWNCYsBcj+oQJj7vP1b4g+oRgdPMLhBhXbvzYbTw1TqOKsyMzyQSHswj3MvSornRMt stkV5flJ7+tt9pEPGiBqw==
X-UI-Out-Filterresults: notjunk:1;V03:K0:WAPgFWwq9Xk=:MVfarWrhkI4kp7CvJ1f6Lq hyE7j5n6L386Qq4UzrMdwHrAw3sAKNbVCteY9DUd+JeEygcQDVyNq6W3SfuhIeu0J49PuSKGb NgRFBNCOKY0mUDTKZ9GSnDGOuaCqjN/WI0pFJsPqyYxWPyjKThHMGvgUPeZvWM7yHoffeivf+ t5PsXFltpPU2sa2le5mccdHlIlyR1kPJ0sxUcT2hSibHF+DE0zIrXXVBaqKekLcuJEO2KxsfD zTcFbOQUQgC2JiUze1wJ9xQYD0e8AlUNzOOvaX5zVPU06pBPQitHWnSxB1wVjh7JdIvht3Nmu MpbeMQB9FsOA2a8x6X4+nTC39k55CobslN2/Kq4gGMwNMPd7MnmxtGICBjZ/J90fP8OjxJuex qVuhsWTTcURLlC9Swqn+wtVyIgxMU8olZ10kGGN14firT7qBGYfpVqdTE58sknjAHv2D85r77 PTerLWMelvfAMpUXjIvR11PRCwfr5UtNaani/B4/8AcvW+wpxmYUp//4kR1OjJnjDYjDLnE2t Y8BKHvgklatuNuVEzEeDrnJg3HZtNfmn4wGAONuEFwI1FjoykprqNXMeOf3ESKFf7Bmn9BznG Ly28wVlmgifaNip/2XG19n8wPUxS3Rml9x322ie63cvB/4kyrZodLfhopnobo4RnAXeAuXxSz Ny+LR//AC+43npWY40dRWBbMz/O5lNabqyTRBYjhrgHfItneqrAdAL5gvQmIuvs7xysoAeT7x aQlCw44KYLdjIcb082jNjzJ01E/tmUno6bQXpIWYP81HV+gKKVycGfxXDLgLQdes2It01Kw9l 7xjSfo4T4GIZYngIGM8/SDVq1VYcXCYyZKtk3STVjHNqAxUGBYwjRqUByqzCO9zkl2DAdn+n4 5Y0Z+9TXkWJNOjTPpNJUsefPkG5fRUpEp2Ow4LGbVWq1/OezIHR2UDzc7c1pEysxEtg1H+JVy L+1JCVJDWzA==
Subject: Re: [rfc-i] Evolving document sources over a long time (Re: Comments on draft-roach-bis-documents-00)
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

On 12.05.2019 18:16, Carsten Bormann wrote:
> ...

First of, +1 to almost everything you said...

> .. >> For RFC5661 and documents derived from it using Adam’s procedure,
that ship has already sailed :-(.
>
> As the references section needs to be updated anyway (for the DOIs), I’m not sure this is really true.  Or, if it is, RFC 5661 maybe isn’t really a candidate for this process, because it may be impractical to re-generate the exact numbering that RFC 5661 used.
>
>>> Since RFC 5661, we also got DOIs on RFCs, so it is inevitable there are a lot of diffs.
>>
>> It is not inevitable as shown by the fact that I didn't run into that issue.   It's kind of nice to know that there was an issue out there that I didn't run into :-)
>>
>> For reasons I  really don't understand, the xml for rfc5661 does not include rfc reference from external libraries.   It includes them inline, so a new rfc derived from that xml  file will not include DOIs.
>
> Yes.  All these RFC references would be updated by the RFC editor into current references.

Actually, I think a processor should optionally insert the DOIs
automatically. The current way of doing things just introduced a
completely unneeded incompatibility.

>>> Of course, I would not recommend directly authoring in XML these days
>>
>> Why not?
>
> Because:
> ...

FWIW, I disagree (but I realize that I'm probably in a minority). The
problem with Markdown is that the simple things are easy, but everything
else gets messy. I'm looking forward to see how you kram (pun intended)
the V3 features into your tool...

>>> but that was the way things were done in 2010.
>>
>> I’m prepared to stick with that, unless there is something better about the alternatives.
>
> Right, for a minor update, digging out the v1 tools and finding a platform where they can still run may actually be the best way to proceed.

All you need is a TCL processor. Works fine over here on a newly
installed notebook with Windows 10 and Cygwin.

Best regards, Julian
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest