Re: [EAI] POP/IMAP authentication?

"Daniel Taharlev" <daniel@taharlev.com> Tue, 14 July 2009 15:49 UTC

Return-Path: <SRS0=ue+pLb=DH=taharlev.com=daniel@srs.bis.na.blackberry.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 EF90C28C2D9 for <ima@core3.amsl.com>; Tue, 14 Jul 2009 08:49:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.599
X-Spam-Level:
X-Spam-Status: No, score=-8.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_MED=-4]
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 aSLpQhfEYqrW for <ima@core3.amsl.com>; Tue, 14 Jul 2009 08:49:34 -0700 (PDT)
Received: from smtp02.bis.na.blackberry.com (smtp02.bis.na.blackberry.com [216.9.248.49]) by core3.amsl.com (Postfix) with ESMTP id 04B843A6945 for <ima@ietf.org>; Tue, 14 Jul 2009 08:49:33 -0700 (PDT)
Received: from bxe1040.bisx.prod.on.blackberry (bxe1040.bisx.prod.on.blackberry [172.20.205.55]) by srs.bis.na.blackberry.com (8.13.7 TEAMON/8.13.7) with ESMTP id n6EF2OOB013620; Tue, 14 Jul 2009 15:23:12 GMT
X-rim-org-msg-ref-id: 1233784060
Message-ID: <1233784060-1247585065-cardhu_decombobulator_blackberry.rim.net-179738162-@bxe1040.bisx.prod.on.blackberry>
Content-Transfer-Encoding: base64
X-Priority: Normal
References: <CAD7705D4A93814F97D3EF00790AF0B315F536BD@tk5ex14mbxc105.redmond.corp.microsoft.com><4A4FD198.9010709@isode.com> <4A5A4DD7.5010605@alvestrand.no><CAD7705D4A93814F97D3EF00790AF0B315FA64C6@tk5ex14mbxc105.redmond.corp.microsoft.com><6c9fcc2a0907140819n2d5170c6s214956445b2f10ac@mail.gmail.com>
In-Reply-To: <6c9fcc2a0907140819n2d5170c6s214956445b2f10ac@mail.gmail.com>
Sensitivity: Normal
Importance: Normal
To: barryleiba@computer.org, Shawn Steele <Shawn.Steele@microsoft.com>
From: Daniel Taharlev <daniel@taharlev.com>
Date: Tue, 14 Jul 2009 15:22:03 +0000
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
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: daniel@taharlev.com
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 16:06:27 -0000

Many of my users also have different machines with different keyboard layouts, and accounts set on several machines, it's not just a mobile phone issue imho... Be gentle it's my first post

daniel@taharlev.com

-----Original Message-----
From: Barry Leiba <barryleiba.mailing.lists@gmail.com>

Date: Tue, 14 Jul 2009 11:19:15 
To: Shawn Steele<Shawn.Steele@microsoft.com>
Cc: ima@ietf.org<ima@ietf.org>
Subject: Re: [EAI] POP/IMAP authentication?


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
_______________________________________________
IMA mailing list
IMA@ietf.org
https://www.ietf.org/mailman/listinfo/ima