rfc-2160

Carrying PostScript in X.400 and MIME

H. Alvestrand

date1998-01 streamIETF areaapp wgmixer statusPROPOSED STANDARD pages5 canonicalhttps://www.rfc-editor.org/rfc/rfc2160 doi10.17487/RFC2160

This document describes methods for carrying PostScript information in the two standard mail systems MIME and X.400, and the conversion between them. [STANDARDS-TRACK]

Extracted elements (8)

design-rationale §1

Two methods for carrying PostScript in X.400 are defined (Extended Body Part and FTBP); the FTAM Body Part method is recommended over the Extended Body Part method.

interoperability-note §5

MIXER conversion between X.400 Extended Body Part (OID mime-postscript-body) and MIME application/postscript requires no conversion; the single octet stream is copied directly between representations.

interoperability-note §6

MIXER conversion between X.400 FTBP (OID mime-ftbp-postscript-body) and MIME application/postscript requires no conversion; the single octet stream is copied directly between representations.

protocol-element §4

In MIME, PostScript is carried in the 'application/PostScript' content-type as defined in RFC 1521.

protocol-element §2

The PostScript Extended Body Part for X.400 is defined with DATA as OCTET STRING and identified by OID mime-postscript-body (mixer-bp-data 2). It has no parameters.

protocol-element §3

The PostScript FTAM Body Part (FTBP) for X.400 is identified by FileTransferParameters.environment.application-reference set to id-mime-ftbp-postscript (mixer-bp-data 6).

registry §7

Two OIDs are assigned under mixer-bp-data: id-mime-postscript-body (mixer-bp-data 2) for the Extended Body Part, and id-mime-ftbp-postscript (mixer-bp-data 6) for the FTBP.

email, registry

security-consideration §8

Security issues for PostScript are discussed in RFC 2046; this memo identifies no additional security issues beyond those already documented there.

security, email