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

Robert Sparks <rjsparks@nostrum.com> Mon, 26 October 2020 17:54 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 445353A0DF8; Mon, 26 Oct 2020 10:54:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.697
X-Spam-Level:
X-Spam-Status: No, score=-2.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, NICE_REPLY_A=-0.247, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 q1XrHitXwNkV; Mon, 26 Oct 2020 10:54:00 -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 98E2B3A0B85; Mon, 26 Oct 2020 10:54:00 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 16836F4073C; Mon, 26 Oct 2020 10:53:50 -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 10EA8F4073C for <rfc-interest@rfc-editor.org>; Mon, 26 Oct 2020 10:53:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.com
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 Iy1aL_AZnCRt for <rfc-interest@rfc-editor.org>; Mon, 26 Oct 2020 10:53:44 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) by rfc-editor.org (Postfix) with ESMTPS id 6D99FF4073B for <rfc-interest@rfc-editor.org>; Mon, 26 Oct 2020 10:53:44 -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 09QHrX0F043991 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 26 Oct 2020 12:53:34 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1603734816; bh=vC6rq8RwuLlc6b5YfoXXMu+sc5C/uDjrcFunHcDz9JM=; h=To:Cc:References:From:Subject:Date:In-Reply-To; b=JhFAkJTfxPMzgSGZrIT81nm0R9T3HD0TazzATf715vlTHLttO6ySWWlYvpp9mjVpn 9WpOl+UnOk5c2MGbvpGNohRwGc7owKiyA6bmsOuL7ra+gNg4V5o0orWC2jFrhVuHsb iJWkc+l4jaDBtnHRnR589VJBabWWn+PM+c9j3vcY=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.30.41] claimed to be unescapeable.local
To: "John R. Levine" <johnl@iecc.com>, rfc-interest@rfc-editor.org, Toerless Eckert <tte@cs.fau.de>, rsoc@iab.org
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> <d935e027-f45b-fbec-0072-23d1481c3e90@nostrum.com> <41d4240-9a6d-67b2-1c20-3ea7895fe8ca@iecc.com>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <9c512e40-1a82-fdfb-a332-154b42456a5e@nostrum.com>
Date: Mon, 26 Oct 2020 12:53:33 -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: <41d4240-9a6d-67b2-1c20-3ea7895fe8ca@iecc.com>
Content-Language: en-US
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>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

On 10/26/20 12:47 PM, John R. Levine wrote:
>> 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.
>
> I am not Heather and I do not remember all the details, but I cannot 
> imagine why you would want to reopen this can of worms.
>
> People can write whatever they want for their own use, but the tools 
> we are paying for produce the output formats that our consensus 
> documents describe.

mmm. Again, I dont think you're quite seeing this aspect of the question.

I (at least) am not trying to reopen any cans about what gets published.

But when the community asks that the tools produce something different 
for their local use, and it's easy and inexpensive to add and maintain, 
it doesn't seem like it's the right thing to do to deny it by policy.

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?

RjS

>
> 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

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