Re: [rfc-i] Not even sort of a Poll: RFCs with page numbers (pretty please) ?

"John R. Levine" <johnl@iecc.com> Mon, 26 October 2020 21:52 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F13913A0FCE; Mon, 26 Oct 2020 14:52:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level:
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" 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 xmG6pbv0iutq; Mon, 26 Oct 2020 14:52:32 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A6A1B3A0FF1; Mon, 26 Oct 2020 14:52:32 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 2CECBF4077E; Mon, 26 Oct 2020 14:52:22 -0700 (PDT)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id C7261F4077E for <rfc-interest@rfc-editor.org>; Mon, 26 Oct 2020 14:52:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8wObWTMtJa-S for <rfc-interest@rfc-editor.org>; Mon, 26 Oct 2020 14:52:17 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) by rfc-editor.org (Postfix) with ESMTPS id 1D27BF4077B for <rfc-interest@rfc-editor.org>; Mon, 26 Oct 2020 14:52:16 -0700 (PDT)
Received: (qmail 76484 invoked from network); 26 Oct 2020 21:52:26 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:reply-to:to:cc:subject:in-reply-to:references:mime-version:content-type; s=12ac2.5f97451a.k2010; i=johnl-iecc.com@submit.iecc.com; bh=cWduxr5vAhaTdvmP2uSAb83hyaBeMgYGlXUcy3kNWR0=; b=ZCp28wIpnUfezO1EbadZsl2I1wx/CO0hjPJqIxhdVZ1A4aE1oRgbGLd/zt4VXbttx/GhCxXYeQnL2M7sqW4aZcFkAFJgSU5XyJwwCKJeZC0L/V6z2NLUVyHvT5WHSgdOLjNfqXtHvxg6SaLGwXumGv8HYbZnHWXZxtFDu5FlxeSdnikv4F4WJmTyov3hlJWNEXynrduDYtCMm4P/9i84sLzO/KcPYvm81IWzeuTwJ7zc9vaIBRY5o2clglul//c3tZ5pJw88LPAubdkYbLKmQ/ZryYnlii0aQFcZABOOWQggEz6yZWHr7Sc3wB8o/0eyXUXyoceDLdPpAmmKYUVagA==
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; 26 Oct 2020 21:52:26 -0000
Date: Mon, 26 Oct 2020 17:52:25 -0400
Message-ID: <87148f61-a54e-d476-a28b-3682872be328@iecc.com>
From: "John R. Levine" <johnl@iecc.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, John Scudder <jgs@juniper.net>
In-Reply-To: <65374aef-e018-7bc8-ce50-d5c0a3982bf7@gmail.com>
References: <20201026020433.GA19475@faui48f.informatik.uni-erlangen.de> <CADaq8je8gMwAkOndTNJ9ndwzOZb2HQMZrCUJ5wNUjw-6ax9QtA@mail.gmail.com> <35EFE952-7786-4E24-B228-9BEE51D3C876@tzi.org> <20201026150241.GK48111@faui48f.informatik.uni-erlangen.de> <20201026162814.GP39170@kduck.mit.edu> <20201026164036.GO48111@faui48f.informatik.uni-erlangen.de> <1a56dc3b-56ef-3ffb-a12b-44d5e0d0f835@levkowetz.com> <20201026171931.GP48111@faui48f.informatik.uni-erlangen.de> <b733240-fc78-5a71-8920-ff84fbf64287@iecc.com> <20201026180105.GQ48111@faui48f.informatik.uni-erlangen.de> <03976f9f-7f49-7bf7-ce29-ee989232a44d@gmail.com> <7FA8EF59-5CDE-42B9-A487-520531EEA1F0@juniper.net> <65374aef-e018-7bc8-ce50-d5c0a3982bf7@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-1746382769-1603749146=:16595"
Subject: Re: [rfc-i] Not even sort of a Poll: RFCs with page numbers (pretty please) ?
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Reply-To: rfc-interest@rfc-editor.org
Cc: "rsoc@iab.org" <rsoc@iab.org>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>, Toerless Eckert <tte@cs.fau.de>
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

> On 27-Oct-20 10:14, John Scudder wrote:
>> The argument that page numbers are harmful as a way of referring to a section of the RFC is reasonable.
>>
>> The argument that page numbers are harmful for *any* *purpose* *whatever* is not reasonable. To offer one glaringly obvious counterexample, people (I, for one) sometimes print RFCs for the purpose of reading them. Sometimes we want to make use of some kind of facility for indexing from a list of headings to facilitate direct access to the right section of the pile of printout. A table of contents, in short. This is literally what tables of contents were invented for. They remain useful for this purpose… unless some bright spark chooses to remove the page numbers from them, because they forgot what tables of contents are FOR.

This whole argument seems to miss a large part of the motivation for the 
new RFC format.  These days, most people read RFCs on screens, not on 
paper.  I can't remember the last time I printed out an RFC, but I look at 
them on my computer screen or my tablet all the time.  That's why we have 
the HTML and PDF formats that display well on screens, and the HTML even 
adjusts dynamically to the window size.  It's also why they have a table 
of contents that links to document sections. When looking at either the 
HTML or the PDF, you can click on a TOC entry and go directly to that part 
of the document.  As Julian mentioned, every section header has an anchor 
so you can share the links with other people.

While I can believe that some people still print out RFCs to read, it is 
surely shrinking as those of us old enough to remember the smell of ditto 
fluid are supplanted by people who've grown up with laptops and tablets.

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
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest