IETF Logo Mail Archive

Re: [Rfced-future] Welcome to the RFC Editor Future Development Program

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 03 April 2020 20:32 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: rfced-future@ietfa.amsl.com
Delivered-To: rfced-future@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A8973A0A56 for <rfced-future@ietfa.amsl.com>; Fri, 3 Apr 2020 13:32:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 II6YbBJIT0GP for <rfced-future@ietfa.amsl.com>; Fri, 3 Apr 2020 13:32:45 -0700 (PDT)
Received: from mail-pg1-x542.google.com (mail-pg1-x542.google.com [IPv6:2607:f8b0:4864:20::542]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B8EFB3A0A53 for <rfced-future@iab.org>; Fri, 3 Apr 2020 13:32:45 -0700 (PDT)
Received: by mail-pg1-x542.google.com with SMTP id 142so4075446pgf.11 for <rfced-future@iab.org>; Fri, 03 Apr 2020 13:32:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=gBKamDYUDVlM6NwOn26od9aDtux62AyWz/jHUGEtjSA=; b=kPev1HNzB+0lRGuVpnIqJMBdWZZy5kYVSd4rXlSElFxkG7AIUY8RtzLHslOrniNUPB X61B7Ntqq2emRrau1MATXdYZNkx+9OXGqSATb9EMy+AnQp+02Lnd5CxrXmhUY9NOavHZ D52s63eiukjhBLIE5DyoZoOQJ/Lvrle7VNFgbJRKneLfaDMfXEDgUsByUCSa2sWnc9cr WiXxTrwJUOXFPQUX1Npmo5a3RVwNNBppODY+c2EjegbQL3+U4yTcCymOk3n1h8D2MT7U 8dQWebuDtLxA1knLyel8K3ScB9c4UrMdrGgnWrsKRXKA4LTBw1zI+TaKilcr4PpcD2CA ctkA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=gBKamDYUDVlM6NwOn26od9aDtux62AyWz/jHUGEtjSA=; b=CAA1wH6fCaRDyVXmNbW3Zu89bJWE8e7QLNSZI1A6/YKOLCUM3t4uqT0EsduGzJLVfB zPUUaJFV58MXCAPK/r4FvQ6MSD7UVdvVI2qxn85/RBtsIcjDT+fkebvdpsPHFjKwdUva KlKQxvwZd108InVP93hQrlqj4+kHfT2rrO6Bn+QxRHFmZsBId6l+CXBqWRSuQMdvWvAt 6Zs+UeLD8wDxeOL46F4NB9GVhN/xRagFuBpCsf2ML/mQPUULisrDojXc6y306qdlyI6W NEfGIcaxBfeaNLivHmB32fNwS7/ltgYsAVgWhQ1Mnwo8DnkWz8Ml7bGjE/Ql4yUx66WJ Zs8w==
X-Gm-Message-State: AGi0PuYmGP2hxk5rGJ6kJ3YMvf1YCizZpIfBo34GQUds1EWxPS5jQl9A 4OuKO/LM5wwuZYdfaQA+sY8=
X-Google-Smtp-Source: APiQypJGbyVmj1kegbiYka8m5YLXmk6uP+EQ2sUnUCWj+53nigACY0lblxIfoBhn4aA+FKdHeik/Mw==
X-Received: by 2002:a63:1245:: with SMTP id 5mr9832469pgs.55.1585945965073; Fri, 03 Apr 2020 13:32:45 -0700 (PDT)
Received: from [192.168.178.30] ([165.84.25.143]) by smtp.gmail.com with ESMTPSA id b125sm5815597pga.92.2020.04.03.13.32.41 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 03 Apr 2020 13:32:44 -0700 (PDT)
To: Julian Reschke <julian.reschke@gmx.de>, Carsten Bormann <cabo@tzi.org>
Cc: "John R. Levine" <johnl@iecc.com>, rfced-future@iab.org, Larry Masinter <LMM@acm.org>, "Andrew G. Malis" <agmalis@gmail.com>
References: <0ac801d6089c$c36031b0$4a209510$@acm.org> <20200402195947.D569E16EE8CE@ary.qy> <CAA=duU2Zyr9gju4J+smtfeWy4iTiJCRQCeGozkbnaHtA66z7PA@mail.gmail.com> <009601d60964$2648e7a0$72dab6e0$@acm.org> <alpine.OSX.2.22.407.2004022303110.37555@ary.qy> <1533669f-6891-e50a-be08-b5293fc5cbbf@gmx.de> <DF6A09DD-C7D4-4542-B83F-C687861F5492@tzi.org> <3b1df23c-d1e4-46f9-d7d4-6fac978be8d3@gmx.de>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <46ebaffc-9c69-f5ce-8155-bd7dda3cde7c@gmail.com>
Date: Sat, 04 Apr 2020 09:32:38 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <3b1df23c-d1e4-46f9-d7d4-6fac978be8d3@gmx.de>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/bGeg-LyKXiJRGWIkorOR6OMFY0I>
Subject: Re: [Rfced-future] Welcome to the RFC Editor Future Development Program
X-BeenThere: rfced-future@iab.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Editor Future Development Program <rfced-future.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/rfced-future>, <mailto:rfced-future-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfced-future/>
List-Post: <mailto:rfced-future@iab.org>
List-Help: <mailto:rfced-future-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/rfced-future>, <mailto:rfced-future-request@iab.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Apr 2020 20:32:47 -0000

Julian,
On 03-Apr-20 19:59, Julian Reschke wrote:
> On 03.04.2020 07:25, Carsten Bormann wrote:
>> On 2020-04-03, at 06:46, Julian Reschke <julian.reschke@gmx.de> wrote:
>>>
>>> On 03.04.2020 05:07, John R. Levine wrote:
>>>>> During the AUTH48 period, whoever is reviewing the document needs to
>>>>> check ALL of the formats, especially around examples and figures and
>>>>> any non-ascii text.
>>>>
>>>> Currently the RPC people are proofreading all of the output formats,
>>>> which takes a lot of work.  I hope authors are also, but that's up to them.
>>>> ...
>>>
>>> That sounds like a bug in the process to me. And it won't scale if we
>>> add ePub.
>>>
>>> There should be *one* format that is to be proofread, HTML. If the other
>>> output formats have an issue, that's a tooling problem that needs to be
>>> solved, and the other formats can be regenerated.
>>
>> This doesn’t work too well in an environment where the tooling is fluid, and in fact the format that the tooling works from and its interpretation is fluid as well.
> 
> If the tooling is that fluid (is it for HTML?), that shows that we
> shouldn't have started the switch yet...

But we did, so that ship has sailed.
 
>> When the tooling has a bug (read: it uses the interpretation of 2020-04-02), and the XML is adapted to work around this bug, and the tooling is then fixed (read: it now uses the interpretation of 2020-04-03), the new output may be erroneous.
> 
> The (canonical, published) XML never ever should be adjusted to work
> around a bug. Is this happening?
 
<heresyAlert>It should be happening. For the period during which v3 is in flux, we should indeed update already-published v3 XML files, not constantly, but on some sort of snapshot or checkpoint basis. Obviously we must not update the substantive content, and we should have an audit trail, but only by doing such updates can we have a reasonable situation at the end.

If there isn't a v3.n sub-version number in the XML files today, there certainly should be.</heresyAlert>

    Brian

v2.23.0 | Report a Bug | By Email