Re: [EAI] POP/IMAP authentication?

Alexey Melnikov <alexey.melnikov@isode.com> Sat, 04 July 2009 22:02 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ima@core3.amsl.com
Delivered-To: ima@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 057E63A67F2 for <ima@core3.amsl.com>; Sat, 4 Jul 2009 15:02:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.835
X-Spam-Level:
X-Spam-Status: No, score=-1.835 tagged_above=-999 required=5 tests=[AWL=-0.632, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kX7gpq5WW52f for <ima@core3.amsl.com>; Sat, 4 Jul 2009 15:02:58 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id B9F2B3A68DD for <ima@ietf.org>; Sat, 4 Jul 2009 15:02:57 -0700 (PDT)
Received: from [92.40.11.137] (92.40.11.137.sub.mbb.three.co.uk [92.40.11.137]) by rufus.isode.com (submission channel) via TCP with ESMTPA id <Sk=RnABV9Bc-@rufus.isode.com>; Sat, 4 Jul 2009 23:03:11 +0100
Message-ID: <4A4FD198.9010709@isode.com>
Date: Sat, 04 Jul 2009 23:03:04 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.21) Gecko/20090303 SeaMonkey/1.1.15
To: Shawn Steele <Shawn.Steele@microsoft.com>
References: <CAD7705D4A93814F97D3EF00790AF0B315F536BD@tk5ex14mbxc105.redmond.corp.microsoft.com>
In-Reply-To: <CAD7705D4A93814F97D3EF00790AF0B315F536BD@tk5ex14mbxc105.redmond.corp.microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-transfer-encoding: quoted-printable
Cc: "ima@ietf.org" <ima@ietf.org>
Subject: Re: [EAI] POP/IMAP authentication?
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Jul 2009 22:02:59 -0000

Hi Shawn,

Shawn Steele wrote:
>
> I’m leaving my comfort area J
>
>  
>
> Replying to Yao Jiankang’s draft, it occurred to me that the 
> alt-address probably needs to be allowed on authentication for email 
> accounts during the “transition period”.  So if I have a Unicode 
> address for my EAI mailbox, I may need to use the alt-address to logon 
> from my non-EAI-aware IMAP/POP client (might take a while to update my 
> phone).  I didn’t see that discussed in a quick peek at the IMAP/POP 
> drafts.
>
Authentication identities used by IMAP/POP servers don't have to look 
like email addresses at all (whether they are ASCII only or EAI email 
addresses).
In practice they frequently are, but this is an implementation detail. 
For example IMAP doesn't prevent use of LDAP DNs as authentication 
identities.


RFC 5255, section 5.1 talks a bit about UTF-8 authentication identities 
(userids). I suppose EAI IMAP document needs to say that it is updating 
RFC 5255.