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