IETF Logo Mail Archive

Re: [ietf-822] What about doing more? (was: Re: Fwd: New Version Notification for draft-crocker-inreply-react-01.txt)

John Levine <johnl@taugh.com> Mon, 12 October 2020 02:44 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: ietf-822@ietfa.amsl.com
Delivered-To: ietf-822@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56B3E3A08BB for <ietf-822@ietfa.amsl.com>; Sun, 11 Oct 2020 19:44:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.851
X-Spam-Level:
X-Spam-Status: No, score=-1.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=KdjWPaua; dkim=pass (2048-bit key) header.d=taugh.com header.b=OnfX6uUs
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 egyerkgfY4HW for <ietf-822@ietfa.amsl.com>; Sun, 11 Oct 2020 19:44:33 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 49DF13A08BA for <ietf-822@ietf.org>; Sun, 11 Oct 2020 19:44:33 -0700 (PDT)
Received: (qmail 1689 invoked from network); 12 Oct 2020 02:44:31 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=696.5f83c30f.k2010; bh=sKnrYWJ3zRIGlY41BVis9jYpYK6xdjkoArt1k9Dph74=; b=KdjWPauaF28NIuM5+txPKbUaWcExoNkvx8jlASqVMrgqmF04exue+AtYa/GigQwKgJSzVKGi3FhQAqtkCboUcImGr/R6O1V1n2OmTmkLv3yP0I4I3jgK05W/ZI3j1PBK7eCBg/j8HfoGZu5sjYUfe/5Q6FbUIpKzOzBSYo/rfX/SObUkNvTKWZ68jnQtCEhWXU7tNwtPmz9uZXcJpL5LzCljDDOcthulZHkx/reP8yfOWQf4FwpiN2cUph0zPI4IDD5T7ka0JQCfhnantB6dCPgeaE49cek4W1GgEiAgQ5YOoBsKTS8VLxNGPcQN6atDIzBE5tWWQ5Y9AdrsS5yBfg==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=696.5f83c30f.k2010; bh=sKnrYWJ3zRIGlY41BVis9jYpYK6xdjkoArt1k9Dph74=; b=OnfX6uUsKD4NqGYqU05v/khS1XDMpHhh5R9dxUGmM7f1IRsjTc48annQWbg8Enn/dJ4EIzU5s6kwKHpqfBuyhxcvImUL3y9FAy159qdwbM+nSkuBHs96DbI1Gmf8j0SrOZ16fBpS84XidmiA73+1KsvSM3x1MyByy/phMrFVB7QtE6MCxe5xwwHGv0lWKv316l48q1MSi5kFo1YM0IUMp3kfuuQcnErm7xX05fLdRVtwbmeL5yfsemYwUh3BpfXT+s7pU+rnx3VUsdd4XXgc7YXLDWGpqtqgfP+83BdxGDGpWIPVg2vh+Zp3TxGUFzGQgIPJ416UK+tmPT+5QYOaMw==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 12 Oct 2020 02:44:31 -0000
Received: by ary.qy (Postfix, from userid 501) id EBB4F23493C8; Sun, 11 Oct 2020 22:44:30 -0400 (EDT)
Date: Sun, 11 Oct 2020 22:44:30 -0400
Message-Id: <20201012024430.EBB4F23493C8@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf-822@ietf.org
Cc: rjbs@semiotic.systems
In-Reply-To: <106aecda-a406-4fc5-8d3d-66c3c364edaa@www.fastmail.com>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-822/LMLnMWNb09bg9mpwV3WfMvNRWEE>
Subject: Re: [ietf-822] What about doing more? (was: Re: Fwd: New Version Notification for draft-crocker-inreply-react-01.txt)
X-BeenThere: ietf-822@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of issues related to Internet Message Format \[RFC 822, RFC 2822, RFC 5322\]" <ietf-822.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-822>, <mailto:ietf-822-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-822/>
List-Post: <mailto:ietf-822@ietf.org>
List-Help: <mailto:ietf-822-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-822>, <mailto:ietf-822-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Oct 2020 02:44:35 -0000

In article <106aecda-a406-4fc5-8d3d-66c3c364edaa@www.fastmail.com> you write:
>The Unicode Emoji List is revised more or less annually.  This means that releasing software that validates this header against the
>contents of UTS #51 is liable to fall out of date.

The entire Unicode standard is revised more or less annually This year
Unicode 13 added over 5000 characters to Unicode 12. If you send a new
emoji or any of those other 5000 characters you run the risk that
someone with last year's software will see a little box. That's life.

>The problem here is that some implementors like to validate data at layers were its validity is (probably) irrelevant to its intended
>use.

"Don't do that".

If they haven't already figured out that it's a fool's errand to
validate Unicode beyond broad rules like don't allow surrogates in
UTF-8, they're not going to figure it out for this tiny hack.

v2.23.0 | Report a Bug | By Email