X.400 Image Body Parts

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.

1. Introduction
2. Newly defined X.400 body parts
    2.1. The JPEG body part
    2.2. The GIF body part
3. Defined equivalences with MIME types
    3.1. image/jpeg - jpeg-body-part
    3.2. image/jpeg - FTAM EMA JPEG
    3.3. image/gif - gif-body-part
    3.4. image/gif - FTAM EMA GIF
4. Security Considerations
5. References (BOILERPLATE)
6. Author's Address (BOILERPLATE)
7. Full Copyright Statement (BOILERPLATE)
§ Author's Address
§ Intellectual Property and Copyright Statements

1. Introduction

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.

2. Newly defined X.400 body parts

2.1. The JPEG body part

The following Extended Body Part is defined for JPEG data streams. It has no parameters.

       jpeg-body-part EXTENDED-BODY-PART-TYPE
         DATA            OCTET STRING
         ::= mime-jpeg-body

       mime-jpeg-body OBJECT IDENTIFIER ::=
               { mixer-bp-data 3 }

2.2. The GIF body part

The following Extended Body Part is defined for GIF data streams. It has no parameters.

       gif-body-part EXTENDED-BODY-PART-TYPE
         DATA            OCTET STRING
         ::= mime-gif-body

       mime-gif-body OBJECT IDENTIFIER ::=
               { mixer-bp-data 4 }

3. Defined equivalences with MIME types

3.1. image/jpeg - jpeg-body-part

X.400 Body Part: Extended Body Part, OID jpeg-body-part MIME Content-Type: image/jpeg Conversion: None

3.2. image/jpeg - FTAM EMA JPEG

   { ema objects(2) messaging (2) attachments(1) jpeg-image(6) }

   { joint-iso-ccitt(2) country(16) us(840) organization(1)
   ema(113694) }

   { 2 16 840 1 113694 2 2 1 6 }

3.3. image/gif - gif-body-part

X.400 Body Part: Extended Body Part, OID gif-body-part MIME Content-Type: image/gif Conversion: None

3.4. image/gif - FTAM EMA GIF

   X.400 Body Part: FTAM EMA GIF
   MIME Content-Type: image/jpeg
   Conversion: None

   { ema objects(2) messaging (2) attachments(1) gif-image(4) }

4. Security Considerations

5. References (BOILERPLATE)

This RFC contained boilerplate in this section which has been moved to the RFC2223-compliant unnumbered section "References."

6. Author's Address (BOILERPLATE)

This RFC contained boilerplate in this section which has been moved to the RFC2223-compliant unnumbered section "Author's Address."

7. Full Copyright Statement (BOILERPLATE)

This RFC contained boilerplate in this section which has been moved to the RFC2223-compliant unnumbered section "Full Copyright Statement."

Author's Address

Full Copyright Statement

This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.

This document and the information contained herein are provided on an “AS IS” basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Intellectual Property

The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.

Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.

The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.

Acknowledgment

Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA).

	Harald Tveit Alvestrand
	UNINETT
	Postboks 6883 Elgeseter
	N-7002 TRONDHEIM
Phone:	+47 73 59 70 94
Email:	Harald.T.Alvestrand@uninett.no