IETF Logo Mail Archive

Re: [EAI] POP/IMAP authentication?

Shawn Steele <Shawn.Steele@microsoft.com> Mon, 13 July 2009 18:01 UTC

Return-Path: <Shawn.Steele@microsoft.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 424EB3A6DA2 for <ima@core3.amsl.com>; Mon, 13 Jul 2009 11:01:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.597
X-Spam-Level:
X-Spam-Status: No, score=-10.597 tagged_above=-999 required=5 tests=[AWL=0.002, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 OnLR-ompyutm for <ima@core3.amsl.com>; Mon, 13 Jul 2009 11:01:40 -0700 (PDT)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.214]) by core3.amsl.com (Postfix) with ESMTP id 086273A6E6C for <ima@ietf.org>; Mon, 13 Jul 2009 10:58:51 -0700 (PDT)
Received: from TK5EX14MLTC101.redmond.corp.microsoft.com (157.54.79.178) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.99.4; Mon, 13 Jul 2009 10:59:17 -0700
Received: from tk5ex14mbxc105.redmond.corp.microsoft.com ([169.254.2.241]) by TK5EX14MLTC101.redmond.corp.microsoft.com ([157.54.79.178]) with mapi; Mon, 13 Jul 2009 10:59:17 -0700
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: Harald Tveit Alvestrand <harald@alvestrand.no>, Alexey Melnikov <alexey.melnikov@isode.com>
Thread-Topic: [EAI] POP/IMAP authentication?
Thread-Index: AQHJ/PNKL504HDqVmE68bFc3apkfNJBy4bmAgADqxxA=
Date: Mon, 13 Jul 2009 17:59:09 +0000
Message-ID: <CAD7705D4A93814F97D3EF00790AF0B315FA64C6@tk5ex14mbxc105.redmond.corp.microsoft.com>
References: <CAD7705D4A93814F97D3EF00790AF0B315F536BD@tk5ex14mbxc105.redmond.corp.microsoft.com> <4A4FD198.9010709@isode.com> <4A5A4DD7.5010605@alvestrand.no>
In-Reply-To: <4A5A4DD7.5010605@alvestrand.no>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-cr-puzzleid: {B9145A02-1B32-4D8B-BCA8-30C43E73E069}
x-cr-hashedpuzzle: AUHe AUnG BCLN EIVx L/Uy OkLs OzIx QJnI QoBP QvQj Q+gy UusL VZJu Wbg8 ZqBm b06E; 3; YQBsAGUAeABlAHkALgBtAGUAbABuAGkAawBvAHYAQABpAHMAbwBkAGUALgBjAG8AbQA7AGgAYQByAGEAbABkAEAAYQBsAHYAZQBzAHQAcgBhAG4AZAAuAG4AbwA7AGkAbQBhAEAAaQBlAHQAZgAuAG8AcgBnAA==; Sosha1_v1; 7; {B9145A02-1B32-4D8B-BCA8-30C43E73E069}; cwBoAGEAdwBuAC4AcwB0AGUAZQBsAGUAQABtAGkAYwByAG8AcwBvAGYAdAAuAGMAbwBtAA==; Mon, 13 Jul 2009 17:59:09 GMT; UgBFADoAIABbAEUAQQBJAF0AIABQAE8AUAAvAEkATQBBAFAAIABhAHUAdABoAGUAbgB0AGkAYwBhAHQAaQBvAG4APwA=
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
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
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: Mon, 13 Jul 2009 18:01:41 -0000

> On my home mailserver, where my mail address is "harald", my login
> identity is "hta".
> On my Google mailserver, where my mail address is "hta@google.com", my
> login identity is "hta@google.com".

> I don't think we need to say anything about the relationship between
> those entities in the EAI documents.

I realize that.  An end user using gmail or live mail or something is used to the email & logon being identical however.  Additionally they're needing EAI to solve an input-level problem.  So it doesn't do me much good to give me a Chinese alias and migrate my account, if I still have to use ASCII to log on.

So I think that the EAI documents should explicitly mention it as a possible paradigm, although as you point out there are many other ways of handling logon.  Certainly it isn't a MUST or SHOULD, but I think it could be informative.

-Shawn

v2.28.0 | Report a Bug | By Email | System Status