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

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 26 October 2020 23:51 UTC

Return-Path: <brian.e.carpenter@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 19BDD3A10E8; Mon, 26 Oct 2020 16:51:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.346
X-Spam-Level:
X-Spam-Status: No, score=-2.346 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, NICE_REPLY_A=-0.247, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 wPW8rLC3l1CM; Mon, 26 Oct 2020 16:51:46 -0700 (PDT)
Received: from mail-pl1-x62b.google.com (mail-pl1-x62b.google.com [IPv6:2607:f8b0:4864:20::62b]) (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 B48C63A10E5; Mon, 26 Oct 2020 16:51:46 -0700 (PDT)
Received: by mail-pl1-x62b.google.com with SMTP id v22so5500022ply.12; Mon, 26 Oct 2020 16:51:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=YpKwTWJIKjuUpqzVzp/pU1ESd5jmax85QPmeisyBO6k=; b=Ci/4HFrKhfhM+3oKCIaOmjbAmkkUJfEgdmJljRoG4BtKx8a4fiDyatpSZKh/w5svLl VOCvT3X3czRFZauHm/o2jCtFy/QJSUvysyRz68Jc6V+sNDXAi03lFmsTGtlPtRQq7lIv kEQp9Z2UZGlYxtf2cXcp49F4N+wY+AAYEBmfliZZU/UoXLHjlYly1UHFn7wwMhIcpRa1 9sfqhJsOQb/rumAS3YkdrxdxXe6lcp5g0WTy0WwFt7nBpzb8gCnyNsdb9v77qxEYh2kS 1C+45/iP5Y/ySTq/hFlb165mObZUPBvBRyGKUu6GYdA9mNGIc7jdyTGSeJSZKebvaB/j uNPw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=YpKwTWJIKjuUpqzVzp/pU1ESd5jmax85QPmeisyBO6k=; b=aP0VytjsmLP47TBLVK8Z7ABKGm/ML7Dge9wNyPZUwReSoJ4Dhi+T5VSNhU2bLvr6sD gCMa2kUVm1inqxj9jjRHPrbsqHlFjvGtV5uFG5kXhrAXwVNSbm3+EcndGh8mD6Ct9ExL /UgutVTrKE5jDUAvOOJZrmNE94yfEpgUOX5kx2dOnRquBKvsQtvHVvkg2s4N3jHyytPa VIEtMbjbNfrBA8wSpCo+U/MftgoWkjWPrFeojTjTp8Q0c0UT5dHn80XK1oiVOg2rEVFg +lOFErwvzxYx87CtZiN/1uaFF5OjSnazP9xrO1q2pY2Tan8WCKj3DNMpf1Z3RAYxjZXJ Zlkw==
X-Gm-Message-State: AOAM533vW0DZyZD8P1TN2MwBC+Cd9ybbnNWFxdwTIkr39h/bM0HUbYFA ruwFLz19EjFuqNA9RMLdwaQ=
X-Google-Smtp-Source: ABdhPJw8AYQuCPwHngpabmbGGAUIF68OEcDPAQx7dRGW3/1xed/RxhiM7v0MBEq7i3AFRcHlSi8R3Q==
X-Received: by 2002:a17:90a:2e03:: with SMTP id q3mr23479773pjd.118.1603756306220; Mon, 26 Oct 2020 16:51:46 -0700 (PDT)
Received: from [192.168.42.189] (219-89-84-78.adsl.xtra.co.nz. [219.89.84.78]) by smtp.gmail.com with ESMTPSA id u124sm13540658pfc.21.2020.10.26.16.51.42 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 26 Oct 2020 16:51:45 -0700 (PDT)
Subject: Re: Poll: RFCs with page numbers (pretty please) ?
To: John C Klensin <john-ietf@jck.com>, Toerless Eckert <tte@cs.fau.de>, ietf@ietf.org
Cc: wgchairs@ietf.org, rfc-interest@rfc-editor.org, rsoc@iab.org, ietf@johnlevine.com
References: <20201026020433.GA19475@faui48f.informatik.uni-erlangen.de> <CADaq8je8gMwAkOndTNJ9ndwzOZb2HQMZrCUJ5wNUjw-6ax9QtA@mail.gmail.c om> <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> <7879175D0ABBB5401B02FEA6@PSB>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <25dcbfb7-3448-8372-36eb-dc323acc7fd8@gmail.com>
Date: Tue, 27 Oct 2020 12:51:39 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <7879175D0ABBB5401B02FEA6@PSB>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/gcOcTADfdz7Sg83Dtv5jYfOLtBc>
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 23:51:48 -0000

John,

Let me retract "useless". What really bothers me is that page numbers are actively misleading in the new format. I think that became true the moment a consensus appeared that the preferred presentation format was HTML with flowed text.

Regards
   Brian

On 27-Oct-20 11:06, John C Klensin wrote:
> Brian,
> 
> I look at the same information and come to a different
> conclusion (quite independent of the question of whether a poll
> at this point is a useful exercise)...
> 
> --On Tuesday, October 27, 2020 07:56 +1300 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
> 
> Cross references (and other references) to page numbers have
> been discouraged since at least RFC 1543 (in 1993) and banned
> soon after that, to the point that the RFC Editor from the last
> half of the 1990s would simply remove such references, replace
> them with references to section numbers, and complain when
> sections got too long for convenient referencing.  Nothing about
> restricting references to page numbers is new with the new
> format.   
> 
>> 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.
> 
> However, getting from "references to information by page numbers
> have always been a bad idea, prohibited for a quarter-century,
> and even more obviously a bad idea as we move to multiple
> formats" to "any purpose whatsoever" is a big jump.  At least
> some of us have tools and macros floating around that are
> dependent on pagination and, as an exception to the
> "referencing" rules, it is still not clear (at least to me) how
> to build and format a document index using anything else (at
> least without a lot of effort).  There are even simple and
> obvious reasons: If one is going to print an RFC from the text
> form (or render it into printable form), something is going to
> do the pagination and being able to easily estimate the page
> count may affect how printing is to be set up.
> 
> FWIW, the questions of "should documents be paginated" and
> "should the pages be numbered" are also separate ones.
> 
> Moreover, the argument that pagination (and page numbers) are
> obsolete and useless for RFCs would be much stronger if the PDF
> form for new RFCs were not paginated (or at least not numbered)
> ... but it is both paginated and numbered.   And, if the issue
> is having things lay out well on many different types of
> devices, eliminating pagination (and headers and footers) to
> facilitate that is bogus: it would be equally or more reasonable
> to eliminate (or rethink) line breaks in running text, etc.   If
> one really wants things optimally formatted for a variety of
> different devices, then the right thing to do is to start from
> the HTML form and a well-designed style sheet or to go back all
> the way to the XML, not to try fussing with the ASCII text form. 
> 
> Conclusion: The main arguments that have been given for
> eliminating pagination, headers and footers, and page numbering
> --at least those based on different devices and references-- are
> mostly bogus.
> 
> So, from my point of view as a fan of pagination in the ASCII
> form of RFCs, one who has never willingly referenced part of an
> RFC by page number, this seems to come down to something else
> entirely: if there is a goal to eliminate (or strongly
> discourage) the use of ASCII format RFCs in favor of the HTML or
> PDF forms (or building directly on the XML), then "no page
> numbers" and "no pagination" are among the first few cuts of a
> death by 1000 of them.    If not, this has all of the hallmarks
> of a gratuitous change to a format that has been useful to many
> people for a very long time.
> 
>     john
> 
> p.s. Just in case I'm the anonymous person John Levine's note
> referred to, I didn't just "not participate" in the discussion.
> It was made extremely clear that my input was not welcome, so
> clear that, after a discussion or two with Heather that I should
> spend my time in other ways.  If there were a significant number
> of others like me (and I have no way to tell, or even to guess)
> then claims that the no-pagination form represents community
> consensus lie somewhere on the scale between "dubious" and
> "bogus".
> 
> 
> .
>