Re: [regext] Internationalized Email Addresses and EPP

Mario Loffredo <> Tue, 20 October 2020 09:25 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 18B923A0EF4 for <>; Tue, 20 Oct 2020 02:25:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.146
X-Spam-Status: No, score=-2.146 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.247, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id UoSC_U83xGud for <>; Tue, 20 Oct 2020 02:25:52 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 4FEAB3A0EF2 for <>; Tue, 20 Oct 2020 02:25:51 -0700 (PDT)
Received: from localhost (localhost []) by (Postfix) with ESMTP id 5AB6EC02D2; Tue, 20 Oct 2020 11:25:50 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id j1ldN0Eexqu7; Tue, 20 Oct 2020 11:25:47 +0200 (CEST)
Received: from [] ( []) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPSA id 8895FC03DB; Tue, 20 Oct 2020 11:25:47 +0200 (CEST)
To: John Levine <>,
References: <20201019182855.978EB23AA539@ary.qy>
From: Mario Loffredo <>
Message-ID: <>
Date: Tue, 20 Oct 2020 11:22:24 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.12.1
MIME-Version: 1.0
In-Reply-To: <20201019182855.978EB23AA539@ary.qy>
Content-Type: text/plain; charset="iso-8859-15"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: it
Archived-At: <>
Subject: Re: [regext] Internationalized Email Addresses and EPP
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Registration Protocols Extensions <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 20 Oct 2020 09:25:54 -0000

Many things are usually allowed by the EPP Schemas but refused according 
to server policies so it seems to me that this case is similar to many 
others. For example, are registrars aware of the TLDs implementing 
DNSSEC or do they simply rely on finding the DNSSEC namespace in EPP 

Besides, I agree with Dimitry that dealing with an ad-hoc EPP extension 
would be more complex than just allowing the EAI email addresses. In 
fact, clients/servers should send/receive an email address in the 
related EPP element.



Il 19/10/2020 20:28, John Levine ha scritto:
> In article <> you write:
>> The registry can support the receipt of UTF-8 addresses based on the EPP RFCs, but full support comes down to the validation of the
>> email addresses, how the email addresses are stored, and what the email addresses are used for.  I would expect an EPP error (2004
>> "Parameter value range error" or 2306 "Parameter value policy error") if an internationalized email address is received when the
>> registry does not support it.
> That makes sense, but it also seems needlessly cruel. I expect
> registrars would build ad-hoc lists of who handles EAI and who
> doesn't, to provide better reports to their users, which would
> then inevitably get out of date.
> If we do this it really would be nice if there were a signal for who
> handles EAI and who doesn't.
> _______________________________________________
> regext mailing list

Dr. Mario Loffredo
Systems and Technological Development Unit
Institute of Informatics and Telematics (IIT)
National Research Council (CNR)
via G. Moruzzi 1, I-56124 PISA, Italy
Phone: +39.0503153497
Mobile: +39.3462122240