[UA-discuss] Review of UASG Charter

[Mark Svancarek]

MUA doesn't necessarily need to understand IDNA since that's being handled by MTA.  It just needs to handle UTF8 in general.

Also, keep in mind again that these are usually separate features prioritized and maintained by separate teams  - so specific end-to-end behavior that one might logically expect isn't always going to be reality.  Hence the need for UASG.

-----Original Message-----
From: Andrew Sullivan [mailto:ajs at anvilwalrusden.com] 
Sent: Thursday, February 18, 2016 3:08 PM
To: Mark Svancarek
Cc: ua-discuss at icann.org
Subject: Re: [UA-discuss] Review of UASG Charter

On Thu, Feb 18, 2016 at 09:38:04PM +0000, Mark Svancarek wrote:
> 
> The app doesn't catch the equivalence simply because it never had to 
> do so in the past

Well, wait: it _does_ have to now, because _ex hypothesi_ it's EAI-aware or at least IDNA-aware.  Otherwise, you'd never have been able to send the mail in the first place, I think.  No?

That is, the whole chain starts when someone sends a mail with

    ascii-local-part at name-with-U-label

If you get back an answer that cc:s

    ascii-local-part at name-with-A-label

your software already knows how to do IDNA, because it coped with the U-label in the first place.  No?

A

--
Andrew Sullivan
ajs at anvilwalrusden.com