Re: [EAI] [eai] #11: Capture the scenario of "SHOULD not use UTF-8 in Message-ID" for future advice draft
Joseph Yee <jyee@afilias.info> Mon, 19 September 2011 19:02 UTC
Return-Path: <jyee@afilias.info>
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 D25AE21F8CD9 for <ima@ietfa.amsl.com>; Mon, 19 Sep 2011 12:02:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.067
X-Spam-Level:
X-Spam-Status: No, score=-6.067 tagged_above=-999 required=5 tests=[AWL=0.046, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_UTF8=0.152]
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 sdOrU9Fokrpv for <ima@ietfa.amsl.com>; Mon, 19 Sep 2011 12:02:48 -0700 (PDT)
Received: from outbound.afilias.info (outbound.afilias.info [69.46.124.26]) by ietfa.amsl.com (Postfix) with ESMTP id 9DD1B21F8C68 for <ima@ietf.org>; Mon, 19 Sep 2011 12:02:48 -0700 (PDT)
Received: from ms6.yyz2.afilias-ops.info ([10.50.129.112] helo=smtp.afilias.info) by outbound.afilias.info with esmtp (Exim 4.69) (envelope-from <jyee@afilias.info>) id 1R5j9T-0004JH-6F for ima@ietf.org; Mon, 19 Sep 2011 19:05:11 +0000
Received: from mail-yx0-f178.google.com ([209.85.213.178]) by smtp.afilias.info with esmtps (TLSv1:RC4-SHA:128) (Exim 4.72) (envelope-from <jyee@afilias.info>) id 1R5j9T-0000y4-8s for ima@ietf.org; Mon, 19 Sep 2011 19:05:11 +0000
Received: by yxj19 with SMTP id 19so4288830yxj.9 for <ima@ietf.org>; Mon, 19 Sep 2011 12:05:11 -0700 (PDT)
Received: by 10.150.69.18 with SMTP id r18mr2834959yba.438.1316459110017; Mon, 19 Sep 2011 12:05:10 -0700 (PDT)
Received: from jyee-lt.tor.afilias-int.info (tor-gateway.afilias.info. [199.15.87.4]) by mx.google.com with ESMTPS id u19sm3853628ybm.19.2011.09.19.12.05.07 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 19 Sep 2011 12:05:09 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Joseph Yee <jyee@afilias.info>
In-Reply-To: <CAHhFybrYC9jFnh7+Zq1-FrTxRvMzHXXjK=qMQnxU4SYK2VSjGw@mail.gmail.com>
Date: Mon, 19 Sep 2011 15:05:06 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <E500DD34-4992-4DBE-9325-280DCC1DC159@afilias.info>
References: <061.9721166081247d3e53392a010db4b79a@trac.tools.ietf.org> <01O68AN5NRSW014O5Z@mauve.mrochek.com> <4E777AED.5010906@dcrocker.net> <CAHhFybrYC9jFnh7+Zq1-FrTxRvMzHXXjK=qMQnxU4SYK2VSjGw@mail.gmail.com>
To: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: dcrocker@bbiw.net, ima@ietf.org
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 19:02:49 -0000
On 2011-09-19, at 2:38 PM, Frank Ellermann wrote: > On 19 September 2011 19:25, Dave CROCKER wrote: > >> A simple question is why this juggling is appropriate here but >> not in the rest of the core drafts, including this one? > > The technical problems of "folks want to use local parts in their > scripts and languages" vs. "messages need a unique part to form a > globally unique message ID" are _technically_ unrelated. > > That unique@ and local@ are _historically_ almost the same syntax > has no _technical_ reason I'm aware of. Besides you would know it > better. For the purposes of NetNews message IDs are as important > as say IP for the purposes of TCP. > > That's as simple as 1-2-3. Don't waste time with MAYs or SHOULDs, > anything below a MUST is "broken by design", details don't matter, > or make it worse. Hi Frank, The recent WG rough consensus agreed to allow UTF-8 in Message-ID. When we look into EAI advice draft in future, would you be interest to write about advice dealing with NNTP, or better (IMHO), look into -bis or extension RFC for NNTP in a new WG/BOF? Thanks Joseph, co-chair of EAI > > -Frank > _______________________________________________ > IMA mailing list > IMA@ietf.org > https://www.ietf.org/mailman/listinfo/ima
- [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