RFC 2157 X.400/MIME Body Mapping January 1998 5.4 X.400 to MIME Table .................................. 23 5.5 Use of OBJECT IDENTIFIERs and ASN.1 MACROS ........... 24 6 Defined Equivalences ................................... 26 6.1 IA5Text - text/plain ................................. 26 6.2 GeneralText - text/plain (ISO-8859) .................. 27 6.3 BilaterallyDefined - application/octet-stream ...................................................... 29 6.4 FTBP EMA Unknown Attachment - application/octet-stream ............................. 29 6.5 MessageBodyPart - message/RFC 822 ..................... 30 6.6 MessageBodyPart - multipart/* ........................ 31 6.7 Teletex - Text/Plain (Teletex) ....................... 32 7 Body parts where encapsulation is recommended .......... 33 7.1 message/external-body ................................ 34 7.2 message/partial ...................................... 35 7.3 multipart/signed ..................................... 35 7.4 multipart/encrypted .................................. 36 8 Conformance requirements ............................... 37 9 Security Considerations ................................ 38 10 Author's Address ...................................... 38 11 Acknowledgements ...................................... 38 References .............................................. 38 APPENDIXES .............................................. 41 Appendix A: Escape code normalization ................... 41 Appendix B: OID Assignments ............................. 44 Appendix C: Registration information for the Teletex character set ............................... 46 Appendix D: IANA Registration form for new mappings ................................................ 48 Full Copyright Statement ................................. 49 1. Introduction This document is a companion to [MIXER], which defines the principles and translation of headers for interworking between MIME-based RFC- 822 mail and X.400 mail. This document defines how to map body parts of X.400 messages into MIME entities and vice versa, including the handling of multipart messages and forwarded messages. Alvestrand Standards Track