Re: Poll: RFCs with page numbers (pretty please) ?

Flemming Andreasen <fandreas@cisco.com> Mon, 26 October 2020 22:00 UTC

Return-Path: <fandreas@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1EA53A0FF8; Mon, 26 Oct 2020 15:00:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.845
X-Spam-Level:
X-Spam-Status: No, score=-9.845 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.247, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 E6lM0C7CDzkt; Mon, 26 Oct 2020 15:00:28 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D2D13A0FF6; Mon, 26 Oct 2020 15:00:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13203; q=dns/txt; s=iport; t=1603749628; x=1604959228; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to; bh=LJcv/bMkWQpDuR6TA6SC78F7QiBwG3RsYVjPtwTFJ8I=; b=WlRNnKIW3WD1w9k+p8blMKtHUM77VNs34VcYExLpOaF/83iN+Sn4HkwF r+84yvZjClIOX0lXHPMvslUPyLRxzi9qq4X7YkwH8nZ1EN9ACaYYjolUI 6icMCXyPMWWqZ3ynEJf9Bh6HT9yZrcoMPPJCXB+6dW39cnpiaw3ePz6so 0=;
X-IPAS-Result: A0CnBgBtRZdf/5ldJa1gHQEBAQEJARIBBQUBgg+BI1IGL4FFATIshDyQZAgmihAPiWyIGgsBAQEPLwQBAYRKAoILAiU4EwIDAQEBAwIDAQEBAQUBAQECAQYEbYVthXMBBSNWEAsYJwMCAiElEQYBDAYCAQGDIoJMAwklpCh2gTKFV4JNDWKBQoE4h2iFURuBQT+BOAyCXT6CGoU6gl8EkxWkHVSCdI9hhguFAQUHAx+DF4oNhSCPGpM9jWOSfYFrI4FXTSMVO4JpUBkNj0QBCY00JQMwAjYCBgEJAQEDCY5IAQE
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.77,421,1596499200"; d="scan'208,217";a="564350260"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 26 Oct 2020 22:00:20 +0000
Received: from [10.118.10.20] (rtp-fandreas-2-8813.cisco.com [10.118.10.20]) by rcdn-core-2.cisco.com (8.15.2/8.15.2) with ESMTP id 09QM0EiD020300; Mon, 26 Oct 2020 22:00:15 GMT
Subject: Re: Poll: RFCs with page numbers (pretty please) ?
To: John Scudder <jgs=40juniper.net@dmarc.ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>, "ietf@johnlevine.com" <ietf@johnlevine.com>, "ietf@ietf.org" <ietf@ietf.org>, Toerless Eckert <tte@cs.fau.de>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>, "rsoc@iab.org" <rsoc@iab.org>
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>
From: Flemming Andreasen <fandreas@cisco.com>
Message-ID: <2326663a-2534-1004-6cf5-67234a815300@cisco.com>
Date: Mon, 26 Oct 2020 18:00:14 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0) Gecko/20100101 Thunderbird/68.12.1
MIME-Version: 1.0
In-Reply-To: <7FA8EF59-5CDE-42B9-A487-520531EEA1F0@juniper.net>
Content-Type: multipart/alternative; boundary="------------434211B5CA7C60E06EA8F1BA"
Content-Language: en-US
X-Outbound-SMTP-Client: 10.118.10.20, rtp-fandreas-2-8813.cisco.com
X-Outbound-Node: rcdn-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/QeQnAAgg2DWP0opfcGh6xmfnnSY>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Oct 2020 22:00:31 -0000


On 10/26/20 5:14 PM, John Scudder wrote:
> On Oct 26, 2020, at 2:56 PM, Brian E Carpenter 
> <brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>> wrote:
>>
>> As Julian Reschke observed on the rfc-interest list, since the
>> new RFC format was implemented:
>>
>>> page numbers should not be used to refer to parts of the
>>> RFC, because page breaks vary with output formats
>>
>> So I can only see confusion if people use page numbers for
>> any purpose whatever. So it doesn't matter if people want
>> page numbers; they're now useless. So I won't be answering
>> a poll, and I don't think the results are interesting.
>
> 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.
>
+1

Page numbers are also quite helpful to keep the pages in the right order 
after you have printed them, and in a ToC it helps giving you an idea of 
how much material is in each section.

I confess that while most of my reading is on-line, I still buy physical 
books, use highlighters and occasionally print out an RFC either in part 
or in full. It sounds like I'm not the only one, and I have a hard time 
understanding why I am not allowed to get page numbers to help in that 
process.

Thanks

-- Flemming


> (Also, I think the use of the ToC for quickly estimating a document’s 
> throw weight is a valid one. I previously suggested associating a 
> BogoPages metric with each non paginated RFC for this purpose.)
>
> —John