Re: [I18ndir] HTML, email addresses, etc

John Levine <johnl@taugh.com> Mon, 08 June 2020 14:54 UTC

Return-Path: <johnl@iecc.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 D8C2D3A086C for <i18ndir@ietfa.amsl.com>; Mon, 8 Jun 2020 07:54:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.851
X-Spam-Level:
X-Spam-Status: No, score=-1.851 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, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=VIEiXL1W; dkim=pass (1536-bit key) header.d=taugh.com header.b=BrbXnqJ8
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 R3WQeM_WodMm for <i18ndir@ietfa.amsl.com>; Mon, 8 Jun 2020 07:54:55 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB9923A0B6C for <i18ndir@ietf.org>; Mon, 8 Jun 2020 07:54:54 -0700 (PDT)
Received: (qmail 89703 invoked from network); 8 Jun 2020 14:54:53 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=15e62.5ede513d.k2006; bh=qfA+dn/4P0ZlLRYjeH9f7xDeqT9Aza4jYPhCl/1TW2A=; b=VIEiXL1WxyOnYIlrqqEPCwsAhaKT3bA1M6YN00h71IzYoC+eOpCknIrxor9m7BGKDhFkUzKf1atAZwCrfA4t6lBq9ceT9cVBlnEGvJppom5smFOSc8LmKC8CRcq99O+XLjYN/AscxKKDDZ5SFPZtfpaCr3PzUqx2cbvtgHxIIkEsUVKTMagNeuGutFgN2hIya5bQfxF9OjQEGfAMrMRBdNf7zTizz0OtO/ktuVI5fKJ0Dubbu7kFQBx2+vO0O+4c
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=15e62.5ede513d.k2006; bh=qfA+dn/4P0ZlLRYjeH9f7xDeqT9Aza4jYPhCl/1TW2A=; b=BrbXnqJ8sFY1Fm8Uny+76wDJv/4m/xqrq8pKKc6nBPF2bzEYhPUbdSyo7OFypIoCCDAa3BKR0skCwLDu+7Oc7CxevhmmLJfkwR2l+GNm8cKtEbxPOT4qIDV5W4nXJ6i2slISKBAu9eF6XbaBpyV3t1LTdbmjaDywGA/eND8lUn65Zblnb38i5aOxxYOv3k8GeT5XNV/BS8o70bu7xSxNdn9+SltineTS3VsansJ/zN2mpn62GrBOZ1Uq7pVF8XPq
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 08 Jun 2020 14:54:53 -0000
Received: by ary.qy (Postfix, from userid 501) id EB3E51A4BADD; Mon, 8 Jun 2020 10:54:52 -0400 (EDT)
Date: Mon, 08 Jun 2020 10:54:52 -0400
Message-Id: <20200608145452.EB3E51A4BADD@ary.qy>
From: John Levine <johnl@taugh.com>
To: i18ndir@ietf.org
Cc: marc.blanchet@viagenie.ca
In-Reply-To: <C6967F02-35D9-484B-9BF8-7436D1DF3B65@viagenie.ca>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18ndir/39hvy_dtglrkwUjWVTvkxheJj6U>
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: Mon, 08 Jun 2020 14:54:57 -0000

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.