IETF Logo Mail Archive

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

"Andrew G. Malis" <agmalis@gmail.com> Thu, 02 April 2020 21:01 UTC

Return-Path: <agmalis@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 019953A19B5 for <rfced-future@ietfa.amsl.com>; Thu, 2 Apr 2020 14:01:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, HTML_MESSAGE=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 NTtoZvnzBKTk for <rfced-future@ietfa.amsl.com>; Thu, 2 Apr 2020 14:01:21 -0700 (PDT)
Received: from mail-qk1-x72e.google.com (mail-qk1-x72e.google.com [IPv6:2607:f8b0:4864:20::72e]) (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 CF8113A19BA for <rfced-future@iab.org>; Thu, 2 Apr 2020 14:01:20 -0700 (PDT)
Received: by mail-qk1-x72e.google.com with SMTP id b62so5779316qkf.6 for <rfced-future@iab.org>; Thu, 02 Apr 2020 14:01:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=1kTUbTY+aimT0XDDc8zER+chS46cXEo0HjWrPHBDMOM=; b=IML0WmqCStj6Hv+dh3/yqPFGCyZGScltunkoS4AeMs/0EQdEl1Qs3t6Pdep6atZFSK zCil6RLyDhYb3hyFXx2PtBODf8up3U2LvNQYqiPu8faCFN1NcZaPgDbFGyf0C9MyV16D xiP7A7T8XDihiUY7RmgZPOKLXg1oiaOMu1O/oJTR8biUUxOygPvguKK0fx5iVuxsKRjn deVKTzfuQgbcU5tu8tEnV4q+RuxZLK+sYNFxOA0p8tJmZ91iw+PSIvVXehRz8sg3/Ns5 qDFD52raMhL+Lo/cUxasGv/gTX9TCnlI+bRZ4HJJHnlnfTZCThHvMbG3yy9+hpICcohp LBSg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=1kTUbTY+aimT0XDDc8zER+chS46cXEo0HjWrPHBDMOM=; b=V+brpqQKlSF4G2ksqs83TXcnOZaxqI35uBcC9kSj2cggztCqq3aMETRyD6PrBElMyJ 2nLgJzaPtYwkwQrMYfx5eFOOt0mptr527MjmDUYpgfqhayCug+YqpPSVGZ64yPmhOrod XM6yUZKMdNsbJw3VYo2/4C3WTEsXLD+dcSItEInwevZ/nDDbnylZnhIIwn/kmW9Exrsx WgoQuPoVNCQPqOnA3xZLWN2p/h+HnBCNhqQn6FLS6YSaV1oWDGXVhir5bY/5IfHORAak 14h1ZydjpYf+9pE6GRwphKJwg7Zb40PE4ELzc2qch54u+FEPlFJVzD2bdd+lxepv9vBU +ylg==
X-Gm-Message-State: AGi0PuZpYvkD68aV1CNcdELY6Y4ir7753tYTHzJStJ181qV5m297xTGX JXaZIuRpJ2y8OQ3epg5yn/Mc9OfiqHA+W8jWvgc=
X-Google-Smtp-Source: APiQypJF4mRyEIN/wl2KUmkDuGngT4sSObq3o64bhArWZjRA1zt0SzHp9JQN6eNSZEgLqUKn+3VsU90yqPNaZ4BeotU=
X-Received: by 2002:ae9:efd0:: with SMTP id d199mr5197780qkg.406.1585861279702; Thu, 02 Apr 2020 14:01:19 -0700 (PDT)
MIME-Version: 1.0
References: <0ac801d6089c$c36031b0$4a209510$@acm.org> <20200402195947.D569E16EE8CE@ary.qy>
In-Reply-To: <20200402195947.D569E16EE8CE@ary.qy>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Thu, 02 Apr 2020 17:01:08 -0400
Message-ID: <CAA=duU2Zyr9gju4J+smtfeWy4iTiJCRQCeGozkbnaHtA66z7PA@mail.gmail.com>
To: John Levine <johnl@iecc.com>
Cc: rfced-future@iab.org, LMM@acm.org
Content-Type: multipart/alternative; boundary="0000000000003d637b05a2551a62"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/chVGTY_eFvYk7J5lgytfyLn_VRs>
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: Thu, 02 Apr 2020 21:01:23 -0000

John,

I'd like to dig into your reply a bit. We've both been through our share of
AUTH48s. When I get the proposed changes and questions back from the RFC
Editor, I do my best to make sure that the primary output format (until
recently, the text format, and going forward, the HTML format) will be
correct from a content point of view and hasn't changed
anything technically substantive - changes are strictly editorial or to
correct errors like typos. If necessary, I've consulted with the
responsible AD to make sure that she or he agrees with the proposed
changes. I then trust the RFC Editor that the secondary formats (PDF, etc.)
will match the primary from a content viewpoint.  But following this
process, I'm fairly certain that "the to-be-published RFC, in all its
published formats, reflects the intent of the author and the body that
approved it."  So I'm curious why you feel that's not possible.

Cheers,
Andy


On Thu, Apr 2, 2020 at 3:59 PM John Levine <johnl@iecc.com> wrote:

> In article <0ac801d6089c$c36031b0$4a209510$@acm.org> you write:
> >IMHO, the "real problem" from a publishing workflow point of view  is
> that there is a workflow task that is not explicitly
> >assigned, namely to validate that the to-be-published RFC, in all its
> published formats, reflects the intent of the author
> >and the body that approved it.
>
> Trust me, that's not possible.
>
> R's,
> John
>
> --
> Rfced-future mailing list
> Rfced-future@iab.org
> https://www.iab.org/mailman/listinfo/rfced-future
>

v2.23.0 | Report a Bug | By Email