Re: [EAI] [eai] #11: Capture the scenario of "SHOULD not use UTF-8 in Message-ID" for future advice draft
"John Levine" <johnl@taugh.com> Mon, 19 September 2011 20:54 UTC
Return-Path: <johnl@iecc.com>
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 E370821F8D86 for <ima@ietfa.amsl.com>; Mon, 19 Sep 2011 13:54:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.041
X-Spam-Level:
X-Spam-Status: No, score=-111.041 tagged_above=-999 required=5 tests=[AWL=0.006, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, SARE_SUB_ENC_UTF8=0.152, 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 MUNyUg5E5nSo for <ima@ietfa.amsl.com>; Mon, 19 Sep 2011 13:54:26 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 5066721F8D85 for <ima@ietf.org>; Mon, 19 Sep 2011 13:54:25 -0700 (PDT)
Received: (qmail 58349 invoked from network); 19 Sep 2011 20:56:48 -0000
Received: from gal.iecc.com (64.57.183.53) by mail2.iecc.com with SMTP; 19 Sep 2011 20:56:48 -0000
Received: (qmail 3132 invoked from network); 19 Sep 2011 20:56:47 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 19 Sep 2011 20:56:47 -0000
Date: Mon, 19 Sep 2011 20:56:25 -0000
Message-ID: <20110919205625.81521.qmail@joyce.lan>
From: John Levine <johnl@taugh.com>
To: ima@ietf.org
In-Reply-To: <CAHhFybqGwUSmg+BNMpid3+jmHpequ8R=dOxb+UntUJ_m15Bf4g@mail.gmail.com>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 7bit
Cc: hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com
Subject: Re: [EAI] [eai] #11: Capture the scenario of "SHOULD not use UTF-8 in Message-ID" for future advice draft
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: Mon, 19 Sep 2011 20:54:27 -0000
> Gateway operators are used to the idea that they have to do > something with Message-IDs, and while UTF-8 makes this job more > interesting it won't be completely different. Practical Mail->News gateways have to do all sorts of gross stuff due to news systems enforcing syntax rules more strictly than mail systems. Munging message IDs would not be any worse than what they do now. Although I understand the rationale for wanting ASCII message IDs in mail to make non-EAI replies easier, I'm having trouble imagining plausible scenarios in which it would make a difference. Scenario 1: A sends B an EAI message. B replies, and somehow manages to leave out all the elements that made A's message need EAI. This suggests that A and B both have ASCII addresses, A's message was cc'ed to EAI recipient C who B leaves out of the reply, or something like that. Yes, it could happen, but it doesn't impress me as likely enough to be a design point. Scenario 2: A sends B an EAI message, something in the path uses local knowledge to downgrade the message to ASCII. But if it's going to rewrite all the other headers, it can rewrite the message-ID, too. So I'm OK with it being a MAY, but it doesn't seem worth much effort. It's also one of those things where no matter what we say, MUAs and MTAs will make them UTF-8 anyway. R's, John
- [EAI] [eai] #11: Capture the scenario of "SHOULD … eai issue tracker
- Re: [EAI] [eai] #11: Capture the scenario of "SHO… ned+ima
- Re: [EAI] [eai] #11: Capture the scenario of "SHO… Dave CROCKER
- Re: [EAI] [eai] #11: Capture the scenario of "SHO… ned+ima
- Re: [EAI] [eai] #11: Capture the scenario of "SHO… Frank Ellermann
- Re: [EAI] [eai] #11: Capture the scenario of "SHO… ned+ima
- Re: [EAI] [eai] #11: Capture the scenario of "SHO… Joseph Yee
- Re: [EAI] [eai] #11: Capture the scenario of "SHO… Frank Ellermann
- Re: [EAI] [eai] #11: Capture the scenario of "SHO… John Levine
- Re: [EAI] [eai] #11: Capture the scenario of "SHO… ned+ima
- Re: [EAI] [eai] #11: Capture the scenario of "SHO… John C Klensin