< draft-turner-application-pkcs10-media-type-03.txt		draft-turner-application-pkcs10-media-type-04.txt >
	Network Working Group S. Turner		Network Working Group S. Turner
	Internet Draft IECA		Internet Draft IECA
	Intended Status: Informational April 16, 2010		Intended Status: Informational April 22, 2010
	Updates: 2986 (once approved)		Updates: 2986 (once approved)
	Expires: October 16, 2010		Expires: October 22, 2010
	The application/pkcs10 Media Type		The application/pkcs10 Media Type
	draft-turner-application-pkcs10-media-type-03.txt		draft-turner-application-pkcs10-media-type-04.txt
	Abstract		Abstract
	This document specifies a media type used to carry PKCS#10		This document specifies a media type used to carry PKCS#10
	certification requests as defined in RFC 2986. It carries over the		certification requests as defined in RFC 2986. It carries over the
	original specification from RFC 2311, which recently has been moved		original specification from RFC 2311, which recently has been moved
	to Historic state, and properly links it to RFC 2986.		to Historic state, and properly links it to RFC 2986.
	Status of this Memo		Status of this Memo
	skipping to change at page 2, line 5 ¶		skipping to change at page 2, line 5 ¶
	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."
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/ietf/1id-abstracts.txt.		http://www.ietf.org/ietf/1id-abstracts.txt.
	The list of Internet-Draft Shadow Directories can be accessed at		The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.		http://www.ietf.org/shadow.html.
	This Internet-Draft will expire on October 16, 2010.		This Internet-Draft will expire on October 22, 2010.
	Copyright Notice		Copyright Notice
	Copyright (c) 2010 IETF Trust and the persons identified as the		Copyright (c) 2010 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/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	skipping to change at page 4, line 24 ¶		skipping to change at page 4, line 24 ¶
	A typical application only needs to send a certification request. It		A typical application only needs to send a certification request. It
	is a certification authority that has to receive and process the		is a certification authority that has to receive and process the
	request. The steps for recovering the CertificationRequest from the		request. The steps for recovering the CertificationRequest from the
	message are straightforward but are not presented here. The		message are straightforward but are not presented here. The
	procedures for processing the certification request are beyond the		procedures for processing the certification request are beyond the
	scope of this document.		scope of this document.
	3. IANA Considerations		3. IANA Considerations
	IANA is asked to update the registration for the application/pkcs10		IANA is asked to update the registration for the application/pkcs10
	media type using the filled-in template from BCP 13 [RFC4288] given		media subtype using the filled-in template from BCP 13 [RFC4288]
	below.		given below.
	3.1. Registration of media type application/pkcs10		3.1. Registration of media subtype application/pkcs10
	The media type for a PKCS#10 certification request is		The media subtype for a PKCS#10 certification request is
	application/pkcs10.		application/pkcs10.
	To: ietf-types@iana.org
	Subject: Registration of media type application/pkcs10
	Type name: application		Type name: application
	Subtype name: pkcs10		Subtype name: pkcs10
	Required parameters: None		Required parameters: None
	Optional parameters: None		Optional parameters: None
	Encoding considerations:		Encoding considerations: binary; See Section 2.
	This media type carries binary content and needs proper encoding
	for non-8bit clear transports; See Section 2.
	Security considerations:		Security considerations:
	Clients use a certification request to request that a		Clients use a certification request to request that a
	Certification Authority certify a public key. The certification		Certification Authority certify a public key. The certification
	request is digitally signed.		request is digitally signed. Also see Section 6.
	Interoperability considerations: See Section 2.		Interoperability considerations: See Section 2.
	Published specification: RFC 2986		Published specification: [RFC2986] and this specification.
	Applications which use this media type:		Applications which use this media type:
	The content type is used with MIME-compliant transport to		Applications that support PKCS#10 certification requests
	transfer PKCS#10 certification requests [RFC2986].		[RFC2986].
	Additional information:		Additional information:
	Magic number(s): None		Magic number(s): None
	File extension(s): .p10		File extension(s): .p10
	Macintosh File Type Code(s):		Macintosh File Type Code(s):
	Person & email address to contact for further information:		Person & email address to contact for further information:
	Sean Turner <turners@ieca.com>		Sean Turner <turners@ieca.com>
	Restrictions on usage: none		Restrictions on usage: none
	Author:		Author: Sean Turner <turners@ieca.com>
	Sean Turner <turners@ieca.com>
	Intended usage: COMMON		Intended usage: COMMON
	Change controller:		Change controller: The IESG
	The IESG <iesg@ietf.org>
	4. Security Considerations		4. Security Considerations
	The security considerations of [RFC2986] and [RFC5751] apply; no new		The security considerations of [RFC2986] and [RFC5751] apply; no new
	security considerations are introduced by this document.		security considerations are introduced by this document.
	5. Acknowledgements		5. Acknowledgements
	I wish to thank the authors of RFC 2311, Steve Dusse, Paul Hoffman,		I wish to thank the authors of RFC 2311, Steve Dusse, Paul Hoffman,
	Blake Ramsdell, Laurence Lundblade, and Lisa Repka.		Blake Ramsdell, Laurence Lundblade, and Lisa Repka.
			I would also like to thank Bjoern Hoehrmann for his review of the
			media subtype application.
	6. References		6. References
	6.1. Normative References		6.1. Normative References
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	[RFC2986] Nystrom, M, and B. Kaliski, "PKCS #10: Certification		[RFC2986] Nystrom, M, and B. Kaliski, "PKCS #10: Certification
	Request Syntax Specification Version 1.7", RFC 2986,		Request Syntax Specification Version 1.7", RFC 2986,
	November 2000.		November 2000.
End of changes. 15 change blocks.
	24 lines changed or deleted		18 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/