home *** CD-ROM | disk | FTP | other *** search
/ NetNews Usenet Archive 1993 #3 / NN_1993_3.iso / spool / comp / mail / mime / 181 < prev    next >
Encoding:
Internet Message Format  |  1993-01-22  |  4.3 KB
  1. Xref: sparky comp.mail.mime:181 alt.security.pgp:588
  2. Path: sparky!uunet!psgrain!ee.und.ac.za!tplinfm
  3. From: barrett@daisy.ee.und.ac.za (Alan P Barrett)
  4. Newsgroups: comp.mail.mime,alt.security.pgp
  5. Subject: Re: pgp headers for MIME
  6. Date: 22 Jan 1993 18:33:26 +0200
  7. Organization: Dept. Elec. Eng., Univ. Natal, Durban, S. Africa
  8. Lines: 104
  9. Message-ID: <1jp7kmINNkif@daisy.ee.und.ac.za>
  10. References: <C18C4r.6K8@wizzy.com>
  11. NNTP-Posting-Host: daisy.ee.und.ac.za
  12.  
  13. In article <C18C4r.6K8@wizzy.com>,
  14. andyr@wizzy.com (Andy Rabagliati) writes:
  15. > In correspondence with Tobias Weingartner <weingart@inf.ethz.ch> he
  16. > suggests 
  17. > TW> I think pgp data should go so:
  18. > TW> 
  19. > TW> Content-Type: text/plain; charset=ISO-8859-1
  20. > TW> Content-transfer-encoding: X-PGP-{VERSION}
  21.  
  22. No!  PGP is not a content-transfer-encoding.  If anything, its an
  23. application.
  24.  
  25. I strongly suggest that any PGP-MIME format should be compatible with
  26. the proposed PEM-MIME format, described in dratf-ietf-pem-mime-00.txt
  27. available from your friendly Internet-Drafts repository.  Here's the
  28. example from section 7 of the Nov 1992 version of the draft.  (Note,
  29. as always that I-D's are subject to change without notice.)
  30.  
  31. draft>   7.  An Example
  32. draft>
  33. draft>   For example, suppose the following message was being readied
  34. draft>   for submission:
  35. draft>
  36. draft>        Date:    Thu, 12 Nov 1992 21:43:40 -0800
  37. draft>        From:    scrocker@tis.com
  38. draft>        To:      ned@innosoft.com
  39. draft>        Subject: example #1
  40. draft>        MIME-Version:    1.0
  41. draft>        Content-Type:    text/plain; charset=us-ascii
  42. draft>        Content-Privacy: mic-clear
  43. draft>
  44. draft>        Hi Ned.  See how much nicer this works!
  45. draft>
  46. draft>   After applying pre-submission algorithm, the message submitted
  47. draft>   for delivery would appear as:
  48. draft>
  49. draft>        Date:    Thu, 12 Nov 1992 21:43:40 -0800
  50. draft>        From:    scrocker@tis.com
  51. draft>        To:      ned@innosoft.com
  52. draft>        Subject: example #1
  53. draft>        MIME-Version: 1.0
  54. draft>        Content-Type: multipart/pem; boundary="next-part";
  55. draft>                                     privacy=mic-clear
  56. draft>
  57.               [ The draft forgot the boundary line here.  --apb ]
  58. draft>        Content-Type: text/plain; charset=us-ascii
  59. draft>
  60. draft>        Hi Ned.  See how much nicer this works!
  61. draft>
  62. draft>        --next-part
  63. draft>        Content-Type: application/pem
  64. draft>
  65. draft>        Proc-Type: 4,MIC-CLEAR
  66. draft>        Content-Domain: RFC822
  67. draft>        Originator-ID-Asymmetric: ...
  68. draft>        MIC-Info: RSA-MD5,RSA, ...
  69. draft>
  70. draft>        --next-part--
  71. draft>
  72. draft>   After applying the post-delivery algorithm, the resulting
  73. draft>   message would appear as:
  74. draft>
  75. draft>        Date:    Thu, 12 Nov 1992 21:43:40 -0800
  76. draft>        From:    scrocker@tis.com
  77. draft>        To:      ned@innosoft.com
  78. draft>        Subject: example #1
  79. draft>        MIME-Version:      1.0
  80. draft>        Content-Type:      text/plain; charset=us-ascii
  81. draft>        Content-Annotation: mic-clear;
  82. draft>                            Thu, 12 Nov 1992 22:13:40 -0800
  83. draft>                            (integrity verified)
  84. draft>
  85. draft>        Hi Ned.  See how much nicer this works!
  86. draft>
  87. draft>   Of course, as the message being submitted was only plain text,
  88. draft>   the Content-Type: header could be ommitted.  In that case,
  89. draft>   after applying the pre-submission algorithm, the message
  90. draft>   submitted for delivery would appear as:
  91. draft>
  92. draft>        Date:    Thu, 12 Nov 1992 21:43:40 -0800
  93. draft>        From:    scrocker@tis.com
  94. draft>        To:      ned@innosoft.com
  95. draft>        Subject: example #1
  96. draft>        MIME-Version: 1.0
  97. draft>        Content-Type: multipart/pem; boundary="next-part";
  98. draft>                                     privacy=mic-clear
  99. draft>
  100.               [ The draft forgot the boundary line here.  --apb ]
  101.           [ also the blank line below the boundary line.   --apb ]
  102. draft>        Hi Ned.  See how much nicer this works!
  103. draft>
  104. draft>        --next-part
  105. draft>        Content-Type: application/pem
  106. draft>
  107. draft>        Proc-Type: 4,MIC-CLEAR
  108. draft>        Content-Domain: RFC822
  109. draft>        Originator-ID-Asymmetric: ...
  110. draft>        MIC-Info: RSA-MD5,RSA, ...
  111. draft>
  112. draft>        --next-part--
  113.  
  114. --apb
  115. Alan Barrett, Dept. of Electronic Eng., Univ. of Natal, Durban, South Africa
  116. RFC822: barrett@ee.und.ac.za
  117.