draft                PostScript body parts              Jan 96


              Carrying PostScript in X.400 and MIME

                   Fri Jan  5 09:55:37 MET 1996


                     Harald Tveit Alvestrand
                             UNINETT
                  Harald.T.Alvestrand@uninett.no



    Status of this Memo

    The name of this draft is draft-ietf-mixer-
    postscript-00.txt

    The following text is required for all drafts:

         This document is an Internet Draft.  Internet Drafts
         are working documents of the Internet Engineering
         Task Force (IETF), its Areas, and its Working Groups.
         Note that other groups may also distribute working
         documents as Internet Drafts.

         Internet Drafts are draft documents valid for a
         maximum of six months. Internet Drafts may be
         updated, replaced, or obsoleted by other documents at
         any time.  It is not appropriate to use Internet
         Drafts as reference material or to cite them other
         than as a "working draft" or "work in progress."

         Please check the I-D abstract listing contained in
         each Internet Draft directory to learn the current
         status of this or any other Internet Draft.


    This document is an update to part of RFC 1494.

    Please send comments to the MIXER mailing list:
    <ietf-mixer@innosoft.com>










Alvestrand                Exp July 96                 [Page 1]

draft                PostScript body parts              Jan 96


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


    2.  The PostScript body part

    Carrying PostScript in X.400 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 Application/PostScript content-type

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


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







Alvestrand                Exp July 96                 [Page 2]

draft                PostScript body parts              Jan 96


    5.  OID Assignments

    This 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 };

    END

    6.  Security issues

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


    7.  Trademark issues

    PostScript is a trademark of Adobe Systems, Inc.


    8.  References


    [MIXER]
         S.E. Hardcastle-Kille, MIXER: Mapping between X.400
         and RFC 822/MIME (in preparation)

    [BODYMAP]
         Mapping between X.400 and RFC 822/MIME message bodies
         (in preparation)












Alvestrand                Exp July 96                 [Page 3]

draft                PostScript body parts              Jan 96


    9.  Author's address

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


    Table of Contents


     Status of this Memo ................................    1
    1 Introduction ......................................    2
    2 The PostScript body part ..........................    2
    3 The Application/PostScript content-type ...........    2
    4 MIXER conversion ..................................    2
    5 OID Assignments ...................................    3
    6 Security issues ...................................    3
    7 Trademark issues ..................................    3
    8 References ........................................    3
    9 Author's address ..................................    4
     Table of Contents ..................................    4


























Alvestrand                Exp July 96                 [Page 4]