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

[Martin Duerst <duerst at it.aoyama.ac.jp>]

For the Archived-At header, defined in http://www.ietf.org/rfc/rfc5064.txt,
which is related to list headers but somewhat different because it
indicates per-message archival location, I took a forward-looking
approach and included this:

2.4.  Syntax Extension for Internationalized Message Headers

   There are some efforts to allow non-ASCII text directly in message
   header field bodies.  In such contexts, the URI non-terminal in the
   syntax defined in Section 2.1 is to be replaced by an
   Internationalized Resource Identifier (IRI) as defined in [RFC3987].
   The specifics of the actual octet encoding of the IRI will follow the
   rules for general direct encoding of non-ASCII text.  For conversion
   between IRIs and URIs, the procedures defined in [RFC3987] are to be
   applied.

My understanding is that this is enough for people to figure out
that with EAI, they can use IRIs (encoded in UTF-8) in the
Archived-At header(s) of EAI messages. If somebody thinks that's
not enough, and a revision of RFC 5064 is needed, please tell me.

Regards,    Martin.

At 02:34 08/07/29, Randall Gellens 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.
>
>This is accomplished by creating a new WG document for 2369-bis to extend List-* headers to "permit UTF8 whenever UTF8 is otherwise permitted in header fields".  There isn't a need to do more than adding this one sentence to the existing 2369, I think.  So hopefully it will be very simple to produce.  We need to be very clear that, as 2369-bis is being done by EAI, its scope is strictly limited to permitting UTF8 and not to any other changes that anyone might desire in 2369.
>
>A preference is for List-ID to be considered special and remain ASCII (same as Message-ID). 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.
>
>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).
>
>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.
>
>----------------------------------------------
>New text in -framework-bis:
>
>New versions of List-* headers are also defined, which permit native UTF8.
>
>----------------------------------------------
>-utf8headers:
>
>My suggestion is to create an I-D for utf8headers-bis which adds
>List-* headers, and keep it around as an I-D for when we go to
>standards track.
>
>-- 
>Randall Gellens
>Opinions are personal;    facts are suspect;    I speak for myself only
>-------------- Randomly-selected tag: ---------------
>Nobody can be exactly like me. Even I have trouble doing it.
>                                        --Tallulah Bankhead
>_______________________________________________
>IMA mailing list
>IMA at ietf.org
>https://www.ietf.org/mailman/listinfo/ima


#-#-#  Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University
#-#-#  http://www.sw.it.aoyama.ac.jp       mailto:duerst at it.aoyama.ac.jp     

_______________________________________________
IMA mailing list
IMA at ietf.org
https://www.ietf.org/mailman/listinfo/ima