Re: [EAI] POP/IMAP authentication?

Barry Leiba <barryleiba.mailing.lists@gmail.com> Tue, 14 July 2009 15:19 UTC

Return-Path: <barryleiba.mailing.lists@gmail.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 A3FB83A6A81 for <ima@core3.amsl.com>; Tue, 14 Jul 2009 08:19:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, GB_I_LETTER=-2]
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 TPTlzF4SuDZz for <ima@core3.amsl.com>; Tue, 14 Jul 2009 08:19:47 -0700 (PDT)
Received: from mail-bw0-f228.google.com (mail-bw0-f228.google.com [209.85.218.228]) by core3.amsl.com (Postfix) with ESMTP id 849693A68F5 for <ima@ietf.org>; Tue, 14 Jul 2009 08:19:47 -0700 (PDT)
Received: by bwz28 with SMTP id 28so845116bwz.37 for <ima@ietf.org>; Tue, 14 Jul 2009 08:19:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:reply-to:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=yic5IovNXtzoGrVCIPi5J3M6fAHr8LdJBzG9nCys8lg=; b=sgNhKWzqqhuUikc6IGPRMBQSeiSus5x02S8MMmvNRLVzW4ID/XWIm39ztF0S1kQW6B /XpkCvn8G82YquDFjYnXAIOiGlDCDf91aH6db3d2g/HUYsJy21yBwPsDwJbEtb1QynFH XVitHGSVXybfUlwwy5T2OAHztgDb1JAbJ3+K8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; b=XX3n976NbldBXcKFd7dkfxzpu5UhtkNvwFdnsSnVqlJrrLzEgur9G6//QTS/WIUUqi 7vu2Xid7tQBfbWh7m9Fj/ETjhqMzPXRYXhGlpLNsh2JSH5wtG+Zny7d6DZcQKjBxtzmK oehWAqe/VOiHD/5y0qM6gxz5xVbnOxJRyvLGU=
MIME-Version: 1.0
Received: by 10.239.152.3 with SMTP id t3mr632689hbb.19.1247584755201; Tue, 14 Jul 2009 08:19:15 -0700 (PDT)
In-Reply-To: <CAD7705D4A93814F97D3EF00790AF0B315FA64C6@tk5ex14mbxc105.redmond.corp.microsoft.com>
References: <CAD7705D4A93814F97D3EF00790AF0B315F536BD@tk5ex14mbxc105.redmond.corp.microsoft.com> <4A4FD198.9010709@isode.com> <4A5A4DD7.5010605@alvestrand.no> <CAD7705D4A93814F97D3EF00790AF0B315FA64C6@tk5ex14mbxc105.redmond.corp.microsoft.com>
Date: Tue, 14 Jul 2009 11:19:15 -0400
Message-ID: <6c9fcc2a0907140819n2d5170c6s214956445b2f10ac@mail.gmail.com>
From: Barry Leiba <barryleiba.mailing.lists@gmail.com>
To: Shawn Steele <Shawn.Steele@microsoft.com>
Content-Type: text/plain; charset="UTF-8"
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
Reply-To: barryleiba@computer.org
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: Tue, 14 Jul 2009 15:19:48 -0000

I think what Shawn's getting at, which Alexey and Harald haven't
addressed and which Shawn might not be making clear, isn't so much the
connection between the IMAP login and the email address as it is the
idea of limitations on, say, the user's device.

If I'm migrated to a new email address and if, in the process, I also
get a nifty new non-ASCII login (whether or not it's the same as the
email address... surely we can see that migrating both at the same
time might be a common thing), that may be OK when I'm using my
laptop, where I can enter, say, "лзыба" just fine.  But I might not
have a mobile phone yet that can enter Cyrillic letters (or Thai
characters, or whatever), and then I'd have a hard time logging in
from my mobile.

And I think Shawn's point, which I agree with if I'm getting that
right, is that it wouldn't be a bad thing to point that out and to
suggest that an ASCII version of the login be available for a
transition.  Perhaps some text vaguely like this:

---
When a user's email address is changed, it may be common -- perhaps
desirable -- to change the user's login identification as well.  It's
possible, however, that a user who gets a non-ASCII email address
might still have devices that are unable to enter a non-ASCII login
ID.  It is probably wise, therefore, to continue to accept an ASCII
version of the user's login ID -- perhaps the old one, or perhaps an
alternate ASCII version of the new one -- until the user confirms that
it is no longer necessary.
---

Barry