IETF Logo Mail Archive

Re: [Idna-update] emoji and security

"Patrik Fältström " <paf@frobbit.se> Wed, 14 March 2018 11:04 UTC

Return-Path: <paf@frobbit.se>
X-Original-To: idna-update@ietfa.amsl.com
Delivered-To: idna-update@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FE49129C51 for <idna-update@ietfa.amsl.com>; Wed, 14 Mar 2018 04:04:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.711
X-Spam-Level:
X-Spam-Status: No, score=-0.711 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 VaNajsyNLXX4 for <idna-update@ietfa.amsl.com>; Wed, 14 Mar 2018 04:04:40 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [85.30.129.185]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3868212711E for <idna-update@ietf.org>; Wed, 14 Mar 2018 04:04:39 -0700 (PDT)
Received: from [172.20.5.159] (unknown [67.203.214.34]) by mail.frobbit.se (Postfix) with ESMTPSA id 57FE826BCB; Wed, 14 Mar 2018 12:04:35 +0100 (CET)
From: "Patrik =?utf-8?b?RsOkbHRzdHLDtm0=?=" <paf@frobbit.se>
To: "Asmus Freytag" <asmusf@ix.netcom.com>
Cc: idna-update@ietf.org
Date: Wed, 14 Mar 2018 07:04:33 -0400
X-Mailer: MailMate (2.0BETAr6106)
Message-ID: <34EF799D-892E-48C5-93AE-AE71A8821F56@frobbit.se>
In-Reply-To: <ac2e51de-a9ad-c8ee-96b0-5b50a0e225c4@ix.netcom.com>
References: <533bb471-da9b-64d0-76aa-a8a1251d256b@ix.netcom.com> <DM5PR1901MB219712F39A6297F9A147312DA2D30@DM5PR1901MB2197.namprd19.prod.outlook.com> <20180313202505.ztersmy2z5xuxlvp@mx4.yitter.info> <DM5PR1901MB2197A704B3233E5236EB703AA2D20@DM5PR1901MB2197.namprd19.prod.outlook.com> <ac2e51de-a9ad-c8ee-96b0-5b50a0e225c4@ix.netcom.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_MailMate_656B1DE2-4839-45C2-9C9B-78959649305B_="; micalg=pgp-sha1; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idna-update/X4Vf-0rXRZtl0maMfLz_mznZvYU>
Subject: Re: [Idna-update] emoji and security
X-BeenThere: idna-update@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Internationalized Domain Names in Applications \(IDNA\) implementation and update discussions" <idna-update.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idna-update>, <mailto:idna-update-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idna-update/>
List-Post: <mailto:idna-update@ietf.org>
List-Help: <mailto:idna-update-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idna-update>, <mailto:idna-update-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Mar 2018 11:04:46 -0000

On 13 Mar 2018, at 20:09, Asmus Freytag wrote:

> The design of IDNA2008 reflects two or three conflicting thrusts:
>
> 1) it was intended to be updatable to newer versions by simply applying the properties, with using an exception list as a fail-safe.

Not really. The normative rules in the IDNA2008 standard where to be applied to the Unicode Versions so that derived property values where calculated, and this independent of the Unicode Version. There are no properties that are applied.

> 2) it was intended to avoid clear-cut cases of dual encoding (via normalization)
> 3) it was intended to be usable on all levels of the tree - therefore it could not be maximally restrictive

   Patrik

v2.8.7 | Report a Bug | By Email