Re: [rfc-i] What do do about SVG

Martin Thomson <mt@lowentropy.net> Wed, 16 December 2020 07:15 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA0C93A106F; Tue, 15 Dec 2020 23:15:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level:
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=lowentropy.net header.b=fV6Jihe4; dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=messagingengine.com header.b=dkV5XwND
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 FDVPJTbTZ-0b; Tue, 15 Dec 2020 23:15:51 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 867583A105F; Tue, 15 Dec 2020 23:15:51 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id F1A3AF40759; Tue, 15 Dec 2020 23:15:44 -0800 (PST)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 7A7B9F40759 for <rfc-interest@rfc-editor.org>; Tue, 15 Dec 2020 23:15:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lowentropy.net header.b=fV6Jihe4; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=dkV5XwND
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R64lI4kf1-gF for <rfc-interest@rfc-editor.org>; Tue, 15 Dec 2020 23:15:42 -0800 (PST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by rfc-editor.org (Postfix) with ESMTPS id 4D4EAF40757 for <rfc-interest@rfc-editor.org>; Tue, 15 Dec 2020 23:15:42 -0800 (PST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 027335C0110 for <rfc-interest@rfc-editor.org>; Wed, 16 Dec 2020 02:15:47 -0500 (EST)
Received: from imap10 ([10.202.2.60]) by compute1.internal (MEProxy); Wed, 16 Dec 2020 02:15:47 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm1; bh=VuVabccRdZS2uXxMMsINPmjSkms0gz9 ORgMM1zGSiSM=; b=fV6Jihe46LO5dlpKcelD4bW3C7SNVJ+O6Sz0Zqc1dHt8hct OlJvJ/ujeHBwCwPj0zGsmM0jPG1UXYWPN0o8M/2I9FBekMvXjDWuFguvwhRLhgDH byZ6FwwMEGwadPKQsL4s9UEuBo3OF8FABb3EKt7sppuC1uEAoMPIbe8ge37Pa1uD HffuvBzydleHTaR5UCA2U3q/apllsSc56SgcseAbh81Gn187ky2jSRn9YQd+tWM1 kTDYjMgm/C1z1Tn0uahtL6ciSNJPqzkcn+L7kCHmMHG/j7lol9FGSivsjgln2EGA FNKZ92lXKK3gtDmuzSvHc3tAnki9gCVUh74qC0Q==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=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=VuVabc cRdZS2uXxMMsINPmjSkms0gz9ORgMM1zGSiSM=; b=dkV5XwNDauU5dUBWy121R0 EH6sS4Fbyelkl7cM+64lLlzGx0unw2QhdJq55YjW7VUxHfrJRkGeuuTwhQS997/h 7wkLHF6iYqouGxjkmpNwO37M9aTwjjo/3ELPz1JQGJ6JOegIyRrGTNpbScTSuD0S 0v83VT6wDvkA1+5rYSNKJbduY74Fa73193gvZU0Rp489pILptho9Pe3R/IlDHcEz Xc+NG3oNgmxc1HyDmxeOjtbbQOlcLHkfnmywhO3mz/x50XOsXEcYBi4OvwcfVU4C XhxRk+QQWWrVDvGdAeUMUSE69/gdPwfq4xZO9AzsLrPvcwlIoVyeu+vf7LlZdbKg ==
X-ME-Sender: <xms:IbTZX-u69DYSkU5xBSAfhmpXex8NllY_f9St6dCVURmrgZa4AMh--g> <xme:IbTZXzfUvKgVo1hcW1hfMx5nuG78Da0TZm5XgzEnRjLzYQY237oeGtyIvnwMKqn2w TPzpyEGNkCtH90QYLQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrudeluddguddtgecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesth dtredtreertdenucfhrhhomhepfdforghrthhinhcuvfhhohhmshhonhdfuceomhhtsehl ohifvghnthhrohhphidrnhgvtheqnecuggftrfgrthhtvghrnhepkeetueeikedtkeelfe ekvefhkeffvedvvefgkefgleeugfdvjeejgeffieegtdejnecuvehluhhsthgvrhfuihii vgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhhtsehlohifvghnthhrohhphidrnh gvth
X-ME-Proxy: <xmx:IbTZX5wdJMvrD3FuRklHWvFhvhCak5duGMMQ2gyn-aez4aX06PLJvw> <xmx:IbTZX5Mvrsmjo9ZmAsj3q3hxPldwdlpl4NqdfBp4DTPwZAK1UC9WWg> <xmx:IbTZX-8XsO9f7SM2qDDY1h5MKBGWLuOwSCyzXDZOB0ASTBVpkWkkLg> <xmx:IrTZXxJ465q8SL3U9ZPVAQjjup-5jIBlZLn5HVqglJLJHk8nm_pKqQ>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id AEAA720063; Wed, 16 Dec 2020 02:15:45 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.3.1-61-gb52c239-fm-20201210.001-gb52c2396
Mime-Version: 1.0
Message-Id: <626b2ec4-be70-4028-9047-62fa9ca4bafb@www.fastmail.com>
In-Reply-To: <dca14b37-525a-ac60-20c2-8c8cbfb2830d@nostrum.com>
References: <f564019-d8b1-76c2-2768-c135d834dc32@iecc.com> <763b8195-6139-fb20-aa4e-2b4d89b5681c@gmail.com> <7b8ef1d3-f33b-fc1b-88d3-c399c7cb6279@alum.mit.edu> <0d979304-d3d6-3b8b-acab-7cbc37276250@joelhalpern.com> <916267c9-bf4c-7c0c-eb99-a24e73fc22df@gmail.com> <dca14b37-525a-ac60-20c2-8c8cbfb2830d@nostrum.com>
Date: Wed, 16 Dec 2020 18:15:26 +1100
From: Martin Thomson <mt@lowentropy.net>
To: rfc-interest@rfc-editor.org
Subject: Re: [rfc-i] What do do about SVG
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

On Wed, Dec 16, 2020, at 15:53, Adam Roach wrote:
> Perhaps rather than using syntax to enforce policy, we could shift to 
> using editorial control to enforce policy. That is, we specify that 
> non-ASCII diagrams in RFCs are in full-fledged SVG, which has really, 
> *really* good support in a lot of tools. And then put have in place 
> instructions to the authors and to the RPC that describe the policy 
> restrictions (such as those I list above), along with a tool -- in the 
> style of id-nits -- that helps identify (in an advisory way) when those 
> policies might not have been followed.

I think that is entirely sensible.

I will note that your requirements permit the inclusion of raster images as data: URIs.  Those might be hard to detect without tools.  We'll likely need a little back and forth on what the true requirements are.
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest