A new Request for Comments is now available in online RFC libraries. RFC 1496: Title: Rules for downgrading messages from X.400/88 to X.400/84 when MIME content-types are present in the messages Author: H. Alvestrand, J. Romaguera & K. Jordan Mailbox: Harald.T.Alvestrand@delab.sintef.no, Kevin.E.Jordan@mercury.oss.arh.cpg.cdc.com, Romaguera@netconsult.ch Pages: 5 Characters: 8,411 Updates: 1328 Interworking between X.400(88) and X.400 (84) is achieved by RFC 1328. That document does not describe what to do in the case where body parts arrive at the gateway that cannot be adequately represented in the X.400(84) system. This document describes how RFC 1328 must be modified in order to provide adequate support for the scenarios: SMTP(MIME) -> X.400(84), and X.400(84) -> SMTP(MIME). This is now a Proposed Standard Protocol. This RFC specifies an IAB standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "IAB Official Protocol Standards" 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@CNRI.RESTON.VA.US. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-REQUEST@NIC.DDN.MIL. 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 NIC.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 1111, "Instructions to RFC Authors", for further information. Joyce K. Reynolds USC/Information Sciences Institute