draft-ietf-openpgp-mime-03.txt   draft-ietf-openpgp-mime-04.txt 
OpenPGP Working Group M. Elkins OpenPGP Working Group M. Elkins
draft-ietf-openpgp-mime-03.txt Network Associates, Inc. draft-ietf-openpgp-mime-04.txt Network Presence, LLC.
Obsoletes: 2015 D. Del Torto Obsoletes: 2015 D. Del Torto
CryptoRights Foundation CryptoRights Foundation
R. Levien R. Levien
University of California at Berkeley University of California at Berkeley
T. Roessler T. Roessler
August 2000 February 2001
MIME Security with OpenPGP MIME Security with OpenPGP
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 3, line 25 skipping to change at page 3, line 25
Note: Trailing white space does not alter the actual contents of a Note: Trailing white space does not alter the actual contents of a
Quoted-Printable or Base64 encoded body part, or the meaning of Quoted-Printable or Base64 encoded body part, or the meaning of
MIME headers. However, the presence of trailing white space may MIME headers. However, the presence of trailing white space may
trigger a compatibility problem which was introduced in [1]: With trigger a compatibility problem which was introduced in [1]: With
traditional implementations of PGP, trailing whitespace was traditional implementations of PGP, trailing whitespace was
included with signatures of canonical text documents. [1] changes included with signatures of canonical text documents. [1] changes
this behaviour in an incompatible way, by specifying that trailing this behaviour in an incompatible way, by specifying that trailing
white space is ignored in signatures of canonical text documents. white space is ignored in signatures of canonical text documents.
Note: If any line begins with the string "From", it is strongly Note: If any line begins with the string "From", it is strongly
recommended that Quoted-Printable encoding be applied and that at suggested that either the Quoted-Printable or Base64 MIME encoding
least one of the characters in the string is encoded using the be applied. If Quoted-Printable is used, at least one of the
hexadecimal coding rule. This is because many mail transfer and characters in the string should be encoded using the hexadecimal
delivery agents treat "From " (the word "from" followed coding rule. This is because many mail transfer and delivery
immediately by a space character) as the start of a new message agents treat "From " (the word "from" followed immediately by a
and thus insert a right angle-bracket (>) in front of any line space character) as the start of a new message and thus insert a
beginning with "From" to distinguish this case, invalidating the right angle-bracket (>) in front of any line beginning with "From"
signature. to distinguish this case, invalidating the signature.
Data that is ONLY to be encrypted is allowed to contain 8-bit Data that is ONLY to be encrypted is allowed to contain 8-bit
characters and therefore need not be converted to a 7-bit format. characters and therefore need not be converted to a 7-bit format.
Implementor's note: It cannot be stressed enough that applications Implementor's note: It cannot be stressed enough that applications
using this standard follow MIME's suggestion that you "be using this standard follow MIME's suggestion that you "be
conservative in what you generate, and liberal in what you conservative in what you generate, and liberal in what you
accept." In this particular case it means it would be wise for an accept." In this particular case it means it would be wise for an
implementation to accept messages with any content-transfer- implementation to accept messages with any content-transfer-
encoding, but restrict generation to the 7-bit format required by encoding, but restrict generation to the 7-bit format required by
skipping to change at page 10, line 44 skipping to change at page 10, line 44
The principal authors of this draft are: The principal authors of this draft are:
Dave Del Torto Dave Del Torto
CryptoRights Foundation CryptoRights Foundation
80 Alviso Street, Mailstop: CRF 80 Alviso Street, Mailstop: CRF
San Francisco CA 94127 USA San Francisco CA 94127 USA
Tel: +1.415.334.5533, vm: #2 Tel: +1.415.334.5533, vm: #2
Email: ddt@cryptorights.org, ddt@openpgp.net Email: ddt@cryptorights.org, ddt@openpgp.net
Michael Elkins Michael Elkins
Network Associates, Inc. Network Presence, LLC.
3415 S. Sepulveda Blvd Suite 700 548 S. Spring St, Suite 1015
Los Angeles CA 90034 USA Los Angeles CA 90013 USA
Tel: +1.310.737.1623 Tel: +1.213.627.4356
Fax: +1.310.737.1755 Fax: +1.213.627.4357
Email: michael_elkins@nai.com Email: me@netpr.com
Raph Levien Raph Levien
University of California at Berkeley University of California at Berkeley
579 Soda Hall 579 Soda Hall
Berkeley CA 94720 USA Berkeley CA 94720 USA
Tel: +1.510.642.6509 Tel: +1.510.642.6509
Email: raph@acm.org Email: raph@acm.org
Thomas Roessler Thomas Roessler
Nordstrasse 99 Nordstrasse 99
D-53111 Bonn D-53111 Bonn
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/