[governance] Internationalization of email addresses completed

[Ian Peter]

That's really good news, Stephane! Thanks for bringing it to the list's
attention

Ian Peter
Ian Peter and Associates Pty Ltd
PO Box 10670 Adelaide St  Brisbane 4000
Australia
Tel (+614) 1966 7772 or (+612) 6687 0773
www.ianpeter.com
 
 

> -----Original Message-----
> From: Stephane Bortzmeyer [mailto:bortzmeyer at internatif.org]
> Sent: 08 September 2008 05:23
> To: governance at lists.cpsr.org
> Subject: [governance] Internationalization of email addresses completed
> 
> Since we often talk about internationalization...
> 
> Three new RFCs have been published on friday. They (almost) finalize
> the standards for the internationalization of email addresses (email
> content in Unicode is standard since 1992). Soon :-) I'll be able to
> use stéphane at bortzmeyer.fr with the accent. Congratulations for the
> EAI Working Group.
> 
> Now, we can say that almost all the IETF standards are
> Unicode-able.
> 
> (The main missing one is FTP, which has an option TEXT which is only
> for ASCII. An Unicode version is under work.)
> 
>         RFC 5335
> 
>         Title:      Internationalized Email Headers
>         Author:     Y. Abel, Ed.
>         Status:     Experimental
>         Date:       September 2008
>         Mailbox:    abelyang at twnic.net.tw
>         Pages:      14
>         Characters: 27945
>         Updates:    RFC2045, RFC2822
> 
>         I-D Tag:    draft-ietf-eai-utf8headers-12.txt
> 
>         URL:        http://www.rfc-editor.org/rfc/rfc5335.txt
> 
> Full internationalization of electronic mail requires not only the
> capabilities to transmit non-ASCII content, to encode selected
> information in specific header fields, and to use non-ASCII
> characters in envelope addresses.  It also requires being able to
> express those addresses and the information based on them in mail
> header fields.  This document specifies an experimental variant of
> Internet mail that permits the use of Unicode encoded in UTF-8,
> rather than ASCII, as the base form for Internet email header field.
> This form is permitted in transmission only if authorized by an SMTP
> extension, as specified in an associated specification.  This
> specification Updates section 6.4 of RFC 2045 to conform with the
> requirements.  This memo defines an Experimental Protocol for the Internet
> community.
> 
> This document is a product of the Email Address Internationalization
> Working Group of the IETF.
> 
> 
> 
>         RFC 5336
> 
>         Title:      SMTP Extension for Internationalized Email
>                     Addresses
>         Author:     J. Yao, Ed.,
>                     W. Mao, Ed.
>         Status:     Experimental
>         Date:       September 2008
>         Mailbox:    yaojk at cnnic.cn,
>                     maowei_ietf at cnnic.cn
>         Pages:      22
>         Characters: 48110
>         Updates:    RFC2821, RFC2822, RFC4952
> 
>         I-D Tag:    draft-ietf-eai-smtpext-13.txt
> 
>         URL:        http://www.rfc-editor.org/rfc/rfc5336.txt
> 
> This document specifies an SMTP extension for transport and delivery
> of email messages with internationalized email addresses or header
> information.  Communication with systems that do not implement this
> specification is specified in another document.  This document
> updates some syntaxes and rules defined in RFC 2821 and RFC 2822, and
> has some material updating RFC 4952This memo defines an Experimental
> Protocol for the Internet community.
> 
> This document is a product of the Email Address Internationalization
> Working Group of the IETF.
> 
> 
> 
>         RFC 5337
> 
>         Title:      Internationalized Delivery Status and Disposition
>                     Notifications
>         Author:     C. Newman, A. Melnikov, Ed.
>         Status:     Experimental
>         Date:       September 2008
>         Mailbox:    chris.newman at sun.com,
>                     Alexey.Melnikov at isode.com
>         Pages:      18
>         Characters: 36324
>         Updates:    RFC3461, RFC3464, RFC3798
> 
>         I-D Tag:    draft-ietf-eai-dsn-06.txt
> 
>         URL:        http://www.rfc-editor.org/rfc/rfc5337.txt
> 
> Delivery status notifications (DSNs) are critical to the correct
> operation of an email system.  However, the existing Draft Standards
> (RFC 3461, RFC 3462, RFC 3464) are presently limited to US-ASCII text
> in the machine-readable portions of the protocol.  This specification
> adds a new address type for international email addresses so an
> original recipient address with non-US-ASCII characters can be
> correctly preserved even after downgrading.  This also provides
> updated content return media types for delivery status notifications
> and message disposition notifications to support use of the new
> address type.
> 
> This document experimentally extends RFC 3461, RFC 3464, and RFC
> 3798.  This memo defines an Experimental Protocol for the Internet
> community.
> 
> This document is a product of the Email Address Internationalization
> Working Group of the IETF.
> 
> 
> ____________________________________________________________
> You received this message as a subscriber on the list:
>      governance at lists.cpsr.org
> To be removed from the list, send any message to:
>      governance-unsubscribe at lists.cpsr.org
> 
> For all list information and functions, see:
>      http://lists.cpsr.org/lists/info/governance
> Internal Virus Database is out of date.
> Checked by AVG - http://www.avg.com
> Version: 8.0.138 / Virus Database: 270.6.0/1602 - Release Date: 8/9/2008
> 1:22 PM

____________________________________________________________
You received this message as a subscriber on the list:
     governance at lists.cpsr.org
To be removed from the list, send any message to:
     governance-unsubscribe at lists.cpsr.org

For all list information and functions, see:
     http://lists.cpsr.org/lists/info/governance