Internationalized Email Headers
RFC 5335

Approval announcement
Draft of message to be sent after approval:

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Internet Architecture Board <iab@iab.org>,
    RFC Editor <rfc-editor@rfc-editor.org>, 
    eai mailing list <ima@ietf.org>, 
    eai chair <eai-chairs@tools.ietf.org>
Subject: Document Action: 'SMTP extension for internationalized 
         email address' to Experimental RFC 

The IESG has approved the following documents:

- 'Internationalized Email Headers '
   <draft-ietf-eai-utf8headers-13.txt> as an Experimental RFC
- 'SMTP extension for internationalized email address '
   <draft-ietf-eai-smtpext-14.txt> as an Experimental RFC

These documents are products of the Email Address Internationalization 
Working Group. 

The IESG contact persons are Chris Newman and Lisa Dusseault.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-eai-smtpext-14.txt

Technical Summary

    These two documents form the core specification for an
    extension to SMTP and RFC 2822 that allow the use of
    UTF-8 in message headers without encoding.

    This includes the use of non-ASCII characters in email
    addresses, both on the left and right hand sides of the
    @ character.

Working Group Summary

    The WG was chartered to explore one particular approach
    to email internationalization, and succeeded in keeping
    to that charter.
    There was extensive discussion of one particular design
    choice - on which MIME type to use.

Document Quality

    The documents have been extensively reviewed by people
    with mail expertise. There have been reports of
    implementations, but no interoperability tests have been
    reported to date.

Note to RFC Editor

    The document draft-ietf-eai-utf8headers-12.txt has a number of
    English grammar issues and may require extensive editorial work,
    please plan accordingly.
    
    draft-ietf-eai-utf8headers-12.txt header, please add:
      Updates: RFC2045, 2822