Re: John/rsoc: Re: Page numbers in RFCs questions / preferences

Robert Sparks <rjsparks@nostrum.com> Mon, 26 October 2020 17:44 UTC

Return-Path: <rjsparks@nostrum.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 117F13A0E06; Mon, 26 Oct 2020 10:44:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.651
X-Spam-Level:
X-Spam-Status: No, score=-1.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, KHOP_HELO_FCRDNS=0.275, NICE_REPLY_A=-0.247, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.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 GaqqjM0y_luY; Mon, 26 Oct 2020 10:44:24 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 C50123A0E03; Mon, 26 Oct 2020 10:44:20 -0700 (PDT)
Received: from unescapeable.local ([47.186.30.41]) (authenticated bits=0) by nostrum.com (8.16.1/8.16.1) with ESMTPSA id 09QHi4ZD040553 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 26 Oct 2020 12:44:05 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1603734246; bh=I/cdX6mqFwjXBcTn8QFV1CVjNElJlVh2B3SYbGa9aJg=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=fopQfGGelGZl8eUig3d456n2HG3IJIwNe00d9j/bTfYq7uzYyUyq52YvN1JQpYQkA gSYDi9lxFHxWL+MboM1b+0LKLWtbK8/K6kEmcx5DnvUmOSLVNNZ9/xMiHlSfvgKnin 99FdNOc1HltKD71WNqHVcWXUzU5QfEdww7hek0ns=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.30.41] claimed to be unescapeable.local
Subject: Re: John/rsoc: Re: Page numbers in RFCs questions / preferences
To: rfc-interest@rfc-editor.org, Toerless Eckert <tte@cs.fau.de>, ietf@johnlevine.com, rsoc@iab.org
Cc: WG Chairs <wgchairs@ietf.org>, Henrik Levkowetz <henrik@levkowetz.com>
References: <20201026020433.GA19475@faui48f.informatik.uni-erlangen.de> <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>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <d935e027-f45b-fbec-0072-23d1481c3e90@nostrum.com>
Date: Mon, 26 Oct 2020 12:44:04 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:78.0) Gecko/20100101 Thunderbird/78.4.0
MIME-Version: 1.0
In-Reply-To: <b733240-fc78-5a71-8920-ff84fbf64287@iecc.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/j5_mEtxhuDPJdTEftcILoKE3ak8>
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 17:44:29 -0000

John - you've answered why RFCs are not published with page numbers and 
where/when the community discussion that took place for that decision.

You haven't answered whether/how the RSOC engaged the community on the 
question of whether the tools should let someone produce an RFC locally 
that has page numbers in it for themselves if they want to. The 
reasoning for not letting the tools produce such a thing is certainly 
not explicitly captured in the series of RFCs you point to.

Julian has alluded to the principle behind the pressure already, but I'm 
still at a small loss for why RSOC, or the RSE, should care about what 
people make for themselves?

RjS

On 10/26/20 12:35 PM, 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
>