IETF Logo Mail Archive

Re: [art] New RFCs text formatting

Jeffrey Yasskin <jyasskin@google.com> Thu, 28 November 2019 19:58 UTC

Return-Path: <jyasskin@google.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 AD6551208C9 for <ietf@ietfa.amsl.com>; Thu, 28 Nov 2019 11:58:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.499
X-Spam-Level:
X-Spam-Status: No, score=-17.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 Ay1U8-TpqAZC for <ietf@ietfa.amsl.com>; Thu, 28 Nov 2019 11:58:09 -0800 (PST)
Received: from mail-qt1-x82b.google.com (mail-qt1-x82b.google.com [IPv6:2607:f8b0:4864:20::82b]) (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 A64171208C8 for <ietf@ietf.org>; Thu, 28 Nov 2019 11:58:09 -0800 (PST)
Received: by mail-qt1-x82b.google.com with SMTP id n4so30189458qte.2 for <ietf@ietf.org>; Thu, 28 Nov 2019 11:58:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=gxMOS47/rqXvyUrG6Js2HPsTMMmP4w02Xhyf6Jq7Bsg=; b=DvqnUxodr97n+Q/2Ran11rQQtdafEMsrzW6cG4OGkH9hdigdmplWjaaC3LuAzJXbA7 +yrthl3eKzzL8zDyk3R7OCh5avOOLTXBnL3FuZ3ahpNl4xbUXHy7cyQn/87hgQlK6YUK 2sF6hJPr4YnwtKAmEZ7VKe1EPeyPhAdMYbNeNEkfg82F5TnqnylKcgN31Cz5zL/upOri gEOp+goioK9SvGgALoyQRhOBdkcEnkmNN8WMpVF2rXaCwGCAMtk1uZ4Xaf3SKay+487Y RgpX1g5ETOmwseDARVW631nS7PZpDPkg6ruAvcpffCArdOgy5i0bPmDzqsBcWKX9jeK1 T+jg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=gxMOS47/rqXvyUrG6Js2HPsTMMmP4w02Xhyf6Jq7Bsg=; b=NPMMLJB8qgLTFQ4bnl2XHZLbXIYderGIgjd3c6y1a3vZ4MQVrBCD8Oj7BaE6KmqGW9 iEnTw3jJjeIjBcrfzgTWhIgWUxNRDkHdR4pFDFpg+lnYBXoLVfZFGH0co1pFQ9czPQ9s rDawroA0BCJu83L9DvRM8AmnhCqehE89oFHDYv2Z1tl/LpnjCU6LObRa3mZxmWbuz/tG GEHprlrodsoi6vNSdI5xcD7bQVrYoDYWxTUmjrb/5FWtvbalsNjQwMMroIWS/kZ5pIEo ejiv6M24qMiPwGV/cs0tBJKSDnqCZcVbtsketIJPqXh0lx1e7EcjMtzD9SmZylo+g68+ WqPw==
X-Gm-Message-State: APjAAAXvllHJYP8eeVMrDuOGWEFtb+xzOh4SWGVPKB5I8++MpuE601Mp 0059qq6ZDso3qIdz20sTDApY2m0K80mar33IDFYEGjjv1HQ=
X-Google-Smtp-Source: APXvYqzgXDAJnBLjjSIjLuf4vkzzXRmI+M6OXAhwGdNCVI0w8UyVVNV/wHDZ3dBvc5fAC+w4J177svWtZo7FpCr+fGY=
X-Received: by 2002:ac8:1afc:: with SMTP id h57mr36584526qtk.250.1574971087901; Thu, 28 Nov 2019 11:58:07 -0800 (PST)
MIME-Version: 1.0
References: <20191127233129.9829F%steffen@sdaoden.eu> <db882e3c-d3fb-4742-8456-7b400225ecce@www.fastmail.com> <20191128005000.yMa3P%steffen@sdaoden.eu> <08EE9B7B7C15D8F8B5DE6AF5@PSB> <8FEF3892-AB75-4D61-AB5B-CF837C0D1773@vpnc.org>
In-Reply-To: <8FEF3892-AB75-4D61-AB5B-CF837C0D1773@vpnc.org>
From: Jeffrey Yasskin <jyasskin@google.com>
Date: Thu, 28 Nov 2019 11:57:56 -0800
Message-ID: <CANh-dXmr1hwk+qBOoCDTiV4-8_Mhhmu=2g8Jiwd_VMpX+bTxyQ@mail.gmail.com>
Subject: Re: [art] New RFCs text formatting
To: Paul Hoffman <paul.hoffman@vpnc.org>
Cc: John C Klensin <john-ietf@jck.com>, IETF Discussion <ietf@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Content-Type: multipart/alternative; boundary="0000000000003a4afb05986d8826"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/W9blWB48Q_Cx51xpvUgaYWo8EOo>
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 19:58:12 -0000

On Thu, Nov 28, 2019, 10:25 AM Paul Hoffman <paul.hoffman@vpnc.org> wrote:

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

https://www.rfc-editor.org/rse/format-faq/#10 points to
https://www.rfc-editor.org/rfc/rfc6949.html#section-3.3, which explicitly
retires pagination as a goal.

Jeffrey

v2.23.0 | Report a Bug | By Email