No Description
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

xep-0119.xml 12KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180
  1. <?xml version='1.0' encoding='UTF-8'?>
  2. <!DOCTYPE xep SYSTEM 'xep.dtd' [
  3. <!ENTITY % ents SYSTEM 'xep.ent'>
  4. %ents;
  5. ]>
  6. <?xml-stylesheet type='text/xsl' href='xep.xsl'?>
  7. <xep>
  8. <header>
  9. <title>Extended Presence Protocol Suite</title>
  10. <abstract>This document specifies a set of XMPP extensions that provide support for extended presence information.</abstract>
  11. &LEGALNOTICE;
  12. <number>0119</number>
  13. <status>Retracted</status>
  14. <type>Standards Track</type>
  15. <sig>Standards</sig>
  16. <dependencies>
  17. <spec>XMPP Core</spec>
  18. <spec>XMPP IM</spec>
  19. <spec>XEP-0060</spec>
  20. <spec>XEP-0073</spec>
  21. <spec>XEP-0080</spec>
  22. <spec>XEP-0084</spec>
  23. <spec>XEP-0107</spec>
  24. <spec>XEP-0108</spec>
  25. <spec>XEP-0112</spec>
  26. <spec>XEP-0163</spec>
  27. </dependencies>
  28. <supersedes/>
  29. <supersededby>
  30. <spec>XEP-0163</spec>
  31. </supersededby>
  32. <shortname>N/A</shortname>
  33. &stpeter;
  34. <revision>
  35. <version>0.8</version>
  36. <date>2006-08-08</date>
  37. <initials>psa</initials>
  38. <remark><p>Retracted: superseded by Personal Eventing via Pubsub (XEP-0163).</p></remark>
  39. </revision>
  40. <revision>
  41. <version>0.7</version>
  42. <date>2006-01-19</date>
  43. <initials>psa</initials>
  44. <remark><p>Updated to reflect Personal Eventing via Pubsub (XEP-0163).</p></remark>
  45. </revision>
  46. <revision>
  47. <version>0.6</version>
  48. <date>2005-03-28</date>
  49. <initials>psa</initials>
  50. <remark><p>Added avatar support to required protocols.</p></remark>
  51. </revision>
  52. <revision>
  53. <version>0.5</version>
  54. <date>2004-07-22</date>
  55. <initials>psa</initials>
  56. <remark><p>Further defined the pubsub/disco interaction.</p></remark>
  57. </revision>
  58. <revision>
  59. <version>0.4</version>
  60. <date>2004-05-12</date>
  61. <initials>psa</initials>
  62. <remark><p>Removed text on auto-subscribe functionality.</p></remark>
  63. </revision>
  64. <revision>
  65. <version>0.3</version>
  66. <date>2004-05-11</date>
  67. <initials>psa</initials>
  68. <remark><p>Added introduction and background; defined well-known service discovery node for extended presence information; described auto-subscribe functionality.</p></remark>
  69. </revision>
  70. <revision>
  71. <version>0.2</version>
  72. <date>2003-11-24</date>
  73. <initials>psa</initials>
  74. <remark><p>Status changed to Deferred.</p></remark>
  75. </revision>
  76. <revision>
  77. <version>0.1</version>
  78. <date>2003-09-08</date>
  79. <initials>psa</initials>
  80. <remark><p>Initial version.</p></remark>
  81. </revision>
  82. </header>
  83. <section1 topic='Introduction' anchor='intro'>
  84. <p>A number of network services enable the exchange of information about an entity's availability for communications over the network. This information is usually called "presence". Examples include a person's availability to talk over a traditional or mobile telephony network, chat over an instant messaging (IM) network, or participate in a video conference. In this core sense, presence is a boolean, "on/off" indicator of network availability.</p>
  85. <p>Over time, this core notion of presence has been extended to include other information about the entity that either (1) changes quickly or (2) affects the entity's interest in or ability to engage in communications. Examples of such "extended presence" include a person's proximity to or interaction with a user agent (e.g., "away" or "do not disturb"), activity (e.g., "driving"), ambient environment (e.g., "noisy"), and mood (e.g., "grumpy"). Related information includes data about the person's available devices (e.g., "phone" or "IM"), current contact modes or address, and date/time ranges for availability. Because extended presence information can change quite often (e.g., several times in the course of a typical IM session), it is distinct from more stable information about the individual (such as is captured in a vCard or other user profile).</p>
  86. <p>This document describes a unified approach to the provision and communication of extended presence information using the Extensible Messaging and Presence Protocol (XMPP), in the form of a "protocol suite" that incorporates by reference a number of existing XMPP extensions.</p>
  87. </section1>
  88. <section1 topic='Background' anchor='background'>
  89. <p>XMPP began life as a dedicated instant messaging and presence protocol within the Jabber community. The needs of this community were not advanced (simple IM and presence), and the presence model designed by that community mainly takes account of basic presence only (i.e., on/off availability on an IM network). Within this model (and using the terminology of &rfc2778;), the only watchers are those in the principal's contact list (in XMPP called a "roster"). In addition, authorization to receive basic presence broadcasts is handled by the principal through a combination of roster management and basic presence subscriptions as defined in &xmppim;. The presence service is tied to the principal's session with a server, and the server's internal session manager handles both presence and instant messaging functionality (although IM and presence can be separated in system configuration or "on the fly" via negative presence priorities).</p>
  90. <p>This basic presence model was not designed for the more advanced world of extended presence. While some existing IM clients publish extended presence information as XML extensions to the XMPP &PRESENCE; stanza, that model does not scale well, does not respect the bandwidth restrictions of many clients on the network, and does not provide for more granular control over information access (anyone who receives presence will also receive geolocation data and the like). However, there is a more advanced protocol that is specially designed to fully implement the publish-subscribe design pattern on top of XMPP, specified in <strong>XEP-0060:</strong> &xep0060;. The publish-subscribe protocol can be used to create a service that provides full control over each type of extended presence data, sending that data only to those specifically authorized to receive it and those who have an active interest in each extension. In particular, for extended presence related to IM users, we specify the use of the personal eventing subset of <cite>XEP-0060</cite>, as defined in <cite>XEP-0163</cite>.</p>
  91. <p>The provision and communication of extended presence information follows the classic publish-subscribe design pattern: an individual publishes information such as geographical location data, and the data is broadcasted to all subscribers who are authorized to receive that data. (Alternatively, the data can be published on behalf of the individual, such as by a mobile telephony service that has knowledge of the individual's geographical location and authorization to act as a publisher of that data.) In general, the relationship between the publisher and subscriber is mediated by a service that receives publication requests, broadcasts data to subscribers, and enables the individual to manage lists of entities that are authorized to publish or subscribe to the data. This model makes it possible to deploy highly flexible extended presence services within the context of XMPP.</p>
  92. <p>The following diagram provides a schematic representation of such a service.</p>
  93. <code>
  94. Mobile XMPP
  95. Telephony Principal Session
  96. Service | Manager
  97. |__________ ________|_________ __________|
  98. | | | | | | | |
  99. |1| |2| |3| |4| |5| |6|
  100. +-------------------------+
  101. | |
  102. | Extended Presence |
  103. | Service |
  104. | |
  105. +-------------------------+
  106. |1| |2| |3| |4| |5| |6|
  107. |___| |_| | _______|_
  108. | | || | |
  109. Sub Sub Sub Sub Sub
  110. </code>
  111. <p>In this example, there are six different extended presence nodes (these might be, for example, geographical location, avatar, activity, mood, network availability, etc.). The principal is authorized to publish to all six, a Mobile Telephony Service is also authorized to publish to Node 1 (e.g., geolocation), and an XMPP Session Manager is also authorized to publish to Node 6 (e.g., network availability). There are five subscribers: Subscriber 1 is authorized to receive data from Node 1 and Node 2, Subscriber 2 is authorized to Node 2 and Node 3, Subscriber 3 is authorized to receive data from Node 4 and Node 6, and Subscribers 4 and 5 are authorized to receive data from Node 6 only.</p>
  112. </section1>
  113. <section1 topic='Requirements' anchor='reqs'>
  114. <p>This document follows the same approach as &xep0073;. By design, the Basic IM Protocol Suite does not include more advanced functionality related to "extended presence"; the present document fills the need for a protocol suite that addresses such functionality.</p>
  115. <p>A protocol is deemed worthy of inclusion in this protocol suite if:</p>
  116. <ul>
  117. <li>It addresses "extended presence" data that is defined in other presence services or protocols (e.g., Wireless Village or SIMPLE), or that is felt to be needed within the Jabber/XMPP community.</li>
  118. <li>It has achieved a status of at least Draft within the XMPP Standards Foundation's standards process (as defined in &xep0001;).</li>
  119. </ul>
  120. </section1>
  121. <section1 topic='Extended Presence Protocol Suite' anchor='suite'>
  122. <p>We define the Extended Presence Protocol Suite as follows:</p>
  123. <table caption='Required and Recommended Specifications'>
  124. <tr>
  125. <th>Specification</th>
  126. <th>Requirement Level</th>
  127. </tr>
  128. <tr>
  129. <td><strong>XEP-0073: Basic IM Protocol Suite</strong></td>
  130. <td>REQUIRED (prerequisite)</td>
  131. </tr>
  132. <tr>
  133. <td><strong>XEP-0163: Personal Eventing via Pubsub</strong></td>
  134. <td>REQUIRED (prerequisite)</td>
  135. </tr>
  136. <tr>
  137. <td>&xep0080;</td>
  138. <td>REQUIRED</td>
  139. </tr>
  140. <tr>
  141. <td>&xep0112;</td>
  142. <td>REQUIRED</td>
  143. </tr>
  144. <tr>
  145. <td>&xep0108;</td>
  146. <td>REQUIRED</td>
  147. </tr>
  148. <tr>
  149. <td>&xep0107;</td>
  150. <td>REQUIRED</td>
  151. </tr>
  152. <tr>
  153. <td>&xep0084;</td>
  154. <td>REQUIRED *</td>
  155. </tr>
  156. </table>
  157. <p>* <em>Note:</em> The User Avatar specification (<cite>XEP-0084</cite>) has not yet advanced to a status of Draft within the XSF's standards process, and the Extended Presence Protocol Suite will not be submitted for approval until it does so.</p>
  158. </section1>
  159. <section1 topic='Node Discovery' anchor='discovery'>
  160. <p>Discovery of extended presence pubsub nodes is expedited through the use of <cite>Personal Eventing via Pubsub</cite> (PEP), since in PEP services there is a one-to-one relationship between payload types and NodeIDs. The NodeIDs MUST be as follows:</p>
  161. <ul>
  162. <li>Activity: http://jabber.org/protocol/activity</li>
  163. <li>Avatar: http://jabber.org/protocol/avatar#metadata</li>
  164. <li>Geolocation: http://jabber.org/protocol/geoloc</li>
  165. <li>Mood: http://jabber.org/protocol/mood</li>
  166. <li>Physical Location: http://jabber.org/protocol/physloc</li>
  167. </ul>
  168. <p>These nodes SHOULD have an access model of either "presence" or "roster".</p>
  169. </section1>
  170. <section1 topic='Security Considerations' anchor='security'>
  171. <p>This document introduces no new security considerations above and beyond those defined in the documents on which it depends. Because publicly exposing some forms of extended presence information (e.g., geolocation information) may lead to unnecessary risks, care should be taken in setting the access model for the relevant pubsub nodes (minimally, an access model of "presence" to take advantage of the bidirectional authorization scheme inherent in XMPP presence subscriptions).</p>
  172. </section1>
  173. <section1 topic='IANA Considerations' anchor='iana'>
  174. <p>This document requires no interaction with &IANA;.</p>
  175. </section1>
  176. <section1 topic='XMPP Registrar Considerations' anchor='registrar'>
  177. <p>This document requires no interaction with the &REGISTRAR;.</p>
  178. </section1>
  179. </xep>