Re: [art] New RFCs text formatting

Phillip Hallam-Baker <phill@hallambaker.com> Sun, 01 December 2019 03:59 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51E8C12081E for <ietf@ietfa.amsl.com>; Sat, 30 Nov 2019 19:59:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level:
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
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 to5jwF5EmTx2 for <ietf@ietfa.amsl.com>; Sat, 30 Nov 2019 19:59:33 -0800 (PST)
Received: from mail-oi1-f174.google.com (mail-oi1-f174.google.com [209.85.167.174]) (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 E2770120041 for <ietf@ietf.org>; Sat, 30 Nov 2019 19:59:32 -0800 (PST)
Received: by mail-oi1-f174.google.com with SMTP id 6so4211423oix.7 for <ietf@ietf.org>; Sat, 30 Nov 2019 19:59:32 -0800 (PST)
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=fdgoqspd1dD9Gk3WVCaxsCXPphKG0feOz/5lEOxniTg=; b=ZlD4sXM4eNWYDOdp/jtxBhHynTzFxlNVjyYQWC1aSFOWq1QebHeNl8xMb4U1j/737S iz5nnoUWrDxAq8R+lklv1zz10nr8SFkv8YjMTAtxTg4NOFY9Rf3a0f3Geniemlebmkk0 gF6Tl28kgyI3ZVeIiMilcUBWw/IkdSSmAoNVthz7oIthB1eZYYzMS04N0nnisbovvkm+ 6jK708OEWI0cgtVAh6WboKJJ/mJiZp9/rbPTTpWf4WKOjtm+77taqz/E518fHy3Tlx9d HrnPgfEesDb3CUAf3rAJu6t5jxBawxd85zQYkMBhg661O23/vBe53PNtW0QkXLBnQjwf vNzw==
X-Gm-Message-State: APjAAAUt4LPJS++sxiBJi/IMTsnF4PZEb90Q6vfvVAGirn0ygD2sXsxO mViw/rDdOAJkSn2BiOPipbOhmN8BAC/mynzflP0=
X-Google-Smtp-Source: APXvYqwB+pDjEV8McODup1+HKzTzL85gitaxXcy0uCjt/rCEe2fRInXu9sREtSr27CWvYwUCt8p1trqS37ffosuqBBI=
X-Received: by 2002:aca:6186:: with SMTP id v128mr7335616oib.17.1575172772058; Sat, 30 Nov 2019 19:59:32 -0800 (PST)
MIME-Version: 1.0
References: <20191127233129.9829F%steffen@sdaoden.eu> <db882e3c-d3fb-4742-8456-7b400225ecce@www.fastmail.com> <20191128005000.yMa3P%steffen@sdaoden.eu> <08EE9B7B7C15D8F8B5DE6AF5@PSB> <8c144ffb-ca56-4a80-a994-9b8002eac17b@network-heretics.com> <abc32be6-c156-7a7a-104e-517c6d3167f0@levkowetz.com> <A8A2B5E6-64BE-47D7-AB87-2A4C2619995C@tzi.org> <40cb6637-48af-0d27-94d7-9388417c17ba@network-heretics.com> <449e262a-6c7e-4278-812b-c40476af7af0@joelhalpern.com> <161FDFC81FC520658407B2C6@PSB> <e4721d36-e0aa-ae99-7f17-5d6f18f2b704@joelhalpern.com>
In-Reply-To: <e4721d36-e0aa-ae99-7f17-5d6f18f2b704@joelhalpern.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Sat, 30 Nov 2019 22:59:20 -0500
Message-ID: <CAMm+LwieSEvCZmfK4pkOnN7Jgp=e0TEyS51ALVW9Kqn2NRxS7w@mail.gmail.com>
Subject: Re: [art] New RFCs text formatting
To: Joel Halpern Direct <jmh.direct@joelhalpern.com>
Cc: John C Klensin <john-ietf@jck.com>, IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000089dcba05989c7d2f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/eqrzAc4oXeDCMHZHcbnhjOCtnlM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Dec 2019 03:59:34 -0000

On Sat, Nov 30, 2019 at 10:12 PM Joel Halpern Direct <
jmh.direct@joelhalpern.com> wrote:

> That (the suggestions that RFC-interest is the wrong place to judge such
> things) may be, which is why I listed alternatives.  But just saying
> that two people liked the idea, and no one screamed, in one day, is
> clearly NOT enough to change the default.


Quite. The botched pagination of the old plaintext format was one of the
main reasons I hated it. The parochial US-centric design ensures that it
only works reliably on US paper which is only used in North America.

So for years, I would have to make multiple attempts at tweaking page
lengths on printers to get RFCs to print out right. And after a while, I
gave up, and wrote myself a PERL script to convert them to HTML and those
are the docs I worked from all the time I was at the Web consortium and
then at VRSN until xml2rfc appeared with a HTML output.

I have never used the plaintext format. I have always regarded it as
garbage. This is a technology business. If we are going to get nostalgic
about stuff, perhaps we should start with all the newspaper people,
shopworkers, etc. etc. we put out of work. It seems rather incongruous and
not a little self-indulgent to find the vanguard of the digerati waxing
nostalgic over emulating 1960s line printer formats while they are merrily
shredding the fabric of the old economic order for everyone else.


What does concern me with the current state of affairs is that we have HTML
output of RFCs but not yet of IDs it would seem.