<?xml version="1.0"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc="yes"?>

<!--
     ASCII to XML transformation by Invisible Worlds, Inc.
     http://invisible.net/
     Last transformation: 03-Feb-1999, 02:04:13

     Cannonical version of this document is at:
     http://info.internet.isi.edu/in-notes/rfc/files/rfc2158.txt

     Implementors should verify all content with
     cannonical version.  Failure to do so may result in
     protocol failures.
-->

<rfc number="2158"
     category="std">
<front>
<title>X.400 Image Body Parts</title>
<author initials="H.T." surname="Alvestrand" fullname="Harald Tveit Alvestrand">
<organization>UNINETT</organization>
<address>
<postal>
<street>Postboks 6883 Elgeseter</street>
<street>N-7002 TRONDHEIM</street>
</postal>
<phone>+47 73 59 70 94</phone>
<email>Harald.T.Alvestrand@uninett.no</email>
</address>
</author>
<date month="January" year="1998"/>
<area>Applications</area>
<keyword>X.400</keyword>
<keyword>ITU message handling service protocol</keyword>
<keyword>multipurpose internet mail extensions</keyword>
</front>
<middle>
<!-- RFC original section: (1.) -->
<section title="Introduction">
<t>
   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.
</t>
<t>
   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.
</t>
</section>
<!-- RFC original section: (2.) -->
<section title="Newly defined X.400 body parts">
<t>
</t>
<!-- RFC original section: (2.1.) -->
<section title="The JPEG body part">
<t>
   The following Extended Body Part is defined for JPEG data streams.
   It has no parameters.
</t>
<figure><artwork>
       jpeg-body-part EXTENDED-BODY-PART-TYPE
         DATA            OCTET STRING
         ::= mime-jpeg-body

       mime-jpeg-body OBJECT IDENTIFIER ::=
               { mixer-bp-data 3 }
</artwork></figure>
<t>
   The content is as defined in [MIME].
</t>
</section>
<!-- RFC original section: (2.2.) -->
<section title="The GIF body part">
<t>
   The following Extended Body Part is defined for GIF data streams.  It
   has no parameters.
</t>
<figure><artwork>
       gif-body-part EXTENDED-BODY-PART-TYPE
         DATA            OCTET STRING
         ::= mime-gif-body

       mime-gif-body OBJECT IDENTIFIER ::=
               { mixer-bp-data 4 }
</artwork></figure>
<t>
   The content is as defined in [MIME].
</t>
</section>
</section>
<!-- RFC original section: (3.) -->
<section title="Defined equivalences with MIME types">
<t>
</t>
<!-- RFC original section: (3.1.) -->
<section title="image/jpeg - jpeg-body-part">
<t>
   X.400 Body Part: Extended Body Part, OID jpeg-body-part
   MIME Content-Type: image/jpeg
   Conversion: None
</t>
</section>
<!-- RFC original section: (3.2.) -->
<section title="image/jpeg - FTAM EMA JPEG">
<t>
   X.400 Body Part: FTAM EMA JPEG
   MIME Content-Type: image/jpeg
   Conversion: None
</t>
<t>
   The OID assigned to JPEG by EMA in [MAWG] is
</t>
<figure><artwork>
   { ema objects(2) messaging (2) attachments(1) jpeg-image(6) }
</artwork></figure>
<t>
   while EMA&apos;s OID is
</t>
<figure><artwork>
   { joint-iso-ccitt(2) country(16) us(840) organization(1)
   ema(113694) }
</artwork></figure>
<t>
   making the total OID, numeric only
</t>
<figure><artwork>
   { 2 16 840 1 113694 2 2 1 6 }
</artwork></figure>
</section>
<!-- RFC original section: (3.3.) -->
<section title="image/gif - gif-body-part">
<t>
   X.400 Body Part: Extended Body Part, OID gif-body-part
   MIME Content-Type: image/gif
   Conversion: None
</t>
</section>
<!-- RFC original section: (3.4.) -->
<section title="image/gif - FTAM EMA GIF">
<figure><artwork>
   X.400 Body Part: FTAM EMA GIF
   MIME Content-Type: image/jpeg
   Conversion: None
</artwork></figure>
<t>
   The OID assigned to JPEG by EMA in [MAWG] is
</t>
<figure><artwork>
   { ema objects(2) messaging (2) attachments(1) gif-image(4) }
</artwork></figure>
</section>
</section>
<!-- RFC original section: (4.) -->
<section title="Security Considerations">
<t>
   Security issues are not considered in this memo.
</t>
</section>
<!-- RFC original section: (5.) -->
<section title="References (BOILERPLATE)">
<t>
This RFC contained boilerplate in this section which has been moved
to the RFC2223-compliant unnumbered section &quot;References.&quot;
</t>
</section>
<!-- RFC original section: (6.) -->
<section title="Author&apos;s Address (BOILERPLATE)">
<t>
This RFC contained boilerplate in this section which has been moved
to the RFC2223-compliant unnumbered section &quot;Author&apos;s Address.&quot;
</t>
</section>
<!-- RFC original section: (7.) -->
<section title="Full Copyright Statement (BOILERPLATE)">
<t>
This RFC contained boilerplate in this section which has been moved
to the RFC2223-compliant unnumbered section &quot;Full Copyright Statement.&quot;
</t>
</section>
</middle>
<back>
</back>
</rfc>
