Re: FIXED: Poll: RFCs with page numbers (pretty please) ? (was: Re: John/rsoc: Re: Page numbers in RFCs questions / preferences)

Jim Fenton <fenton@bluepopcorn.net> Tue, 27 October 2020 23:57 UTC

Return-Path: <fenton@bluepopcorn.net>
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 4204B3A097F; Tue, 27 Oct 2020 16:57:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bluepopcorn.net
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 vxWLaJNgk8o9; Tue, 27 Oct 2020 16:57:44 -0700 (PDT)
Received: from v2.bluepopcorn.net (v2.bluepopcorn.net [IPv6:2607:f2f8:a994::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 851083A097C; Tue, 27 Oct 2020 16:57:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bluepopcorn.net; s=supersize; h=Content-Transfer-Encoding:Content-Type: MIME-Version:References:In-Reply-To:Message-ID:Date:Subject:Cc:To:From:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=HeY7QmvLNW96o1xDbjfk+H+B45yO7xrxNI/kH9HNrdk=; b=AxwxAZiTgXa6Jiw/CKxULBEmdZ TVv7RfjvUGUv4AqlIgGxos8f1wuwN96VQNEuO05QJMAC19RNkzMuYPOBUmDoB59RDYbR1vH0+cDIp 6DLE1S/pbIXzxuBc2c2Jag/0mHvGuOjXWCSsOmRBTRwl47g8PtTLuae+ohVOhc+Hte3s=;
Received: from [2601:647:4400:1261:ac45:fb1a:7502:2d] (helo=[10.10.20.144]) by v2.bluepopcorn.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <fenton@bluepopcorn.net>) id 1kXYqR-0002Tf-0z; Tue, 27 Oct 2020 16:57:39 -0700
From: "Jim Fenton" <fenton@bluepopcorn.net>
To: "David Noveck" <davenoveck@gmail.com>
Cc: "Phillip Hallam-Baker" <phill@hallambaker.com>, "Working Group Chairs" <wgchairs@ietf.org>, "John Levine" <ietf@johnlevine.com>, "IETF Discussion Mailing List" <ietf@ietf.org>, "RFC Interest" <rfc-interest@rfc-editor.org>, rsoc@iab.org
Subject: Re: FIXED: Poll: RFCs with page numbers (pretty please) ? (was: Re: John/rsoc: Re: Page numbers in RFCs questions / preferences)
Date: Tue, 27 Oct 2020 16:57:38 -0700
X-Mailer: MailMate (1.13.2r5673)
Message-ID: <D2D0455D-8D6C-4A19-ACAE-4DD972D83DC1@bluepopcorn.net>
In-Reply-To: <CADaq8jdSeTDWy_0fCV25ykxKFMV1ZBtUMMNesoOuaXCzFVfpOA@mail.gmail.com>
References: <20201026181442.GA2438@faui48f.informatik.uni-erlangen.de> <CAMm+LwiVmE=qtSPCMD-3foPODL8bgETj3dQDKS-3BOM2021dEg@mail.gmail.com> <CADaq8jdSeTDWy_0fCV25ykxKFMV1ZBtUMMNesoOuaXCzFVfpOA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/09o_g3o9g7YWzDy22Td_hoLpO9o>
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: Tue, 27 Oct 2020 23:57:46 -0000

[Yikes, this discussion is getting crossposted everywhere, it seems. 
I’ll keep it brief]

On 27 Oct 2020, at 16:36, David Noveck wrote:

> The issue comes up with PDF files.  Currently, you get page numbers
> together with a TOC that has no page numbers.  I'm OK with a no-TXT 
> option
> but I have a problem with a not-usefully-printable option for RFCs.

When RFC 8689 was about to be published about a year ago, I had a chat 
with the staff at the RFC Editor table in Singapore about this. It 
seemed a little strange to have a table of contents without page 
numbers, 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. 
References should be to section numbers, and if sections are so big that 
it’s hard to find some text there, the author should really think 
about structuring the document with smaller subsections.

What does seem strange (and maybe it has changed in the past year) is 
that the plain text and PDF versions have tables of contents, and the 
html version does not. I would like for the html version to have a table 
of contents with links to anchors for each section.

-Jim

> On Tue, Oct 27, 2020, 6:51 PM Phillip Hallam-Baker 
> <phill@hallambaker.com>
> wrote:
>
>> Whooaah there...
>>
>> What is the status of this poll? I am all for moving from the 
>> subjective
>> consensus model in which certain parties get a veto because their 
>> opinions
>> are considered weightier than the rest of us. Objective measures of
>> consensus are good. But is this an official poll? What does it mean?
>>
>> But of course, as John K. pointed out, this is not actually an IETF
>> process. Only of course it is in every meaningful sense except 
>> insofar as
>> IETF rules of the road apply.
>>
>>
>> Page numbers is not the hill I would choose to die on here. They 
>> don't
>> work in HTML and the whole point of this process is that the TXT 
>> documents
>> reflect very badly on the IETF as an organization. It spoke of an
>> organization that is stuck in the 1960s ranting on about how vinyl is
>> better than CD.
>>
>> There are serious issues with the new format. Not least the fact that 
>> SVG
>> is not actually supported. The supported format is SVG/Tiny which is 
>> an
>> obsolete format originally proposed back in the WAP days as a means 
>> of
>> crippling the spec to fit the capabilities of the devices back before 
>> Steve
>> Jobs showed us an iPhone for the first time. There are no tools that
>> produce SVG/Tiny, not even GOAT - I had to modify the source code to 
>> comply.
>>
>> I don't mind retooling to support an improved specification. Having 
>> to
>> retool to support an obsolete one is nonsense.
>>
>>
>> Anyway, how about as a compromise, authors can opt to suppress 
>> generation
>> of the TXT version so that the page number issue doesn't come up at 
>> all?