Re: Jim: Re: [rfc-i] FIXED: Poll: RFCs with page numbers (pretty please) ? (was: Re: John/rsoc: Re: Page numbers in RFCs questions / preferences)

John C Klensin <john-ietf@jck.com> Wed, 28 October 2020 19:19 UTC

Return-Path: <john-ietf@jck.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 DF5003A0114; Wed, 28 Oct 2020 12:19:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 FrINQiUfKM96; Wed, 28 Oct 2020 12:19:57 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0636D3A0BAD; Wed, 28 Oct 2020 12:19:56 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1kXqz7-0008Us-NF; Wed, 28 Oct 2020 15:19:49 -0400
Date: Wed, 28 Oct 2020 15:19:43 -0400
From: John C Klensin <john-ietf@jck.com>
To: Toerless Eckert <tte@cs.fau.de>, Jim Fenton <fenton@bluepopcorn.net>
cc: Working Group Chairs <wgchairs@ietf.org>, Phillip Hallam-Baker <phill@hallambaker.com>, John Levine <ietf@johnlevine.com>, IETF Discussion Mailing List <ietf@ietf.org>, RFC Interest <rfc-interest@rfc-editor.org>, rsoc@iab.org, David Noveck <davenoveck@gmail.com>
Subject: Re: Jim: Re: [rfc-i] FIXED: Poll: RFCs with page numbers (pretty please) ? (was: Re: John/rsoc: Re: Page numbers in RFCs questions / preferences)
Message-ID: <263C265C19B24BA97AF48934@PSB>
In-Reply-To: <20201028164053.GB12700@faui48f.informatik.uni-erlangen.de>
References: <20201026181442.GA2438@faui48f.informatik.uni-erlangen.de> <CAMm+LwiVmE=qtSPCMD-3foPODL8bgETj3dQDKS-3BOM2021dEg@mail.gmail.c om> <CADaq8jdSeTDWy_0fCV25ykxKFMV1ZBtUMMNesoOuaXCzFVfpOA@mail.gmail.com> <D2D0455D-8D6C-4A19-ACAE-4DD972D83DC1@bluepopcorn.net> <20201028164053.GB12700@faui48f.informatik.uni-erlangen.de>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/K39JqZ_9VfQTFQ_oy7la1ST4y4Y>
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: Wed, 28 Oct 2020 19:19:59 -0000


--On Wednesday, October 28, 2020 17:40 +0100 Toerless Eckert
<tte@cs.fau.de> wrote:

> On Tue, Oct 27, 2020 at 04:57:38PM -0700, Jim Fenton wrote:
>> but if some
>> people are reading HTML versions, PDF versions, and TXT
>> versions, the pagination is different anyway (and nonexistent
>> for HTML) so trying to reference something by page number is
>> problematic.
> 
> The thread is getting long so it is hard to not miss things
> said earlier, so let me repeat: My proposal was to add on IETF
> pages renderings with page numbers (not to remove any of the
> non-paginated renderings), AND make sure the pagination is
> consistent across them.

And, also to repeat, the expectation of consistent numbering (or
consistent pagination) across different renderings is
impractical and unwise.   As a specific and concrete example,
consider the relationship between a PDF document that contains
representations of several graphic images and the associated
text version.  The only way I can think of to make the
pagination (and numbering) consistent between them would be to
leave large areas of white space in the text.   That could be
done, but would make the text file longer and less useful.

AFAICT, the arguments against page numbers in the text files are:

(1) They are not allowed to be used in crossreferences within
the document, therefore they are utterly useless.
   Response: See many comments that contradict "utterly useless"
in this set of threads.  And we've had that rule for decades and
the RFC Editor and then the RFC Production Center enforce it.

(2) They are not allowed to be used in references within the RFC
Series to parts of other RFCs.
   Response: We've had that rule for decades and the RFC Editor
and then the RFC Production Center enforce it.

(3) We don't want them used by third parties or their documents
to references parts of RFCs.
   Response: As you point out, many other publications already
prohibit page number references to identify particular material
and do so for much the same reason we have.  But, as long as we
paginate documents, nothing we do is going to prevent someone
who insists on page numbers from counting and using them.  And,
as long as we have at least one paginated form (numbered or not)
that will be possible.  However, page numbers that are
inconsistent among renderings actually reinforces the "don't use
page numbers in references" rule because it is then clear that
they are too unstable to make good references, so maybe we
should be promoting their inclusion.

(4) Page numbers in plain text documents are so inherently evil
and/or the risk to horrible damage being done by anyone using
them so high that we need to suppress them and headers and
footers (and perhaps even pagination) as well.  That evilness
and risk of damage is acceptable in the PDF form, just not in
the plain-text one.
    Response: In fairness, no one whose comments I have read has
actually said/ claimed that, but it seems to me that it is were
several arguments against page identification (numbered or not)
seem to be heading.  YMMD.

By contrast, there are, it seems to me only two reasons for
retaining the page numbers (and pagination, headers, and
footers) in the plain text rendering:

 (a) They are traditional in the RFC Series and
	preserving that rendering in a format consistent with a
	significant fraction of the first 7000 or so of RFCs
	would seem to have some advantages.  Of course, no one
	is forced to use them, any more than anyone has been
	forced to use the standard text form since HTML and PDF
	forms became generally available years ago.
	
 (b) Of the fraction of the community that still prefers
	to use the plain text form (at least sometimes) and for
	one purpose or another, some fraction of them prefer to
	have the headers and footers and many of those prefer,
	or are not disturbed by, the page numbers.  Because many
	of the arguments against page numbers seem to be coming
	from people who do not find the plain text form useful,
	probably we should pay attention to that preference ...
	or start making the case for getting rid of the plain
	text form entirely, perhaps because those who prefer it
	(for any purpose) need to be persuaded to join the
	modern era and get with the programs.

Probably I'm missing something important but, if the above
analysis is even nearly correct, I don't understand why we are
still having this conversation.

    john