IETF Logo Mail Archive

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

Larry Masinter <LMM@acm.org> Fri, 03 April 2020 03:01 UTC

Return-Path: <masinter@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 D6AE33A0D03 for <rfced-future@ietfa.amsl.com>; Thu, 2 Apr 2020 20:01:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.747
X-Spam-Level:
X-Spam-Status: No, score=-1.747 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no 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 Aw4Ew0d0bh3s for <rfced-future@ietfa.amsl.com>; Thu, 2 Apr 2020 20:01:21 -0700 (PDT)
Received: from mail-pf1-x436.google.com (mail-pf1-x436.google.com [IPv6:2607:f8b0:4864:20::436]) (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 98C7E3A0D01 for <rfced-future@iab.org>; Thu, 2 Apr 2020 20:01:21 -0700 (PDT)
Received: by mail-pf1-x436.google.com with SMTP id b72so2767920pfb.11 for <rfced-future@iab.org>; Thu, 02 Apr 2020 20:01:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-language:thread-index; bh=6T/2KKgh1E4osoSCKnZrC+LIEDqueh/q6ETFMAFm9uo=; b=fkWeonK8ht5Iru4+AxUsxa4KO9Uvh6l0MgYireeAUwKYNH9W5ofcK/ptK4V6BWIvuu L/DqaPLf1hUaifHsjkqwBri9fd7Gfe7OqUJn8G2JSiHUSdg9IfidYS01CQncmpX8Ip2O YUqGfmBsxPcJcDGVIKB8qm/nT6ek6Q4lqjeaaW1HHQNv+Cd2Ps0u7+2l9F+3Haxa/Mep BJUPqWGD4ClzwY7bSwT/HuwkHnksCt/2g1hqOQX71Fnd6mIueBNIFSvFCE7Ht2lV16xH jqMuCB5+JZC9TWirGO3WkR60bKJodyvGkAjH5R26ZAl8e/Q7NvvO/WSeb0CugM6Gpz5F ILgQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:to:cc:references:in-reply-to:subject :date:message-id:mime-version:content-language:thread-index; bh=6T/2KKgh1E4osoSCKnZrC+LIEDqueh/q6ETFMAFm9uo=; b=U8HoadMDPTpU3AqlwFZQsnSYzaO9VpIQbjFqxIRjk9RK1mhYeYOnDucO8X6OggAeJX zd9SC+AuyHHc9MYH+wd8oIuAVRv9cnYq6d7cy7jsVEwgfcC1wodu4YgFz9EkNneP956G TRo7lnEG6bgthp8QamOEai6wgSqr5PDNrglvXB7x1I0abMYjrrLlqc9a+Ogi2SSuNtYO KkSRGeiiM4HzCzCZoG9TJUaQCsrQvcNZes03OGetR6GqDtK5Ml7qEDK3KdILyW02tdba WqYgjodWXz9NVmQnKD0JA/2KGj0Sfh+1/8XH1gpUc4j8KSkdtQMQLBTH+AMipBQTbyo4 P/lA==
X-Gm-Message-State: AGi0PubFKYZO09emVs+EjeA0yXZ2DH4z0/A06w8Nly16s13KLMmkOHf7 Yynn00HT4nuZ2bU2wXqGL54=
X-Google-Smtp-Source: APiQypL5m4tgYGVk30NIJppnyj51wZ2ygZAoaK13Ny7nUHxenTrzeKtZq2j3n8WnY9bqxI5hvWrkVA==
X-Received: by 2002:a63:3850:: with SMTP id h16mr6146902pgn.326.1585882880735; Thu, 02 Apr 2020 20:01:20 -0700 (PDT)
Received: from TVPC (c-67-169-101-78.hsd1.ca.comcast.net. [67.169.101.78]) by smtp.gmail.com with ESMTPSA id x186sm4691854pfb.151.2020.04.02.20.01.18 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 02 Apr 2020 20:01:19 -0700 (PDT)
Sender: Larry Masinter <masinter@gmail.com>
From: Larry Masinter <LMM@acm.org>
X-Google-Original-From: "Larry Masinter" <lmm@acm.org>
To: "'Andrew G. Malis'" <agmalis@gmail.com>, 'John Levine' <johnl@iecc.com>
Cc: rfced-future@iab.org
References: <0ac801d6089c$c36031b0$4a209510$@acm.org> <20200402195947.D569E16EE8CE@ary.qy> <CAA=duU2Zyr9gju4J+smtfeWy4iTiJCRQCeGozkbnaHtA66z7PA@mail.gmail.com>
In-Reply-To: <CAA=duU2Zyr9gju4J+smtfeWy4iTiJCRQCeGozkbnaHtA66z7PA@mail.gmail.com>
Date: Thu, 02 Apr 2020 20:01:18 -0700
Message-ID: <009601d60964$2648e7a0$72dab6e0$@acm.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0097_01D60929.79EA5DC0"
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-us
Thread-Index: AQGkjSKuW/6XuDC0UyTNV+RTdQKGoQHzE8PkAcIhXdCorADEcA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/yKIQosgIVdeAFubrGyYSXx23mYY>
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 03:01:23 -0000

 

> I then trust the RFC Editor that the secondary formats (PDF, etc.) will match the primary from a content viewpoint.  

 

There’s a reason why typical publishing workflows involve proofreading a “galley proof”

the already “typeset” format with the exact placement.

 

 

I don’t want to belabor the “AUTH48” problem except as an example of the mismatch of expectation (trust) against something not in the job description might lead to problems.

 

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.

v2.23.0 | Report a Bug | By Email