IETF Logo Mail Archive

Re: [art] New RFCs text formatting

Bob Hinden <bob.hinden@gmail.com> Fri, 29 November 2019 16:35 UTC

Return-Path: <bob.hinden@gmail.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 AB82E120A1E; Fri, 29 Nov 2019 08:35:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 HQ7mEIAuG_Iy; Fri, 29 Nov 2019 08:35:30 -0800 (PST)
Received: from mail-wr1-x443.google.com (mail-wr1-x443.google.com [IPv6:2a00:1450:4864:20::443]) (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 93D01120A25; Fri, 29 Nov 2019 08:35:30 -0800 (PST)
Received: by mail-wr1-x443.google.com with SMTP id z3so35900846wru.3; Fri, 29 Nov 2019 08:35:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=AId8iazP5fJe2cxeDN4Ow+x9YK6uUhmDB4lgk1JUYRc=; b=oySlBXejVnyjAnxA+Ldtb++TCv2ZzZ9+AnT2fLtJyGf4r774cPLhzUzs+GO5QvYJrY HWtcCeRuD3EDYuE3O67Ile4xLUjzspSW0NvH5AGzOk5dtIUS+a1iYgrCQ5AWkzYqtopA qL9X0PS3qKediJMizypWTeDF88/O59IOwAkvAF6ih/C8LHszxo3cLexkWOB69gCyvXsT NdcBe0hjxUk4oRWf1YFZ7br3XJmES2ZNl/O+7hgd0tblAaj+P80vtKh/cwJaXWq0r6i6 xlAQZR9LyWyCVWsZCsWFd4IeFDbFQbBWftlu212CgnqKDkExFxL+uJZrIgKC0yleINng +J6Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=AId8iazP5fJe2cxeDN4Ow+x9YK6uUhmDB4lgk1JUYRc=; b=C7uWKGTFtn7b/uN3WpZw093GpMjgt61em3M1axww7vQ45LaReO9Bv2CNVU7AZM2891 PWrKlyV+4jTVygw1H7EYX65A5U+vDdHG7i3dF1gZHa5Zdi4f76h7B80itRuUL4y9BVrs CvPtQu/tiBLjYHsImuyHYyP2Xm261Vu8XMQmf4ss0SzNtvaJToIjDDbYl6r64erswFuK T+7kyEOSY5xR9R89JkI2oUNUzLY/fDhKXNcUtj/vZvf/PBgjEHOFCxo1cTqDSBwm9CYI eicFI+ZJk+At/Gm+U9FzWb3anpa1DfM2vU0hc6gf1sPlH/znYFbzcFtwl6/ofNtrD104 w7NA==
X-Gm-Message-State: APjAAAVmml7bYMPt3LqAzkNM3/rkg+CFXd41oTJsUcbTFORN4dw3RVAh vedRVaV93Ub1yKUVdr33WdU=
X-Google-Smtp-Source: APXvYqwr+Fhuv2o+nTDhjJzgfAdjeZ2JEip6Mh2xtLDfQqFrd7gY+IyEW1TnQ01ZMhTesnE6VfgP1A==
X-Received: by 2002:adf:f803:: with SMTP id s3mr33472936wrp.7.1575045328918; Fri, 29 Nov 2019 08:35:28 -0800 (PST)
Received: from ?IPv6:2601:647:5a00:ef0b:289f:98c9:af3:443d? ([2601:647:5a00:ef0b:289f:98c9:af3:443d]) by smtp.gmail.com with ESMTPSA id d67sm13766547wmd.13.2019.11.29.08.35.26 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 29 Nov 2019 08:35:28 -0800 (PST)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <95AE48FA-BBBA-40DC-939E-D81B41B73E22@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_205A6B93-4FF4-4CCB-A1BA-F23325EDAF28"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: [art] New RFCs text formatting
Date: Fri, 29 Nov 2019 08:35:22 -0800
In-Reply-To: <136271A4-28AD-4615-AD7E-EB63B95C05C3@tzi.org>
Cc: Bob Hinden <bob.hinden@gmail.com>, John C Klensin <john-ietf@jck.com>, art@ietf.org, RFC Editor <rfc-editor@rfc-editor.org>, Steffen Nurpmeso <steffen@sdaoden.eu>, IETF <ietf@ietf.org>
To: Carsten Bormann <cabo@tzi.org>
References: <20191127233129.9829F%steffen@sdaoden.eu> <db882e3c-d3fb-4742-8456-7b400225ecce@www.fastmail.com> <20191128005000.yMa3P%steffen@sdaoden.eu> <08EE9B7B7C15D8F8B5DE6AF5@PSB> <136271A4-28AD-4615-AD7E-EB63B95C05C3@tzi.org>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Symxpb2fvx6Jd6ujI5rDtjRhS0E>
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: Fri, 29 Nov 2019 16:35:33 -0000

Carsten,

> On Nov 28, 2019, at 8:59 AM, Carsten Bormann <cabo@tzi.org> wrote:
> 
> On Nov 28, 2019, at 17:33, John C Klensin <john-ietf@jck.com> wrote:
>> 
>> So, even if it is too late to reconsider these decisions, I hope
>> we can at least be aware of possible negative side effects.
> 
> It is never too late to fix this bug.
> 
> I think the last few months have uncovered a lot of usages for the plain text form of RFCs, as well as the fact that “nobody will ever look at the plain text now that we have HTML” is maybe true for 80 %, but not for 100 %.

I think that is about right, I use both html and txt.  Html for reading on the screen, txt for doing comments and markups, excerpts in email, etc.

I have one active document that I converted to V3.   I note that the txt output of XML2RFC produces headers, footers, and page breaks.

The other thing I have noticed, since I now have the latest draft produced by V3 and the previous drafts produced by V2, is that several things changed that make this transition more difficult than needed.

The first I have found was when doing the conversion from V2 to V3, the default was to expand references, instead of the one line version.   This can be worked around when using the

--add-xinclude

when doing the conversion.

The other was default symbols in lists.   These can be worked around by using the --legacy-list-symbols when running XML2RFC.

My point is that in both cases I think the defaults should have been to make it closer to V2.  The current defaults make it harder to deal with converting an existing in progress draft from V2 to V3.  I suspect these are issues that many will run into when starting to use V3.

Thanks,
Bob

v2.23.0 | Report a Bug | By Email