< draft-ietf-simple-xcap-diff-08.txt		draft-ietf-simple-xcap-diff-09.txt >
	SIMPLE J. Rosenberg		SIMPLE J. Rosenberg
	Internet-Draft Cisco		Internet-Draft Cisco
	Intended status: Standards Track J. Urpalainen		Intended status: Standards Track J. Urpalainen
	Expires: August 28, 2008 Nokia		Expires: November 6, 2008 Nokia
	February 25, 2008		May 5, 2008
	An Extensible Markup Language (XML) Document Format for Indicating A		An Extensible Markup Language (XML) Document Format for Indicating A
	Change in XML Configuration Access Protocol (XCAP) Resources		Change in XML Configuration Access Protocol (XCAP) Resources
	draft-ietf-simple-xcap-diff-08		draft-ietf-simple-xcap-diff-09
	Status of this Memo		Status of this Memo
	By submitting this Internet-Draft, each author represents that any		By submitting this Internet-Draft, each author represents that any
	applicable patent or other IPR claims of which he or she is aware		applicable patent or other IPR claims of which he or she is aware
	have been or will be disclosed, and any of which he or she becomes		have been or will be disclosed, and any of which he or she becomes
	aware will be disclosed, in accordance with Section 6 of BCP 79.		aware will be disclosed, in accordance with Section 6 of BCP 79.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF), its areas, and its working groups. Note that		Task Force (IETF), its areas, and its working groups. Note that
	skipping to change at page 1, line 36 ¶		skipping to change at page 1, line 36 ¶
	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 August 28, 2008.		This Internet-Draft will expire on November 6, 2008.
	Copyright Notice
	Copyright (C) The IETF Trust (2008).
	Abstract		Abstract
	This specification defines a document format that can be used to		This specification defines a document format that can be used to
	indicate that a change has occurred in a document managed by the		indicate that a change has occurred in a document managed by the
	Extensible Markup Language (XML) Configuration Access Protocol		Extensible Markup Language (XML) Configuration Access Protocol
	(XCAP). This format indicates the document that has changed and its		(XCAP). This format indicates the document that has changed and its
	former and new entity tags. It also can indicate the specific change		former and new entity tags. It also can indicate the specific change
	that was made in the document, using an XML patch format. This		that was made in the document, using an XML patch format. This
	format allows also indications of element and attribute content of an		format allows also indications of element and attribute content of an
	skipping to change at page 2, line 21 ¶		skipping to change at page 2, line 17 ¶
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
	2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4		2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
	3. Structure of an XCAP Diff Document . . . . . . . . . . . . . . 4		3. Structure of an XCAP Diff Document . . . . . . . . . . . . . . 4
	4. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 7		4. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 7
	5. Example Document . . . . . . . . . . . . . . . . . . . . . . . 9		5. Example Document . . . . . . . . . . . . . . . . . . . . . . . 9
	6. Security Considerations . . . . . . . . . . . . . . . . . . . 10		6. Security Considerations . . . . . . . . . . . . . . . . . . . 10
	7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11		7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
	7.1. application/xcap-diff+xml MIME Type . . . . . . . . . . . 11		7.1. application/xcap-diff+xml MIME Type . . . . . . . . . . . 11
	7.2. URN Sub-Namespace Registration for		7.2. URN Sub-Namespace Registration for
	urn:ietf:params:xml:ns:xcap-diff . . . . . . . . . . . . . 12		urn:ietf:params:xml:ns:xcap-diff . . . . . . . . . . . . . 12
	7.3. Schema Registration . . . . . . . . . . . . . . . . . . . 12		7.3. Schema Registration . . . . . . . . . . . . . . . . . . . 13
	8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 13		8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 13
	9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13		9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13
	9.1. Normative References . . . . . . . . . . . . . . . . . . . 13		9.1. Normative References . . . . . . . . . . . . . . . . . . . 13
	9.2. Informative References . . . . . . . . . . . . . . . . . . 14		9.2. Informative References . . . . . . . . . . . . . . . . . . 14
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14
	Intellectual Property and Copyright Statements . . . . . . . . . . 16		Intellectual Property and Copyright Statements . . . . . . . . . . 16
	1. Introduction		1. Introduction
	The Extensible Markup Language (XML) Configuration Access Protocol		The Extensible Markup Language (XML) Configuration Access Protocol
	skipping to change at page 11, line 6 ¶		skipping to change at page 11, line 6 ¶
	6. Security Considerations		6. Security Considerations
	XCAP diff documents can include changes from one document to another.		XCAP diff documents can include changes from one document to another.
	As a consequence, if the document itself is sensitive and requires		As a consequence, if the document itself is sensitive and requires
	confidentiality, integrity or authentication, then the same applies		confidentiality, integrity or authentication, then the same applies
	to the XCAP diff format. Therefore, protocols which transport XCAP		to the XCAP diff format. Therefore, protocols which transport XCAP
	diff documents must provide sufficient security capabilities for		diff documents must provide sufficient security capabilities for
	transporting the document itself.		transporting the document itself.
			The SIP event package framework specified in RFC 3265 [RFC3265] is
			the most typical use-case for this format. Then in general its
			security considerations apply, but event packages MAY also have other
			specific threats which MUST be considered on an application-by-
			application basis.
	7. IANA Considerations		7. IANA Considerations
	There are several IANA considerations associated with this		There are several IANA considerations associated with this
	specification.		specification.
	7.1. application/xcap-diff+xml MIME Type		7.1. application/xcap-diff+xml MIME Type
	MIME media type name: application		MIME media type name: application
	MIME subtype name: xcap-diff+xml		MIME subtype name: xcap-diff+xml
	skipping to change at page 13, line 4 ¶		skipping to change at page 13, line 11 ¶
	</body>		</body>
	</html>		</html>
	END		END
	7.3. Schema Registration		7.3. Schema Registration
	This section registers a new XML schema per the procedures in		This section registers a new XML schema per the procedures in
	[RFC3688].		[RFC3688].
	URI: urn:ietf:params:xml:schema:xcap-diff		URI: urn:ietf:params:xml:schema:xcap-diff
	Registrant Contact: IETF, SIMPLE working group, (simple@ietf.org),		Registrant Contact: IETF, SIMPLE working group, (simple@ietf.org),
	Jonathan Rosenberg (jdrosen@jdrosen.net).		Jonathan Rosenberg (jdrosen@jdrosen.net).
	The XML for this schema can be found as the sole content of		The XML for this schema can be found as the sole content of
	Section 4.		Section 4.
	8. Acknowledgments		8. Acknowledgments
	The authors would like to thank Pavel Dostal, Jeroen van Bemmel,		The authors would like to thank Pavel Dostal, Jeroen van Bemmel,
	Martin Hynar and Anders Lindgren for their valuable comments.		Martin Hynar, Anders Lindgren and Mary Barnes for their valuable
			comments.
	9. References		9. References
	9.1. Normative References		9.1. Normative References
	[W3C.REC-xml-20060816]		[W3C.REC-xml-20060816]
	Maler, E., Paoli, J., Bray, T., Yergeau, F., and C.		Maler, E., Paoli, J., Bray, T., Yergeau, F., and C.
	Sperberg-McQueen, "Extensible Markup Language (XML) 1.0		Sperberg-McQueen, "Extensible Markup Language (XML) 1.0
	(Fourth Edition)", World Wide Web Consortium		(Fourth Edition)", World Wide Web Consortium
	Recommendation REC-xml-20060816, August 2006,		Recommendation REC-xml-20060816, August 2006,
	skipping to change at page 16, line 44 ¶		skipping to change at line 677 ¶
	attempt made to obtain a general license or permission for the use of		attempt made to obtain a general license or permission for the use of
	such proprietary rights by implementers or users of this		such proprietary rights by implementers or users of this
	specification can be obtained from the IETF on-line IPR repository at		specification can be obtained from the IETF on-line IPR repository at
	http://www.ietf.org/ipr.		http://www.ietf.org/ipr.
	The IETF invites any interested party to bring to its attention any		The IETF invites any interested party to bring to its attention any
	copyrights, patents or patent applications, or other proprietary		copyrights, patents or patent applications, or other proprietary
	rights that may cover technology that may be required to implement		rights that may cover technology that may be required to implement
	this standard. Please address the information to the IETF at		this standard. Please address the information to the IETF at
	ietf-ipr@ietf.org.		ietf-ipr@ietf.org.
	Acknowledgment
	Funding for the RFC Editor function is provided by the IETF
	Administrative Support Activity (IASA).
End of changes. 8 change blocks.
	10 lines changed or deleted		14 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/