IETF Logo Mail Archive

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

"John R. Levine" <johnl@iecc.com> Fri, 03 April 2020 03:07 UTC

Return-Path: <johnl@iecc.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 159173A0D1D for <rfced-future@ietfa.amsl.com>; Thu, 2 Apr 2020 20:07:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.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 wT3ShWgWEcEK for <rfced-future@ietfa.amsl.com>; Thu, 2 Apr 2020 20:07:54 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 59BDD3A0D01 for <rfced-future@iab.org>; Thu, 2 Apr 2020 20:07:54 -0700 (PDT)
Received: (qmail 84457 invoked from network); 3 Apr 2020 03:07:52 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=149e7.5e86a888.k2004; i=johnl-iecc.com@submit.iecc.com; bh=72fL4LyzlcTFE1BD0HF7XLYGOBe+LAHwbvSSd4ViZkc=; b=kE5nfwKFtfo8Vob11x1hncn0D2rocIRT43iawMd81OSeoXpIfn1LIMxeBlxi6j+RVljrY1M35ClbLOMjnn5uNUsOoVevIMFVf+TpY/JeCz5C9O6vjtjW5Ommt04uxUhjeYAD5FOfh+o7we2wM1QarQliW60mB9xXWEE7qutWtV4tR2jwURNdAGNolrWlfDRnR2pGOUiRWMTW43AFEaZfMUmcpiFmPDzwMwXI7njOtMTCrAHfyqHMX6/Y8/LsrNI6
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPSA (TLS1.3 ECDHE-RSA AES-256-GCM AEAD, johnl@iecc.com) via TCP6; 03 Apr 2020 03:07:51 -0000
Date: Thu, 02 Apr 2020 23:07:51 -0400
Message-ID: <alpine.OSX.2.22.407.2004022303110.37555@ary.qy>
From: "John R. Levine" <johnl@iecc.com>
To: Larry Masinter <LMM@acm.org>, "'Andrew G. Malis'" <agmalis@gmail.com>
Cc: rfced-future@iab.org
In-Reply-To: <009601d60964$2648e7a0$72dab6e0$@acm.org>
References: <0ac801d6089c$c36031b0$4a209510$@acm.org> <20200402195947.D569E16EE8CE@ary.qy> <CAA=duU2Zyr9gju4J+smtfeWy4iTiJCRQCeGozkbnaHtA66z7PA@mail.gmail.com> <009601d60964$2648e7a0$72dab6e0$@acm.org>
User-Agent: Alpine 2.22 (OSX 407 2020-02-09)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/iZcySxo73D9WrMfbm9OZTV7uDLs>
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:07:56 -0000

> 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.

Keeping in mind that only the XML is canonical, and that PDF layout turns 
out to be surprisingly hard, one of the things we're considering to keep 
the documents flowing is to live with less than perfect PDF rendering for 
now, and to rerender them later once we understand the issues better.

I am NOT suggesting that we thrash this out now, just that we need to keep 
that not every file one might see is necessarily part of the permanent 
archive.

Regards,
John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. https://jl.ly

v2.23.0 | Report a Bug | By Email