inline
From: UA-discuss [mailto:ua-discuss-bounces@icann.org]
On Behalf Of Ajay Data
Sent: Saturday, March 10, 2018 10:50 PM
To: ua-discuss@icann.org
Subject: [UA-discuss] Issue needs discussion and closure
|
This sender failed our fraud detection checks and may not be who they appear to be. Learn about spoofing |
Hello Friends,
In UASG workshop today, we had a detailed recap and discussion on UA + EAI issues. During discussion, we agreed the following points to be discussed further and need resolution…
If email server receives an email FROM xn--anything@validdomain , should email server at receiving end Do..
[Mark Svancarek] IF you host the mailbox and IF
xn—anything maps to a UTF8 mailbox that you already administer, and IF you have no mailboxes with
xn—anything as the local part: then you may transform. But this is not an officially recommended practice.
[Mark Svancarek] In all other cases, this is forbidden. The official guidance is don’t ever do it. UASG should not be accountable to spell out the very specific exception case I define above.
[Mark Svancarek] I don’t think there is any specific existing rule or even guidance on this example, for or against. I vote that UASG support this example.
[Mark Svancarek] We should recognize that the local part rules are very permissive and therefore this should be an ALLOWED case per the spec. But I vote that UASG declare it as a NOT RECOMMENDED case EXCEPT for
script combinations which are already allowed to be mixed in the root zone.
We already agreed that Downgrading of Alias is good practice and to be followed by email servers while communicating with legacy systems , however we have not discussed how Alias will be made
available on MUA and if there are many Alias, than which will be used for downgrading.
[Mark Svancarek] I don’t recall this topic, and I don’t understand the question – sorry! Please clarify.
Lets discuss.
Thanks.
Ajay.