Re: [Last-Call] New Version Notification for draft-crocker-inreply-react-07.txt

Patrik Fältström <paf@frobbit.se> Thu, 25 February 2021 15:58 UTC

Return-Path: <paf@frobbit.se>
X-Original-To: last-call@ietfa.amsl.com
Delivered-To: last-call@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A67683A1B93 for <last-call@ietfa.amsl.com>; Thu, 25 Feb 2021 07:58:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=frobbit.se
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 LJyhjvro6nYA for <last-call@ietfa.amsl.com>; Thu, 25 Feb 2021 07:58:01 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE1C53A1B8F for <last-call@ietf.org>; Thu, 25 Feb 2021 07:58:01 -0800 (PST)
Received: from [172.18.243.123] (w193-11-200-250.eduroam.sunet.se [193.11.200.250]) by mail.frobbit.se (Postfix) with ESMTPSA id 1D32F2A1C6 for <last-call@ietf.org>; Thu, 25 Feb 2021 16:57:59 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=frobbit.se; s=mail; t=1614268679; bh=+Y2no8t6EDE4iuR4vsrBBnwS2eASr1d4NNDaJCvnNkY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=mlYdRzE6yMbLQi8ZrGRQITCjH+IQU5illtd9RHUr1jhTp7LqRx6VXhluczSsD102V +lbD0WTjW8MsbY+QZinWONcU3/f1PLDx0jjwJr8QX0243OOlQ4gcLVgUjTPpVP7k6a woQtjW+Pth9Z4s/U+OSW91oX8YPiSc92LBmG3VJs=
From: Patrik Fältström <paf@frobbit.se>
To: last-call@ietf.org
Date: Thu, 25 Feb 2021 16:57:58 +0100
X-Mailer: MailMate (1.14r5757)
Message-ID: <731E05DA-E528-4892-B062-F6A1D673D597@frobbit.se>
In-Reply-To: <400c0e6f-ee6f-d5a4-ad8d-2fdd739693a3@bbiw.net>
References: <161101034209.26517.6109459219578848244@ietfa.amsl.com> <400c0e6f-ee6f-d5a4-ad8d-2fdd739693a3@bbiw.net>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_MailMate_33B91687-A498-42DC-A100-5EB8511CBD43_="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/2w1RvgctKeQyZfpEM7tQyrvn9Yo>
Subject: Re: [Last-Call] New Version Notification for draft-crocker-inreply-react-07.txt
X-BeenThere: last-call@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Last Calls <last-call.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/last-call>, <mailto:last-call-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/last-call/>
List-Post: <mailto:last-call@ietf.org>
List-Help: <mailto:last-call-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/last-call>, <mailto:last-call-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Feb 2021 15:58:04 -0000

I am asked to repeat comments I have made on this document on the last-call list.

1. Personal comment: Cultural or technical experiment

The document must make it clear whether it is an experiment in technical solution to send simple well formed messages OR if it is a cultural experiment whether people do agree all over the planet what "thumbs up" means.

We already know that differences in culture and norm do vary over the planet, specifically when body parts are involved.

I would personally because of this rather see a signalling mechanism of "agree" or "disagree" or whatever, and then a mapping from these signals to emojis or otherwise indications that can be displayed in the email client or similar.

But, if the document will be about "sending emojis" it must be very very clear that IETF do understand that the meaning of emojis is definitely not the same in different cultures and the conclusion from sending an emoji might surprise people. A lot. Not worse than on social media, but we all know how bad that is.

2. As liaison from IETF to Unicode Consortium

I see the document do specify emoji sequences to make it possible to send such things.

emoji = emoji_sequence
emoji_sequence = { defined in [Emoji-Seq] }

I am strongly objecting to allow any emoji sequences without having a very well defined rule what what they are. This description above is in an EBNF and the spec references is definitely not that clear.

We also do know (see for example SAC-095) how problematic sequences of emoji are and we have definitely not a stable definition of emoji sequences yet.

I.e. I object to allow emoji sequences in this document unless it can be proven the definition is to the same level of clarity as an ABNF (i.e. copied an really included in this specification, just like the "base emoji"). While at the same time saying the field itself is not only one Unicode Code Point but can be more than one.



To summarise, let me say explicitly I do like the document, that it should be published, but, the dangers and dragons within it are still pretty large. Very large. And they have teeth.

   Patrik