< draft-ietf-pkix-tamp-07.txt		draft-ietf-pkix-tamp-08.txt >
	Network Working Group R. Housley		Network Working Group R. Housley
	Internet-Draft Vigil Security, LLC		Internet-Draft Vigil Security, LLC
	Intended status: Standards Track S. Ashmore		Intended status: Standards Track S. Ashmore
	Expires: September 23, 2010 National Security Agency		Expires: October 23, 2010 National Security Agency
	C. Wallace		C. Wallace
	Cygnacom Solutions		Cygnacom Solutions
	March 22, 2010		April 21, 2010
	Trust Anchor Management Protocol (TAMP)		Trust Anchor Management Protocol (TAMP)
	draft-ietf-pkix-tamp-07		draft-ietf-pkix-tamp-08
	Abstract		Abstract
	This document describes a transport independent protocol for the		This document describes a transport independent protocol for the
	management of trust anchors and community identifiers stored in a		management of trust anchors and community identifiers stored in a
	trust anchor store. The protocol makes use of the Cryptographic		trust anchor store. The protocol makes use of the Cryptographic
	Message Syntax (CMS), and a digital signature is used to provide		Message Syntax (CMS), and a digital signature is used to provide
	integrity protection and data origin authentication. The protocol		integrity protection and data origin authentication. The protocol
	can be used to manage trust anchor stores containing trust anchors		can be used to manage trust anchor stores containing trust anchors
	represented as Certificate, TBSCertificate or TrustAnchorInfo		represented as Certificate, TBSCertificate or TrustAnchorInfo
	skipping to change at page 1, line 46 ¶		skipping to change at page 1, line 46 ¶
	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 September 23, 2010.		This Internet-Draft will expire on October 23, 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
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	skipping to change at page 4, line 5 ¶		skipping to change at page 4, line 5 ¶
	9. Apex trust anchor info certificate extension . . . . . . . . . 60		9. Apex trust anchor info certificate extension . . . . . . . . . 60
	10. Security Considerations . . . . . . . . . . . . . . . . . . . 61		10. Security Considerations . . . . . . . . . . . . . . . . . . . 61
	11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 64		11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 64
	12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 65		12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 65
	12.1. Normative References . . . . . . . . . . . . . . . . . . . 65		12.1. Normative References . . . . . . . . . . . . . . . . . . . 65
	12.2. Informative References . . . . . . . . . . . . . . . . . . 65		12.2. Informative References . . . . . . . . . . . . . . . . . . 65
	Appendix A. ASN.1 Modules . . . . . . . . . . . . . . . . . . . . 67		Appendix A. ASN.1 Modules . . . . . . . . . . . . . . . . . . . . 67
	A.1. ASN.1 Module Using 1993 Syntax . . . . . . . . . . . . . . 67		A.1. ASN.1 Module Using 1993 Syntax . . . . . . . . . . . . . . 67
	A.2. ASN.1 Module Using 1988 Syntax . . . . . . . . . . . . . . 76		A.2. ASN.1 Module Using 1988 Syntax . . . . . . . . . . . . . . 76
	Appendix B. MIME Media Type Registrations . . . . . . . . . . . . 84		Appendix B. Media Type Registrations . . . . . . . . . . . . . . 84
	B.1. application/tamp-status-query . . . . . . . . . . . . . . 84		B.1. application/tamp-status-query . . . . . . . . . . . . . . 84
	B.2. application/tamp-status-response . . . . . . . . . . . . . 85		B.2. application/tamp-status-response . . . . . . . . . . . . . 85
	B.3. application/tamp-update . . . . . . . . . . . . . . . . . 86		B.3. application/tamp-update . . . . . . . . . . . . . . . . . 86
	B.4. application/tamp-update-confirm . . . . . . . . . . . . . 87		B.4. application/tamp-update-confirm . . . . . . . . . . . . . 87
	B.5. application/tamp-apex-update . . . . . . . . . . . . . . . 88		B.5. application/tamp-apex-update . . . . . . . . . . . . . . . 88
	B.6. application/tamp-apex-update-confirm . . . . . . . . . . . 89		B.6. application/tamp-apex-update-confirm . . . . . . . . . . . 89
	B.7. application/tamp-community-update . . . . . . . . . . . . 90		B.7. application/tamp-community-update . . . . . . . . . . . . 90
	B.8. application/tamp-community-update-confirm . . . . . . . . 91		B.8. application/tamp-community-update-confirm . . . . . . . . 91
	B.9. application/tamp-sequence-adjust . . . . . . . . . . . . . 92		B.9. application/tamp-sequence-adjust . . . . . . . . . . . . . 92
	B.10. application/tamp-sequence-adjust-confirm . . . . . . . . . 93		B.10. application/tamp-sequence-adjust-confirm . . . . . . . . . 93
	skipping to change at page 64, line 10 ¶		skipping to change at page 64, line 10 ¶
	of loss, sequence number state can be restored by inspecting the most		of loss, sequence number state can be restored by inspecting the most
	recently generated TAMP message, provided the messages are logged, or		recently generated TAMP message, provided the messages are logged, or
	in collaboration with a trust anchor store manager who can		in collaboration with a trust anchor store manager who can
	successfully issue a TAMPStatusQuery message.		successfully issue a TAMPStatusQuery message.
	11. IANA Considerations		11. IANA Considerations
	The details of TAMP requests and responses are communicated using		The details of TAMP requests and responses are communicated using
	object identifiers (OIDs). The objects are defined in an arc		object identifiers (OIDs). The objects are defined in an arc
	delegated by IANA to the PKIX Working Group. This document also		delegated by IANA to the PKIX Working Group. This document also
	includes eleven MIME type registrations in Appendix B. No further		includes eleven media type registrations in Appendix B. No further
	action by IANA is necessary for this document or any anticipated		action by IANA is necessary for this document or any anticipated
	updates.		updates.
	12. References		12. References
	12.1. Normative References		12.1. Normative References
	[I-D.ietf-pkix-new-asn1]		[I-D.ietf-pkix-new-asn1]
	Hoffman, P. and J. Schaad, "New ASN.1 Modules for PKIX",		Hoffman, P. and J. Schaad, "New ASN.1 Modules for PKIX",
	draft-ietf-pkix-new-asn1-07 (work in progress),		draft-ietf-pkix-new-asn1-07 (work in progress),
	skipping to change at page 84, line 5 ¶		skipping to change at page 84, line 5 ¶
	id-pe-wrappedApexContinKey OBJECT IDENTIFIER ::=		id-pe-wrappedApexContinKey OBJECT IDENTIFIER ::=
	{ iso(1) identified-organization(3) dod(6) internet(1)		{ iso(1) identified-organization(3) dod(6) internet(1)
	security(5) mechanisms(5) pkix(7) pe(1) 20 }		security(5) mechanisms(5) pkix(7) pe(1) 20 }
	ApexContingencyKey ::= SEQUENCE {		ApexContingencyKey ::= SEQUENCE {
	wrapAlgorithm AlgorithmIdentifier,		wrapAlgorithm AlgorithmIdentifier,
	wrappedContinPubKey OCTET STRING }		wrappedContinPubKey OCTET STRING }
	END		END
	Appendix B. MIME Media Type Registrations		Appendix B. Media Type Registrations
	Eleven MIME media type registrations are provided in this appendix.		Eleven media type registrations are provided in this appendix. As
	As noted in Section 2, in all cases TAMP messages are encapsulated		noted in Section 2, in all cases TAMP messages are encapsulated
	within ContentInfo structures. Signed messages are additionally		within ContentInfo structures. Signed messages are additionally
	encapsulated within a SignedData structure.		encapsulated within a SignedData structure.
	B.1. application/tamp-status-query		B.1. application/tamp-status-query
	To: ietf-types@iana.org		To: ietf-types@iana.org
	Subject: Registration of MIME media type application/		Subject: Registration of media type application/tamp-status-query
	tamp-status-query
	MIME media type name: application		Media type name: application
	MIME subtype name: tamp-status-query		Subtype name: tamp-status-query
	Required parameters: None		Required parameters: None
	Optional parameters: None		Optional parameters: None
	Encoding considerations: Binary		Encoding considerations: Binary
	Security considerations: Carries a signed request for status		Security considerations: Carries a signed request for status
	information. Integrity protection is discussed in section 4.1.		information. Integrity protection is discussed in section 4.1.
	Replay detection is discussed in section 6.		Replay detection is discussed in section 6.
	skipping to change at page 84, line 44 ¶		skipping to change at page 84, line 43 ¶
	Published specification: TBD		Published specification: TBD
	Applications that use this media type: TAMP clients responding to		Applications that use this media type: TAMP clients responding to
	requests for status information.		requests for status information.
	Additional information:		Additional information:
	Magic number(s): None		Magic number(s): None
	File extension(s): .TSQ		File extension(s): .tsq
	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:
	Sam Ashmore - srashmo@radium.ncsc.mil		Sam Ashmore - srashmo@radium.ncsc.mil
	Intended usage: COMMON		Intended usage: COMMON
	Restrictions on usage: None		Restrictions on usage: None
	Author: Sam Ashmore - srashmo@radium.ncsc.mil		Author: Sam Ashmore - srashmo@radium.ncsc.mil
	Change controller: IESG		Change controller: IESG
	B.2. application/tamp-status-response		B.2. application/tamp-status-response
	To: ietf-types@iana.org		To: ietf-types@iana.org
	Subject: Registration of MIME media type application/		Subject: Registration of media type application/tamp-status-response
	tamp-status-response
	MIME media type name: application		Media type name: application
	MIME subtype name: tamp-status-response		Subtype name: tamp-status-response
	Required parameters: None		Required parameters: None
	Optional parameters: None		Optional parameters: None
	Encoding considerations: Binary		Encoding considerations: Binary
	Security considerations: Carries optionally signed status		Security considerations: Carries optionally signed status
	information. Integrity protection is discussed in section 4.2.		information. Integrity protection is discussed in section 4.2.
	skipping to change at page 85, line 41 ¶		skipping to change at page 85, line 40 ¶
	Published specification: TBD		Published specification: TBD
	Applications that use this media type: TAMP clients responding to		Applications that use this media type: TAMP clients responding to
	requests for status information.		requests for status information.
	Additional information:		Additional information:
	Magic number(s): None		Magic number(s): None
	File extension(s): .TSR		File extension(s): .tsr
	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:
	Sam Ashmore - srashmo@radium.ncsc.mil		Sam Ashmore - srashmo@radium.ncsc.mil
	Intended usage: COMMON		Intended usage: COMMON
	Restrictions on usage: None		Restrictions on usage: None
	Author: Sam Ashmore - srashmo@radium.ncsc.mil		Author: Sam Ashmore - srashmo@radium.ncsc.mil
	Change controller: IESG		Change controller: IESG
	B.3. application/tamp-update		B.3. application/tamp-update
	To: ietf-types@iana.org		To: ietf-types@iana.org
	Subject: Registration of MIME media type application/tamp-update		Subject: Registration of media type application/tamp-update
	MIME media type name: application		Media type name: application
	MIME subtype name: tamp-update		Subtype name: tamp-update
	Required parameters: None		Required parameters: None
	Optional parameters: None		Optional parameters: None
	Encoding considerations: Binary		Encoding considerations: Binary
	Security considerations: Carries a signed trust anchor update		Security considerations: Carries a signed trust anchor update
	message. Integrity protection is discussed in section 4.3. Replay		message. Integrity protection is discussed in section 4.3. Replay
	detection is discussed in section 6.		detection is discussed in section 6.
	skipping to change at page 86, line 39 ¶		skipping to change at page 86, line 39 ¶
	Published specification: TBD		Published specification: TBD
	Applications that use this media type: TAMP clients responding to		Applications that use this media type: TAMP clients responding to
	requests to update trust anchor information.		requests to update trust anchor information.
	Additional information:		Additional information:
	Magic number(s): None		Magic number(s): None
	File extension(s): .TUR		File extension(s): .tur
	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:
	Sam Ashmore - srashmo@radium.ncsc.mil		Sam Ashmore - srashmo@radium.ncsc.mil
	Intended usage: COMMON		Intended usage: COMMON
	Restrictions on usage: None		Restrictions on usage: None
	Author: Sam Ashmore - srashmo@radium.ncsc.mil		Author: Sam Ashmore - srashmo@radium.ncsc.mil
	Change controller: IESG		Change controller: IESG
	B.4. application/tamp-update-confirm		B.4. application/tamp-update-confirm
	To: ietf-types@iana.org		To: ietf-types@iana.org
	Subject: Registration of MIME media type application/		Subject: Registration of media type application/tamp-update-confirm
	tamp-update-confirm
	MIME media type name: application		Media type name: application
	MIME subtype name: tamp-update-confirm		Subtype name: tamp-update-confirm
	Required parameters: None		Required parameters: None
	Optional parameters: None		Optional parameters: None
	Encoding considerations: Binary		Encoding considerations: Binary
	Security considerations: Carries an optionally signed TAMP update		Security considerations: Carries an optionally signed TAMP update
	response. Integrity protection is discussed in section 4.4.		response. Integrity protection is discussed in section 4.4.
	skipping to change at page 87, line 37 ¶		skipping to change at page 87, line 36 ¶
	Published specification: TBD		Published specification: TBD
	Applications that use this media type: TAMP clients responding to		Applications that use this media type: TAMP clients responding to
	requests to update trust anchor information		requests to update trust anchor information
	Additional information:		Additional information:
	Magic number(s): None		Magic number(s): None
	File extension(s): .TUC		File extension(s): .tuc
	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:
	Sam Ashmore - srashmo@radium.ncsc.mil		Sam Ashmore - srashmo@radium.ncsc.mil
	Intended usage: COMMON		Intended usage: COMMON
	Restrictions on usage: None		Restrictions on usage: None
	Author: Sam Ashmore - srashmo@radium.ncsc.mil		Author: Sam Ashmore - srashmo@radium.ncsc.mil
	Change controller: IESG		Change controller: IESG
	B.5. application/tamp-apex-update		B.5. application/tamp-apex-update
	To: ietf-types@iana.org		To: ietf-types@iana.org
	Subject: Registration of MIME media type application/tamp-apex-update		Subject: Registration of media type application/tamp-apex-update
	MIME media type name: application		Media type name: application
	MIME subtype name: tamp-apex-update		Subtype name: tamp-apex-update
	Required parameters: None		Required parameters: None
	Optional parameters: None		Optional parameters: None
	Encoding considerations: Binary		Encoding considerations: Binary
	Security considerations: Carries a signed request to update an apex		Security considerations: Carries a signed request to update an apex
	trust anchor information. Integrity protection is discussed in		trust anchor information. Integrity protection is discussed in
	section 4.5. Replay detection is discussed in section 6.		section 4.5. Replay detection is discussed in section 6.
	skipping to change at page 88, line 36 ¶		skipping to change at page 88, line 36 ¶
	Published specification: TBD		Published specification: TBD
	Applications that use this media type: TAMP clients responding to		Applications that use this media type: TAMP clients responding to
	requests to update an apex trust anchor.		requests to update an apex trust anchor.
	Additional information:		Additional information:
	Magic number(s): None		Magic number(s): None
	File extension(s): .TAU		File extension(s): .tau
	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:
	Sam Ashmore - srashmo@radium.ncsc.mil		Sam Ashmore - srashmo@radium.ncsc.mil
	Intended usage: COMMON		Intended usage: COMMON
	Restrictions on usage: None		Restrictions on usage: None
	Author: Sam Ashmore - srashmo@radium.ncsc.mil		Author: Sam Ashmore - srashmo@radium.ncsc.mil
	Change controller: IESG		Change controller: IESG
	B.6. application/tamp-apex-update-confirm		B.6. application/tamp-apex-update-confirm
	To: ietf-types@iana.org		To: ietf-types@iana.org
	Subject: Registration of MIME media type application/		Subject: Registration of media type application/
	tamp-apex-update-confirm		tamp-apex-update-confirm
	MIME media type name: application		Media type name: application
	MIME subtype name: tamp-apex-update-confirm		Subtype name: tamp-apex-update-confirm
	Required parameters: None		Required parameters: None
	Optional parameters: None		Optional parameters: None
	Encoding considerations: Binary		Encoding considerations: Binary
	Security considerations: Carries an optionally signed response to an		Security considerations: Carries an optionally signed response to an
	apex update request. Integrity protection is discussed in section		apex update request. Integrity protection is discussed in section
	4.6.		4.6.
	skipping to change at page 89, line 37 ¶		skipping to change at page 89, line 37 ¶
	Published specification: TBD		Published specification: TBD
	Applications that use this media type: TAMP clients responding to		Applications that use this media type: TAMP clients responding to
	requests to update an apex trust anchor.		requests to update an apex trust anchor.
	Additional information:		Additional information:
	Magic number(s): None		Magic number(s): None
	File extension(s): .AUC		File extension(s): .auc
	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:
	Sam Ashmore - srashmo@radium.ncsc.mil		Sam Ashmore - srashmo@radium.ncsc.mil
	Intended usage: COMMON		Intended usage: COMMON
	Restrictions on usage: None		Restrictions on usage: None
	Author: Sam Ashmore - srashmo@radium.ncsc.mil		Author: Sam Ashmore - srashmo@radium.ncsc.mil
	Change controller: IESG		Change controller: IESG
	B.7. application/tamp-community-update		B.7. application/tamp-community-update
	To: ietf-types@iana.org		To: ietf-types@iana.org
	Subject: Registration of MIME media type application/		Subject: Registration of media type application/tamp-community-update
	tamp-community-update
	MIME media type name: application		Media type name: application
	MIME subtype name: tamp-community-update		Subtype name: tamp-community-update
	Required parameters: None		Required parameters: None
	Optional parameters: None		Optional parameters: None
	Encoding considerations: Binary		Encoding considerations: Binary
	Security considerations: Carries a signed request to update community		Security considerations: Carries a signed request to update community
	membership information. Integrity protection is discussed in section		membership information. Integrity protection is discussed in section
	4.7. Replay detection is discussed in section 6.		4.7. Replay detection is discussed in section 6.
	skipping to change at page 90, line 37 ¶		skipping to change at page 90, line 36 ¶
	Published specification: TBD		Published specification: TBD
	Applications that use this media type: TAMP clients responding to		Applications that use this media type: TAMP clients responding to
	requests to update community membership.		requests to update community membership.
	Additional information:		Additional information:
	Magic number(s): None		Magic number(s): None
	File extension(s): .TCU		File extension(s): .tcu
	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:
	Sam Ashmore - srashmo@radium.ncsc.mil		Sam Ashmore - srashmo@radium.ncsc.mil
	Intended usage: COMMON		Intended usage: COMMON
	Restrictions on usage: None		Restrictions on usage: None
	Author: Sam Ashmore - srashmo@radium.ncsc.mil		Author: Sam Ashmore - srashmo@radium.ncsc.mil
	Change controller: IESG		Change controller: IESG
	B.8. application/tamp-community-update-confirm		B.8. application/tamp-community-update-confirm
	To: ietf-types@iana.org		To: ietf-types@iana.org
	Subject: Registration of MIME media type application/		Subject: Registration of media type application/
	tamp-community-update-confirm		tamp-community-update-confirm
	MIME media type name: application		Media type name: application
	MIME subtype name: tamp-community-update-confirm		Subtype name: tamp-community-update-confirm
	Required parameters: None		Required parameters: None
	Optional parameters: None		Optional parameters: None
	Encoding considerations: Binary		Encoding considerations: Binary
	Security considerations: Carries an optionally signed response to a		Security considerations: Carries an optionally signed response to a
	community update request. Integrity protection is discussed in		community update request. Integrity protection is discussed in
	section 4.8.		section 4.8.
	skipping to change at page 91, line 37 ¶		skipping to change at page 91, line 37 ¶
	Published specification: TBD		Published specification: TBD
	Applications that use this media type: TAMP clients responding to		Applications that use this media type: TAMP clients responding to
	requests to update community membership.		requests to update community membership.
	Additional information:		Additional information:
	Magic number(s): None		Magic number(s): None
	File extension(s): .CUC		File extension(s): .cuc
	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:
	Sam Ashmore - srashmo@radium.ncsc.mil		Sam Ashmore - srashmo@radium.ncsc.mil
	Intended usage: COMMON		Intended usage: COMMON
	Restrictions on usage: None		Restrictions on usage: None
	Author: Sam Ashmore - srashmo@radium.ncsc.mil		Author: Sam Ashmore - srashmo@radium.ncsc.mil
	Change controller: IESG		Change controller: IESG
	B.9. application/tamp-sequence-adjust		B.9. application/tamp-sequence-adjust
	To: ietf-types@iana.org		To: ietf-types@iana.org
	Subject: Registration of MIME media type application/		Subject: Registration of media type application/tamp-sequence-adjust
	tamp-sequence-adjust
	MIME media type name: application		Media type name: application
	MIME subtype name: tamp-sequence-adjust		Subtype name: tamp-sequence-adjust
	Required parameters: None		Required parameters: None
	Optional parameters: None		Optional parameters: None
	Encoding considerations: Binary		Encoding considerations: Binary
	Security considerations: Carries a signed request to update sequence		Security considerations: Carries a signed request to update sequence
	number information. Integrity protection is discussed in section		number information. Integrity protection is discussed in section
	4.9. Replay detection is discussed in section 6.		4.9. Replay detection is discussed in section 6.
	skipping to change at page 92, line 37 ¶		skipping to change at page 92, line 36 ¶
	Published specification: TBD		Published specification: TBD
	Applications that use this media type: TAMP clients responding to		Applications that use this media type: TAMP clients responding to
	requests to update sequence number information.		requests to update sequence number information.
	Additional information:		Additional information:
	Magic number(s): None		Magic number(s): None
	File extension(s): .TSA		File extension(s): .tsa
	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:
	Sam Ashmore - srashmo@radium.ncsc.mil		Sam Ashmore - srashmo@radium.ncsc.mil
	Intended usage: COMMON		Intended usage: COMMON
	Restrictions on usage: None		Restrictions on usage: None
	Author: Sam Ashmore - srashmo@radium.ncsc.mil		Author: Sam Ashmore - srashmo@radium.ncsc.mil
	Change controller: IESG		Change controller: IESG
	B.10. application/tamp-sequence-adjust-confirm		B.10. application/tamp-sequence-adjust-confirm
	To: ietf-types@iana.org		To: ietf-types@iana.org
	Subject: Registration of MIME media type application/		Subject: Registration of media type application/
	tamp-sequence-adjust-confirm		tamp-sequence-adjust-confirm
	MIME media type name: application		Media type name: application
	MIME subtype name: tamp-sequence-adjust-confirm		Subtype name: tamp-sequence-adjust-confirm
	Required parameters: None		Required parameters: None
	Optional parameters: None		Optional parameters: None
	Encoding considerations: Binary		Encoding considerations: Binary
	Security considerations: Carries an optionally signed sequence number		Security considerations: Carries an optionally signed sequence number
	adjust confirmation message. Integrity protection is discussed in		adjust confirmation message. Integrity protection is discussed in
	section 4.10.		section 4.10.
	skipping to change at page 93, line 37 ¶		skipping to change at page 93, line 37 ¶
	Published specification: TBD		Published specification: TBD
	Applications that use this media type: TAMP clients responding to		Applications that use this media type: TAMP clients responding to
	requests to update sequence number information.		requests to update sequence number information.
	Additional information:		Additional information:
	Magic number(s): None		Magic number(s): None
	File extension(s): .SAC		File extension(s): .sac
	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:
	Sam Ashmore - srashmo@radium.ncsc.mil		Sam Ashmore - srashmo@radium.ncsc.mil
	Intended usage: COMMON		Intended usage: COMMON
	Restrictions on usage: None		Restrictions on usage: None
	Author: Sam Ashmore - srashmo@radium.ncsc.mil		Author: Sam Ashmore - srashmo@radium.ncsc.mil
	Change controller: IESG		Change controller: IESG
	B.11. application/tamp-error		B.11. application/tamp-error
	To: ietf-types@iana.org		To: ietf-types@iana.org
	Subject: Registration of MIME media type application/tamp-error		Subject: Registration of media type application/tamp-error
	MIME media type name: application		Media type name: application
	MIME subtype name: tamp-error		Subtype name: tamp-error
	Required parameters: None		Required parameters: None
	Optional parameters: None		Optional parameters: None
	Encoding considerations: Binary		Encoding considerations: Binary
	Security considerations: Carries optionally signed error information		Security considerations: Carries optionally signed error information
	collecting during TAMP processing. Integrity protection is discussed		collecting during TAMP processing. Integrity protection is discussed
	in section 4.11.		in section 4.11.
	skipping to change at page 94, line 36 ¶		skipping to change at page 94, line 36 ¶
	Published specification: TBD		Published specification: TBD
	Applications that use this media type: TAMP clients processing TAMP		Applications that use this media type: TAMP clients processing TAMP
	messages.		messages.
	Additional information:		Additional information:
	Magic number(s): None		Magic number(s): None
	File extension(s): .TER		File extension(s): .ter
	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:
	Sam Ashmore - srashmo@radium.ncsc.mil		Sam Ashmore - srashmo@radium.ncsc.mil
	Intended usage: COMMON		Intended usage: COMMON
	Restrictions on usage: None		Restrictions on usage: None
End of changes. 52 change blocks.
	58 lines changed or deleted		53 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/