Re: [EAI] Proposed resolution of List-* and downgrade- Issues
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [EAI] Proposed resolution of List-* and downgrade- Issues



On Mon, 28 Jul 2008 18:34:57 +0100, Randall Gellens <randy at 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?

A preference is for List-ID to be considered special and remain ASCII (same as Message-ID).

Agreed.

... 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 at 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 at mañana.com<list at manana.com>>
(i.e. and Alt address).

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.

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.

--
Charles H. Lindsey ---------At Home, doing my own thing------------------------
Tel: +44 161 436 6131     Web: http://www.cs.man.ac.uk/~chl
Email: chl at clerew.man.ac.uk      Snail: 5 Clerewood Ave, CHEADLE, SK8 3JU, U.K.
PGP: 2C15F1A9      Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5
_______________________________________________
IMA mailing list
IMA at ietf.org
https://www.ietf.org/mailman/listinfo/ima



Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.