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

Toerless Eckert <tte@cs.fau.de> Mon, 26 October 2020 19:10 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
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 58FCA3A0E1D; Mon, 26 Oct 2020 12:10:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.869
X-Spam-Level:
X-Spam-Status: No, score=-0.869 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=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 XCNl_lySUMca; Mon, 26 Oct 2020 12:10:47 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 089093A0E28; Mon, 26 Oct 2020 12:10:47 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [131.188.34.52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 29A02548659; Mon, 26 Oct 2020 20:10:42 +0100 (CET)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 22D00440059; Mon, 26 Oct 2020 20:10:42 +0100 (CET)
Date: Mon, 26 Oct 2020 20:10:42 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: ietf@ietf.org, wgchairs@ietf.org, ietf@johnlevine.com, rfc-interest@rfc-editor.org, rsoc@iab.org
Subject: Re: Poll: RFCs with page numbers (pretty please) ?
Message-ID: <20201026191042.GA59330@faui48f.informatik.uni-erlangen.de>
References: <CADaq8je8gMwAkOndTNJ9ndwzOZb2HQMZrCUJ5wNUjw-6ax9QtA@mail.gmail.com> <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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <03976f9f-7f49-7bf7-ce29-ee989232a44d@gmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/FcDBldfFtt7j5SUzTitbr5n9z2U>
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 19:10:49 -0000

Brian:

RFC editor can easily check that new RFC will not have references to
other RFCs with page numbers.

Its also perfectly easy to have only one rendering of page numbers, so
therre won't be inconsistencies of page numbers on official IETF pages.

Cheers
    Toerless

On Tue, Oct 27, 2020 at 07:56:36AM +1300, Brian E Carpenter 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
> 
> 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.
> 
> Regards
>    Brian 
> 
> Regards
>    Brian Carpenter
> 
> On 27-Oct-20 07:01, Toerless Eckert wrote:
> > Since about RFC8650, newer RFC will not have any renderings with
> > page numbers on {datatracker,tools}.ietf.org. See explanation from
> > John Levine below.
> > 
> > Not having followed the details of the RFC/XMLv3 standardization process,
> > i was surprised by this because i think there is no reason to
> > have additional renderings, maybe even only on tools.ietf.org that
> > do include page numbers (and technically it does not seem to be a problem
> > either). 
> > 
> > If you care to express your position,
> > i have created a poll for this, please chime in there:
> > 
> > https://www.poll-maker.com/results3188562x294441dA-98
> > 
> > Cheers
> >     toerless
> > 
> > On Mon, Oct 26, 2020 at 01:35:43PM -0400, John R. Levine wrote:
> >>> Could you please explain why RSOC does not want to permit the ability
> >>> to have paginated RFC output options ? Also, where and when was this
> >>> discussed with the community ?
> >>
> >> It was discussed in the multi-year process leading to the IAB
> >> publishing RFCs 7990, 7991, 7992, 7993, 7994, 7995, 7996, 7997, and
> >> 7998 in 2016. I'm sure you know how to find the discussions in the
> >> archives.  Henrik knows all of this and I cannot imagine why he did not tell
> >> you the same thing.
> >>
> >> I am aware there is one recent RFC author who did not participate in
> >> the process at all and has been complaining that the text version of
> >> his RFC doesn't have page numbers. I've explained this to him more
> >> than once, and see no reason to waste more time on it.
> >>
> >> R's,
> >> John
> > 
> > .
> > 

-- 
---
tte@cs.fau.de