< draft-housley-ct-keypackage-receipt-n-error-03.txt		draft-housley-ct-keypackage-receipt-n-error-04.txt >
	Internet Engineering Task Force (IETF) Russ Housley		Internet Engineering Task Force (IETF) Russ Housley
	Internet-Draft Vigil Security		Internet-Draft Vigil Security
	Intended Status: Standards Track 17 June 2013		Intended Status: Standards Track 22 June 2013
	Expires: 17 December 2013		Expires: 22 December 2013
	Cryptographic Message Syntax (CMS)		Cryptographic Message Syntax (CMS)
	Key Package Receipt and Error Content Types		Key Package Receipt and Error Content Types
	draft-housley-ct-keypackage-receipt-n-error-03.txt		draft-housley-ct-keypackage-receipt-n-error-04.txt
	Abstract		Abstract
	This document defines the syntax for two Cryptographic Message Syntax		This document defines the syntax for two Cryptographic Message Syntax
	(CMS) content types, one for key package receipts, and another for		(CMS) content types, one for key package receipts, and another for
	key package errors. The key package receipt content type is used to		key package errors. The key package receipt content type is used to
	confirm receipt of an identified key package or collection of key		confirm receipt of an identified key package or collection of key
	packages. The key package error content type is used to indicate an		packages. The key package error content type is used to indicate an
	error occurred during the processing of a key package. CMS can be		error occurred during the processing of a key package. CMS can be
	used to digitally sign, digest, authenticate, or encrypt these		used to digitally sign, digest, authenticate, or encrypt these
	skipping to change at page 6, line 37 ¶		skipping to change at page 6, line 37 ¶
	identified key package or collection of key packages. This content		identified key package or collection of key packages. This content
	type MUST be Distinguished Encoding Rules (DER) encoded [X.690].		type MUST be Distinguished Encoding Rules (DER) encoded [X.690].
	The key package receipt content type has the following syntax:		The key package receipt content type has the following syntax:
	ct-key-package-receipt CONTENT-TYPE ::= {		ct-key-package-receipt CONTENT-TYPE ::= {
	TYPE KeyPackageReceipt		TYPE KeyPackageReceipt
	IDENTIFIED BY id-ct-KP-keyPackageReceipt }		IDENTIFIED BY id-ct-KP-keyPackageReceipt }
	id-ct-KP-keyPackageReceipt OBJECT IDENTIFIER ::= {		id-ct-KP-keyPackageReceipt OBJECT IDENTIFIER ::= {
	iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs9(9)		joint-iso-itu-t(2) country(16) us(840) organization(1)
	smime(16) ct(1) TBD1 }		gov(101) dod(2) infosec(1) formats(2)
			key-package-content-types(78) 3 }
	KeyPackageReceipt ::= SEQUENCE {		KeyPackageReceipt ::= SEQUENCE {
	version KeyPkgVersion DEFAULT v2,		version KeyPkgVersion DEFAULT v2,
	receiptOf KeyPkgIdentifier,		receiptOf KeyPkgIdentifier,
	receivedBy SIREntityName }		receivedBy SIREntityName }
	-- Revised definition of KeyPkgVersion from [RFC6031]		-- Revised definition of KeyPkgVersion from [RFC6031]
	KeyPkgVersion ::= INTEGER { v1(1), v2(2) } (1 .. 65535)		KeyPkgVersion ::= INTEGER { v1(1), v2(2) } (1 .. 65535)
	KeyPkgIdentifier ::= CHOICE {		KeyPkgIdentifier ::= CHOICE {
	skipping to change at page 8, line 19 ¶		skipping to change at page 8, line 21 ¶
	reason for rejection of a key package or collection of key packages.		reason for rejection of a key package or collection of key packages.
	This content type MUST be Distinguished Encoding Rules (DER) encoded		This content type MUST be Distinguished Encoding Rules (DER) encoded
	[X.690].		[X.690].
	The key package error content type has the following syntax:		The key package error content type has the following syntax:
	ct-key-package-error CONTENT-TYPE ::= {		ct-key-package-error CONTENT-TYPE ::= {
	TYPE KeyPackageError IDENTIFIED BY id-ct-KP-keyPackageError }		TYPE KeyPackageError IDENTIFIED BY id-ct-KP-keyPackageError }
	id-ct-KP-keyPackageError OBJECT IDENTIFIER ::= {		id-ct-KP-keyPackageError OBJECT IDENTIFIER ::= {
	iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs9(9)		joint-iso-itu-t(2) country(16) us(840) organization(1)
	smime(16) ct(1) TBD2 }		gov(101) dod(2) infosec(1) formats(2)
			key-package-content-types(78) 6 }
	KeyPackageError ::= SEQUENCE {		KeyPackageError ::= SEQUENCE {
	version KeyPkgVersion DEFAULT v2,		version KeyPkgVersion DEFAULT v2,
	errorOf [0] KeyPkgIdentifier OPTIONAL,		errorOf [0] KeyPkgIdentifier OPTIONAL,
	errorBy SIREntityName,		errorBy SIREntityName,
	errorCode ErrorCodeChoice }		errorCode ErrorCodeChoice }
	KeyPkgVersion ::= INTEGER { v1(1), v2(2) } (1 .. 65535)		KeyPkgVersion ::= INTEGER { v1(1), v2(2) } (1 .. 65535)
	KeyPkgIdentifier ::= CHOICE {		KeyPkgIdentifier ::= CHOICE {
	skipping to change at page 20, line 13 ¶		skipping to change at page 20, line 13 ¶
	Management Protocol (TAMP)", RFC 5934, August 2010.		Management Protocol (TAMP)", RFC 5934, August 2010.
	Appendix A: ASN.1 Module		Appendix A: ASN.1 Module
	This annex provides the normative ASN.1 definitions for the		This annex provides the normative ASN.1 definitions for the
	structures described in this specification using ASN.1 as defined in		structures described in this specification using ASN.1 as defined in
	[X.680], [X.681], [X.682], and [X.683].		[X.680], [X.681], [X.682], and [X.683].
	KeyPackageReceiptAndErrorModuleV2		KeyPackageReceiptAndErrorModuleV2
	{ iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9)		{ iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9)
	smime(16) modules(0) TBD }		smime(16) modules(0) id-mod-keyPkgReceiptAndErrV2(63) }
	-- TO DO: Get module OID value assigned.
	DEFINITIONS IMPLICIT TAGS ::=		DEFINITIONS IMPLICIT TAGS ::=
	BEGIN		BEGIN
	-- EXPORTS ALL		-- EXPORTS ALL
	IMPORTS		IMPORTS
	-- FROM New SMIME ASN.1 [RFC6268]		-- FROM New SMIME ASN.1 [RFC6268]
End of changes. 5 change blocks.
	10 lines changed or deleted		10 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/