2160
PROPOSED STANDARD
Carrying PostScript in X.400 and MIME
Authors: H. Alvestrand
Date: January 1998
Area: app
Working Group: mixer
Stream: IETF
Abstract
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]
RFC 2160
PROPOSED STANDARD
Network Working Group H. Alvestrand
Request for Comments: 2160 UNINETT
Category: Standards Track January 1998
<span class="h1">Carrying PostScript in X.400 and MIME</span>
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
<a href="#section-1">1</a> Introduction ............................................ <a href="#page-1">1</a>
<a href="#section-2">2</a> The PostScript body part ................................ <a href="#page-1">1</a>
<a href="#section-3">3</a> The PostScript FTBP ..................................... <a href="#page-2">2</a>
<a href="#section-4">4</a> The Application/PostScript content-type ................. <a href="#page-2">2</a>
<a href="#section-5">5</a> MIXER conversion ........................................ <a href="#page-2">2</a>
<a href="#section-6">6</a> MIXER conversion ........................................ <a href="#page-2">2</a>
<a href="#section-7">7</a> OID Assignments ......................................... <a href="#page-3">3</a>
<a href="#section-8">8</a> Security Issues ......................................... <a href="#page-3">3</a>
<a href="#section-9">9</a> Trademark Issues ........................................ <a href="#page-3">3</a>
<a href="#section-10">10</a> References ............................................. <a href="#page-3">3</a>
<a href="#section-11">11</a> Author's Address ....................................... <a href="#page-4">4</a>
<a href="#section-12">12</a> Full Copyright Statement ............................... <a href="#page-5">5</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
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 [<a href="#ref-BODYMAP">BODYMAP</a>], and
the conversion is further described in [<a href="#ref-MIXER">MIXER</a>].
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 <a href="./rfc1494">RFC 1494</a>.
The FTAM method is recommended.
<span class="grey">Alvestrand Standards Track [Page 1]</span><span id="page-2" ></span>
<span class="grey"><a href="./rfc2160">RFC 2160</a> Carrying PostScript in X.400 and MIME January 1998</span>
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. The PostScript body part</span>
Carrying PostScript in X.400 as an Extended Body Part was originally
defined in <a href="./rfc1494">RFC 1494</a>. This specification carries that work forward
now that <a href="./rfc1494">RFC 1494</a> is obsoleted by [<a href="#ref-BODYMAP">BODYMAP</a>].
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 }
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. The PostScript FTBP</span>
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 }
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. The Application/PostScript content-type</span>
In MIME, PostScript is carried in the body part
"application/PostScript", which is defined in <a href="./rfc1521">RFC 1521</a>.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. MIXER conversion</span>
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.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. MIXER conversion</span>
X.400 Body Part: FTBP, OID mime-ftbp-postscript-body MIME Content-
Type: application/postscript Conversion Type: No conversion
<span class="grey">Alvestrand Standards Track [Page 2]</span><span id="page-3" ></span>
<span class="grey"><a href="./rfc2160">RFC 2160</a> Carrying PostScript in X.400 and MIME January 1998</span>
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.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. OID Assignments</span>
The first OID is also defined in [<a href="#ref-BODYMAP">BODYMAP</a>].
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
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Security Issues</span>
The issues concerning PostScript and security are well discussed in
<a href="./rfc2046">RFC 2046</a>. No additional security issues are identified by this memo.
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Trademark Issues</span>
PostScript is a trademark of Adobe Systems, Inc.
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. References</span>
[<a id="ref-MIXER">MIXER</a>]
Kille, S., "MIXER: Mapping between X.400
and <a href="./rfc822">RFC 822</a>/MIME", <a href="./rfc2156">RFC 2156</a>, January 1998.
[<a id="ref-BODYMAP">BODYMAP</a>]
Alvestrand, H., "Mapping between X.400 and <a href="./rfc822">RFC 822</a>/MIME
Message Bodies", <a href="./rfc2157">RFC 2157</a>, January 1998.
<span class="grey">Alvestrand Standards Track [Page 3]</span><span id="page-4" ></span>
<span class="grey"><a href="./rfc2160">RFC 2160</a> Carrying PostScript in X.400 and MIME January 1998</span>
<span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. Author's Address</span>
Harald Tveit Alvestrand
UNINETT
Postboks 6883 Elgeseter
N-7002 TRONDHEIM
Phone: +47 73 59 70 94
EMail: [email protected]
<span class="grey">Alvestrand Standards Track [Page 4]</span><span id="page-5" ></span>
<span class="grey"><a href="./rfc2160">RFC 2160</a> Carrying PostScript in X.400 and MIME January 1998</span>
<span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a>. Full Copyright Statement</span>
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 assigns.
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.
Alvestrand Standards Track [Page 5]
Annotations
Select text to annotate