[EAI] How to prevent up-conversion (Re: Respawn "Messages on original form" (Re: I-D ACTION:draft-ietf-eai-imap-utf8-01.txt))

[Kari Hurtta <hurtta+gmane at siilo.fmi.fi>]

Kari Hurtta <hurtta+gmane at siilo.fmi.fi> writes in gmane.ietf.ima:

> Internet-Drafts at ietf.org writes in gmane.ietf.ima:
> 
> > A New Internet-Draft is available from the on-line Internet-Drafts 
> > directories.
> > This draft is a work item of the Email Address Internationalization Working Group of the IETF.
> > 
> > 	Title		: IMAP Support for UTF-8
> > 	Author(s)	: P. Resnick, C. Newman
> > 	Filename	: draft-ietf-eai-imap-utf8-01.txt
> > 	Pages		: 15
> > 	Date		: 2007-3-7
> > 	
> > This specification extends the Internet Message Access Protocol
> >    version 4rev1 (IMAP4rev1) to support unencoded international
> >    characters in user names, mail addresses and message headers.  This
> >    is an early draft and intended as a framework for discussion.  Please
> >    do not deploy implementations of this draft.
> > 
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-ietf-eai-imap-utf8-01.txt
> 
> Just note. I'm still concernes about these things what I noted on thread,
> which I started with message:
> 
>       From: Kari Hurtta <hurtta+gmane at siilo.fmi.fi>
>       Subject: [EAI] Messages on original form (Re: I-D
> 	ACTION:draft-ietf-eai-imap-utf8-00.txt)
>       Newsgroups: gmane.ietf.ima
>       To: ima at ietf.org
>       Date: 06 Feb 2007 21:29:49 +0200
> 
> 
> In general that is concern that UTF8SMTP capable mailstore should
> store messages on that form what it is received them. And
> that form should be accessible.

Specially question is:

        How to prevent up-conversion of non-UTF8SMTP messages 
        without to triggering downgrading of UTF8SMTP messages ?

        ( Up-conversion of downgraded UTF8SMTP messages is OK. )

draft-ietf-eai-imap-utf8-01.txt: --------------------------------------
8.  Up-Conversion Server Requirements

   When an IMAP4 server uses a traditional mailbox format that includes
   7-bit headers and it chooses to permit access to that mailbox with
   the UTF8 parameter, it MUST support minimal up-conversion as
   described in this section.  Minimal up-conversion is described in
   this section.

   The server MUST support up-conversion of the following address
   header-fields in the message header: From, Sender, To, CC, Bcc,
   Resent-From, Resent-Sender, Resent-To, Resent-CC, Resent-Bcc, and
   Reply-To.  This up-conversion MUST include address local-parts
   encoded according to [TBD], address domains encoded according to IDNA
   [RFC3490], and MIME header encoding [RFC2047] of display-names and
   any RFC 2822 comments.

   The following charsets MUST be supported for up-conversion of MIME
   header encoding [RFC2047]: UTF-8, US-ASCII, ISO-8859-1, ISO-8859-2,
   ISO-8859-3, ISO-8859-4, ISO-8859-5, ISO-8859-6, ISO-8859-7,
   ISO-8859-8, ISO-8859-9, ISO-8859-10, ISO-8859-14, and ISO-8859-15.
   Other widely deployed MIME charsets SHOULD be supported.

   Up-conversion of MIME header encoding of the following headers MUST
   also be implemented: Subject, Date (RFC 2822 comments only),
   Comments, Keywords, Content-Description.

   Server implementations also SHOULD up-convert all MIME body headers,
   SHOULD up-convert or remove the deprecated (and misused) name
------------------------------------------------------------------------

/ Kari Hurtta

( This is somewhat sidestepped on

  http://www.elmme-mailer.org/ID/draft-hurtta-eai-messagestore-00.txt
  http://www.elmme-mailer.org/ID/draft-hurtta-eai-messagestore-00.xml

  These are posted to RFC Editor some days ago, but seems that there is
  some backlog.

  There is also 

  http://www.elmme-mailer.org/ID/draft-hurtta-eai-encapsulation-01.txt
  http://www.elmme-mailer.org/ID/draft-hurtta-eai-encapsulation-01.xml
)



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