< draft-ietf-smime-msg-07.txt		draft-ietf-smime-msg-08.txt >
	Internet Draft Editor: Blake Ramsdell,		Internet Draft Editor: Blake Ramsdell,
	draft-ietf-smime-msg-07.txt Worldtalk		draft-ietf-smime-msg-08.txt Worldtalk
	March 31, 1999		April 23, 1999
	Expires September 30, 1999		Expires October 23, 1999
	S/MIME Version 3 Message Specification		S/MIME Version 3 Message Specification
	Status of this memo		Status of this memo
	This document is an Internet-Draft and is in full conformance with all		This document is an Internet-Draft and is in full conformance with all
	provisions of Section 10 of RFC2026.		provisions of Section 10 of RFC2026.
	Internet-Drafts are working documents of the Internet Engineering Task		Internet-Drafts are working documents of the Internet Engineering Task
	Force (IETF), its areas, and its working groups. Note that other		Force (IETF), its areas, and its working groups. Note that other
	skipping to change at line 90 ¶		skipping to change at line 90 ¶
	also derives from the likelihood that there will be S/MIME systems		also derives from the likelihood that there will be S/MIME systems
	that involve software other than traditional Internet mail clients.		that involve software other than traditional Internet mail clients.
	S/MIME can be used with any system that transports MIME data. An		S/MIME can be used with any system that transports MIME data. An
	automated process that sends an encrypted message might not be able to		automated process that sends an encrypted message might not be able to
	receive an encrypted message at all, for example. Thus, the		receive an encrypted message at all, for example. Thus, the
	requirements and recommendations for the two types of agents are		requirements and recommendations for the two types of agents are
	listed separately when appropriate.		listed separately when appropriate.
	1.2 Terminology		1.2 Terminology
	Throughout this draft, the terms MUST, MUST NOT, SHOULD, and SHOULD		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	NOT are used in capital letters. This conforms to the definitions in		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	[MUSTSHOULD]. [MUSTSHOULD] defines the use of these key words to help		document are to be interpreted as described in [MUSTSHOULD].
	make the intent of standards track documents as clear as possible. The
	same key words are used in this document to help implementors achieve
	interoperability.
	1.3 Definitions		1.3 Definitions
	For the purposes of this draft, the following definitions apply.		For the purposes of this draft, the following definitions apply.
	ASN.1: Abstract Syntax Notation One, as defined in CCITT X.208.		ASN.1: Abstract Syntax Notation One, as defined in CCITT X.208.
	BER: Basic Encoding Rules for ASN.1, as defined in CCITT X.209.		BER: Basic Encoding Rules for ASN.1, as defined in CCITT X.209.
	Certificate: A type that binds an entity's distinguished name to a		Certificate: A type that binds an entity's distinguished name to a
	skipping to change at line 1360 ¶		skipping to change at line 1357 ¶
	[RC2] "A Description of the RC2 (r) Encryption Algorithm", RFC 2268		[RC2] "A Description of the RC2 (r) Encryption Algorithm", RFC 2268
	[SHA1] NIST FIPS PUB 180-1, "Secure Hash Standard," National Institute		[SHA1] NIST FIPS PUB 180-1, "Secure Hash Standard," National Institute
	of Standards and Technology, U.S. Department of Commerce, DRAFT, 31May		of Standards and Technology, U.S. Department of Commerce, DRAFT, 31May
	1994.		1994.
	[SMIMEV2] "S/MIME Version 2 Message Specification", RFC 2311		[SMIMEV2] "S/MIME Version 2 Message Specification", RFC 2311
	C. Acknowledgements		C. Acknowledgements
	<TBD>		Many thanks go out to the other authors of the S/MIME Version 2
			Message Specification RFC: Steve Dusse, Paul Hoffman, Laurence
			Lundblade and Lisa Repka. Without v2, there wouldn't be a v3.
			A number of the members of the S/MIME Working Group have also worked
			very hard and contributed to this document. Any list of people is
			doomed to omission, and for that I apologize. In alphabetical order,
			the following people stand out in my mind due to the fact that they
			made direct contributions to this document.
			Dave Crocker
			Bill Flanigan
			Paul Hoffman
			Russ Housley
			John Pawling
			Jim Schaad
	D. Changes from last draft		D. Changes from last draft
	Clarified section 2.4.1 in the case of multipart/signed (eContent is		Changed section 1.3 to contain correct reference language for
	absent in that case) (Jim Schaad)		MUSTSHOULD (Thomas Narten)
	Removed receipt request attribute from section 2.5 (Jim Schaad)		Renumbered section F to section E (Blake Ramsdell)
	Capitalized MUST for use of the issuerAndSerialNumber CHOICE in		Changed section E to update author's address (Blake Ramsdell)
	section 2.6 (Jim Schaad)		Changed <TBD> in section C to actual list (Blake Ramsdell)
	Capitalized NOT in section 3.2.1 regarding reliance on file extensions
	(Jim Schaad)
	Changed [DH] reference to refer to draft-ietf-smime-x942-*.txt (Jim
	Schaad)
	Replaced section A with ASN.1 module (Jim Schaad)
	Rewording of 2.7.3 to explain that the content of the strongly-
	encrypted message can be learned by decrypting the weaker message
	(Russ Housley)
	Provided example OID. string for new smime-type values in section
	3.2.2 (Russ Housley)
	Rewording of section 5 regarding sending two messages with different
	levels of encryption (Russ Housley)
	Added [RANDOM] reference in section 4.1 and to section B (Russ
	Housley)
	Explained in section 2.5.2 that section A contains all of the MUST and
	SHOULD OIDs (Russ Housley)
	Added language to 2.2 and 2.3 about S/MIME v2 clients only have
	rsaEncryption (Paul Hoffman)
	F. Edito's address		E. Editor’s address
	Blake Ramsdell		Blake Ramsdell
	Worldtalk		Worldtalk
	13122 NE 20th St., Suite C		17720 NE 65th St Ste 201
	Bellevue, WA 98005		Redmond, WA 98052
	(425) 882-8861		+1 425 376 0225
	blaker@deming.com		blaker@deming.com
End of changes. 6 change blocks.
	37 lines changed or deleted		31 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/