IETF Logo Mail Archive

Re: [Tools-discuss] UTF-8 box characters with wavy lines in XML2RFC v3 draft

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 06 November 2019 15:14 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2704F120CA6 for <tools-discuss@ietfa.amsl.com>; Wed, 6 Nov 2019 07:14:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 9i_dAOHdE3Xl for <tools-discuss@ietfa.amsl.com>; Wed, 6 Nov 2019 07:14:43 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 50C15120C99 for <tools-discuss@ietf.org>; Wed, 6 Nov 2019 07:14:39 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 37C943818F; Wed, 6 Nov 2019 10:11:43 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 7BCAE14; Wed, 6 Nov 2019 10:14:38 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Carsten Bormann <cabo@tzi.org>
cc: Adam Roach <adam@nostrum.com>, "Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org>, tools-discuss <tools-discuss@ietf.org>, Tom Pusateri <pusateri=40bangj.com@dmarc.ietf.org>
In-Reply-To: <E7785FD5-A9E1-4C20-9C2E-D6FCA2E9781E@tzi.org>
References: <31468A3A-FF68-4F58-BC89-54B277A423F1@bangj.com> <8F23347E-D33C-415E-8D0D-EC3AF2017268@nostrum.com> <32583250-B918-42DD-83D7-A770E6BDB71F@tzi.org> <E7785FD5-A9E1-4C20-9C2E-D6FCA2E9781E@tzi.org>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Wed, 06 Nov 2019 10:14:38 -0500
Message-ID: <16922.1573053278@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/pq7aeFznx8aJy0YLIDQhCx4pO-M>
Subject: Re: [Tools-discuss] UTF-8 box characters with wavy lines in XML2RFC v3 draft
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Nov 2019 15:14:45 -0000

Carsten Bormann <cabo@tzi.org> wrote:
    > I believe that, once the tools have stabilized, it will be easier to
    > stay within a reasonable repertoire.  Instead of standardizing this in
    > some rigid spec, it should be the RPC that guides the authors towards
    > “reasonable” (and the tools should help with this).

And, at the risk of invoking https://tools.ietf.org/html/draft-iab-protocol-maintenance-04
(which clearly nobody wants to apply to email), it would be nice if our tools
were capable of doing more than the subset that the RFC-editor wants to
publish, as there are some other entities that like our approach.
(I recall GRID being one of them)

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email