draft-ietf-openpgp-mime-06.txt   draft-ietf-openpgp-mime-07.txt 
Network Working Group M. Elkins Network Working Group M. Elkins
draft-ietf-openpgp-mime-06.txt Network Presence, LLC. draft-ietf-openpgp-mime-07.txt Network Associates, Inc.
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
April 2001 July 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 10, line 21 skipping to change at page 10, line 21
It is explicitly allowed for an agent to decrypt a combined message It is explicitly allowed for an agent to decrypt a combined message
and rewrite it as a multipart/signed object using the signature data and rewrite it as a multipart/signed object using the signature data
embedded in the encrypted version. embedded in the encrypted version.
7. Distribution of OpenPGP public keys 7. Distribution of OpenPGP public keys
Content-Type: application/pgp-keys Content-Type: application/pgp-keys
Required parameters: none Required parameters: none
Optional parameters: none Optional parameters: none
A MIME body part of this content type contains ASCII-armored A MIME body part of the content type "application/pgp-keys" contains
transferable Public Key Packets as defined in [1], section 10.1. ASCII-armored transferable Public Key Packets as defined in [1],
section 10.1.
8. Security Considerations 8. Security Considerations
Signatures of a canonical text document as defined in [1] ignore Signatures of a canonical text document as defined in [1] ignore
trailing white space in signed material. Implementations which trailing white space in signed material. Implementations which
choose to use signatures of canonical text documents will not be able choose to use signatures of canonical text documents will not be able
to detect the addition of whitespace in transit. to detect the addition of whitespace in transit.
See [3], [4] for more information on the security considerations See [3], [4] for more information on the security considerations
concerning the underlying protocols. concerning the underlying protocols.
9. Notes 9. IANA Considerations
This document defines three media types: "application/pgp-encrypted",
"application/pgp-signature" and "application/pgp-keys". The following
sections specify the IANA registrations for these types.
9.1. Registration of the application/pgp-encrypted media type
MIME media type name: application
MIME subtype name: pgp-encrypted
Required parameters: none
Optional parameters: none
Encoding considerations:
Currently this media type always consists of a single 7bit text
string.
Security considerations:
See Section 8 and RFC 2440 Section 13.
Interoperability considerations: none
Published specification:
This document.
Additional information:
Magic number(s): none
File extension(s): none
Macintosh File Type Code(s): none
Person & email address to contact for further information:
Michael Elkins
Email: me@cs.hmc.edu
Intended usage: common
Author/Change controller:
Michael Elkins
Email: me@cs.hmc.edu
9.2. Registration of the application/pgp-signature media type
MIME media type name: application
MIME subtype name: pgp-signature
Required parameters: none
Optional parameters: none
Encoding considerations:
The content of this media type always consists of 7bit text.
Security considerations:
See Section 8 and RFC 2440 Section 13.
Interoperability considerations: none
Published specification:
RFC 2440 and this document.
Additional information:
Magic number(s): none
File extension(s): asc
Macintosh File Type Code(s): pgDS
Person & email address to contact for further information:
Michael Elkins
Email: me@cs.hmc.edu
Intended usage: common
Author/Change controller:
Michael Elkins
Email: me@cs.hmc.edu
9.3. Registration of the application/pgp-keys media type
MIME media type name: application
MIME subtype name: pgp-keys
Required parameters: none
Optional parameters: none
Encoding considerations:
The content of this media type always consists of 7bit text.
Security considerations:
See Section 8 and RFC 2440 Section 13.
Interoperability considerations: none
Published specification:
RFC 2440 and this document.
Additional information:
Magic number(s): none
File extension(s): asc
Macintosh File Type Code(s): pgPR
Person & email address to contact for further information:
Michael Elkins
Email: me@cs.hmc.edu
Intended usage: common
Author/Change controller:
Michael Elkins
Email: me@cs.hmc.edu
10. Notes
"PGP" and "Pretty Good Privacy" are registered trademarks of Network "PGP" and "Pretty Good Privacy" are registered trademarks of Network
Associates, Inc. Associates, Inc.
10. Acknowledgements 11. Acknowledgements
This draft document relies on the work of the IETF's OpenPGP Working This draft document relies on the work of the IETF's OpenPGP Working
Group's definitions of the OpenPGP Message Format. The OpenPGP Group's definitions of the OpenPGP Message Format. The OpenPGP
message format is currently described in RFC 2440 [1]. message format is currently described in RFC 2440 [1].
Special thanks are due: to Philip Zimmermann for his original and Special thanks are due: to Philip Zimmermann for his original and
ongoing work on PGP; to Charles Breed, Jon Callas and Dave Del Torto ongoing work on PGP; to Charles Breed, Jon Callas and Dave Del Torto
for originally proposing the formation of the OpenPGP Working Group; for originally proposing the formation of the OpenPGP Working Group;
and to Steve Schoenfeld for helpful feedback during the draft and to Steve Schoenfeld for helpful feedback during the draft
process. The authors would also like to thank the engineers at Pretty process. The authors would also like to thank the engineers at Pretty
skipping to change at page 11, line 21 skipping to change at page 14, line 5
whitespace; to John Gilmore, Hugh Daniel and Fred Ringel (at whitespace; to John Gilmore, Hugh Daniel and Fred Ringel (at
Rivertown) and Ian Bell (at Turnpike) for their timely critical Rivertown) and Ian Bell (at Turnpike) for their timely critical
commentary; and to the international members of the IETF's OpenPGP commentary; and to the international members of the IETF's OpenPGP
mailing list, including William Geiger, Lutz Donnerhacke and Kazu mailing list, including William Geiger, Lutz Donnerhacke and Kazu
Yamamoto. The idea to use multipart/mixed with multipart/signed has Yamamoto. The idea to use multipart/mixed with multipart/signed has
been attributed to James Galvin. Finally, our gratitude is due to the been attributed to James Galvin. Finally, our gratitude is due to the
many members of the "Cypherpunks," "Coderpunks" and "pgp-users" many members of the "Cypherpunks," "Coderpunks" and "pgp-users"
<http://cryptorights.org/pgp-users> mailing lists and the many users <http://cryptorights.org/pgp-users> mailing lists and the many users
of PGP worldwide for helping keep the path to privacy open. of PGP worldwide for helping keep the path to privacy open.
11. Addresses of the Authors and OpenPGP Working Group Chair 12. Addresses of the Authors and OpenPGP Working Group Chair
The OpenPGP working group can be contacted via the current chair: The OpenPGP working group can be contacted via the current chair:
John W. Noerenberg II John W. Noerenberg II
Qualcomm, Inc. Qualcomm, Inc.
5775 Morehouse Dr. 5775 Morehouse Dr.
San Diego CA 92121 USA San Diego CA 92121 USA
Tel: +1 619 658 3510 Tel: +1 619 658 3510
Email: jwn2@qualcomm.com Email: jwn2@qualcomm.com
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 Presence, LLC. Network Associates, Inc.
548 S. Spring St, Suite 1015 3415 S. Sepulveda Blvd Suite 700
Los Angeles CA 90013 USA Los Angeles CA 90034 USA
Tel: +1.213.627.4356
Fax: +1.213.627.4357 Tel: +1.310.737.1663
Email: me@netpr.com Fax: +1.310.737.1755
Email: Michael_Elkins@nai.com, me@cs.hmc.edu
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
 End of changes. 

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