< draft-ietf-simple-prescaps-ext-09.txt		draft-ietf-simple-prescaps-ext-10.txt >
	SIMPLE WG M. Lonnfors		SIMPLE WG M. Lonnfors
	Internet-Draft K. Kiss		Internet-Draft K. Kiss
	Intended status: Standards Track Nokia		Intended status: Standards Track Nokia
	Expires: September 19, 2008 March 18, 2008		Expires: November 15, 2008 May 14, 2008
	Session Initiation Protocol (SIP) User Agent Capability Extension to		Session Initiation Protocol (SIP) User Agent Capability Extension to
	Presence Information Data Format (PIDF)		Presence Information Data Format (PIDF)
	draft-ietf-simple-prescaps-ext-09		draft-ietf-simple-prescaps-ext-10
	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 35 ¶		skipping to change at page 1, line 35 ¶
	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 19, 2008.		This Internet-Draft will expire on November 15, 2008.
	Abstract		Abstract
	Presence Information Data Format (PIDF) defines a common presence		Presence Information Data Format (PIDF) defines a common presence
	data format for Common Profile for Presence (CPP) compliant Presence		data format for Common Profile for Presence (CPP) compliant Presence
	protocols. This memo defines an extension to represent SIP User		protocols. This memo defines an extension to represent SIP User
	Agent capabilities in the Presence Information Document Format (PIDF)		Agent capabilities in the Presence Information Document Format (PIDF)
	compliant presence documents.		compliant presence documents.
	Table of Contents		Table of Contents
	skipping to change at page 2, line 49 ¶		skipping to change at page 2, line 49 ¶
	3.3.3. <description> element . . . . . . . . . . . . . . . . 15		3.3.3. <description> element . . . . . . . . . . . . . . . . 15
	4. Usage guidelines . . . . . . . . . . . . . . . . . . . . . . . 15		4. Usage guidelines . . . . . . . . . . . . . . . . . . . . . . . 15
	4.1. Use of <supported> and <notsupported> elements . . . . . . 16		4.1. Use of <supported> and <notsupported> elements . . . . . . 16
	5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 16		5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
	6. XML schema definitions . . . . . . . . . . . . . . . . . . . . 18		6. XML schema definitions . . . . . . . . . . . . . . . . . . . . 18
	7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26		7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26
	7.1. URN sub-namespace registration for		7.1. URN sub-namespace registration for
	'urn:ietf:params:xml:ns:pidf:caps' . . . . . . . . . . . . 26		'urn:ietf:params:xml:ns:pidf:caps' . . . . . . . . . . . . 26
	8. Security Considerations . . . . . . . . . . . . . . . . . . . 27		8. Security Considerations . . . . . . . . . . . . . . . . . . . 27
	9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 27		9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 27
	10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 27		10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 28
	10.1. Normative references . . . . . . . . . . . . . . . . . . . 27		10.1. Normative references . . . . . . . . . . . . . . . . . . . 28
	10.2. Informative references . . . . . . . . . . . . . . . . . . 28		10.2. Informative references . . . . . . . . . . . . . . . . . . 28
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 28		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 29
	Intellectual Property and Copyright Statements . . . . . . . . . . 30		Intellectual Property and Copyright Statements . . . . . . . . . . 30
	1. Introduction		1. Introduction
	Common Profile for Presence (CPP) [RFC3859] and Common Profile for		Common Profile for Presence (CPP) [RFC3859] and Common Profile for
	Instant Messaging (CPIM) [RFC3860] define common operations and		Instant Messaging (CPIM) [RFC3860] define common operations and
	formats which all presence and instant messaging services must agree		formats which all presence and instant messaging services must agree
	upon so that basic interoperability would be possible. The actual		upon so that basic interoperability would be possible. The actual
	base format for the presence is defined in the Presence Information		base format for the presence is defined in the Presence Information
	Document Format (PIDF) [RFC3863]. The PIDF has been designed to		Document Format (PIDF) [RFC3863]. The PIDF has been designed to
	skipping to change at page 15, line 33 ¶		skipping to change at page 15, line 33 ¶
	device as defined in [RFC3840].		device as defined in [RFC3840].
	The <description> element is of string type and does not have any		The <description> element is of string type and does not have any
	attributes.		attributes.
	The <description> element SHOULD be labeled with the 'xml:lang'		The <description> element SHOULD be labeled with the 'xml:lang'
	attribute to indicate its language and script. The specification		attribute to indicate its language and script. The specification
	allows multiple occurrences of this elements so that the presentity		allows multiple occurrences of this elements so that the presentity
	can convey <description> elements in multiple scripts and languages.		can convey <description> elements in multiple scripts and languages.
	If no 'xml:lang' attribute is provided, the default value is		If no 'xml:lang' attribute is provided, the default value is
	"i-default" as defined in RFC 2277[RFC2277].		"i-default" as defined in [RFC2277].
	4. Usage guidelines		4. Usage guidelines
	The User Agent Capabilities extension [RFC3840] recommends that a UA		The User Agent Capabilities extension [RFC3840] recommends that a UA
	provides complete information in its contact predicate. However, it		provides complete information in its contact predicate. However, it
	may be that presentity is not willing to publish presence information		may be that presentity is not willing to publish presence information
	which would be consistent with actual device or service capabilities		which would be consistent with actual device or service capabilities
	(e.g. presentity may not want to indicate that he/she supports voice		(e.g. presentity may not want to indicate that he/she supports voice
	when the service actually is able to support it). Authorization		when the service actually is able to support it). Authorization
	rules or policies in presence server may limit or modify the		rules or policies in presence server may limit or modify the
	skipping to change at page 16, line 9 ¶		skipping to change at page 16, line 9 ¶
	mismatch of information.		mismatch of information.
	It is RECOMMENDED that Presence User Agents (PUAs) using this		It is RECOMMENDED that Presence User Agents (PUAs) using this
	extension provide as complete presence information as they can. If		extension provide as complete presence information as they can. If
	the PUA is publishing sensitive information using this extension, it		the PUA is publishing sensitive information using this extension, it
	SHOULD obtain a permission from a user. PUAs can indicate all the		SHOULD obtain a permission from a user. PUAs can indicate all the
	explicitly supported capabilities using the <supported> element and		explicitly supported capabilities using the <supported> element and
	all the explicitly not supported capabilities using the		all the explicitly not supported capabilities using the
	<notsupported> element, where appropriate.		<notsupported> element, where appropriate.
	However, it is not mandated that this presence information should be		It is not mandated that presence information should be consistent
	consistent with actual device capabilities. Because of this watchers		with actual service or device capabilities. However, it is the
	should not expect that the presence information represented by this		presentity's best interest to avoid publishing false presence
	extension fully represents the actual presentity's device		information and provide accurate information to help to minimize
	capabilities or that signaled SIP session would support certain		unsuccessful communication invitations. Otherwise, watchers may
	capabilities. As explained in section Section 1.2 presence of this		conclude that communication cannot be established with the presentity
	extension does not replace the use of SIP signaling.		but in reality it would be possible, or certain communication
			capabilities are available but in reality a communication
			establishment attempt would fail using those capabilities. In any
			case, watchers should not expect the presence information represented
			by this extension to be fully aligned with the actual presentity's
			service or device capabilities. As explained in section Section 1.2
			presence of this extension does not replace the use of SIP signaling
			for capability negotiation.
	4.1. Use of <supported> and <notsupported> elements		4.1. Use of <supported> and <notsupported> elements
	PUAs should add information under <supported> and <notsupported>		PUAs should add information under <supported> and <notsupported>
	elements only when they believe it may affect the decision making in		elements only when they believe it may affect the decision making in
	the watcher's end, i.e. information should be relevant and valuable		the watcher's end, i.e. information should be relevant and valuable
	for the watcher. Listing all possible information under <supported>		for the watcher. Listing all possible information under <supported>
	and <notsupported> is rarely needed.		and <notsupported> is rarely needed.
	For example, if the PUA wants to advertise a message service that		For example, if the PUA wants to advertise a message service that
	skipping to change at page 18, line 42 ¶		skipping to change at page 18, line 45 ¶
	<xs:element name="audio" type="tns:audiotype" minOccurs="0"/>		<xs:element name="audio" type="tns:audiotype" minOccurs="0"/>
	<xs:element name="automata" type="tns:automatatype"		<xs:element name="automata" type="tns:automatatype"
	minOccurs="0"/>		minOccurs="0"/>
	<xs:element name="class" type="tns:classtype"		<xs:element name="class" type="tns:classtype"
	minOccurs="0"/>		minOccurs="0"/>
	<xs:element name="control" type="tns:controltype"		<xs:element name="control" type="tns:controltype"
	minOccurs="0"/>		minOccurs="0"/>
	<xs:element name="data" type="tns:datatype"		<xs:element name="data" type="tns:datatype"
	minOccurs="0"/>		minOccurs="0"/>
	<xs:element name="description" type="tns:descriptiontype"		<xs:element name="description" type="tns:descriptiontype"
	minOccurs="0"/>		minOccurs="0" maxOccurs="unbounded"/>
	<xs:element name="duplex" type="tns:duplextype"		<xs:element name="duplex" type="tns:duplextype"
	minOccurs="0"/>		minOccurs="0"/>
	<xs:element name="event-packages" type="tns:event-packagestype"		<xs:element name="event-packages" type="tns:event-packagestype"
	minOccurs="0"/>		minOccurs="0"/>
	<xs:element name="extensions" type="tns:extensionstype"		<xs:element name="extensions" type="tns:extensionstype"
	minOccurs="0"/>		minOccurs="0"/>
	<xs:element name="isfocus" type="tns:isfocustype"		<xs:element name="isfocus" type="tns:isfocustype"
	minOccurs="0"/>		minOccurs="0"/>
	<xs:element name="message" type="tns:messagetype"		<xs:element name="message" type="tns:messagetype"
	minOccurs="0"/>		minOccurs="0"/>
	skipping to change at page 19, line 29 ¶		skipping to change at page 19, line 33 ¶
	<xs:any namespace="##other" processContents="lax"		<xs:any namespace="##other" processContents="lax"
	minOccurs="0" maxOccurs="unbounded"/>		minOccurs="0" maxOccurs="unbounded"/>
	</xs:sequence>		</xs:sequence>
	<xs:anyAttribute namespace="##any" processContents="lax"/>		<xs:anyAttribute namespace="##any" processContents="lax"/>
	</xs:complexType>		</xs:complexType>
	<xs:element name="devcaps" type="tns:devcaps"/>		<xs:element name="devcaps" type="tns:devcaps"/>
	<xs:complexType name="devcaps">		<xs:complexType name="devcaps">
	<xs:sequence>		<xs:sequence>
	<xs:element name="description" type="tns:descriptiontype"		<xs:element name="description" type="tns:descriptiontype"
	minOccurs="0"/>		minOccurs="0" maxOccurs="unbounded"/>
	<xs:element name="mobility" type="tns:mobilitytype"		<xs:element name="mobility" type="tns:mobilitytype"
	minOccurs="0"/>		minOccurs="0"/>
	<xs:any namespace="##other" processContents="lax"		<xs:any namespace="##other" processContents="lax"
	minOccurs="0" maxOccurs="unbounded"/>		minOccurs="0" maxOccurs="unbounded"/>
	</xs:sequence>		</xs:sequence>
	<xs:anyAttribute namespace="##any" processContents="lax"/>		<xs:anyAttribute namespace="##any" processContents="lax"/>
	</xs:complexType>		</xs:complexType>
	<!-- AUDIO -->		<!-- AUDIO -->
	<xs:simpleType name="audiotype">		<xs:simpleType name="audiotype">
	skipping to change at page 21, line 33 ¶		skipping to change at page 21, line 38 ¶
	<xs:element name="receive-only" type="xs:string"		<xs:element name="receive-only" type="xs:string"
	minOccurs="0"/>		minOccurs="0"/>
	<xs:element name="send-only" type="xs:string"		<xs:element name="send-only" type="xs:string"
	minOccurs="0"/>		minOccurs="0"/>
	<xs:any namespace="##other" processContents="lax"		<xs:any namespace="##other" processContents="lax"
	minOccurs="0" maxOccurs="unbounded"/>		minOccurs="0" maxOccurs="unbounded"/>
	</xs:sequence>		</xs:sequence>
	</xs:complexType>		</xs:complexType>
	<!-- DESCRIPTION -->		<!-- DESCRIPTION -->
	<xs:simpleType name="descriptiontype">		<xs:complexType name="descriptiontype">
	<xs:restriction base="xs:string"/>		<xs:simpleContent>
	</xs:simpleType>		<xs:extension base="xs:string">
			<xs:attribute ref="xml:lang"/>
			</xs:extension>
			</xs:simpleContent>
			</xs:complexType>
	<!-- EVENT-PACKAGES -->		<!-- EVENT-PACKAGES -->
	<xs:complexType name="event-packagestype">		<xs:complexType name="event-packagestype">
	<xs:sequence>		<xs:sequence>
	<xs:element name="supported" type="tns:eventtypes"		<xs:element name="supported" type="tns:eventtypes"
	minOccurs="0"/>		minOccurs="0"/>
	<xs:element name="notsupported" type="tns:eventtypes"		<xs:element name="notsupported" type="tns:eventtypes"
	minOccurs="0"/>		minOccurs="0"/>
	</xs:sequence>		</xs:sequence>
	</xs:complexType>		</xs:complexType>
	<xs:complexType name="eventtypes">		<xs:complexType name="eventtypes">
	<xs:sequence>		<xs:sequence>
	<xs:element name="conference" type="xs:string"		<xs:element name="conference" type="xs:string"
	minOccurs="0"/>		minOccurs="0"/>
	<xs:element name="dialog" type="xs:string"		<xs:element name="dialog" type="xs:string"
	minOccurs="0"/>		minOccurs="0"/>
	<xs:element name="kpml" type="xs:string"		<xs:element name="kpml" type="xs:string"
	minOccurs="0"/>		minOccurs="0"/>
	skipping to change at page 26, line 43 ¶		skipping to change at page 27, line 4 ¶
	This memo calls for IANA to register one new XML namespace URNs as		This memo calls for IANA to register one new XML namespace URNs as
	defined in [RFC3688].		defined in [RFC3688].
	7.1. URN sub-namespace registration for		7.1. URN sub-namespace registration for
	'urn:ietf:params:xml:ns:pidf:caps'		'urn:ietf:params:xml:ns:pidf:caps'
	URI:		URI:
	urn:ietf:params:xml:ns:pidf:caps		urn:ietf:params:xml:ns:pidf:caps
	Description:		Description:
	This is the XML namespace for XML elements defined by [[[RFCXXXX]]]		This is the XML namespace for XML elements defined by [[[RFCXXXX]]]
	to describe service and device capabilities in application/pidf+xml		to describe service and device capabilities in application/pidf+xml
	content type.		content type.
	Registrant Contact:		Registrant Contact:
	IETF, SIMPLE working group, <simple@ietf.org>		IETF, SIMPLE working group, <simple@ietf.org>
	Mikko Lonnfors, <mikko.lonnfors@nokia.com>		Mikko Lonnfors, <mikko.lonnfors@nokia.com>
	XML:		XML:
	BEGIN		BEGIN
	<?xml version="1.0"?>		<?xml version="1.0"?>
	<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"		<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
	"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">		"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
	<html xmlns="http://www.w3.org/1999/xhtml>		<html> xmlns="http://www.w3.org/1999/xhtml
	<head>		<head>
	<meta http-equiv="content-type"		<meta http-equiv="content-type"
	content="text/html;charset=iso-8859-1"/>		content="text/html;charset=iso-8859-1"/>
	<title>Namespace for PIDF user agent capability		<title>Namespace for PIDF user agent capability
	extension</title>		extension</title>
	</head>		</head>
	<body>		<body>
	<h1>Namespace for PIDF service capability extension</h1>		<h1>Namespace for PIDF service capability extension</h1>
	<h2>urn:ietf:params:xml:ns:pidf:caps</h2>		<h2>urn:ietf:params:xml:ns:pidf:caps</h2>
	<p>See <a href="[[[URL of published RFC]]]">RFCXXXX</a>.</p>		<p>See <a href="[[[URL of published RFC]]]">RFCXXXX</a>.</p>
End of changes. 13 change blocks.
	20 lines changed or deleted		33 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/