Re: [art] New RFCs text formatting
Keith Moore <moore@network-heretics.com> Sun, 01 December 2019 01:49 UTC
Return-Path: <moore@network-heretics.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 91318120835 for <ietf@ietfa.amsl.com>; Sat, 30 Nov 2019 17:49:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.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 qy-FYW-okXW0 for <ietf@ietfa.amsl.com>; Sat, 30 Nov 2019 17:49:08 -0800 (PST)
Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CBC5412082D for <ietf@ietf.org>; Sat, 30 Nov 2019 17:49:08 -0800 (PST)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id F102B6E2; Sat, 30 Nov 2019 20:49:07 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Sat, 30 Nov 2019 20:49:08 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=x/r3zLfWf4nu5RhAIC6AFELev1JL9X+h/6lAoccSB MM=; b=Suk+B4rOlhZf76TZffhU0+T4NuzB18T9ffuKivV4DPkd2pu+pMxT/+BVF i6AbMXWksciyFAmldRPmKMEzl/aXNVCqziH2Xck1EPZ93fReR508zW/8rSbgt/Ib IdAneq38g1o/CQSNEUKppObK9hOHHsKmVEYCKAwYUhp6BWxl7G6OeZjiLq9h2kRP KQPytAyqOmo/hdvydzAvX7CmvRDxIdAmn/mwZ6fMEVCuolIj/OqO7QNmslooVzgz pAQQMlTcjjniseffdgAAklKshVwpAA4FGGR0ezhzy11KW8KkgUrytV8dGIveaNS/ Ys4/keCUy6pu/x0AK2UUQvRvlXMfA==
X-ME-Sender: <xms:EhzjXT8e72mOyHlF4wm8D6iapbjONo-1tXtKxJemM2xtnCRSAUzYrA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudejvddgfeelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepuffvfhfhkffffgggjggtgfesthekredttdefjeenucfhrhhomhepmfgvihht hhcuofhoohhrvgcuoehmohhorhgvsehnvghtfihorhhkqdhhvghrvghtihgtshdrtghomh eqnecuffhomhgrihhnpehrfhgtqdgvughithhorhdrohhrghenucfkphepuddtkedrvddv uddrudektddrudehnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmohhorhgvsehnvghtfi horhhkqdhhvghrvghtihgtshdrtghomhenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:EhzjXW2sL-c-pA5YPav-NFEJe9faX4BOQhzgVoZBLdAagfFbMmR48A> <xmx:EhzjXTbVjK5WRuwT_CgOrfT8xaJ8cuPH8a8NyYyNeLrWlsCRGmnnyg> <xmx:EhzjXZI2rfjXUJtGWSPGZgnT0UBzrF6BwXnxvZTu3cMY3CyfF_PpnQ> <xmx:ExzjXfi-NTpBfnlyKzgh9vdZeVAPqnsEEuwTM4Wr4A1duD-L70xxug>
Received: from [192.168.1.97] (108-221-180-15.lightspeed.knvltn.sbcglobal.net [108.221.180.15]) by mail.messagingengine.com (Postfix) with ESMTPA id 844AB30600AD; Sat, 30 Nov 2019 20:49:06 -0500 (EST)
Subject: Re: [art] New RFCs text formatting
To: John Levine <johnl@taugh.com>, ietf@ietf.org
References: <20191201012449.1FA60FF1ABE@ary.qy>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <2ea342a3-5969-f097-e178-b50e9181261f@network-heretics.com>
Date: Sat, 30 Nov 2019 20:49:05 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <20191201012449.1FA60FF1ABE@ary.qy>
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/ietf/P49VvEBIdXgHDyj_SjMeuOzhReE>
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: Sun, 01 Dec 2019 01:49:11 -0000
On 11/30/19 8:24 PM, John Levine wrote: > In article <e5ca2a0e-53f9-8679-a7cd-093d6b2319be@network-heretics.com> you write: >> It appears that having the canonical format of RFCs be a format other >> than one that people actually use, has "interesting" consequences. For >> example, anyone can generate RFCs in their own preferred format, using >> whatever typeface, pagination, TOC format, references format, etc. they >> wish, > That's a feature. If you don't like the format, you can pick another. > If you don't like any of the existing formats, you can write or adapt > tools to create any format you want. If, say, you want line printer > pages for A4 paper, you can have them. In some ways I agree that it is a feature. But it may also bring some undesirable consequences with it. >> and it's difficult to tell (either by looking or comparison with >> the copy from the RFC Editor's site) whether such an RFC is genuine. > Aw, c'mon. If that's a problem, take the canonical XML and run it through > your favorite formatter yourself to get a fresh authentic copy. On several occasions I've been asked to verify the authenticity of old documents (including some Usenet posts, some RFCs, and some academic papers) for patent litigation purposes. Sometimes what I've been asked to do is verify a document that has already been used as an exhibit in a prior filing, so it's important that the version of the document that was used in the exhibit be verified. If the exhibit was of a plain text RFC, it's pretty easy to do - download the same plain text RFC from rfc-editor.org, verify its date (say using FTP to the file server, and perhaps via other means, like an archived email announcement that was sent concurrent with RFC publication), and optically compare the two documents. But on several occasions when I've been asked to do this, the exhibit was printed-out HTML and the document that could be readily authenticated (the one that the HTML was derived from) was in a different format. It can be tricky to explain the differences in a way that is convincing to a jury. I may be more sensitive to this issue than some because I've had to do this several times in 2019. But having the old canonical format for RFCs also be the one that was most widely read, was indeed a feature. Keith
- Re: [art] New RFCs text formatting John C Klensin
- Re: [art] New RFCs text formatting Carsten Bormann
- Re: [art] New RFCs text formatting John Levine
- Re: [art] New RFCs text formatting Claudio Allocchio
- Re: [art] New RFCs text formatting Paul Hoffman
- Re: [art] New RFCs text formatting Julian Reschke
- Re: [art] New RFCs text formatting Jeffrey Yasskin
- Re: [art] New RFCs text formatting Brian E Carpenter
- Re: [art] New RFCs text formatting Marc Petit-Huguenin
- Re: [art] New RFCs text formatting Paul Hoffman
- Re: [art] New RFCs text formatting John C Klensin
- Re: [art] New RFCs text formatting Julian Reschke
- Re: [art] New RFCs text formatting Keith Moore
- Re: [art] New RFCs text formatting John C Klensin
- Re: [art] New RFCs text formatting Brian E Carpenter
- Re: [art] New RFCs text formatting Keith Moore
- Re: [art] New RFCs text formatting Bob Hinden
- Re: [art] New RFCs text formatting Julian Reschke
- Re: [art] New RFCs text formatting Carsten Bormann
- Re: [art] New RFCs text formatting Keith Moore
- Re: [art] New RFCs text formatting Julian Reschke
- Re: [art] New RFCs text formatting John C Klensin
- Re: [art] New RFCs text formatting Carsten Bormann
- Re: [art] New RFCs text formatting John Levine
- Re: [art] New RFCs text formatting Julian Reschke
- Re: [art] New RFCs text formatting Julian Reschke
- Re: [art] New RFCs text formatting Henrik Levkowetz
- Re: [art] New RFCs text formatting Carsten Bormann
- Re: [art] New RFCs text formatting Keith Moore
- Re: [art] New RFCs text formatting Joel M. Halpern
- Re: [art] New RFCs text formatting Keith Moore
- Re: [art] New RFCs text formatting Henrik Levkowetz
- Re: [art] New RFCs text formatting Keith Moore
- Re: [art] New RFCs text formatting John C Klensin
- Re: [art] New RFCs text formatting Joel Halpern Direct
- Re: [art] New RFCs text formatting Phillip Hallam-Baker
- Re: [art] New RFCs text formatting Nick Hilliard
- Re: [art] New RFCs text formatting Keith Moore
- Re: [art] New RFCs text formatting Scott O. Bradner
- Re: [art] New RFCs text formatting Eric Heflin
- Re: [art] New RFCs text formatting Paul Hoffman
- Re: [art] New RFCs text formatting Keith Moore
- Re: [art] New RFCs text formatting John Levine
- Re: [art] New RFCs text formatting John C Klensin
- Re: [art] New RFCs text formatting Scott O. Bradner
- Re: [art] New RFCs text formatting Scott O. Bradner
- Re: [art] New RFCs text formatting Brian E Carpenter
- Re: [art] New RFCs text formatting Scott O. Bradner
- Re: [art] New RFCs text formatting Julian Reschke
- Re: [art] New RFCs text formatting Brian Carpenter
- Re: [art] New RFCs text formatting Salz, Rich
- Re: [art] New RFCs text formatting John C Klensin
- Re: [art] New RFCs text formatting Carsten Bormann
- Re: [art] New RFCs text formatting Salz, Rich
- Handling HTAB in artwork/sourcecode, was: [art] N… Julian Reschke
- Re: Handling HTAB in artwork/sourcecode, was: [ar… John C Klensin
- Re: Handling HTAB in artwork/sourcecode, was: [ar… Carsten Bormann
- Re: Handling HTAB in artwork/sourcecode, was: [ar… John C Klensin
- Re: Handling HTAB in artwork/sourcecode, was: [ar… Julian Reschke
- Re: [art] New RFCs text formatting John C Klensin