Re: [EAI] Proposed resolution of List-* and downgrade- Issues
Randall Gellens <randy@qualcomm.com> Tue, 29 July 2008 13:04 UTC
Return-Path: <ima-bounces@ietf.org>
X-Original-To: ima-archive@megatron.ietf.org
Delivered-To: ietfarch-ima-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1A6B728C17E; Tue, 29 Jul 2008 06:04:59 -0700 (PDT)
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 BDE0E3A6A60 for <ima@core3.amsl.com>; Tue, 29 Jul 2008 06:04:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.599
X-Spam-Level:
X-Spam-Status: No, score=-104.599 tagged_above=-999 required=5 tests=[AWL=2.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 nAELhtGodXIR for <ima@core3.amsl.com>; Tue, 29 Jul 2008 06:04:56 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by core3.amsl.com (Postfix) with ESMTP id 0542728C2A5 for <ima@ietf.org>; Tue, 29 Jul 2008 06:04:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=randy@qualcomm.com; q=dns/txt; s=qcdkim; t=1217336692; x=1248872692; h=message-id:in-reply-to:references:x-mailer: x-message-flag:date:to:from:subject:content-type: content-transfer-encoding:x-random-sig-tag:x-ironport-av; z=Message-Id:=20<p0624060cc4b4c1a603c8@[172.16.14.74]> |In-Reply-To:=20<op.ue1rv0sn6hl8nm@clerew.man.ac.uk> |References:=20<p06240609c4b3aaea35c0@[130.129.20.99]>=0D =0A=20<op.ue1rv0sn6hl8nm@clerew.man.ac.uk>|X-Mailer:=20Eu dora=20for=20Mac=20OS=20X|X-message-flag:=20Warning:=20Ou tlook=20in=20use.=20=20Upgrade=20to=20Eudora:=20<http://w ww.eudora.com>|Date:=20Tue,=2029=20Jul=202008=2005:59:36 =20-0700|To:=20"Charles=20Lindsey"=20<chl@clerew.man.ac.u k>,=20IMA=20<ima@ietf.org>|From:=20Randall=20Gellens=20<r andy@qualcomm.com>|Subject:=20Re:=20[EAI]=20Proposed=20re solution=20of=20List-*=20and=20downgrade-=20Issues |Content-Type:=20text/plain=3B=20charset=3D"iso-8859-1" =20=3B=20format=3D"flowed"|Content-Transfer-Encoding:=20q uoted-printable|X-Random-Sig-Tag:=201.0b28|X-IronPort-AV: =20E=3DMcAfee=3Bi=3D"5200,2160,5348"=3B=20a=3D"5138141"; bh=UGA2ra44rusAOD+Ow6lu8Rgj6CXIig/6StjU4vKSD14=; b=Vx8Ce20SrEfHgDZ+c3JaDRoF6dHSHv+efDCCynaKotVIwV1dd2FZSBur XSmkOZx+zhfIcedJVQn8dpt58SYIkUHMfSTnhMM05GfwILPPbcl1uTkbA lbJ4rKKajOSvP0Krtii0VgS2+F56BePz9WUdNJlwRcxwVZvV0jVHIEs9I w=;
X-IronPort-AV: E=McAfee;i="5200,2160,5348"; a="5138141"
Received: from pdmz-ns-mip.qualcomm.com (HELO numenor.qualcomm.com) ([199.106.114.10]) by wolverine01.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 29 Jul 2008 06:04:52 -0700
Received: from msgtransport02.qualcomm.com (msgtransport02.qualcomm.com [129.46.61.151]) by numenor.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id m6TD4pOR020247 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 29 Jul 2008 06:04:52 -0700
Received: from [172.16.14.74] (vpn-10-50-0-105.qualcomm.com [10.50.0.105]) by msgtransport02.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id m6TD4gfc014733; Tue, 29 Jul 2008 06:04:50 -0700
Mime-Version: 1.0
Message-Id: <p0624060cc4b4c1a603c8@[172.16.14.74]>
In-Reply-To: <op.ue1rv0sn6hl8nm@clerew.man.ac.uk>
References: <p06240609c4b3aaea35c0@[130.129.20.99]> <op.ue1rv0sn6hl8nm@clerew.man.ac.uk>
X-Mailer: Eudora for Mac OS X
X-message-flag: Warning: Outlook in use. Upgrade to Eudora: <http://www.eudora.com>
Date: Tue, 29 Jul 2008 05:59:36 -0700
To: Charles Lindsey <chl@clerew.man.ac.uk>, IMA <ima@ietf.org>
From: Randall Gellens <randy@qualcomm.com>
Mime-Version: 1.0
X-Random-Sig-Tag: 1.0b28
Subject: Re: [EAI] Proposed resolution of List-* and downgrade- Issues
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/pipermail/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>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Sender: ima-bounces@ietf.org
Errors-To: ima-bounces@ietf.org
At 10:41 AM +0100 7/29/08, Charles Lindsey wrote: > On Mon, 28 Jul 2008 18:34:57 +0100, Randall > Gellens <randy@qualcomm.com> wrote: > >> ---------------------------------------------- >> Proposed resolution of "List-*" headers: >> >> EAI to define new versions of List-* headers >> which can have unencoded UTF8 values. This is >> just a trivial revision of the current forms. >> Like the current forms, each header can have >> multiple IRI, URL, URL, etc. >> Note that this is orthogonal to new "mailto" >> -- when mailto-bis is ready, it just drops in >> as any other scheme such as HTTP. > > But is that not equivalent to just saying that > IRIs are to be permitted (within the UTF8SMTP > universe) in places where URIs are currently > allowed? > > And if it is not equivalent, then why cannot it be made so? I'm no expert in IRIs, but my understanding is that an IRI can be represented either in UTF8 or in percent-encoded form. I specifically said "unencoded UTF8 values" because I think this is the key point. > >> A preference is for List-ID to be considered >> special and remain ASCII (same as Message-ID). > > Agreed. Yes, but, there is the sticky point in the next paragraph.... > >> ... There is an open question on >> internationalized domain names: since these >> are used in Sieve scripts, users need to be >> able to type them in. > > Ah! So if we have > List-Post: <mailto:list@mañana.com> > (which is presumably an IRI), then is the > corresponding URI just a %-encoding of > "mañana", or is it a punycode thereof? > Actually, I think we have to wait for > mailto-bis to answer this question, because > mailto-bis might well allow something of the > form > List-Post: <mailto:list@mañana.com<list@manana.com>> > (i.e. and Alt address). The point about internationalized domain names and Sieve scripts is specifically about List-ID. Since this is the unique identifier for a list and hence used in Sieve scripts, it should be permitted to be something meaningful that users can type in. So, the example might be List-ID: list.mañana.com Which would be meaningful, and presumably easy for users to remember and to type in. Forcing this List-ID to be in punycode turns it from something meaningful and easy to type into gobbledegook. However, permitting UTF8 means that during downconversion it will be encoded, and then there is the question as to if anything will recognize an encoded List-ID as being identical to the unencoded version. >> >> Note that allowing UTF8 in List-* headers is >> equivalent to allowing UTF8 in address >> headers. Presumably, only EAI-aware clients >> will see either. >> >> ---------------------------------------------- >> New text in -downgrade: >> >> List-* headers which contain native UTF8 should be copied into >> Downgrade-List-* and the UTF8 IRI should be dropped (alternate: >> encoded per IRI). > > No! Don't drop it. Downgrade it to a URI, and > let mailto-bis sort out the result. mailto is just one possible scheme that can be used in a List-* header. I'm OK with encoding it, if the encoded result is always as valid and usable as the unencoded form. >> >> Add informative reference to new 2369-bis >> draft along the lines of "Since [2369-bis] >> permits UTF8 in List-* headers, which are >> vital to user's experience of mailing lists, >> this document needs to specify how such >> headers are to be downgraded and remain valid." >> >> ---------------------------------------------- >> New text in -mailinglist: >> >> Where available, mailing lists SHOULD include >> an ASCII form of List-* headers as well as a >> UTF8 form. Because these headers are vital to >> good operations and use of mailing lists, >> special rules are defined in [downgrade] so >> that such headers are not stripped during >> downgrade, but are preserved with working >> values whenever possible. > > Having invented alt-addresses for use elsewhere > within EAI, let us stick with them here. The > last thing we want is two mechanisms for > achieving the same result. I don't follow. What are the two versions? The point is that an EAI-aware list can be created that operates behind a UTF8 email address which has no ASCII version. That's perfectly OK, if people want to do this. Presumably, the list is only for people who have EAI-aware clients. -- Randall Gellens Opinions are personal; facts are suspect; I speak for myself only -------------- Randomly-selected tag: --------------- Never doubt that a small group of thoughtful, committed citizens can change the world. Indeed, it's the only thing that ever has. --Margaret Meed _______________________________________________ IMA mailing list IMA@ietf.org https://www.ietf.org/mailman/listinfo/ima
- [EAI] Proposed resolution of List-* and downgrade… Randall Gellens
- Re: [EAI] Proposed resolution of List-* and downg… Frank Ellermann
- Re: [EAI] Proposed resolution of List-* and downg… Randall Gellens
- Re: [EAI] Proposed resolution of List-* and downg… Charles Lindsey
- Re: [EAI] Proposed resolution of List-* and downg… Randall Gellens
- Re: [EAI] Proposed resolution of List-* and downg… Martin Duerst
- Re: [EAI] Proposed resolution of List-* and downg… Frank Ellermann
- Re: [EAI] Proposed resolution of List-* and downg… Charles Lindsey
- Re: [EAI] Proposed resolution of List-* and downg… Randall Gellens
- Re: [EAI] Proposed resolution of List-* and downg… Randall Gellens
- Re: [EAI] Proposed resolution of List-* and downg… Charles Lindsey
- Re: [EAI] Proposed resolution of List-* and downg… Frank Ellermann
- Re: [EAI] Proposed resolution of List-* and downg… Charles Lindsey
- Re: [EAI] Proposed resolution of List-* and downg… Frank Ellermann
- Re: [EAI] Proposed resolution of List-* and downg… Charles Lindsey