Re: [I18nrp] Mappings for IDNA2008 ?

"Asmus Freytag (c)" <> Tue, 05 February 2019 01:13 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7E1DA130DDA for <>; Mon, 4 Feb 2019 17:13:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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: (amavisd-new); dkim=pass (2048-bit key); domainkeys=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id IYJL-bBQY4Mp for <>; Mon, 4 Feb 2019 17:13:24 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B68AB130DD3 for <>; Mon, 4 Feb 2019 17:13:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=dk12062016; t=1549329204; bh=Rb/BYbz7r1GMAQ7ktMKVZMJUdcth2G5NSDWs 2OE7OCg=; h=Received:Subject:To:Cc:References:From:Message-ID:Date: User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Language: X-ELNK-Trace:X-Originating-IP; b=n6MTBNpJM5Mepom5XxD4qQfiDUtqE1TPS WxpSrRLDjGw0qXHqeucJNKbt3WzLSzd007av0MXDz7YKGK5zI0NecIdrCSGQWY0s9jy UEU6PB1lftcFa0J71h7TrxQnYHklOkGz5TioLlzVvapGNlMtAsK9RQxDZJg137tf5Pf C4YoP8//arVnZLp9IZI24AxcJy0DBcWbnNvFUpOlLU8L1i5h0GdB1siClpHbrXKKwuc QtCNktGvPVci9bHjQszPDdwHJ0ePzG98VzhzNPFmIFPqo0FGPl7sdxAviMd45GzOf5L 4p/s8xWFtDaLCVKse4xpwaE3iYiIcrWI+/8gr80+A==
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk12062016;; b=SawQZFLIJpj3cewTQnWdI7qDRCCHvGfBaRi2KUOrinveLMTVukjrwVV+Sd94hy+TB493wmZay+dlTttWVxmk6BstyIbPJZeRdafU6QqoCM7Mvsuwah/9uRfEpqsTw+E1/zxmjChqfLyxP4dcDmN1h7vih23Nv8yxJ4SkCesb8VfMgmLW6gOGxL4FtzM+Qv5Qehz2GcRa59TZrKB95rWgvtykzEnG2TkMxe+LZKuKqbvi6XV/LSb3XZVGD0yOhZ4R8aOwckeeVpmOdSNY504X/qjzY+i8kBSukn5eLghK2gzDnpWm1K9RMQYeFV/CXD4IPonlxdn8PSqjxJ5xm+Qz7g==; h=Received:Subject:To:Cc:References:From:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Language:X-ELNK-Trace:X-Originating-IP;
Received: from [] (helo=[]) by with esmtpa (Exim 4) (envelope-from <>) id 1gqpIg-000BFc-RO; Mon, 04 Feb 2019 20:13:23 -0500
To: John R Levine <>
References: <20190205002555.1AFBA200DC1DB1@ary.qy> <> <alpine.OSX.2.21.1902041956400.33017@ary.qy>
From: "Asmus Freytag (c)" <>
Message-ID: <>
Date: Mon, 4 Feb 2019 17:13:23 -0800
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <alpine.OSX.2.21.1902041956400.33017@ary.qy>
Content-Type: multipart/alternative; boundary="------------995F4FAA4CF83CCA343078A1"
Content-Language: en-US
X-ELNK-Trace: 464f085de979d7246f36dc87813833b28d93432b0f0788b9bfc1afda922012df426b661983c96396350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
Archived-At: <>
Subject: Re: [I18nrp] Mappings for IDNA2008 ?
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Internationalization Review Procedures <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 05 Feb 2019 01:13:27 -0000

On 2/4/2019 4:58 PM, John R Levine wrote:
>>>  If you speak Persian, the joiners are wrong.
>> The Root Zone will be like IDNA2003 here, disallowing the joiners. 
>> Yes, stuff looks "wrong" without in some languages - worse for 
>> Sinhala (used in Sri Lanka) than for Persian, by the way.
>> This one is a no-win situation. Some zones may support these, others 
>> won't - what is a generic mapping to do?
> Well, you know, the whole point of this inquiry is to find mappings 
> that are NOT generic.  If you know what language your user speaks, why 
> not give her a mapping that makes sense for that language?  That's why 
> IDNA2008 doesn't have a generic mapping.
> Regards,
> John Levine,, Taughannock Networks, Trumansburg NY
> Please consider the environment before reading this e-mail.
Now you are going in circles.

Yes, give the user a tailored mapping, but nobody is served by everyone 
having to reinvent the wheel for the generic case.

So, some generic mapping (not built into the protocol, so it can, in 
fact be tailored) is clearly useful.

That people are too lazy / don' t know enough to tailor it, is  not the 
fault of a generic mapping.