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

Ricardo Signes <rjbs@semiotic.systems> Fri, 26 February 2021 02:50 UTC

Return-Path: <rjbs@semiotic.systems>
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 1E6153A166C for <last-call@ietfa.amsl.com>; Thu, 25 Feb 2021 18:50:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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=semiotic.systems header.b=hVPwRBiw; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=fQgLJapr
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 CH4cQtGEH7S0 for <last-call@ietfa.amsl.com>; Thu, 25 Feb 2021 18:50:33 -0800 (PST)
Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BCAF83A166B for <last-call@ietf.org>; Thu, 25 Feb 2021 18:50:33 -0800 (PST)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id 3834D180C for <last-call@ietf.org>; Thu, 25 Feb 2021 21:50:31 -0500 (EST)
Received: from imap35 ([10.202.2.85]) by compute5.internal (MEProxy); Thu, 25 Feb 2021 21:50:31 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= semiotic.systems; h=mime-version:message-id:in-reply-to :references:date:from:to:subject:content-type; s=fm3; bh=S6xL5OO DeSMfcVp3z8dvxYiwH19PZ0nc4AN3fP4Qg7w=; b=hVPwRBiwTHz8w3ziUu0s4SZ 3/TylWdSK4Pu07TAKJ4FeNHEYP/bz52Lb7EjGvKU/ipXmCRr1o3FQXnS2m70gqZn oDgmPbd9mwDIdaC64opdsIEPuQrHCLNxUeIgP+iCnOOFroPmcAivVOW6Xg7G1Ob4 IA7Wc1DyE2FEGULsIrlHwqXnmFT/oovLZefN/sW+YkNnKYwa0dgJqodi7EUrDeFr qoHPBg1sx/F0uvALgT2o56qyOFiCH22vGhsN23QtDZB8gon2Cm1K9og0KvfUzU/3 o0ZLPcfTzOh+w/q23Po4PWzSJbOv/FouBQXUoxW41lDPyKt0wMO3pzYWMHl9IVA= =
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=fm2; bh=S6xL5O ODeSMfcVp3z8dvxYiwH19PZ0nc4AN3fP4Qg7w=; b=fQgLJaprESGVPFtmz2+Ino LsU7o4g5Oykyb9EGqsCVGtoL+Mleg33syb+TG1n5yhllwSzltQDFtPTcY4ebUHeL kl975aM72G7zwJtRNeXQacJtn+2P+UHKmExyVk14WFbztUVUWJvS/eeIlRHAQpwF Twf9eeDquXkh6posmIq3RWFnStZzQWbBIUktmIIR9DBMKmxXE+3sMBOce5oRxX0P IgpKfGog//wZHB1JWLef2ZISSEzqX+AFMZShwZzWJeHcQatR9bLSvYM03ePj09cj 39SZLhf2Dzjt8PbBp136BWcMT8D3ZGoSCLE+u8PuTOSeBhINWuS0APPVmw3xLuWg ==
X-ME-Sender: <xms:9mE4YHWHtfz9pwqEd-1dGFPQjzqPeB7DtmAcPTA-h-6l7-KHm_M6Rg> <xme:9mE4YPnmz059wsP0yoO9BryakJAkM0_59-y2ius1sPeAey-C0Ksb82g4wh8xLN5eZ QF4vwfUAg5Ik2dFt5k>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrledtgdehvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesrgdtre erreerjeenucfhrhhomhepfdftihgtrghrughoucfuihhgnhgvshdfuceorhhjsghssehs vghmihhothhitgdrshihshhtvghmsheqnecuggftrfgrthhtvghrnhepueefhfdtffdtff elkeduleevleeivdeifeevieevffduveehkedtgfegffehvdfgnecuvehluhhsthgvrhfu ihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprhhjsghssehsvghmihhothhitg drshihshhtvghmsh
X-ME-Proxy: <xmx:9mE4YDZm9So-mwOt3mQ2wD1sD7mhA4LGQhyw8V9bVq585vUzhQZm_g> <xmx:9mE4YCV1_BbsWQGCB49ML9bWTNas8tLxtFVRRIjWZadrLBw6ponR3Q> <xmx:9mE4YBnjHOuAyePvLc2ykkaOkyo3d6KszrNNFX4SlC12ae7Xn6-MXw> <xmx:9mE4YNyLwR0auGiYgf15txSvzWL0mD02L0P1JTllv2pP4IQJhoYgdQ>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id F12F815A005D; Thu, 25 Feb 2021 21:50:29 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-141-gf094924a34-fm-20210210.001-gf094924a
Mime-Version: 1.0
Message-Id: <489d7342-a642-40e5-be21-584b49772d59@beta.fastmail.com>
In-Reply-To: <731E05DA-E528-4892-B062-F6A1D673D597@frobbit.se>
References: <161101034209.26517.6109459219578848244@ietfa.amsl.com> <400c0e6f-ee6f-d5a4-ad8d-2fdd739693a3@bbiw.net> <731E05DA-E528-4892-B062-F6A1D673D597@frobbit.se>
Date: Thu, 25 Feb 2021 21:50:08 -0500
From: Ricardo Signes <rjbs@semiotic.systems>
To: last-call@ietf.org
Content-Type: multipart/alternative; boundary="260cc62b501747af8d56f585385c14d6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/U38nJ3Y1ljEefVA521d1qzrRUdE>
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: Fri, 26 Feb 2021 02:50:35 -0000

On Thu, Feb 25, 2021, at 10:57 AM, Patrik Fältström wrote:
> 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.

It looks like objections have perhaps been rescinded now, but:  I don't understand the nature of this objection, if it stands.

This is not like the use of non-ASCII characters in domain names, because reactions are not used as resource locators.  If a visually confusable emoji is used to replace another, the reader is not misled into arriving at the wrong resource.

It's true that the definition of emoji sequence is not (yet?) entirely stable.  In the context of message content, I'm not sure what teeth the dragon is presenting here.  I agree that I would not want to use this reference to TR51 in specifying many kinds of things, but in this context, I don't see the problem.

-- 
rjbs