Re: [rfc-i] John/rsoc: Re: Page numbers in RFCs questions / preferences

Jay Daley <jay@ietf.org> Mon, 26 October 2020 19:56 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEE203A0E83; Mon, 26 Oct 2020 12:56:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.648
X-Spam-Level:
X-Spam-Status: No, score=-2.648 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-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 gwNaGuGY5B90; Mon, 26 Oct 2020 12:56:34 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B8BF3A0E7F; Mon, 26 Oct 2020 12:56:34 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 9C211F40769; Mon, 26 Oct 2020 12:56:23 -0700 (PDT)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 2FCA5F40769 for <rfc-interest@rfc-editor.org>; Mon, 26 Oct 2020 12:56:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yOeu7Iik2O8W for <rfc-interest@rfc-editor.org>; Mon, 26 Oct 2020 12:56:17 -0700 (PDT)
Received: from mail.ietf.org (mail.ietf.org [4.31.198.44]) by rfc-editor.org (Postfix) with ESMTPS id C109EF40767 for <rfc-interest@rfc-editor.org>; Mon, 26 Oct 2020 12:56:17 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E2EC3A0E83; Mon, 26 Oct 2020 12:56:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.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 Mr5fbeoDRHYL; Mon, 26 Oct 2020 12:56:26 -0700 (PDT)
Received: from jays-mbp.localdomain (unknown [158.140.230.105]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id 295833A0E7F; Mon, 26 Oct 2020 12:56:25 -0700 (PDT)
From: Jay Daley <jay@ietf.org>
Message-Id: <800D499F-9D59-4E5A-A400-6AA30CB01445@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
Date: Tue, 27 Oct 2020 08:56:22 +1300
In-Reply-To: <20201026195118.GX48111@faui48f.informatik.uni-erlangen.de>
To: Toerless Eckert <tte@cs.fau.de>
References: <1a56dc3b-56ef-3ffb-a12b-44d5e0d0f835@levkowetz.com> <20201026171931.GP48111@faui48f.informatik.uni-erlangen.de> <b733240-fc78-5a71-8920-ff84fbf64287@iecc.com> <d935e027-f45b-fbec-0072-23d1481c3e90@nostrum.com> <41d4240-9a6d-67b2-1c20-3ea7895fe8ca@iecc.com> <9c512e40-1a82-fdfb-a332-154b42456a5e@nostrum.com> <5f64e230-1aca-7083-9aac-ba497295f80@iecc.com> <adb49858-babf-bbee-07d8-0b73c24e2c22@nostrum.com> <20201026190300.GV48111@faui48f.informatik.uni-erlangen.de> <1bf9797a-0410-883b-3630-bc55e6a134e5@nostrum.com> <20201026195118.GX48111@faui48f.informatik.uni-erlangen.de>
X-Mailer: Apple Mail (2.3608.120.23.2.1)
Subject: Re: [rfc-i] John/rsoc: Re: Page numbers in RFCs questions / preferences
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Cc: "John R. Levine" <johnl@iecc.com>, rfc-interest@rfc-editor.org, rsoc@iab.org
Content-Type: multipart/mixed; boundary="===============2236100131254932533=="
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>


> On 27/10/2020, at 8:51 AM, Toerless Eckert <tte@cs.fau.de> wrote:
> 
> On Mon, Oct 26, 2020 at 02:09:59PM -0500, Robert Sparks wrote:
>>> Who could point me to an RFC and a page# in that RFC (;-) that does
>>> actually include the magical words like "THERE SHALL BE NO RFC
>>> REPRESENTATION WITH PAGE NUMERS" ? Would really appreciate not having
>>> to read through the whole list of the RFC.
>> 
>> 7990 section 7.3
>> 
>> 7994 section 4.1 (doesn't mention page numbers explicitly, but their absence
>> is a direct consequence of this section's requirements).
> 
> Thank, Robert
> 
> Section 4. of 7994 mentions a paginated text format (58 lines/page at most).
> Where are those text files ?

On the canonical site.  e.g. https://www.rfc-editor.org/info/rfc7994 <https://www.rfc-editor.org/info/rfc7994>

Jay

> 
> Cheers
>    Toerless
> 
>>>  then we're probably out of luck anyhow. If
>>> this could be driven by the community, i wonder what WG it would need to
>>> go to to have ough consensus applied to it.
>>> 
>>> Cheers
>>>     Toerless
>>> 
>>>>>   If we're going to add every tweak that one person wants, it's going to
>>>>> get awfully expensive.
>>>> That's a terrible generalization to bring to the question I was pointing at.
>>>> _This_ tweak is extremely cheap - the code already has to produce these
>>>> numbers for internet-drafts, so the cost is a flag.
>>>> 
>>>> The cost of a well-known published set of documents that look like RFCs but
>>>> have had some changes made is different and should be addressed separately.
>>>> (I'll point here to the inline errata for pre-v3 format rfcs.)
>>>> 
>>>>>> The RFC editor does not publish an epub format, for example. If
>>>>>> someone were to contribute an epub formatter that was reasonable to
>>>>>> merge and maintain, we should merge that. Allowing the tools to
>>>>>> produce page numbers for local use falls pretty close to that
>>>>>> doesn't it?
>>>>> No, it's something the IETF explicitly considered and rejected when it
>>>>> designed the new format.
>>>> Which "it"? If you meant epub, RFC7990 says
>>>> 
>>>>> 7.4.  Potential Future Publication Formats
>>>>> 
>>>>> 7.4.1.  EPUB
>>>>> 
>>>>>     This format is intended for use by ebook readers and will be
>>>>>     available for RFCs after the requirements have been defined.  No
>>>>>     document on this topic is currently available.
>>>> That certainly isn't rejection - certainly not of creating epub, and not
>>>> even of publishing things in epub in the long run. We had to choose what was
>>>> feasible with the initial tooling effort, and epub didn't make _that_ cut.
>>>> 
>>>>> Regards,
>>>>> John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for
>>>>> Dummies",
>>>>> Please consider the environment before reading this e-mail. https://jl.ly
> 
> -- 
> ---
> tte@cs.fau.de <mailto:tte@cs.fau.de>
-- 
Jay Daley
IETF Executive Director
jay@ietf.org

_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest