From: barrett@daisy.ee.und.ac.za (Alan P Barrett)
Newsgroups: comp.mail.mime,alt.security.pgp
Subject: Re: pgp headers for MIME
Date: 22 Jan 1993 18:33:26 +0200
Organization: Dept. Elec. Eng., Univ. Natal, Durban, S. Africa
NNTP-Posting-Host: daisy.ee.und.ac.za

In article <C18C4r.6K8@wizzy.com>,
andyr@wizzy.com (Andy Rabagliati) writes:
> In correspondence with Tobias Weingartner <weingart@inf.ethz.ch> he
> suggests 
> TW> I think pgp data should go so:
> TW> 
> TW> Content-Type: text/plain; charset=ISO-8859-1
> TW> Content-transfer-encoding: X-PGP-{VERSION}

No!  PGP is not a content-transfer-encoding.  If anything, its an
application.

I strongly suggest that any PGP-MIME format should be compatible with
the proposed PEM-MIME format, described in dratf-ietf-pem-mime-00.txt
available from your friendly Internet-Drafts repository.  Here's the
example from section 7 of the Nov 1992 version of the draft.  (Note,
as always that I-D's are subject to change without notice.)

draft>   7.  An Example
draft>
draft>   For example, suppose the following message was being readied
draft>   for submission:
draft>
draft>        Date:    Thu, 12 Nov 1992 21:43:40 -0800
draft>        From:    scrocker@tis.com
draft>        To:      ned@innosoft.com
draft>        Subject: example #1
draft>        MIME-Version:    1.0
draft>        Content-Type:    text/plain; charset=us-ascii
draft>        Content-Privacy: mic-clear
draft>
draft>        Hi Ned.  See how much nicer this works!
draft>
draft>   After applying pre-submission algorithm, the message submitted
draft>   for delivery would appear as:
draft>
draft>        Date:    Thu, 12 Nov 1992 21:43:40 -0800
draft>        From:    scrocker@tis.com
draft>        To:      ned@innosoft.com
draft>        Subject: example #1
draft>        MIME-Version: 1.0
draft>        Content-Type: multipart/pem; boundary="next-part";
draft>                                     privacy=mic-clear
draft>
              [ The draft forgot the boundary line here.  --apb ]
draft>        Content-Type: text/plain; charset=us-ascii
draft>
draft>        Hi Ned.  See how much nicer this works!
draft>
draft>        --next-part
draft>        Content-Type: application/pem
draft>
draft>        Proc-Type: 4,MIC-CLEAR
draft>        Content-Domain: RFC822
draft>        Originator-ID-Asymmetric: ...
draft>        MIC-Info: RSA-MD5,RSA, ...
draft>
draft>        --next-part--
draft>
draft>   After applying the post-delivery algorithm, the resulting
draft>   message would appear as:
draft>
draft>        Date:    Thu, 12 Nov 1992 21:43:40 -0800
draft>        From:    scrocker@tis.com
draft>        To:      ned@innosoft.com
draft>        Subject: example #1
draft>        MIME-Version:      1.0
draft>        Content-Type:      text/plain; charset=us-ascii
draft>        Content-Annotation: mic-clear;
draft>                            Thu, 12 Nov 1992 22:13:40 -0800
draft>                            (integrity verified)
draft>
draft>        Hi Ned.  See how much nicer this works!
draft>
draft>   Of course, as the message being submitted was only plain text,
draft>   the Content-Type: header could be ommitted.  In that case,
draft>   after applying the pre-submission algorithm, the message
draft>   submitted for delivery would appear as:
draft>
draft>        Date:    Thu, 12 Nov 1992 21:43:40 -0800
draft>        From:    scrocker@tis.com
draft>        To:      ned@innosoft.com
draft>        Subject: example #1
draft>        MIME-Version: 1.0
draft>        Content-Type: multipart/pem; boundary="next-part";
draft>                                     privacy=mic-clear
draft>
              [ The draft forgot the boundary line here.  --apb ]
	      [ also the blank line below the boundary line.   --apb ]
draft>        Hi Ned.  See how much nicer this works!
draft>
draft>        --next-part
draft>        Content-Type: application/pem
draft>
draft>        Proc-Type: 4,MIC-CLEAR
draft>        Content-Domain: RFC822
draft>        Originator-ID-Asymmetric: ...
draft>        MIC-Info: RSA-MD5,RSA, ...
draft>
draft>        --next-part--

--apb
Alan Barrett, Dept. of Electronic Eng., Univ. of Natal, Durban, South Africa
RFC822: barrett@ee.und.ac.za
Newsgroups: comp.mail.mime