Carrying PostScript in X.400 and MIMEUNINETTPostboks 6883 ElgeseterN-7002 TRONDHEIM+47 73 59 70 94Harald.T.Alvestrand@uninett.no
Applications
MIMEPostScriptITU message handling service protocolmultipurpose internet mail extensions
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.
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 }
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 }
In MIME, PostScript is carried in the body part
"application/PostScript", which is defined in RFC 1521.
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.
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.
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
The issues concerning PostScript and security are well discussed in
RFC 2046. No additional security issues are identified by this memo.
PostScript is a trademark of Adobe Systems, Inc.
This RFC contained boilerplate in this section which has been moved
to the RFC2223-compliant unnumbered section "References."
This RFC contained boilerplate in this section which has been moved
to the RFC2223-compliant unnumbered section "Author's Address."
This RFC contained boilerplate in this section which has been moved
to the RFC2223-compliant unnumbered section "Full Copyright Statement."