< draft-leiba-smime-type-registry-00.txt		draft-leiba-smime-type-registry-01.txt >
	Security Area B. Leiba		Security Area B. Leiba
	Internet-Draft Huawei Technologies		Internet-Draft Huawei Technologies
	Intended status: Standards Track August 28, 2013		Intended status: Standards Track October 18, 2013
	Expires: March 01, 2014		Expires: April 19, 2014
	Creation of a registry for smime-type parameter values		Creation of a registry for smime-type parameter values
	draft-leiba-smime-type-registry-00		draft-leiba-smime-type-registry-01
	Abstract		Abstract
	Secure/Multipurpose Internet Mail Extensions (S/MIME) defined the		Secure/Multipurpose Internet Mail Extensions (S/MIME) defined the
	Content-Type parameter "smime-type". As the list of defined values		Content-Type parameter "smime-type". As the list of defined values
	for that parameter has increased, it has become clear that a registry		for that parameter has increased, it has become clear that a registry
	is needed to document those values. This document creates that		is needed to document those values. This document creates that
	registry, registers the current values, and specifies the policies		registry, registers the current values, and specifies the policies
	for registration of new values.		for registration of new values.
	Status of This Memo		Status of this Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at http://datatracker.ietf.org/drafts/current/.		Drafts is at http://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	This Internet-Draft will expire on March 01, 2014.		This Internet-Draft will expire on April 19, 2014.
	Copyright Notice		Copyright Notice
	Copyright (c) 2013 IETF Trust and the persons identified as the		Copyright (c) 2013 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents (http://trustee.ietf.org/
	(http://trustee.ietf.org/license-info) in effect on the date of		license-info) in effect on the date of publication of this document.
	publication of this document. Please review these documents		Please review these documents carefully, as they describe your rights
	carefully, as they describe your rights and restrictions with respect		and restrictions with respect to this document. Code Components
	to this document. Code Components extracted from this document must		extracted from this document must include Simplified BSD License text
	include Simplified BSD License text as described in Section 4.e of		as described in Section 4.e of the Trust Legal Provisions and are
	the Trust Legal Provisions and are provided without warranty as		provided without warranty as described in the Simplified BSD License.
	described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
	2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2		2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2
	3. Security Considerations . . . . . . . . . . . . . . . . . . . 3		3. Security Considerations . . . . . . . . . . . . . . . . . . . 3
	4. References . . . . . . . . . . . . . . . . . . . . . . . . . 3		4. References . . . . . . . . . . . . . . . . . . . . . . . . . . 3
	4.1. Normative References . . . . . . . . . . . . . . . . . . 3		4.1. Normative References . . . . . . . . . . . . . . . . . . . 3
	4.2. Informative References . . . . . . . . . . . . . . . . . 3		4.2. Informative References . . . . . . . . . . . . . . . . . . 3
	Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4		Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 3
	1. Introduction		1. Introduction
	Secure/Multipurpose Internet Mail Extensions (S/MIME) defined the		Secure/Multipurpose Internet Mail Extensions (S/MIME) defined the
	Content-Type "application/pkcs7-mime" and the parameter "smime-type",		Content-Type "application/pkcs7-mime" and the parameter "smime-type",
	along with four valid values for the parameter [RFC3851].		along with four valid values for the parameter [RFC3851].
	Certificate Management over CMS (CMC) added two new parameter values		Certificate Management over CMS (CMC) added two new parameter values
	[RFC5273]. [RFC5751] replaced RFC 3851 and registered the		[RFC5273]. [RFC5751] replaced RFC 3851 and registered the
	application/pkcs7-mime media type, but did not create a registry for		application/pkcs7-mime media type, but did not create a registry for
	the smime-type values.		the smime-type values.
	skipping to change at page 3, line 24 ¶		skipping to change at page 3, line 4 ¶
	| CMC-Response | [RFC5273] Section 3 |		| CMC-Response | [RFC5273] Section 3 |
	| compressed-data | [RFC5751] Section 3.2.2 |		| compressed-data | [RFC5751] Section 3.2.2 |
	| enveloped-data | [RFC5751] Section 3.2.2 |		| enveloped-data | [RFC5751] Section 3.2.2 |
	| server-generated-key | [RFC-ietf-pkix-est] Section 4.4.2 |		| server-generated-key | [RFC-ietf-pkix-est] Section 4.4.2 |
	| signed-data | [RFC5751] Section 3.2.2 |		| signed-data | [RFC5751] Section 3.2.2 |
	+----------------------+-----------------------------------+		+----------------------+-----------------------------------+
	[[RFC Editor: please replace RFC-ietf-pkix-est in the table above		[[RFC Editor: please replace RFC-ietf-pkix-est in the table above
	with the RFC number assigned to draft-ietf-pkix-est. Note that it is		with the RFC number assigned to draft-ietf-pkix-est. Note that it is
	NOT the RFC number for this RFC!]]		NOT the RFC number for this RFC!]]
	New values can be registered using the RFC Required policy, as		New values can be registered using the RFC Required policy, as
	defined in [RFC5226]. The S/MIME Message Specification [RFC5751],		defined in [RFC5226]. The S/MIME Message Specification [RFC5751],
	Section 3.2.2, specifies guidelines for assigning new smime-type		Section 3.2.2, specifies guidelines for assigning new smime-type
	parameter values, and those guidelines apply to the assignment of		parameter values, and those guidelines apply to the assignment of
	values in this registry.		values in this registry.
	3. Security Considerations		3. Security Considerations
	This document is purely administrative, and presents no security		This document is purely administrative, and presents no security
	issues.		issues.
	4. References		4. References
	4.1. Normative References		4.1. Normative References
	[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an		[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
	IANA Considerations Section in RFCs", BCP 26, RFC 5226,		IANA Considerations Section in RFCs", BCP 26, RFC 5226,
	May 2008.		May 2008.
			[RFC5751] Ramsdell, B. and S. Turner, "Secure/Multipurpose Internet
			Mail Extensions (S/MIME) Version 3.2 Message
			Specification", RFC 5751, January 2010.
	4.2. Informative References		4.2. Informative References
	[I-D.ietf-pkix-est]		[I-D.ietf-pkix-est]
	Pritikin, M., Yee, P., and D. Harkins, "Enrollment over		Pritikin, M., Yee, P. and D. Harkins, "Enrollment over
	Secure Transport", draft-ietf-pkix-est-09 (work in		Secure Transport", Internet-Draft draft-ietf-pkix-est-09,
	progress), August 2013.		August 2013.
	[RFC3851] Ramsdell, B., "Secure/Multipurpose Internet Mail		[RFC3851] Ramsdell, B., "Secure/Multipurpose Internet Mail
	Extensions (S/MIME) Version 3.1 Message Specification",		Extensions (S/MIME) Version 3.1 Message Specification",
	RFC 3851, July 2004.		RFC 3851, July 2004.
	[RFC5273] Schaad, J. and M. Myers, "Certificate Management over CMS		[RFC5273] Schaad, J. and M. Myers, "Certificate Management over CMS
	(CMC): Transport Protocols", RFC 5273, June 2008.		(CMC): Transport Protocols", RFC 5273, June 2008.
	[RFC5751] Ramsdell, B. and S. Turner, "Secure/Multipurpose Internet
	Mail Extensions (S/MIME) Version 3.2 Message
	Specification", RFC 5751, January 2010.
	Author's Address		Author's Address
	Barry Leiba		Barry Leiba
	Huawei Technologies		Huawei Technologies
	Phone: +1 646 827 0648		Phone: +1 646 827 0648
	Email: barryleiba@computer.org		Email: barryleiba@computer.org
	URI: http://internetmessagingtechnology.org/		URI: http://internetmessagingtechnology.org/
End of changes. 10 change blocks.
	28 lines changed or deleted		26 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/