RFC 2152 on UTF-7

[RFC Editor <rfc-ed@xxxxxxx>]

- --NextPart


A new Request for Comments is now available in online RFC libraries.


 
        RFC 2152:
 
        Title:      UTF-7
                    A Mail-Safe Transformation Format of Unicode
        Author:     D. Goldsmith,  M. Davis
        Date:       May 1997
        Mailbox:    goldsmith@xxxxxxxxx, mark_davis@xxxxxxxxxxxx
        Pages:      15
        Characters: 28065
        Obsoletes:  1642

        URL:        ftp://ds.internic.net/rfc/rfc2152.txt


This document describes a transformation format of Unicode that
contains only 7-bit ASCII octets and is intended to be readable by
humans in the limiting case that the document consists of characters
from the US-ASCII repertoire. It also specifies how this
transformation format is used in the context of MIME and RFC 1641,
"Using Unicode with MIME". 

This memo provides information for the Internet community.  This memo
does not specify an Internet standard of any kind.  Distribution of
this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@xxxxxxxxxxxxxxxxx.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@xxxxxxx.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@xxxxxxx with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@xxxxxxx
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to admin@xxxxxxxxxxxxxxx.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@xxxxxxx.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Mary Kennedy
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

- --NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

- --OtherAccess
Content-Type:  Message/External-body;
        access-type="mail-server";
        server="mailserv@xxxxxxxxxxxxxxx"