Re: [EAI] Shepherd report review of mailinglist-02

"Martin J. Dürst" <duerst@it.aoyama.ac.jp> Sat, 14 July 2012 02:06 UTC

Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7184121F85B1 for <ima@ietfa.amsl.com>; Fri, 13 Jul 2012 19:06:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.57
X-Spam-Level:
X-Spam-Status: No, score=-99.57 tagged_above=-999 required=5 tests=[AWL=0.220, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c5ZMkYKYfCjJ for <ima@ietfa.amsl.com>; Fri, 13 Jul 2012 19:06:36 -0700 (PDT)
Received: from scintmta01.scbb.aoyama.ac.jp (scintmta01.scbb.aoyama.ac.jp [133.2.253.33]) by ietfa.amsl.com (Postfix) with ESMTP id 9B4F821F85AD for <ima@ietf.org>; Fri, 13 Jul 2012 19:06:35 -0700 (PDT)
Received: from scmse01.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta01.scbb.aoyama.ac.jp (secret/secret) with SMTP id q6E273Ao007101 for <ima@ietf.org>; Sat, 14 Jul 2012 11:07:05 +0900
Received: from (unknown [133.2.206.133]) by scmse01.scbb.aoyama.ac.jp with smtp id 4aad_3f5a_9af2fe6a_cd58_11e1_a1d8_001d096c566a; Sat, 14 Jul 2012 11:07:03 +0900
Received: from [IPv6:::1] ([133.2.210.1]:48378) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S15E1F3E> for <ima@ietf.org> from <duerst@it.aoyama.ac.jp>; Sat, 14 Jul 2012 11:07:06 +0900
Message-ID: <5000D440.1000503@it.aoyama.ac.jp>
Date: Sat, 14 Jul 2012 11:06:56 +0900
From: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: John R Levine <johnl@taugh.com>
References: <CAF1dMVE+2_288HmqaFfqANyB1r+KzBYXQ37i0_Gm_x1w1COqVw@mail.gmail.com> <alpine.BSF.2.00.1207121737350.66870@joyce.lan> <B693E26DE56016D0E4FE6295@JcK-HP8200.jck.com> <50000609.4020509@it.aoyama.ac.jp> <alpine.BSF.2.00.1207130934580.95156@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1207130934580.95156@joyce.lan>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: EAI WG <ima@ietf.org>
Subject: Re: [EAI] Shepherd report review of mailinglist-02
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 14 Jul 2012 02:06:37 -0000

Hello John,

Thanks for your mail. I think we are getting closer to where we have a 
misunderstanding.

On 2012/07/13 22:36, John R Levine wrote:
>> Also, my proposal of different text for the "%-routing problem", which
>> is clearer about the source of the problem, in particular that it's an
>> implementation problem (correct escaping/unescaping) and not an
>> a-priori problem, hasn't been taken into account, and I don't know why.
>
> I looked at your language, and it seemed to me less clear than what's
> there.

Sorry about that. I don't claim that my text is perfect.

> The problem is very simple, some MTAs mishandle addresses that
> contain % signs.

Here is where we have the misunderstanding/disagreement. The original 
problem is NOT what MTAs do with addresses that contain % signs. If e.g. 
I enter something like gorby%kremvax@example.com into a To field in my 
MUA, then that might work somehow, or not, but that's secondary.

To continue, if there is an URI mailto:gorby%25kremvax@example.com, and 
it gets correctly converted to gorby%kremvax@example.com, then that 
might work somehow, or not, but that's again irrelevant.

The actual problem we want to discuss (on which point I very strongly 
agree with John Klensin) is the case where there is e.g. an URI of the 
form mailto:unlikely%3Faddress@example.com, which should end up in a 
mail to unlikely?address@example.com, but because the unescaping is 
missing, produces a mail to unlikely%3Faddress@example.com.

The address unlikely%3Faddress@example.com is essentially wrong. What 
some mailers do with such an address, or with addresses containing % in 
general, just affects who wrongly gets (or doesn't get) the mail, and 
how easy it might be to debug the problem. But the problem happened earlier.


> All we need to do is note it, not tell people how we
> think they should fix it or work around it.

Just to note it may be okay (a nugde in the right direction for a fix 
can't hurt though), but what's important is that the focus has to be on 
unescaping %-encoding when moving from mailto: to raw email addresses, 
rather than on what mailers do with mail addresses that have a % in them.

BTW, the examples are all taken from RFC 6068, so again it might not be 
such a bad idea to reference it.

Regards,   Martin.


> Regards,
> John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
> "I dropped the toothpaste", said Tom, crestfallenly.
>