Re: Can we back up a bit and ask some basic questions? Analternate model

On Saturday 15 February 2003 16:40, Roy Badami wrote:
<snip>
> But I'd urge you to consider the four scenarios I just put forward in
> the thread "What is IMAA: some scenarios for deployment"

I'd like to extend this to include IMAA-ACE-opaque, IMAA-ACE-split and 
IMAA-UTF8:

> Scenario 1a:
(ISP IMAA-unaware, user want to use IMAs with her local MUA):
> with IMAA there's a reasonable hope of basic support
> with just an updated mail client, and better support with minor
> updates to the ISPs sign-up systems.  With UTF8ADDRESSES this will
> require in addition a major upgrade to the ISP's mail infrastructure.

IMAA-ACE-* are no different here.

> Scenario 1b:
(1a with webmail)
> IMAA and UTF8ADDRESSES both require a major upgrade to
> the ISP's infrastructure.

IMAA-ACE-* yes, IMAA-UTF8 probably not. It might suffice to add or 
change to
<meta http-equiv="content-type" content="text/html; charset=utf-8">
in the delivered html page.

> Scenario 2a:
(IMAA-unaware ISP and company mail server, IMA/IDN use)
> IMAA requires only an upgrade to the mail clients;
> UTF8ADDRESSES requires an upgrade to the clients, the organization's
> MTA, and the ISP's mail infrastructure (so that the backup MX will
> continue to work).

No change here, too.

> Scenario 2b: IMAA requires upgrades to the mail clients and, as
> currently specified in the draft, an upgrade to the organization's
> MTA (though the need to upgrade the MTA might disappear depending on
> the design decisions we take in IMAA).  UTF8ADDRESSES requires
> upgrades to the clients, the MTA and the ISP's infrastructure.
<snip>

IMAA-ACE-opaque requires that.
IMAA-ACE-split requires no modification on the server side, just like 
2a.

Marc

-- 
'When you see the ping of death, duck and cover.'
                        -- Bruce Schneier, Crypto-Gram Oct 2002