Email Address Internationalization                        Y. YONEYA, Ed.
(EAI)                                                   K. Fujiwara, Ed.
Internet-Draft                                                      JPRS
Intended status: Experimental                               July 6,                          November 18, 2007
Expires: January 7, May 21, 2008

      Downgrading mechanism for Email Address Internationalization
                    draft-ietf-eai-downgrade-04.txt
                    draft-ietf-eai-downgrade-05.txt

Status of this Memo

   By submitting this Internet-Draft, each author represents that any
   applicable patent or other IPR claims of which he or she is aware
   have been or will be disclosed, and any of which he or she becomes
   aware will be disclosed, in accordance with Section 6 of BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on January 7, May 21, 2008.

Copyright Notice

   Copyright (C) The IETF Trust (2007).

Abstract

   Traditional mail systems handle only US-ASCII ASCII characters in SMTP
   envelope and mail header fields.  The Email Address
   Internationalization (UTF8SMTP) extension allows UTF-8 characters in
   SMTP envelope and mail header fields.  To deliver avoid bouncing
   internationalized Email messages to/via when a server in the delivery path
   does not support the UTF8SMTP non-compliant environment, extension, some sort of converting
   mechanism is required.  This document describes a downgrading
   mechanism for Email Address Internationalization.  Note that this is
   a way to downgrade, not tunnel.  There is no associated up-conversion
   mechanism, although internationalized email clients might use
   original internationalized addresses or other data when displaying or
   replying to downgraded messages.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  4
   3.  New header fields definition . . . . . . . . . . . . . . . . .  4  5
     3.1.  Envelope information preservation headers  . . . . . . . .  5
     3.2.  Address header field preservation headers  . . . . . . . .  5
     3.3.  Unknown header fields preservation headers . . . . . . . .  6
   4.  SMTP Downgrading . . . . . . . . . . . . . . . . . . . . . . .  5  7
   5.  Email header fields downgrading  . . . . . . . . . . . . . . .  6  8
     5.1.  Downgrading method for each header field . . . . . . . . .  9
   6.  MIME body part headers downgrading . . . . . . . . . . . . . .  9 11
   7.  Security considerations  . . . . . . . . . . . . . . . . . . . 10 11
   8.  Implementation notes . . . . . . . . . . . . . . . . . . . . . 12
     8.1.  Trivial downgrading  . . . . . . . . . . . . . . . . . . . 12
   9.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 10
   9. 13
   10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 11
   10. 15
   11. Change History . . . . . . . . . . . . . . . . . . . . . . . . 11
     10.1. 15
     11.1. draft-yoneya-ima-downgrade: Version 00 . . . . . . . . . 11
     10.2. . 15
     11.2. draft-yoneya-ima-downgrade: Version 01 . . . . . . . . . 11
     10.3. . 15
     11.3. draft-ietf-eai-downgrade: Version 00 . . . . . . . . . . 11
     10.4. . 16
     11.4. draft-ietf-eai-downgrade: Version 01 . . . . . . . . . . 12
     10.5. . 16
     11.5. draft-ietf-eai-downgrade: Version 02 . . . . . . . . . . 12
     10.6. . 16
     11.6. draft-ietf-eai-downgrade: Version 03 . . . . . . . . . . 12
     10.7. . 16
     11.7. draft-ietf-eai-downgrade: Version 04 . . . . . . . . . . 12
   11. . 16
     11.8. draft-ietf-eai-downgrade: Version 05 . . . . . . . . . . . 17
   12. Normative References . . . . . . . . . . . . . . . . . . . . . 12 17
   Appendix A.  Displaying downgraded message . . . . . . . . . . . . 14 18
     A.1.  Displaying technique 1 . . . . . . . . . . . . . . . . . 14 . 18
     A.2.  Displaying technique 2 . . . . . . . . . . . . . . . . . 14 . 19
   Appendix B.  Examples  . . . . . . . . . . . . . . . . . . . . . . 14 19
     B.1.  Downgrading example 1  . . . . . . . . . . . . . . . . . . 14 19
     B.2.  Displaying example (Displaying technique 1) . . . . . . . 17
     B.3. . . . . . . . . . . . . . 22
       B.2.1.  Displaying technique 1 example (Displaying . . . . . . . . . . . . 23
       B.2.2.  Displaying technique 2) 2 example . . . . . . . 17
     B.4. . . . . . 24
     B.3.  Downgrading example 2  . . . . . . . . . . . . . . . . . . 19 27
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 21 28
   Intellectual Property and Copyright Statements . . . . . . . . . . 22 30

1.  Introduction

   Traditional mail systems which are defined by [RFC2821] and [RFC2822]
   allow US-ASCII ASCII characters in SMTP envelope and mail header field values.
   The UTF8SMTP proposals [I-D.ietf-eai-framework], extension [RFC4952], [I-D.ietf-eai-utf8headers] and
   [I-D.ietf-eai-smtpext] allow allows UTF-8 characters in SMTP envelope and
   mail header field values.

   Delivering

   If an envelope address or header field contains non-ASCII mail addresses from a sender to recipients
   requires all components on characters,
   the mail delivery route are UTF8SMTP
   compliant.  Otherwise, non-ASCII mail address can't message cannot be delivered. delivered unless every system in the delivery
   path supports UTF8SMTP.  To
   solve avoid bouncing such messages when a
   server is encountered which does not support the problem, UTF8SMTP extension,
   this document describes a downgrading mechanism that
   enables delivering non-ASCII mail addresses to traditional mail
   system by converting them mechanism.  Downgrading a
   message converts envelope and header fields to corresponding US-ASCII an all-ASCII
   representation.
   And more,

   [I-D.ietf-eai-utf8headers] expands that allows UTF-8 characters to be used in mail
   header fields and MIME header fields are allowed to use any UTF-8 characters.  This fields.  The downgrading mechanism targets
   specified here converts mail header fields and MIME header fields to be converted to US-ASCII only to send
   ASCII.

   This document does not change any protocols except by defining new
   header fields.  It describes the conversion method from the
   internationalized email envelopes/messages which are defined in
   [RFC4952] [I-D.ietf-eai-utf8headers] [I-D.ietf-eai-smtpext] to UTF8SMTP non-
   compliant receivers. the
   traditional email envelopes/messages which are defined in [RFC2821]
   [RFC2822].

   [I-D.ietf-eai-smtpext] section 2.2 defines when downgrading occurs.
   Mail clients (MUAs, MSAs, MTAs) try to deliver Email messages to SMTP
   servers by static setting or DNS MX resource records resolution.
   If the SMTP client has an UTF8SMTP envelope or an UTF8SMTP internationalized
   message and the SMTP client detects that SMTP server doesn't support "UTF8SMTP"
   option at EHLO, the UTF8SMTP SMTP
   extension, then the SMTP client MUST NOT send the a UTF8SMTP envelope or UTF8SMTP
   an internationalized message to the SMTP server.  The section shows 4
   choices.  The second choice "reject or generate a notification of
   non-deliverability" is always allowed.  The fourth choice is
   downgrading. downgrading, as described here.

   Downgrading may be implemented in MUAs, MSAs, MTAs, MDAs MTAs which
   generates act as the
   SMTP client, or in MDAs, POP servers, IMAP servers which store or receives
   offer UTF8SMTP envelopes or UTF8SMTP internationalized messages and may
   send them to non-UTF8SMTP non-
   UTF8SMTP compliant systems. systems which include message stores.

   This document tries to define the downgrading process clearly and it
   preserves the original information as much as possible.

   Downgrading in UTF8SMTP consists of the following four parts:
   o  New header fields definition
   o  SMTP downgrading
   o  Email header fields downgrading
   o  MIME header fields downgrading
   Before sending to traditional SMTP server, the downgrading process
   need to perform SMTP downgrading, Email header fields downgrading,
   and MIME header fields downgrading.

   In Section 3, two many header fields starting with "downgraded" are
   introduced.  One is "Envelope-
   Downgraded:", it preserves  They preserve the original envelope information.  The
   other is "Downgraded:", it preserves information and the
   original header fields which
   contains non-ASCII email addresses or which does not have clear
   downgrading definition. fields.

   The SMTP downgradin downgrading is described in Section 4.  It generates US-ASCII ASCII
   only envelope information from an UTF8SMTP envelope.

   The Email header fields downgrading is described in Section 5.  It
   generates US-ASCII ASCII only header fields.

   The MIME header fields are expanded in [I-D.ietf-eai-utf8headers].
   The MIME header fields downgrading is described in Section 6.  It
   generates US-ASCII ASCII only MIME header fields.

2.  Terminology

   The key words "MUST", "SHALL", "REQUIRED", "SHOULD", "RECOMMENDED",
   and "MAY" in this document are to be interpreted as

   Decoding downgraded message is described in RFC
   2119 [RFC2119].

   All specialized Appendix A.  This
   mechanism is for use by internationalized email clients.  Once a
   message has been downgraded, there is no up-conversion which can be
   applied on the SMTP delivery path.

2.  Terminology

   The key words "MUST", "SHALL", "REQUIRED", "SHOULD", "RECOMMENDED",
   and "MAY" in this document are to be interpreted as described in RFC
   2119 [RFC2119].

   All specialized terms used in this specification are defined in the
   EAI overview [I-D.ietf-eai-framework] [RFC4952] or in [RFC2821][RFC2822], MIME documents
   [RFC2045] [RFC2047] [RFC2183] [RFC2231].  The terms "ASCII address",
   "internationalized email address", "non-ASCII address", "i18mail
   address", "UTF8SMTP", "message" and "mailing list" are used with the
   definitions from [I-D.ietf-eai-framework] [RFC4952] document.

   This document depends on [I-D.ietf-eai-smtpext],
   [I-D.ietf-eai-utf8headers], and [I-D.ietf-eai-dsn].  Key words used
   in these document are used in this document, too.

   The term "non-ASCII" is an UTF-8 string which contains at least one
   non-ASCII character.

   An "UTF8SMTP envelope" has Email originator/recipient addresses
   expanded by [I-D.ietf-eai-smtpext] and [I-D.ietf-eai-dsn].

   An "UTF8SMTP message" is Email messages expanded by
   [I-D.ietf-eai-utf8headers].

3.  New header fields definition

   A generic encapsulation

   New header "Downgraded:" is fields starting with "downgraded" are defined here to
   preserve
   the those original envelope and header field.  It has two value fields.  The former
   value field holds the original values which contain
   UTF-8 characters.  During downgrading, one new "downgraded" header
   field name.  The latter value
   field holds the is added for each original envelope or header field value.  Any which
   cannot be passed as-is to a server which does not support UTF8SMTP.
   The original envelope or header field value is treated as an unstructured value. removed or altered.  Only
   those envelope and header fields which contain non-ASCII characters
   are affected.  The latter value
   field result of this header MUST process is a message which is
   compliant with existing email specifications [RFC2821] and [RFC2822].
   The original internationalized information can be encoded retrieved by [RFC2047] section 5(1) method
   with charset='UTF-8' same
   examining the "downgraded" header fields which were added.  Even
   though the information is not lost, the original message cannot be
   perfectly reconstructed.  Hence, downgrading is a one-way process.
   However, an internationalized client might use the information in the
   "downgraded" header fields when processing a downgraded message, for
   example, such as displaying or composing a 'Subject' header. reply.

3.1.  Envelope information preservation headers

   Two headers "Downgraded-Mail-From:" and "Downgraded-Rcpt-To:" are
   defined to preserve SMTP envelope downgraded information.  SMTP
   envelope downgraded information consists of the original non-ASCII
   address and the downgraded all-ASCII address.  The header field
   syntax is specified as follows:

fields      =/ downgraded
   downgraded downgradedmailfrom / downgradedrcptto
downgradedmailfrom =  "Downgraded:" "Downgraded-Mail-From:" [FWS] "<" uPath ">" 1*[FWS]
                                     "<" Mailbox ">" [FWS] field-name ":" unstructured CRLF

   Encapsulating a header
downgradedrcptto = "Downgraded-Rcpt-To:" [FWS] "<" uPath ">" 1*[FWS]
                                     "<" Mailbox ">" [FWS] CRLF

   Original non-ASCII address <uPath> is defined in a Downgraded:
   [I-D.ietf-eai-smtpext]; it is treated as unstructured in this header
   and it is encoded according to [RFC2047]. <Mailbox> is defined as:
   1.  Generate new Downgraded: in
   [RFC2821], section 4.1.2.

3.2.  Address header whose former field preservation headers

   The address header fields preservation headers are defined to
   preserve the original header field.  Their value is field holds the
   original header field name value.  Any original header field value is
   treated as an <unstructured> and latter it MUST be encoded according to
   [RFC2047] with charset='UTF-8'.  The header field syntax is specified
   as follows:

   fields     =/ known-downgraded-headers ":" unstructued CRLF
   known-downgraded-headers =  "Downgraded-" original-headers
   original-headers = "From" / "To" / "Cc" / "Bcc" /
                      "Sender" / "Reply-To" /
                      "Resent-From" / "Resent-Sender" /
                      "Resent-To" / "Resent-Cc" / "Return-Path"

   Preserving a header field in a downgraded header field is defined as:
   1.  Generate new downgraded header field whose value is the original
       header fleid field value.
   2.  Encode the generated header by according to [RFC2047] section 5(1) method with
       charset='UTF-8'.
   3.  Replace the

3.3.  Unknown header fields preservation headers

   The unknown header fields preservation headers are defined to
   encapsulate those original header field as which contains non-ASCII
   characters and are not otherwise provided for in the generated header field.

   Another new this
   specification.  The encapsulation header "Envelope-Downgraded:" field name is defined to preserve SMTP
   envelope downgraded information.  SMTP envelope downgraded
   information consists of the original non-ASCII address
   concatenation of "Downgraded-" and the
   downgraded all-ASCII address. original name.  The non-ASCII address value
   field holds the original header field value.

   Any original header field value is treated as an unstructured value
   and it MUST be encoded by according to [RFC2047] with charset='UTF-8'.
   The header field syntax is specified as follows:

  fields     =/ edowngraded
   edowngraded = "Envelope-Downgraded:" [FWS] edowngraded-field unknown-downgraded-headers ":"
                                        [FWS] "<" uPath ">" [FWS]
                                        "<" Mailbox ">" [FWS] unstructued CRLF
   edowngraded-field
  unknown-downgraded-headers =  "From"  "Downgraded-" original-header-field-name
  original-header-field-name = field-name

  field-name      =       1*ftext

  ftext           =       %d33-57 / "To"

   Original non-ASCII address <uPath> is defined               ; Any character except
                          %d59-126                ;  controls, SP, and
                                                  ;  ":".

   Encapsulating a header field in
   [I-D.ietf-eai-smtpext]. <Mailbox> a Downgraded header field is defined in [RFC2821], section
   4.1.2.  The "Envelope-Downgraded:"
   as:
   1.  Generate new Downgraded header field whose value is encoded by
   [RFC2047] in the downgraded message.

4.  SMTP Downgrading

   Target of downgrading elements original header
       field value.

   2.  Encode the generated header field according to [RFC2047] with
       charset='UTF-8'.
   3.  Remove the original header field.

4.  SMTP Downgrading

   Target of downgrading elements in SMTP envelope are below:

   o  MAIL FROM:
   o  RCPT TO:
   o  ORCPT parameter

   Downgrading in the SMTP envelope uses ALT-ADDRESS parameter defined in
   [I-D.ietf-eai-smtpext].  An address is downgradable if the address is
   US-ASCII address or the
   non-ASCII address and has US-ASCII ASCII address specified by ALT-ADDRESS
   parameter.

   If each recipient  Since only non-ASCII addresses are downgradable,
   specifying an ALT-ADDRESS value for an all-ASCII address is invalid
   for use with this specification, and the return address no interpretation is downgradable, the
   SMTP assigned to
   it.  This restriction allows for future extension of the recipient is downgradable.

   Even
   specification even though no such extensions are currently
   anticipated.

   Note that even if no downgrading is performed for envelope from/to, MUA/MTA
   MUST downgrade on the envelope,
   message header fields and message body MIME header fields in the
   message body including that
   contain non-ASCII characters. characters MUST be downgraded.  This is described
   in Section 5 and Section 6.

   MTA replaces

   When downgrading, replace each non-ASCII mail address in the envelope
   with its specified alternative US- ASCII address when downgrading. and preserve the
   original information using "Downgraded-Mail-From" and "Downgraded-
   Rcpt-To" header fields as defined in Section 3.  Before replacing,
   decode the ALT-
   ADDRESS ALT-ADDRESS parameter value because it is encoded as xtest
   [RFC3461].
   Also MTA preserves original information using "Envelope-Downgraded"
   header defined in Section 3 with From or

   To field name.  The non-
   ASCII mail addresses are encoded by [RFC2047] and put into "Envelope-
   Downgraded" header.

   Not to disclose whole avoid disclosing recipient addresses, MUA/MTA the downgrading process MUST
   NOT add
   "Envelope-Downgraded: To:" "Downgraded-Rcpt-To:" header if the SMTP downgrading targets
   multiple recipients.  See Section 7 for more detail.

   While the recipient address downgrading, the

   The "RCPT TO" command may have an ORCPT parameter. parameter when the recipient
   address is downgraded.  The ORCPT parameter is used for DSN
   [RFC3461].  If the ORCPT parameter contains an "utf-8" address type
   address and
   the address contains non-ASCII characters, the ORCPT parameter MUST
   be converted to utf-8-addr-xtext form or utf-8-addr-
   unitext utf-8-addr-unitext form
   which is are described in [I-D.ietf-eai-dsn].

5.  Email header fields downgrading

   This section defines the conversion method to US-ASCII ASCII for each header
   field which may contain non-ASCII characters.

   [I-D.ietf-eai-utf8headers] expands Received: header fields, [RFC2822]
   ABNF elements <mailbox>, <word>, <comment>, <unstructured>, [RFC2045]
   ABNF element <value>.

   Header fields are
   listed field downgrading is defined below for each ABNF element.
   Downgrading an unknown header field is also defined as ENCAPSULATION
   downgrading.  Converting the header field terminates when no non-
   ASCII characters remain in [RFC4021]. the header field.

   RECEIVED downgrading:   If the whole mail header field name is "Received:" and
      the FOR clause contains a non-ASCII addresses, remove the FOR
      clause from the header field.  The other part except in the
      comments does not contain non-ASCII characters, email header field downgrading is not required. values.

   UNSTRUCTURED downgrading:   If the header field has an <unstructured>
      field which contains non-ASCII characters, convert encode the field
      according to [RFC2047] with charset='UTF-8'.

   WORD downgrading:   If the header
   field.  Each header field's downgrading method is described below.

   o  Downgrading Address header fields

      From:
      Sender:

      Reply-To:
      To:
      Cc:
      Bcc:
      Resent-From:
      Resent-Sender:
      Resent-To:
      Resent-Cc:

      The header field value is composed of single or multiple <angle-
      addr>/<utf8-addr-spec> has any <word> fields defined in
      [I-D.ietf-eai-utf8headers]. which
      contains non-ASCII characters, encode the fields according to
      [RFC2047] with charset='UTF-8'.

   COMMENT downgrading:   If the header field has no <angle-addr> or <utf8-addr-spec> any <comment> fields
      which contains non-ASCII characters, only "display-name" part or
      comments contain non-ASCII characters, encode the "display-name" or
      comments are encoded by fields according
      to [RFC2047] with charset='UTF-8'.
      Otherwise, preserve

   MIME-VALUE downgrading:   If the header field in "Downgraded:" header,
      generate US-ASCII only address header, has any <value>
      elements defined by [RFC2045] and replace the original elements contain non-ASCII
      characters, encode the <value> elements by [RFC2231] with
      charset='UTF-8' and the Language information empty.  If the
      <value> element is <quoted-string> and it contains <CFWS> outside
      the DQUOTE, remove the <CFWS> before this conversion.

   DISPLAY-NAME downgrading:   If the header field has any <mailbox>
      elements and they have <display-name> elements which contain non-
      ASCII characters, encode the <display-name> elements according to
      [RFC2047] with charset='UTF-8'.

   MAILBOX downgrading:   The <mailbox> elements have no equivalent
      format for non-ASCII addresses.  If the generated US-ASCII only header field.  New field has any
      <mailbox> elements which contain non-ASCII characters, preserve
      the header generation method are shown field in below.

      Extract every each Address header field preservation header
      defined in Section 3.2, and downgrade rewrite each <mailbox>/<angle-addr>/
      <utf8-addr-spec>.

      If the <mailbox> element to
      ASCII only format.  The <mailbox> element which contains non-ASCII address
      characters is in <utf8-addr-spec> form, then rewrite one of three formats.

      *  [ Display-name ] "<" Utf8-addr-spec 1*FCS "<" Addr-spec ">>"

         Rewrite it as

         [ Display-name ] "<" Addr-spec ">"

      *  [ Display-name ] "<" Utf8-addr-spec ">"
      *  Utf8-addr-spec

         Rewrite both as
         [ Display-name ] "Internationalized Address utf8-addr-spec-encoded
      Removed:;". "utf8-addr-spec" " Encoded-word
         " Removed:;"

         where the <Encoded-word> is the original <Utf8-addr-spec>
         encoded according to "utf8-addr-spec-
      encoded" by [RFC2047].

      The field may contain multiple <comment> fields.  The <comment>
      fields are encoded by [RFC2047] with charset='UTF-8',

   ENCAPSULATION downgrading:   if
      necessary.

      <mailbox> the header field contains non-ASCII
      characters and for which no rule is defined as "display-name <angle-addr>" given above, encapsulate it in
      [I-D.ietf-eai-utf8headers].  The "display-name"
      a Downgraded header field is encoded
      by [RFC2047] with charset='UTF-8', if necessary.

      The <angle-addr> may contain comments.  Before processing, remove
      comments from the <angle-addr>.

      UTF8SMTP <angle-addr> defined described in [I-D.ietf-eai-utf8headers]
      consists of 3 forms. Section 3.3 as a last
      resort.

5.1.  Downgrading method is defined for each form.

      *  <US-ASCII>
         <US-ASCII> is used as is.
      *  <non-ASCII>
         Non-ASCII header field

   Header fields are listed in [RFC4021].  This section describes the
   downgrading method for each header field.

   If the whole mail address without sender-specified US-ASCII
         address header field does not contain non-ASCII characters,
   email header field downgrading is replaced as
         "Internationalized not required.  Each header field's
   downgrading method is described below.

   o  Address non-ASCII-encoded Removed:;". header fields which contain <mailbox>s

      From:
      Sender:
      Reply-To:
      To:
      Cc:
      Bcc:
      Resent-From:
      Resent-Sender:

      Resent-To:
      Resent-Cc:
      Return-Path:

      If the header field contains <mailbox> elements which contains
      non-ASCII address is encoded to "non-ASCII-encoded" by
         [RFC2047].
      *  <non-ASCII <US-ASCII>>
         Non-ASCII mail address with sender-specified US-ASCII address
         MUST be replaced as "display-name <US-ASCII>". addresses, preserve the header field in a downgraded
      header before the conversion.  Then do COMMENT downgrading,
      DISPLAY-NAME downgrading and MAILBOX downgrading.

   o  Downgrading Non-ASCII in comments

      Date:
      Message-ID:
      In-Reply-To:
      References:
      Resent-Date:
      Resent-Message-ID:
      MIME-Version:
      Content-ID:

      These header fields do not contain non-ASCII characters except in
      comments.  If the header contains UTF-8 characters in comments,
      encode the header by [RFC2047] with charset='UTF-8'. do
      COMMENT downgrading.

   o  Trace header fields

      Received:

      If the FOR clause contains non-ASCII addresses, remove the FOR
      clause in the header.  The other part does not contain non-ASCII
      values.

      do COMMENT downgrading and do RECEIVED downgrading.

   o  MIME Content header fields

      Content-Type:
      Content-Disposition:

      Encode the header by [RFC2231] with charset='UTF-8'.

      Do MIME-VALUE downgrading.

   o  Unstructured text headers and structured text headers  Non-ASCII in <unstructured>

      Subject:
      Comments:
      Keywords:
      Content-Description:

      Encode the header by [RFC2047] with charset='UTF-8'.

      Do UNSTRUCTURED downgrading.

   o  URI headers

      List-Archive:
      List-Help:
      List-Owner:
      List-Post:
      List-Subscribe:
      List-Unsubscribe:

      If the header contains UTF-8 characters in comments, encode the
      header by [RFC2047] with charset='UTF-8'.  If the header contains
      UTF-8 characters  Non-ASCII in URI, Encode the URI by [RFC3987]. <unstructured> or <phrase>
      Keywords:

      Do WORD downgrading.

   o  Other target headers header fields

      All other headers header fields which contains non-ASCII characters are
      preserved in Downgraded: header and removed.

   o  ASCII only headers

      Content-Transfer-Encoding:

      This header is not target of downgrading.

   Downgraded header fields should be inserted
      user-defined, missing from this draft or replaced at the same
   position of the original future defined header field.
      fields.  Do ENCAPSULATION downgrading as a last resort.

6.  MIME body part headers downgrading

   MIME body part header fields may contain non-ASCII characters
   [I-D.ietf-eai-utf8headers].  This section defines the conversion
   method to US-ASCII ASCII only header fields for each MIME header field which may contain
   contains non-ASCII characters.  Parse the message body's MIME
   structure for all level levels and check all each MIME header fields field whether it
   contains non-ASCII characters.  If the header field contains non-ASCII non-
   ASCII characters in the header value, the header is a target of the
   MIME body part headers downgrading.  Each MIME header field's
   downgrading method is described below: below.  COMMENT downgrading, MIME-
   VALUE downgrading, UNSTRUCTURED downgrading are described in
   Section 5.

   Content-ID:
      The Content-ID: header does not contain non-ASCII characters
      except in comments.  If the header contains UTF-8 characters in
      comments, encode the header by [RFC2047] with charset='UTF-8'. do COMMENT downgrading.

   Content-Type:
   Content-Disposition:
      Encode the header by [RFC2231] with charset='UTF-8'.
      Do MIME-VALUE downgrading.

   Content-Description:
      Encode the header by [RFC2047] with charset='UTF-8'.

   Content-Transfer-Encoding:
      This
      Do UNSTRUCTURED downgrading.

7.  Security considerations

   o  A Downgraded message's header does not fields contain ASCII characters
      only.  But they still contain MIME encapsulated header fields
      which contains non-ASCII UTF-8 characters.

7.  Security considerations  And more, the body
      part may contain UTF-8 message.  The recipients need to accept
      UTF-8 mail body and UTF-8 header fields which is MIME encoded.

   o  Rewriting headers increases the opportunities for undetected
      spoofing.

   o  Recipients addresses can be undisclosed if those addresses are
      listed on Bcc or group address.  Those undisclosed addresses are
      used only in the Envelope.  Copying information from the Envelope
      into headers creates some risk of risks inadvertent information disclosure (not just
      about addresses).  See Section 4 for instructions on recipient
      address handling.

   o  It is likely that the  The techniques suggested described here will invalidate invalidates methods that depend on
      signatures over headers the envelope or any part of the envelope.
      "Issues" does talk about message which
      includes the top-level header or body part headers.  Depending on
      the specific message being downgraded, DKIM especially, but also
      possibly S/MIME, PGP, and similar techniques are all likely to
      break.

   o  Many gateways and servers on the Internet will discard headers
      with which they are not familiar.  To the extent to which the
      downgrade procedures depend on new headers (e.g., "Downgraded") to
      avoid information loss, then the risk of having those headers
      dropped and its implications must be identified.  In particular,
      it appears to me that, but, because if the Downgraded headers are dropped,
      there is no possibility of reconstructing the original information
      at any point (before, during, or after delivery).

   See "Security considerations" section in [RFC4952] for more
   discussion.

8.  Implementation notes

   Downgrading is an alternative to rejection for delivering messages
   which require UTF8SMTP support to a server which does not provide
   this.  Implementing the full specification of this document strongly
      implies that one can downgrade and then upgrade again with no risk
      of loss of information, the topic should be explored further.
   o  Many gateways and servers on the Internet will discard headers
      with which they are not familiar.  To the extent to which the
      downgrade procedures depend on new headers (e.g., "Downgraded") to
      avoid information loss, then the risk of having those headers
      dropped and its implications must be identified.  In particular,
      it appears to me that, if the Downgraded headers are dropped,
      there is no possibility of reconstructing the original information
      at any point (before, during, or after delivery).

   See "Security considerations" section in [I-D.ietf-eai-framework] for
   more discussion.

8.  IANA Considerations

   IANA is requested to register the following header fields in the
   Permanent Message is
   desirable, but a partial implementation is also possible.

   If a partial downgrading implementation confronts an unsupported
   downgrading target, the implementation MUST NOT send the message to
   server which does not support UTF8SMTP.  Instead, it MUST reject the
   message or generate a notification of non-deliverability.

8.1.  Trivial downgrading

   A partial downgrading, Trivial downgrading is discussed.  It does not
   support non-ASCII addresses in SMTP envelope and address header
   fields, unknown header fields downgrading, the MIME body part headers
   downgrading.  It supports
   o  some simple header fields downgrading: Subject
   o  comments and display name downgrading: From, To, CC
   o  trace header field downgrading: Received

   Otherwise, the downgrading fails.

   Trivial downgrading targets mail messages which are generated by
   UTF8SMTP aware MUAs and contain non-ASCII characters in comments,
   display names, unstructured parts without using non-ASCII E-mail
   addresses.  This E-mail message does not contain non-ASCII addresses
   in SMTP Envelope and its header fields.  But it is not deliverable
   via UTF8SMTP un-aware MTA.  Implementing full spec downgrading may be
   hard, but trivial downgrading saves mail messages without using non-
   ASCII addresses.

9.  IANA Considerations

   IANA is requested to register the following header fields in the
   Permanent Message Header Field Repository, in accordance with the
   procedures set out in [RFC3864].

   Header field name:  Downgraded-Mail-From
   Applicable protocol:  mail
   Status:  experimental
   Author/change controller:  IETF
   Specification document(s):  This document (Section 3)

   Header field name:  Downgraded-Rcpt-To
   Applicable protocol:  mail
   Status:  experimental
   Author/change controller:  IETF
   Specification document(s):  This document (Section 3)

   Header field name:  Downgraded-From
   Applicable protocol:  mail
   Status:  experimental
   Author/change controller:  IETF
   Specification document(s):  This document (Section 3)

   Header field name:  Downgraded-Sender
   Applicable protocol:  mail
   Status:  experimental
   Author/change controller:  IETF
   Specification document(s):  This document (Section 3)

   Header field name:  Downgraded-To
   Applicable protocol:  mail
   Status:  experimental
   Author/change controller:  IETF
   Specification document(s):  This document (Section 3)

   Header field name:  Downgraded-Cc
   Applicable protocol:  mail
   Status:  experimental
   Author/change controller:  IETF
   Specification document(s):  This document (Section 3)

   Header field name:  Downgraded-Reply-To
   Applicable protocol:  mail
   Status:  experimental
   Author/change controller:  IETF
   Specification document(s):  This document (Section 3)

   Header field name:  Downgraded-Bcc
   Applicable protocol:  mail
   Status:  experimental
   Author/change controller:  IETF
   Specification document(s):  This document (Section 3)

   Header Field Repository, in accordance with the
   procedures set out in [RFC3864]. field name:  Downgraded-Resent-From
   Applicable protocol:  mail
   Status:  experimental
   Author/change controller:  IETF
   Specification document(s):  This document (Section 3)

   Header field name:  Downgraded  Downgraded-Resent-To
   Applicable protocol:  mail
   Status:  experimental
   Author/change controller:  IETF
   Specification document(s):  This document (Section 3)

   Header field name:  Envelope-Downgraded  Downgraded-Resent-Cc
   Applicable protocol:  mail
   Status:  experimental
   Author/change controller:  IETF
   Specification document(s):  This document (Section 3)

9.
   Header field name:  Downgraded-Resent-Sender
   Applicable protocol:  mail
   Status:  experimental
   Author/change controller:  IETF
   Specification document(s):  This document (Section 3)

   Header field name:  Downgraded-Return-Path
   Applicable protocol:  mail
   Status:  experimental
   Author/change controller:  IETF
   Specification document(s):  This document (Section 3)

   And more, IANA is requested to reserve all the field names that start
   by "Downgraded-" for unknown header fields downgrading described in
   Section 3.3, in accordance with the procedures set out in [RFC3864].

   Header field name:  Names which starts by "Downgraded-"
   Applicable protocol:  mail
   Status:  experimental
   Author/change controller:  IETF
   Specification document(s):  This document (Section 3)

10.  Acknowledgements

   Significant comments and suggestions were received from John Klensin,
   Harald Alvestrand, Chris Newman, Randall Gellens, Charles Lindsey,
   Marcos Sanz, Alexey Melnikov, Frank Ellermann Ellermann, Edward Lewis, S.
   Moonesamy and JET members.

10.

11.  Change History

   This section is used for tracking the update of this document.  Will
   be removed after finalize.

10.1.

11.1.  draft-yoneya-ima-downgrade: Version 00

   o  Initial version
   o  Followed draft-yeh-ima-utf8headers-00 and draft-yao-smtpext-00

10.2.

11.2.  draft-yoneya-ima-downgrade: Version 01

   o  Document structure was changed
   o  Followed draft-yeh-ima-utf8headers-01 and draft-yao-smtpext-02
   o  Downgrading requirements were added
   o  SMTP DATA encapsulation method was proposed
   o  Downgrading examples was provided

10.3.

11.3.  draft-ietf-eai-downgrade: Version 00

   o  Followed draft-yeh-ima-utf8headers-01 and
      draft-ietf-eai-smtpext-00
   o  No header downgrading method was proposed
   o  Header encapsulation method was proposed

10.4.

11.4.  draft-ietf-eai-downgrade: Version 01

   o  Followed draft-ietf-eai-utf8headers-00
   o  Header conversion and encapsulation method was merged
   o  Header conversion method was defined in detail

10.5.

11.5.  draft-ietf-eai-downgrade: Version 02

   o  Followed draft-ietf-eai-utf8headers-01 and
      draft-ietf-eai-smtpext-01
   o  Specification about algorithmic generated address is removed
   o  No header downgrading method was removed
   o  SMTP DATA encapsulation method was removed

10.6.

11.6.  draft-ietf-eai-downgrade: Version 03

   o  Followed draft-ietf-eai-utf8headers-03 and
      draft-ietf-eai-smtpext-03
   o  Downgraded: and Envelope-Downgraded: headers definition was added
   o  Mail header fields downgrading method was refined
   o  Examples in Appendix A were refined

10.7.

11.7.  draft-ietf-eai-downgrade: Version 04

   o  Followed draft-ietf-eai-utf8headers-06, draft-ietf-eai-smtpext-07
      and draft-ietf-eai-dsn-02
   o  Downgrading requirements and conditions were moved to
      Introduction.
   o  Descriptions about upgrading were removed.
   o  SPF and DKIM discussion were removed.
   o  Added many header fields downgrading.
   o  Allow address literal rewriting without alternate US-ASCII ASCII address in
      header fields.
   o  Added MIME body part headers downgrading. downgrading.
   o  Added ORCPT downgrading.

11.8.  draft-ietf-eai-downgrade: Version 05

   o  fixed examples
      *  ALT-ADDRESS parameter mistake
      *  RFC2047(x) notation was changed to encoded-word format
   o  Added implementation consideration section and trivial downgrading
   o  Downgraded: and Envelope-Downgraded: headers are separated for
      each original headers.
   o  Added ORCPT downgrading.

11.  Removed list-* header fields downgrading
   o  Changed the way of writing the header field downgrading section

12.  Normative References

   [I-D.ietf-eai-dsn]
              Newman, C. and A. Melnikov, "International Delivery and
              Disposition Notifications", draft-ietf-eai-dsn-02 (work in
              progress), July 2007.

   [I-D.ietf-eai-framework]
              Klensin, J. and Y. Ko, "Overview and Framework for
              Internationalized Email", draft-ietf-eai-framework-05 draft-ietf-eai-dsn-05 (work in
              progress), February November 2007.

   [I-D.ietf-eai-smtpext]
              Yao, J. and W. Mao, "SMTP extension for internationalized
              email address", draft-ietf-eai-smtpext-07 draft-ietf-eai-smtpext-09 (work in
              progress), June November 2007.

   [I-D.ietf-eai-utf8headers]
              Yeh, J., "Internationalized Email Headers",
              draft-ietf-eai-utf8headers-05
              draft-ietf-eai-utf8headers-07 (work in progress),
              April
              September 2007.

   [RFC2045]  Freed, N. and N. Borenstein, "Multipurpose Internet Mail
              Extensions (MIME) Part One: Format of Internet Message
              Bodies", RFC 2045, November 1996.

   [RFC2047]  Moore, K., "MIME (Multipurpose Internet Mail Extensions)
              Part Three: Message Header Extensions for Non-ASCII Text",
              RFC 2047, November 1996.

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC2183]  Troost, R., Dorner, S., and K. Moore, "Communicating
              Presentation Information in Internet Messages: The
              Content-Disposition Header Field", RFC 2183, August 1997.

   [RFC2231]  Freed, N. and K. Moore, "MIME Parameter Value and Encoded
              Word Extensions:
              Character Sets, Languages, and Continuations", RFC 2231,
              November 1997.

   [RFC2821]  Klensin, J., "Simple Mail Transfer Protocol", RFC 2821,
              April 2001.

   [RFC2822]  Resnick, P., "Internet Message Format", RFC 2822,
              April 2001.

   [RFC3461]  Moore, K., "Simple Mail Transfer Protocol (SMTP) Service
              Extension for Delivery Status Notifications (DSNs)",
              RFC 3461, January 2003.

   [RFC3864]  Klyne, G., Nottingham, M., and J. Mogul, "Registration
              Procedures for Message Header Fields", BCP 90, RFC 3864,
              September 2004.

   [RFC3987]  Duerst, M. and M. Suignard, "Internationalized Resource
              Identifiers (IRIs)", RFC 3987, January 2005.

   [RFC4021]  Klyne, G. and J. Palme, "Registration of Mail and MIME
              Header Fields", RFC 4021, March 2005.

   [RFC4952]  Klensin, J. and Y. Ko, "Overview and Framework for
              Internationalized Email", RFC 4952, July 2007.

Appendix A.  Displaying downgraded message

   A perfect reverse-function of the downgrading does not exist because
   the encoding defined in [RFC2047] is not exactly reversible.  The
   restoration of the downgrading should be done once at the final
   destination of the downgraded message such as MUAs or IMAP servers.
   This document describes the restoration methods as displaying
   technique.

   Displaying downgraded message is mostly retrieved by MIME decoding
   [RFC2047][RFC2231].
   according to [RFC2047] and [RFC2231].  Result of MIME decoding,
   downgraded address
   header fields and undefined header fields are still in Downgraded:
   headers, Downgraded-*: header fields,
   but it is the header field values are MIME decoded.  This  These decoded Downgraded: headers
   Downgraded-*: header fields contain the original headers header field values
   and the recipient can read them.  But the recipient's MUA cannot use
   the original header fields automatically.

   Additionally, MUAs can decode Downgraded: process Downgraded-*: header.  It is described
   in Appendix A.1 and Appendix A.2.

A.1.  Displaying technique 1

   MUA can remove 'Downgraded:' 'Downgraded-' from decoded 'Downgraded:' 'Downgraded-*:' header
   fields.
   fields' name.  With this technique, The address header fields may be
   displayed twice, one is ASCII-only downgraded header field and the
   other is from decoded Downgraded: Downgraded-*: header.

A.2.  Displaying technique 2

   MUA can decode and regenerate headers which contains the original
   non-ASCII addresses.  It is described below:
   o  For each Downgraded: header, Downgraded-*: header field, generate new header field
      which field-name
      is the second field of name is the Downgraded: original header name and the header field value
      is the third decoded header field of the Downgraded: header. value.
      *  If the header is an address header described in Section 5,
         +  Generate ASCII only header fields defined in Section 5 from
            the decoded header. header fields without re-generating
            Downgraded-*: header fields.
         +  Remove the header field which is the same with the generated
            ASCII only header from the header fields.  If the headers
            contain  This comparison
            requires considerations for foldings and [RFC2047] encoded part, decode it before comparison.
            parts.

Appendix B.  Examples

B.1.  Downgrading example 1

   This section shows an SMTP Downgrading example.  Consider a
   downgradable mail
   message.
   o  The sender address is "NON-ASCII-FROM" "NON-ASCII-local@example.com" which is non-ASCII non-
      ASCII address.  Its ASCII alternative is "ASCII-FROM". "ASCII-local@example.com"
      and its display-name is "DISPLAY-local".
   o  The "To" address is "NON-ASCII-TO" "NON-ASCII-remote1@example.net" which is non-ASCII non-
      ASCII address.  Its ASCII alternative is "ASCII-TO".
      "ASCII-remote1@example.net" and its display-name is "DISPLAY-
      remote1".
   o  The "CC" address is non-ASCII address "NON-ASCII-CC"
      "NON-ASCII-remote2@example.org" without alternative US-ASCII ASCII address.
      Its display-name is "DISPLAY-remote2".
   o  Three display-names contains non-ASCII characters.
   o  The Subject header is "NON-ASCII-SUBJECT" which contains non-ASCII
      characters.

   Original UTF8SMTP message
   o  assume To: recipient's MTA (example.net) does not support
      UTF8SMTP.
   o  assume Cc: recipient's MTA (example.org) supports UTF8SMTP.
   The example SMTP envelope/message is showin in Figure 4.  In this
   example, the To: recipient's session is fucused.

   MAIL From: <NON-ASCII-FROM> ALT-ADDRESS <ASCII-FROM> <NON-ASCII-local@example.com>
               ALT-ADDRESS=ASCII-local@example.com
   RCPT TO: <NON-ASCII-TO> ALT-ADDRESS <ASCII-TO> <NON-ASCII-remote1@example.net>
             ALT-ADDRESS=ASCII-remote1@example.net
   RCPT TO: <NON-ASCII-CC> <NON-ASCII-remote2@example.org>
   -------------------------------------------------------------
   Message-Id: MESSAGE_ID
   Mime-Version: 1.0
   Content-Type: text/plain; charset="UTF-8"
   Content-Transfer-Encoding: 8bit
   Subject: NON-ASCII-SUBJECT
   From: <NON-ASCII-FROM <ASCII-FROM>> DISPLAY-local <NON-ASCII-local@example.com
    <ASCII-local@example.com>>
   To: <NON-ASCII-TO <ASCII-TO>> DISPLAY-remote1 <NON-ASCII-remote1@example.net
    <ASCII-remote1@example.net>>
   CC: <NON-ASCII-CC> DISPLAY-remote2 <NON-ASCII-remote2@example.org>
   Date: DATE

   MAIL_BODY

              Figure 3: 4: Original UTF8SMTP message envelope/message (example 1)

   In this example, there are two SMTP recipients, one is To:, the other
   is CC:.  In this example, assume the Cc: recipient's MTA supports
   UTF8SMTP and SMTP recipients, one is To:, the To: recipient's MTA does not support UTF8SMTP. other
   is CC:.  The SMTP downgrading treats To: session downgrading.
   Figure 4 5 shows SMTP downgraded example.

   MAIL From: <ASCII-FROM> <ASCII-local@example.com>
   RCPT TO: <ASCII-TO> <ASCII-remote1@example.net>
   -------------------------------------------------------------
   Envelope-Downgraded: From: <RFC2047(NON-ASCII-FROM)> <ASCII-FROM>
   Envelope-Downgraded: To: <RFC2047(NON-ASCII-TO)> <ASCII-TO>
   Downgraded-Mail-From: =?UTF-8?Q?<NON-ASCII-local@example.com>?=
    <ASCII-local@example.com>
   Downgraded-Rcpt-To: =?UTF-8?Q?<NON-ASCII-remote1@example.net>?=
    <ASCII-remote1@example.net>
   Message-Id: MESSAGE_ID
   Mime-Version: 1.0
   Content-Type: text/plain; charset="UTF-8"
   Content-Transfer-Encoding: 8bit
   Subject: NON-ASCII-SUBJECT
   From: <NON-ASCII-FROM <ASCII-FROM>> DISPLAY-local <NON-ASCII-local@example.com
    <ASCII-local@example.com>>
   To: <NON-ASCII-TO <ASCII-TO>> DISPLAY-remote1 <NON-ASCII-remote1@example.net
    <ASCII-remote1@example.net>>
   CC: <NON-ASCII-CC> DISPLAY-remote2 <NON-ASCII-remote2@example.org>
   Date: DATE

   MAIL_BODY

          Figure 4: 5: SMTP Downgraded UTF8SMTP message envelope/message (example 1)

   After SMTP downgrading, header fields downgrading is performed.
   Final downgraded messages are message is shown in Figure 5. 6.  Return-Path header
   will be added by the final destination MTA.

   Result of the header downgrading.

Return-Path: <ASCII-FROM>
   Envelope-Downgraded: From: <RFC2047(NON-ASCII-FROM)> <ASCII-FROM>
   Envelope-Downgraded: To: <RFC2047(NON-ASCII-TO)> <ASCII-TO> <ASCII-local@example.com>
Downgraded-Mail-From: =?UTF-8?Q?<NON-ASCII-local@example.com>?=
 <ASCII-local@example.com>
Downgraded-Rcpt-To: =?UTF-8?Q?<NON-ASCII-remote1@example.net>?=
 <ASCII-remote1@example.net>
Message-Id: MESSAGE_ID
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Subject: RFC2047(UTF-8_SUBJECT)
   Downgraded: =?UTF-8?Q?NON-ASCII-SUBJECT?=
Downgraded-From: =?UTF-8?Q?DISPLAY-local?=
 =?UTF-8?Q?<NON-ASCII-local@example.com?= <ASCII-local@example.com>>
From: RFC2047(<NON-ASCII-FROM <ASCII-FROM>>)
   From: <ASCII-FROM>
   Downgraded: =?UTF-8?Q?DISPLAY-local?= <ASCII-local@example.com>
To: RFC2047(<NON-ASCII-TO <ASCII-TO>>)
   To: <ASCII-TO>
   Downgraded: CC: RFC2047(<NON-ASCII-CC>) =?UTF-8?Q?DISPLAY-remote1?= <ASCII-remote1@example.net>
Downgraded-To: =?UTF-8?Q?DISPLAY-remote1?=
 =?UTF-8?Q?<NON-ASCII-remote1@example.net?= <ASCII-remote1@example.net>>
CC: =?UTF-8?Q?DISPLAY-remote2?= Internationalized address RFC2047(NON-ASCII-CC)
 =?UTF-8?Q?NON-ASCII-remote2@example.org?= removed:;
Downgraded-CC: =?UTF-8?Q?DISPLAY-remote2?=
 =?UTF-8?Q?<NON-ASCII-remote2@example.org>?=
Date: DATE

MAIL_BODY

                 Figure 5: Header downgraded 6: Downgraded message
   RFC2047() stands for [RFC2047] encoding. (example 1)

B.2.  Displaying example (Displaying technique 1)

   This example

   Figure 7 shows MIME decoded message of Figure 5.

   Result of MIME decoding. 6.

   Return-Path: <ASCII-FROM>
   Envelope-Downgraded: <ASCII-local@example.com>
   Downgraded-Mail-From: <NON-ASCII-local@example.com>
    <ASCII-local@example.com>
   Downgraded-Rcpt-To: <NON-ASCII-remote1@example.net>
    <ASCII-remote1@example.net>
   Message-Id: MESSAGE_ID
   Mime-Version: 1.0
   Content-Type: text/plain; charset="UTF-8"
   Content-Transfer-Encoding: 8bit
   Subject: NON-ASCII-SUBJECT
   Downgraded-From: DISPLAY-local<NON-ASCII-local@example.com
    <ASCII-local@example.com>>
   From: <NON-ASCII-FROM> <ASCII-FROM>
   Envelope-Downgraded: DISPLAY-local <ASCII-local@example.com>
   Downgraded-To: DISPLAY-remote1<NON-ASCII-remote1@example.net
    <ASCII-remote1@example.net>>
   To: <NON-ASCII-TO> <ASCII-TO> DISPLAY-remote1 <ASCII-remote1@example.net>
   Downgraded-CC: DISPLAY-remote2<NON-ASCII-remote2@example.org>
   CC: DISPLAY-remote2 Internationalized address
    NON-ASCII-remote2@example.org removed:;
   Date: DATE

   MAIL_BODY

                      Figure 7: MIME decoded message

B.2.1.  Displaying technique 1 example
   After removing 'Downgraded-' from decoded 'Downgraded-*:' header
   fields

   Return-Path: <ASCII-local@example.com>
   Downgraded-Mail-From: <NON-ASCII-local@example.com>
    <ASCII-local@example.com>
   Downgraded-Rcpt-To: <NON-ASCII-remote1@example.net>
    <ASCII-remote1@example.net>
   Message-Id: MESSAGE_ID
   Mime-Version: 1.0
   Content-Type: text/plain; charset="UTF-8"
   Content-Transfer-Encoding: 8bit
   Subject: UTF-8_SUBJECT
   Downgraded: NON-ASCII-SUBJECT
   From: <NON-ASCII-FROM <ASCII-FROM>> DISPLAY-local<NON-ASCII-local@example.com
    <ASCII-local@example.com>>
   From: <ASCII-FROM>
   Downgraded: DISPLAY-local <ASCII-local@example.com>
   To: <NON-ASCII-TO <ASCII-TO>> DISPLAY-remote1<NON-ASCII-remote1@example.net
    <ASCII-remote1@example.net>>
   To: <ASCII-TO>
   Downgraded: DISPLAY-remote1 <ASCII-remote1@example.net>
   CC: <NON-ASCII-CC> DISPLAY-remote2<NON-ASCII-remote2@example.org>
   CC: DISPLAY-remote2 Internationalized address NON-ASCII-CC
    NON-ASCII-remote2@example.org removed:;
   Date: DATE

   MAIL_BODY

                     Figure 6: MIME decoded message

B.3. 8: Displaying example (Displaying technique 2) 1

B.2.2.  Displaying technique 2 example

   This example shows displaying process of Appendix A.2 for Figure 5. 6.

   First, check 'Downgraded:' downgraded address header fields existence.

   Select 'Downgraded:' headers.

   Downgraded: From: <NON-ASCII-FROM <ASCII-FROM>>
   Downgraded: To: <NON-ASCII-TO <ASCII-TO>>
   Downgraded: CC: <NON-ASCII-CC>

Downgraded-From: =?UTF-8?Q?DISPLAY-local?=
 =?UTF-8?Q?<NON-ASCII-local@example.com?= <ASCII-local@example.com>>
Downgraded-To: =?UTF-8?Q?DISPLAY-remote1?=
 =?UTF-8?Q?<NON-ASCII-remote1@example.net?= <ASCII-remote1@example.net>>
Downgraded-CC: =?UTF-8?Q?DISPLAY-remote2?=
 =?UTF-8?Q?<NON-ASCII-remote2@example.org>?=

   Figure 7: 9: Displaying technique 2: selecting Downgraded headers
   Apply downgraded address header
                                  fields
   Then, decode MIME encoded parts.

   Downgraded-From: DISPLAY-local<NON-ASCII-local@example.com
    <ASCII-local@example.com>>
   Downgraded-To: DISPLAY-remote1<NON-ASCII-remote1@example.net
    <ASCII-remote1@example.net>>
   Downgraded-CC: DISPLAY-remote2<NON-ASCII-remote2@example.org>

    Figure 10: Displaying technique 2: decode downgraded address header
                                  fields

   Apply header fields downgrading to the decoded header without re-
   generating Downgraded-*: header.

   From: <ASCII-FROM> =?UTF-8?Q?DISPLAY-local?= <ASCII-local@example.com>
   To: <ASCII-TO> =?UTF-8?Q?DISPLAY-remote1?= <ASCII-remote1@example.net>
   CC: =?UTF-8?Q?DISPLAY-remote2?= Internationalized address RFC2047(NON-ASCII-CC)
    =?UTF-8?Q?NON-ASCII-remote2@example.org?= removed:;

   Figure 8: 11: Displaying technique 2: downgraded decoded Downgraded
                                  headers 'Downgraded-*:'

   Remove the header line fields which is the same with the downgraded line.
   If the headers contain [RFC2047] encoded part, decode it before
   comparison. Figure 11 from
   Figure 6.

Return-Path: <ASCII-FROM>
   Envelope-Downgraded: From: <NON-ASCII-FROM> <ASCII-FROM>
   Envelope-Downgraded: To: <NON-ASCII-TO> <ASCII-TO> <ASCII-local@example.com>
Downgraded-Mail-From: =?UTF-8?Q?<NON-ASCII-local@example.com>?=
 <ASCII-local@example.com>
Downgraded-Rcpt-To: =?UTF-8?Q?<NON-ASCII-remote1@example.net>?=
 <ASCII-remote1@example.net>
Message-Id: MESSAGE_ID
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Subject: UTF-8_SUBJECT
   Downgraded: From: <NON-ASCII-FROM <ASCII-FROM>>
   Downgraded: To: <NON-ASCII-TO <ASCII-TO>>
   Downgraded: CC: <NON-ASCII-CC <ASCII-CC>> =?UTF-8?Q?NON-ASCII-SUBJECT?=
Downgraded-From: =?UTF-8?Q?DISPLAY-local?=
 =?UTF-8?Q?<NON-ASCII-local@example.com?= <ASCII-local@example.com>>
Downgraded-To: =?UTF-8?Q?DISPLAY-remote1?=
 =?UTF-8?Q?<NON-ASCII-remote1@example.net?= <ASCII-remote1@example.net>>
Downgraded-CC: =?UTF-8?Q?DISPLAY-remote2?=
 =?UTF-8?Q?<NON-ASCII-remote2@example.org>?=
Date: DATE

MAIL_BODY

      Figure 9: 12: Displaying technique 2: Removing duplicated headers

   Decode each 'Downgraded' header and replace it with its decoded
   header.  If each mail header has [RFC2047] encoded part and which
   encoding is "UTF-8", it is a downgraded header, so decode it.

   Return-Path: <ASCII-FROM>
   Envelope-Downgraded: From: <NON-ASCII-FROM> <ASCII-FROM>
   Envelope-Downgraded: To: <NON-ASCII-TO> <ASCII-TO> <ASCII-local@example.com>
   Downgraded-Mail-From: <NON-ASCII-local@example.com>
    <ASCII-local@example.com>
   Downgraded-Rcpt-To: <NON-ASCII-remote1@example.net>
    <ASCII-remote1@example.net>
   Message-Id: MESSAGE_ID
   Mime-Version: 1.0
   Content-Type: text/plain; charset="UTF-8"
   Content-Transfer-Encoding: 8bit
   Subject: UTF-8_SUBJECT NON-ASCII-SUBJECT
   From: <NON-ASCII-FROM <ASCII-FROM>> DISPLAY-local<NON-ASCII-local@example.com
    <ASCII-local@example.com>>
   To: <NON-ASCII-TO <ASCII-TO>> DISPLAY-remote1<NON-ASCII-remote1@example.net
    <ASCII-remote1@example.net>>
   CC: <NON-ASCII-CC <ASCII-CC>> DISPLAY-remote2<NON-ASCII-remote2@example.org>
   Date: DATE

   MAIL_BODY
              Figure 10: 13: Display technique 2: decoded message

   As a result, in this simple example, all original header fields are
   displayed in the original form.

B.4.

B.3.  Downgrading example 2

   In many cases, the sender wants to use non-ASCII address and address, the
   recipient does not support UTF8SMTP and does not have non-ASCII
   address.
   o  The sender address is "NON-ASCII-FROM" "NON-ASCII-local@example.com" which is non-ASCII non-
      ASCII address.  Its ASCII alternative is "ASCII-FROM".
      "ASCII-local@example.com".  It has a display-name "DISPLAY-local"
      which contains non-ASCII characters.
   o  The "To" address is "ASCII-TO" "ASCII-remote1@example.net" which is ASCII
      only.  It has a display-name "DISPLAY-remote1" which contains non-
      ASCII characters.
   o  The Subject header is "NON-ASCII-SUBJECT" which contains non-ASCII
      characters.

   Original UTF8SMTP message SMTP session
   The second example envelope/message is shown in Figure 14.

   MAIL From: <NON-ASCII-FROM> ALT-ADDRESS <ASCII-FROM> <NON-ASCII-local@example.com>
               ALT-ADDRESS=ASCII-local@example.com
   RCPT TO: <ASCII-TO> <ASCII-remote1@example.net>
   -------------------------------------------------------------
   Message-Id: MESSAGE_ID
   Mime-Version: 1.0
   Content-Type: text/plain; charset="UTF-8"
   Content-Transfer-Encoding: 8bit
   Subject: NON-ASCII-SUBJECT
   From: <NON-ASCII-FROM <ASCII-FROM>> DISPLAY-local <NON-ASCII-local@example.com
    <ASCII-local@example.com>>
   To: <ASCII-TO> DISPLAY-remote1 <ASCII-remote1@example.net>
   Date: DATE

   MAIL_BODY

                  Figure 11: 14: Original UTF8SMTP message 2 (example 2)

   In this example, SMTP session is downgradable.  Figure 12 15 shows SMTP
   downgraded example. envelope/message.

   MAIL From: <ASCII-FROM> <ASCII-local@example.com>
   RCPT TO: <ASCII-TO> <ASCII-remote1@example.net>
   -------------------------------------------------------------
   Envelope-Downgraded: From: <RFC2047(NON-ASCII-FROM)> <ASCII-FROM>
   Downgraded-Mail-From: =?UTF-8?Q?<NON-ASCII-local@example.com>?=
    <ASCII-local@example.com>
   Message-Id: MESSAGE_ID
   Mime-Version: 1.0
   Content-Type: text/plain; charset="UTF-8"
   Content-Transfer-Encoding: 8bit
   Subject: NON-ASCII-SUBJECT
   From: <NON-ASCII-FROM <ASCII-FROM>> DISPLAY-local <NON-ASCII-local@example.com
    <ASCII-local@example.com>>
   To: <ASCII-TO> DISPLAY-remote1 <ASCII-remote1@example.net>
   Date: DATE

   MAIL_BODY

          Figure 12: 15: SMTP Downgraded UTF8SMTP message 2 envelope/message (example 2)

   After SMTP downgrading, header fields downgrading is performed.  The
   downgraded example is shown in Figure 13.

   Envelope-Downgraded: From: <RFC2047(NON-ASCII-FROM)> <ASCII-FROM> 16.

   Return-Path: <ASCII-local@example.com>
   Downgraded-Mail-From: =?UTF-8?Q?<NON-ASCII-local@example.com>?=
    <ASCII-local@example.com>
   Message-Id: MESSAGE_ID
   Mime-Version: 1.0
   Content-Type: text/plain; charset="UTF-8"
   Content-Transfer-Encoding: 8bit
   Subject: RFC2047(UTF-8_SUBJECT)
   Downgraded: From: RFC2047(<NON-ASCII-FROM <ASCII-FROM>>) =?UTF-8?Q?NON-ASCII-SUBJECT?=
   Downgraded-From: =?UTF-8?Q?DISPLAY-local?=
    =?UTF-8?Q?<NON-ASCII-local@example.com?= <ASCII-local@example.com>>
   From: <ASCII-FROM> =?UTF-8?Q?DISPLAY-local?= <ASCII-local@example.com>
   To: <ASCII-TO> =?UTF-8?Q?DISPLAY-remote1?= <ASCII-remote1@example.net>
   Date: DATE

   MAIL_BODY

                 Figure 13: Header downgraded 16: Downgraded message 2 (example 2)

Authors' Addresses

   Yoshiro YONEYA (editor)
   JPRS
   Chiyoda First Bldg. East 13F, 3-8-1 Nishi-Kanda
   Chiyoda-ku, Tokyo  101-0065
   Japan

   Phone: +81 3 5215 8451
   Email: yone@jprs.co.jp

   Kazunori Fujiwara (editor)
   JPRS
   Chiyoda First Bldg. East 13F, 3-8-1 Nishi-Kanda
   Chiyoda-ku, Tokyo  101-0065
   Japan

   Phone: +81 3 5215 8451
   Email: fujiwara@jprs.co.jp

Full Copyright Statement

   Copyright (C) The IETF Trust (2007).

   This document is subject to the rights, licenses and restrictions
   contained in BCP 78, and except as set forth therein, the authors
   retain all their rights.

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
   THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
   OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
   THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Intellectual Property

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at
   ietf-ipr@ietf.org.

Acknowledgment

   Funding for the RFC Editor function is provided by the IETF
   Administrative Support Activity (IASA).