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

"Andrew G. Malis" <agmalis@gmail.com> Mon, 26 October 2020 22:02 UTC

Return-Path: <agmalis@gmail.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 44F6A3A0FFB; Mon, 26 Oct 2020 15:02:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 1SM_ocq9YeL3; Mon, 26 Oct 2020 15:02:29 -0700 (PDT)
Received: from mail-qt1-x832.google.com (mail-qt1-x832.google.com [IPv6:2607:f8b0:4864:20::832]) (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 BAD913A0FF7; Mon, 26 Oct 2020 15:02:28 -0700 (PDT)
Received: by mail-qt1-x832.google.com with SMTP id z33so7940278qth.8; Mon, 26 Oct 2020 15:02:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=5kfvaivSN3rEp05My9Eb78DaRi+fg+muGj0iiwPUPsU=; b=Dau88C9dXwFSwU3M+4NhWAnW8YwYNRw1CV0hlrcRvy5WZv7vWLljrwy234wfufHFAw 9yI8T2wYZOcTF3OymF+nhh2NYxJeSZgu5EtpBkgZjJKruaKPcoJt2WJ1DywPqe5M2dNr TEC4/Z9GeNbsyX4oWS+GGZ0W1c/OEpNUqsr+Qx/7ADwgLyocs8xg6rBLYP5dntaZd5lN 1Y3uZax2L46KYsGCtJ3qKk7laY2s81EQn40WobEnYL2yE/LIWasPXQbn7YQMNpvILshz y+DHi1h6jZ4h50sH+L9guh7wsRIQE9Mh2yvnetfqDe3xu+fWduyPTH5jw62AhRY17JtT NVQQ==
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=5kfvaivSN3rEp05My9Eb78DaRi+fg+muGj0iiwPUPsU=; b=h2CagQAd2/gUdY4XlmiRPGD8GoeM1S/g9QL8ONTDc4JpqBQQbMGRRMJIN/HalRF4iQ M+YGatP5dutZfW9rNQOAiP136JdRjgoOuWDMR0OANvmPmqOIKBNLnQTiOp9Nt+cGSa3i g9S7+IZa/txreelIGmL5y7l0BjzIa7vXFdgzme6WpucA5Xtb5/Uf2zcuH6r42waJuV7M iFqabdnlCY8ACLS5Zcd0AK2PO6UC8pegDnuOmz3cK8INtDvDl1BhwZ4jpAOEc2U7kEI2 pibU9N3hU8IQewSjBbOW//si6ymDxTAyXYjbKZOHw7aAIZCHud5MDUdTbByg20HhVW2w i+LA==
X-Gm-Message-State: AOAM533W7nI43Uf4PIht/knQfG7l4uxgG+08XO3Af4mqMG9/un02UgPW +mTIDgK4SRlAg9jrNHieiEASlgjt/lNkbseNb0s=
X-Google-Smtp-Source: ABdhPJwEybB3MUi0jShN2FIQfDAZtGTDTEo948Jt3uH771/hKU7q56N7ZHsNqTaCCMzz503DUVp+Bz6S6xVlH+wC1e4=
X-Received: by 2002:a05:622a:1cb:: with SMTP id t11mr17497220qtw.160.1603749747704; Mon, 26 Oct 2020 15:02:27 -0700 (PDT)
MIME-Version: 1.0
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> <2326663a-2534-1004-6cf5-67234a815300@cisco.com>
In-Reply-To: <2326663a-2534-1004-6cf5-67234a815300@cisco.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Mon, 26 Oct 2020 18:02:16 -0400
Message-ID: <CAA=duU1SfAhnuQdp15hY20PtiwVv8f2yK1BeQiFKcm5NogBxZA@mail.gmail.com>
Subject: Re: Poll: RFCs with page numbers (pretty please) ?
To: Flemming Andreasen <fandreas=40cisco.com@dmarc.ietf.org>
Cc: John Scudder <jgs=40juniper.net@dmarc.ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>, "wgchairs@ietf.org" <wgchairs@ietf.org>, "ietf@johnlevine.com" <ietf@johnlevine.com>, "ietf@ietf.org" <ietf@ietf.org>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>, "rsoc@iab.org" <rsoc@iab.org>
Content-Type: multipart/alternative; boundary="000000000000054b1405b29a1686"
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/Xb5gsU333OWFKil1vpAWFLDVTis>
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:02:31 -0000

Flemming,

If you need a printable version with page numbers, that's provided by the
RFC Editor for every RFC, for example
https://www.rfc-editor.org/rfc/rfc8905.pdf (to cite a recent example). If
you quickly need the last page number, just click in your browser or PDF
reader on the last entry in the TOC.

Cheers,
Andy


On Mon, Oct 26, 2020 at 6:01 PM Flemming Andreasen <fandreas=
40cisco.com@dmarc.ietf.org> wrote:

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