IETF Logo Mail Archive

Re: [I18ndir] HTML, email addresses, etc

John C Klensin <john-ietf@jck.com> Tue, 09 June 2020 13:26 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: i18ndir@ietfa.amsl.com
Delivered-To: i18ndir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C842E3A0921 for <i18ndir@ietfa.amsl.com>; Tue, 9 Jun 2020 06:26:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] 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 7MCDfg07EF1B for <i18ndir@ietfa.amsl.com>; Tue, 9 Jun 2020 06:25:59 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0D693A0919 for <i18ndir@ietf.org>; Tue, 9 Jun 2020 06:25:59 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1jieGI-0008LJ-MW; Tue, 09 Jun 2020 09:25:54 -0400
Date: Tue, 09 Jun 2020 09:25:47 -0400
From: John C Klensin <john-ietf@jck.com>
To: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>, John Levine <johnl@taugh.com>, i18ndir@ietf.org
cc: marc.blanchet@viagenie.ca
Message-ID: <81773E93681984B8836B1915@PSB>
In-Reply-To: <7bf0652a-01a9-79e9-6325-75ea5fa20fca@it.aoyama.ac.jp>
References: <20200608145452.EB3E51A4BADD@ary.qy> <7bf0652a-01a9-79e9-6325-75ea5fa20fca@it.aoyama.ac.jp>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18ndir/m4lMLIq1btbuWI1peap46UoNtDw>
Subject: Re: [I18ndir] HTML, email addresses, etc
X-BeenThere: i18ndir@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Internationalization Directorate <i18ndir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i18ndir>, <mailto:i18ndir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i18ndir/>
List-Post: <mailto:i18ndir@ietf.org>
List-Help: <mailto:i18ndir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i18ndir>, <mailto:i18ndir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jun 2020 13:26:02 -0000


--On Tuesday, June 9, 2020 17:57 +0900 "Martin J. Dürst"
<duerst@it.aoyama.ac.jp> wrote:

> On 08/06/2020 23:54, John Levine wrote:
>> In article <C6967F02-35D9-484B-9BF8-7436D1DF3B65@viagenie.ca>
>> you write:
>>> this is what I was going to say. IMHO, any protocol
>>> identifier (such as EAI) using something more than ASCII
>>> must define a PRECIS profile. This is the only chance to get
>>> it working. Plain UTF8 for an identifier is just plain wrong.
>> 
>> That is true but I'm wondering how many profiles we need. As
>> jck pointed out elsewhere, an address with a Tamil mailbox
>> and a Chinese domain name is unlikely to work.
> 
> Yes, but an address with a Tamil mailbox and a Devanagari
> domain name might indeed work. Similarly for an address with a
> Mongolian mailbox and a Chinese domain name.

Absolutely.   And those are good examples of why a simplistic
rule banning mixed scripts would not be helpful.

    john

v2.23.0 | Report a Bug | By Email