Re: [art] New RFCs text formatting

"Paul Hoffman" <paul.hoffman@vpnc.org> Thu, 28 November 2019 18:25 UTC

Return-Path: <paul.hoffman@vpnc.org>
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 70C1E1208BB; Thu, 28 Nov 2019 10:25:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.499
X-Spam-Level:
X-Spam-Status: No, score=-1.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.399, SPF_HELO_NONE=0.001, SPF_NONE=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 Gj6Ojxqh0Gh0; Thu, 28 Nov 2019 10:25:08 -0800 (PST)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) (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 B68831208B8; Thu, 28 Nov 2019 10:25:08 -0800 (PST)
Received: from [10.10.10.159] (76-209-242-70.lightspeed.mtryca.sbcglobal.net [76.209.242.70]) (authenticated bits=0) by mail.proper.com (8.15.2/8.15.2) with ESMTPSA id xASINdhZ034601 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 28 Nov 2019 11:23:40 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host 76-209-242-70.lightspeed.mtryca.sbcglobal.net [76.209.242.70] claimed to be [10.10.10.159]
From: Paul Hoffman <paul.hoffman@vpnc.org>
To: John C Klensin <john-ietf@jck.com>
Cc: ietf@ietf.org, art@ietf.org, rfc-editor@rfc-editor.org
Subject: Re: [art] New RFCs text formatting
Date: Thu, 28 Nov 2019 10:25:05 -0800
X-Mailer: MailMate (1.13r5655)
Message-ID: <8FEF3892-AB75-4D61-AB5B-CF837C0D1773@vpnc.org>
In-Reply-To: <08EE9B7B7C15D8F8B5DE6AF5@PSB>
References: <20191127233129.9829F%steffen@sdaoden.eu> <db882e3c-d3fb-4742-8456-7b400225ecce@www.fastmail.com> <20191128005000.yMa3P%steffen@sdaoden.eu> <08EE9B7B7C15D8F8B5DE6AF5@PSB>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Eoov0nae12G50gZkFte5wTFicrY>
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: Thu, 28 Nov 2019 18:25:09 -0000

On 28 Nov 2019, at 8:33, John C Klensin wrote:

> (copying the IETF list -- this is not an ART matter alone)
> Hi.  I realize it is very late, probably too late, to be
> complaining about this, but my clear recollection was that, when
> the v3 project was started, the community was promised that,
> while the authoritative/ canonical/ archival format would shift
> to the XML and fully-functional HTML and PDF format (not just
> HTML and PDF produced from plain text forms) would become
> available, the plain text format would be preserved sufficiently
> that tools [1] that were designed for, and used with, RFCs for
> the last 40-odd years would continue to work and work equally
> well [2].

I strongly believe you are wrong: no such promise was made. If you can 
find any actual message that made such a promise, I'm happy to stand 
corrected.

--Paul Hoffman