RFC 
 2160 
 TOC 
Network Working GroupH. Alvestrand
Request for Comments: 2160UNINETT
Category: Standards TrackJanuary 1998


Carrying PostScript in X.400 and MIME

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 © The Internet Society (1998). All Rights Reserved.


 RFC 
 2160 
 TOC 

Table of Contents

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




 TOC 

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.

The FTAM method is recommended.



 TOC 

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 }


 TOC 

3.  The PostScript FTBP

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

The definition is:

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


 TOC 

4.  The Application/PostScript content-type

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



 TOC 

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.



 TOC 

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.



 TOC 

7.  OID Assignments

The first OID is also defined in [BODYMAP].

    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


 TOC 

8.  Security Issues

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



 TOC 

9.  Trademark Issues

PostScript is a trademark of Adobe Systems, Inc.



 TOC 

10.  References (BOILERPLATE)

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



 TOC 

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



 TOC 

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



 TOC 

Author's Address

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


 TOC 

Full Copyright Statement

Intellectual Property