Re: [art] New RFCs text formatting

"Scott O. Bradner" <sob@sobco.com> Sun, 01 December 2019 20:48 UTC

Return-Path: <sob@sobco.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 E4C1A120110 for <ietf@ietfa.amsl.com>; Sun, 1 Dec 2019 12:48:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.108
X-Spam-Level:
X-Spam-Status: No, score=-1.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_PASS=-0.001] autolearn=no 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 eFbw4RJgf3Zg for <ietf@ietfa.amsl.com>; Sun, 1 Dec 2019 12:48:03 -0800 (PST)
Received: from sobco.sobco.com (unknown [136.248.127.164]) by ietfa.amsl.com (Postfix) with ESMTP id 171E7120108 for <ietf@ietf.org>; Sun, 1 Dec 2019 12:48:03 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id 7EFF3257B53C; Sun, 1 Dec 2019 15:48:02 -0500 (EST)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tasIA-U4GY2y; Sun, 1 Dec 2019 15:47:59 -0500 (EST)
Received: from golem.sobco.com (golem.sobco.com [136.248.127.162]) by sobco.sobco.com (Postfix) with ESMTPSA id C09DA257B52D; Sun, 1 Dec 2019 15:47:58 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: [art] New RFCs text formatting
From: "Scott O. Bradner" <sob@sobco.com>
In-Reply-To: <d4dc9942-c660-e856-d352-3e8b83e4e639@gmail.com>
Date: Sun, 01 Dec 2019 15:47:57 -0500
Cc: rfc-interest@ietf.org, ietf@ietf.org, moore@network-heretics.com
Content-Transfer-Encoding: quoted-printable
Message-Id: <869D2C59-A667-4EE6-9D5A-6B7E37C42AA2@sobco.com>
References: <20191201190954.3CC38FF7AAB@ary.qy> <d136f7ad-373d-7a57-8ae1-c391a5b6f7de@gmail.com> <87B6A278-AAB7-45DA-9675-9ABCCC3FE497@sobco.com> <d4dc9942-c660-e856-d352-3e8b83e4e639@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Nz2FNKC4Yr4Ec4mmtdbewUhit2M>
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: Sun, 01 Dec 2019 20:48:05 -0000

the usefulness of a link depends on where the reference is used - I, for example, reference RFCs very
frequently in expert reports in patent cases where everything is still paper-based so the references
need to work when printed on paper

Scott


> On Dec 1, 2019, at 3:45 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> Scott,
> 
> On 02-Dec-19 09:36, Scott O. Bradner wrote:
>> 
>> 
>>> On Dec 1, 2019, at 3:33 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>>> 
>>> On 02-Dec-19 08:09, John Levine wrote:
>>>> In article <1a1726cf-70a0-019d-1138-c5e22f258d4d@network-heretics.com> you write:
>>>>> I thought the format was a compromise between US Letter format, A4 
>>>>> format, and printers.
>>>> 
>>>> I thought it was 72 characters because that's how many you got on a
>>>> punch card, leaving 8 for the sequence number.
>>> 
>>> Keith is right and it was one of Postel+Reynolds's wiser decisions. The only case where it goes wrong is with software or printers that fail to recognise the FF (form feed) character correctly.
>>> 
>>> Phill is correct that it wastes some white space; that's the price of fitting into both paper sizes. When I print drafts, which is rarely, I do it "booklet" style which limits waste paper considerably.
>>> 
>>> As we discussed 3 years ago, numbered pagination is useful in a printable format but irrelevant in a screen-only format.
>> 
>> except for references - section numbers are frequently far too far apart when you want to point someone to a particular
>> chunk of text
> 
> Yes. I sometimes use page numbers for that reason, like https://tools.ietf.org/html/rfc3056#page-15 (random example with no significance). For new-format HTML, any internal <xref/> should generate a link.
> 
>    Brian
> 
>> 
>> Scott
>> 
>>> 
>>> Can we stop now?
>>> 
>>>    Brian
>>>> 
>>>>> What would be parochial would be to assume that nobody in the world 
>>>>> needs to print RFCs using mechanical printers any more - that everyone 
>>>>> in the world should have laser printers, ample power for their fusers, 
>>>>> and a generous supply of suitable paper and toner -
>>>> 
>>>> I think that if you price all the printers made in the past decade or
>>>> two, you'll find that there are a lot of laser and inkjet printers and
>>>> close to nothing else, certainly nothing restricted to fixed pitch
>>>> text.  The only mechanical printers I recall seeing in recent years
>>>> are antique Okidata dot matrix units printing whatever it is they
>>>> print at airport gates.
>>>> 
>>>> R's,
>>>> John
>>>> 
>>>> 
>>> 
>> 
>>