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


        RFC 2158:

        Title:      X.400 Image Body Parts
	Author(s):  H. Alvestrand
        Status:     Proposed Standard
	Date:       January 1998
        Mailbox:    Harald.T.Alvestrand@uninett.no
        Pages:      4
        Characters: 5547
        Updates/Obsoletes: None

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

This document contains the body parts defined in RFC 1495 for carrying
image formats that were originally defined in MIME through an X.400
system.  It also documents the OIDs assigned to these data formats as
FTAM body parts, which allow the MIME types to be converted to FTAM
body parts; this will probably be more useful than the new body parts
defined here.

This document is a product of the MIME - X.400 Gateway Working Group
of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  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@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@ISI.EDU.

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

        To: rfc-info@ISI.EDU
        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@DS.INTERNIC.NET.  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@ISI.EDU.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Alegre Ramos
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@ds.internic.net"

Content-Type: text/plain
Content-ID: <980108143857.RFC@ISI.EDU>

SEND /rfc/rfc2158.txt

--OtherAccess
Content-Type:   Message/External-body;
        name="rfc2158.txt";
        site="ds.internic.net";
        access-type="anon-ftp";
        directory="rfc"

Content-Type: text/plain
Content-ID: <980108143857.RFC@ISI.EDU>

--OtherAccess--
--NextPart--