Status of this Memo

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.

Copyright Notice

Copyright (C) The Internet Society (1998). All Rights Reserved.

Table of Contents

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 }

The content is as defined in [MIME].

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 }

The content is as defined in [MIME].

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

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

The OID assigned to JPEG by EMA in [MAWG] is

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

while EMA's OID is

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

making the total OID, numeric only

   { 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

The OID assigned to JPEG by EMA in [MAWG] is

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

4. Security Considerations

Security issues are not considered in this memo.

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

Intellectual Property Statement

The IETF takes no position regarding the validity or scope of any intellectual property 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; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication 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 implementors or users of this specification can be obtained from the IETF Secretariat.

The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director.

Full Copyright Statement

Copyright (C) The Internet Society (1998). All Rights Reserved.

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.

The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assignees.

This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS 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.

Acknowledgment

Funding for the RFC Editor function is currently provided by the Internet Society.