Re: [Idna-update] Question about ℀
Patrik Fältström <patrik@frobbit.se> Wed, 08 August 2018 05:31 UTC
Return-Path: <patrik@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 38BF9130DD9 for <idna-update@ietfa.amsl.com>; Tue, 7 Aug 2018 22:31:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable 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 ZNPlRhcrWfef for <idna-update@ietfa.amsl.com>; Tue, 7 Aug 2018 22:31:10 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E888F126CB6 for <idna-update@ietf.org>; Tue, 7 Aug 2018 22:31:09 -0700 (PDT)
Received: from [192.168.10.104] (c-40b2d954.028-114-73746f27.bbcust.telenor.se [84.217.178.64]) by mail.frobbit.se (Postfix) with ESMTPSA id C28D42146C; Wed, 8 Aug 2018 07:31:06 +0200 (CEST)
Content-Type: multipart/alternative; boundary="Apple-Mail-BE4E864F-2669-403F-84A8-07F8C1655027"
Mime-Version: 1.0 (1.0)
From: Patrik Fältström <patrik@frobbit.se>
X-Mailer: iPad Mail (15G77)
In-Reply-To: <MW2PR2101MB090887430446886A6D05D2FE82260@MW2PR2101MB0908.namprd21.prod.outlook.com>
Date: Wed, 08 Aug 2018 07:31:06 +0200
Cc: "idna-update@ietf.org" <idna-update@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <65767F4F-4F3C-4C3C-AB2A-3F38D2C6C4D6@frobbit.se>
References: <MW2PR2101MB090887430446886A6D05D2FE82260@MW2PR2101MB0908.namprd21.prod.outlook.com>
To: Shawn Steele <Shawn.Steele=40microsoft.com@dmarc.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idna-update/p81_hp-jovSuX0mb6xYTDzZpYtM>
Subject: Re: [Idna-update] Question about ℀
X-BeenThere: idna-update@ietf.org
X-Mailman-Version: 2.1.27
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, 08 Aug 2018 05:31:12 -0000
> On 8 Aug 2018, at 02:21, Shawn Steele <Shawn.Steele=40microsoft.com@dmarc.ietf.org> wrote: > > For characters like ℀, would it be permissible to disallow them in the mapping step? Currently the tables allow mapping ℀ to a/c, which is obviously not very great behavior since / is illegal in DNS. There are no tables talking about mapping since IDNA2003. IDNA2008 do allow mapping before IDNA2008 rules actually are applied, and what mappings you apply is context and application dependent. So I am confused about what you mean by “tables”. Further, if the code point you refer to is U+2100 its derived property value according to IDNA2008 is DISALLOWED. Patrik
- [Idna-update] Question about ℀ Shawn Steele
- Re: [Idna-update] Question about ℀ John C Klensin
- Re: [Idna-update] Question about ℀ Patrik Fältström
- Re: [Idna-update] Question about ℀ Shawn Steele