IETF Logo Mail Archive

Re: [art] New RFCs text formatting

"Joel M. Halpern" <jmh@joelhalpern.com> Sat, 30 November 2019 23:46 UTC

Return-Path: <jmh@joelhalpern.com>
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 B89FE120129 for <ietf@ietfa.amsl.com>; Sat, 30 Nov 2019 15:46:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, 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=joelhalpern.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 g33Gg-DCn4qe for <ietf@ietfa.amsl.com>; Sat, 30 Nov 2019 15:46:11 -0800 (PST)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 493A4120047 for <ietf@ietf.org>; Sat, 30 Nov 2019 15:46:11 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 47QSgl1YCLz6G8CS; Sat, 30 Nov 2019 15:46:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1575157571; bh=3cEt1fqb/nIYnjixTWlPSQd1+FEa3T847cdiY3QwfxM=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=g1KBCEPSVoby8YpGK51RQUxKQVCLg+FyspOIoHEgVDNQ71X/RfbsKaKaX3YTc9jqN ccNFItkDO9ytK6l/g+5/E7TtOGnAkhCHXmGnATbsEkvaP4R9CjC2O3urH7UDc7KLTu Ir/ICLOMpg7B5xzlNgFdpk+Qn/xRGDiovPIBkth8=
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.128.43] (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 47QSgk16kkz6G8CL; Sat, 30 Nov 2019 15:46:09 -0800 (PST)
Subject: Re: [art] New RFCs text formatting
To: Keith Moore <moore@network-heretics.com>, Carsten Bormann <cabo@tzi.org>
Cc: ietf@ietf.org
References: <20191127233129.9829F%steffen@sdaoden.eu> <db882e3c-d3fb-4742-8456-7b400225ecce@www.fastmail.com> <20191128005000.yMa3P%steffen@sdaoden.eu> <08EE9B7B7C15D8F8B5DE6AF5@PSB> <8c144ffb-ca56-4a80-a994-9b8002eac17b@network-heretics.com> <abc32be6-c156-7a7a-104e-517c6d3167f0@levkowetz.com> <A8A2B5E6-64BE-47D7-AB87-2A4C2619995C@tzi.org> <40cb6637-48af-0d27-94d7-9388417c17ba@network-heretics.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <449e262a-6c7e-4278-812b-c40476af7af0@joelhalpern.com>
Date: Sat, 30 Nov 2019 18:46:08 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <40cb6637-48af-0d27-94d7-9388417c17ba@network-heretics.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9Vubig54RnS4TWensNxk8vE79GA>
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: Sat, 30 Nov 2019 23:46:13 -0000

It seems that it ought to take a consensus call (here, rfc-interest, 
somewhere else?) to change the default output prouced by the IETF tools. 
  The question of pagination of output was more contentious than I would 
have expected in previous rounds.

Yours,
Joel

On 11/30/2019 5:58 PM, Keith Moore wrote:
> On 11/30/19 5:22 PM, Carsten Bormann wrote:
> 
>> On Nov 30, 2019, at 21:26, Henrik Levkowetz<henrik@levkowetz.com>  wrote:
>>> If being able to generate paginated text output for published v3 RFC XML
>>> files is desirable, I'm happy to add a switch to do that.
>> Please do.
> 
> Yes, please do.   Though IMO this should be the default. (paginated, not 
> necessarily including page numbers).
> 
> Keith
> 
>

v2.23.0 | Report a Bug | By Email