Carrying PostScript in X.400 and MIME

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. The PostScript body part
3. The PostScript FTBP
4. The Application/PostScript content-type
5. MIXER conversion
6. MIXER conversion
7. OID Assignments
8. Security Issues
9. Trademark Issues
10. References (BOILERPLATE)
11. Author's Address (BOILERPLATE)
12. Full Copyright Statement (BOILERPLATE)
§ Author's Address
§ Intellectual Property and Copyright Statements

1. Introduction

This document describes methods for carrying PostScript information in the two standard mail systems MIME and X.400, and the conversion between them. It uses the notational conventions of [BODYMAP], and the conversion is further described in [MIXER].

Two ways of carrying PostScript in X.400 are described. One is using the FTAM Body Part, and one uses the Extended Body Part originally described in RFC 1494.

2. The PostScript body part

Carrying PostScript in X.400 as an Extended Body Part was originally defined in RFC 1494. This specification carries that work forward now that RFC 1494 is obsoleted by [BODYMAP].

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

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

      mime-postscript-body OBJECT IDENTIFIER ::=
                { mixer-bp-data 2 }

3. The PostScript FTBP

The PostScript FTBP is identified by having the FileTransferParameters.environment.application-reference set to id- mime-ftbp-postscript.

    id-mime-ftbp-postscript OBJECT IDENTIFIER ::=
                       { mixer-bp-data 6 }

4. The Application/PostScript content-type

In MIME, PostScript is carried in the body part "application/PostScript", which is defined in RFC 1521.

5. MIXER conversion

X.400 Body Part: Extended Body Part, OID mime-postscript-body MIME Content-Type: application/postscript Conversion Type: No conversion

The two representations of PostScript both contain a single stream of octets. This stream of octets can be copied with no problems between the representations. No other data needs to be converted.

6. MIXER conversion

X.400 Body Part: FTBP, OID mime-ftbp-postscript-body MIME Content- Type: application/postscript Conversion Type: No conversion

The two representations of PostScript both contain a single stream of octets. This stream of octets can be copied with no problems between the representations. No other data needs to be converted.

7. OID Assignments

    POSTSCRIPT-MAPPINGS DEFINITIONS ::= BEGIN
    EXPORTS -- everything --;

    IMPORTS
       mixer-bp-data
           FROM MIXER-MAPPINGS

    id-mime-postscript-body OBJECT IDENTIFIER ::=
            { mixer-bp-data 2 };
    id-mime-ftbp-postscript OBJECT IDENTIFIER ::=
            { mixer-bp-data 6 };

    END

8. Security Issues

The issues concerning PostScript and security are well discussed in RFC 2046. No additional security issues are identified by this memo.

9. Trademark Issues

10. References (BOILERPLATE)

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

11. Author's Address (BOILERPLATE)

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

12. 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