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-0152.xml 15KB

  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>Reachability Addresses</title>
  10. <abstract>This document defines an XMPP protocol extension for communicating information about how an entity can be reached temporarily using methods other than the entity's normal JID.</abstract>
  12. <number>0152</number>
  13. <status>Draft</status>
  14. <type>Standards Track</type>
  15. <sig>Standards</sig>
  16. <approver>Council</approver>
  17. <dependencies>
  18. <spec>XMPP Core</spec>
  19. <spec>XMPP IM</spec>
  20. </dependencies>
  21. <supersedes/>
  22. <supersededby/>
  23. <shortname>reach</shortname>
  24. <schemaloc>
  25. <ns>reach</ns>
  26. <url></url>
  27. </schemaloc>
  28. &stpeter;
  29. &hildjj;
  30. <revision>
  31. <version>1.0</version>
  32. <date>2014-02-25</date>
  33. <initials>XEP Editor (mm)</initials>
  34. <remark><p>Per a vote of the XMPP Council, advanced specification from Experimental to Draft.</p></remark>
  35. </revision>
  36. <revision>
  37. <version>0.6</version>
  38. <date>2013-12-02</date>
  39. <initials>psa</initials>
  40. <remark><p>Further clarified the intent of the protocol.</p></remark>
  41. </revision>
  42. <revision>
  43. <version>0.5</version>
  44. <date>2013-09-25</date>
  45. <initials>psa</initials>
  46. <remark><p>Modified the text and examples to better illustrate the primary use case.</p></remark>
  47. </revision>
  48. <revision>
  49. <version>0.4</version>
  50. <date>2013-02-05</date>
  51. <initials>psa</initials>
  52. <remark><p>Updated to reflect new XMPP RFCs; strengthened security considerations.</p></remark>
  53. </revision>
  54. <revision>
  55. <version>0.3</version>
  56. <date>2008-10-06</date>
  57. <initials>psa</initials>
  58. <remark>
  59. <ul>
  60. <li>Modified namespaces to incorporate namespace versioning.</li>
  61. <li>Removed IQ request-response method.</li>
  62. <li>Corrected PEP examples.</li>
  63. <li>Corrected XML schema.</li>
  64. </ul>
  65. </remark>
  66. </revision>
  67. <revision>
  68. <version>0.2</version>
  69. <date>2006-09-17</date>
  70. <initials>psa</initials>
  71. <remark><p>Defined PEP transport.</p></remark>
  72. </revision>
  73. <revision>
  74. <version>0.1</version>
  75. <date>2005-06-16</date>
  76. <initials>psa</initials>
  77. <remark><p>Initial published version.</p></remark>
  78. </revision>
  79. <revision>
  80. <version>0.0.1</version>
  81. <date>2005-06-07</date>
  82. <initials>psa/jjh</initials>
  83. <remark><p>First draft.</p></remark>
  84. </revision>
  85. </header>
  86. <section1 topic='Introduction' anchor='intro'>
  87. <p>Sometimes it is desirable to augment instant messaging (IM) with another real-time communications medium, such as a voice conversation conducted over the traditional public switched telephone network (PSTN) or Voice over Internet Protocol (VoIP) applications. In order to facilitate this functionality, a user needs to advertise the address(es) at which they can be reached. There are several possible ways to do this:</p>
  88. <ul>
  89. <li><p>Publish the address(es) in the user's vCard (see &xep0054; and &xep0292;); this is convenient, but is not very dynamic (e.g., reachability addresses might change when the user moves to a new conference room in an office building).</p></li>
  90. <li><p>Send the address(es) within a &PRESENCE; stanza; this option is described in the <link url='#transport-presence'>Presence Transport</link> section of this document and is consistent with &rfc6121; since reachability is one aspect of a user's availability for communication.</p></li>
  91. <li><p>Send address(es) to the appropriate &xep0060; node; this option is described in the <link url='#transport-pep'>PEP Transport</link> section of this document but might not be available at all service providers.</p></li>
  92. </ul>
  93. <p>This document defines methods for publishing addresses at which a user can be reached temporarily, as opposed to semi-permanent addresses of the kind that are more appropriately communicated in a user's vCard. We illustrate this usage through the scenario of a user sending a reachability address upon entering a physical conference room and then sending an updated notification (without a reachability address) upon leaving the conference room. Similar scenarios might apply when an XMPP implementation is used with technologies such as WebRTC and in deployments of the combined use of SIP and XMPP ("CUSAX"; &rfc7081;).</p>
  94. </section1>
  95. <section1 topic='Requirements' anchor='reqs'>
  96. <p>This document addresses the following requirements:</p>
  97. <ul>
  98. <li>Enable clients to dynamically publish reachability addresses.</li>
  99. <li>Minimize network traffic.</li>
  100. </ul>
  101. </section1>
  102. <section1 topic='Data Format' anchor='format'>
  103. <p>The following is an example of the data format for reachability addresses:</p>
  104. <example caption="Data Format for Reachability Addresses"><![CDATA[
  105. <reach xmlns='urn:xmpp:reach:0'>
  106. <addr uri='tel:+1-303-555-1212'/>
  107. <addr uri=''/>
  108. </reach>
  109. ]]></example>
  110. <p>When publishing reachability addresses, the &lt;reach/&gt; element MUST contain at least one &lt;addr/&gt; element. Each &lt;addr/&gt; element MUST possess a 'uri' attribute, whose value MUST be the Uniform Resource Identifier (&rfc3986;) or Internationalized Resource Identifier (&rfc3987;) of an alternate communications method for reaching the user.</p>
  111. <p>The &lt;addr/&gt; element MAY contain one or more &lt;desc/&gt; children whose XML character data is a natural-language description of the address; this element SHOULD possess an 'xml:lang' attribute whose value is a language tag that conforms to &rfc4646; (although the default language MAY be specified at the stanza level; see &rfc6120;). In order to preserve bandwidth, the &lt;desc/&gt; element SHOULD NOT be included when sending reachability data via presence broadcast, but MAY be included when using directed presence or the personal eventing protocol.</p>
  112. <example caption="Reachability Addresses With Descriptions"><![CDATA[
  113. <reach xmlns='urn:xmpp:reach:0'>
  114. <addr uri='tel:+1-303-555-1212'>
  115. <desc xml:lang='en'>Conference room phone</desc>
  116. </addr>
  117. <addr uri=''>
  118. <desc xml:lang='en'>In-room video system</desc>
  119. </addr>
  120. </reach>
  121. ]]></example>
  122. </section1>
  123. <section1 topic='Data Transport' anchor='transport'>
  124. <p>This document specifies two methods of advertising reachability addresses:</p>
  125. <ul>
  126. <li>Presence</li>
  127. <li>&xep0163; (PEP)</li>
  128. </ul>
  129. <p>This document does not recommend one transport method over the other.</p>
  130. <p>In addition, a contact MAY request a user's reachability addresses in an XMPP &IQ; stanza of type "get" and a user MAY send reachability addresses in an XMPP &MESSAGE; stanza. However, the presence and PEP transport methods are preferred.</p>
  131. <section2 topic='Presence Transport' anchor='transport-presence'>
  132. <p>To broadcast reachability addresses in presence information, a user's client includes the &lt;reach/&gt; element in the &PRESENCE; stanza it sends to its server.</p>
  133. <p>For example, consider someone who walks into a conference room at the office. Via nearfield communication, the user's XMPP client might auto-discover a 'tel:' URI for the room audio system and a 'sip:' URI for the room video system.</p>
  134. <example caption="User&apos;s Client Includes Reachability Addresses in Presence"><![CDATA[
  135. <presence from=''>
  136. <reach xmlns='urn:xmpp:reach:0'>
  137. <addr uri='tel:+1-303-555-1212'/>
  138. <addr uri=''/>
  139. </reach>
  140. </presence>
  141. ]]></example>
  142. <p>The user's server then broadcasts that presence stanza to all entities who are subscribed to the user's presence:</p>
  143. <example caption="User&apos;s Server Broadcasts Presence Information"><![CDATA[
  144. <presence from='' to=''>
  145. <reach xmlns='urn:xmpp:reach:0'>
  146. <addr uri='tel:+1-303-555-1212'/>
  147. <addr uri=''/>
  148. </reach>
  149. </presence>
  150. ]]></example>
  151. <p>(Naturally, a reachability address MAY alternatively be included in directed presence.)</p>
  152. <p>Upon leaving the conference room, the user's client would send updated presence without the reachability extension.</p>
  153. <example caption="User&apos;s Client Sends Updated Presence Without Reachability Addresses"><![CDATA[
  154. <presence from=''/>
  155. ]]></example>
  156. </section2>
  157. <section2 topic='Personal Eventing Protocol' anchor='transport-pep'>
  158. <p>To publish reachability addresses via the personal eventing protocol (<cite>XEP-0163</cite>), the entity publishes data to the "urn:xmpp:reach:0" node.</p>
  159. <example caption='Entity Publishes Reachability Addresses via PEP'><![CDATA[
  160. <iq type='set'
  161. from=''
  162. to='pubsub.shakespeare.example'
  163. id='publish1'>
  164. <pubsub xmlns=''>
  165. <publish node='urn:xmpp:reach:0'>
  166. <item id='a1s2d3f4g5h6bjeh936'>
  167. <reach xmlns='urn:xmpp:reach:0'>
  168. <addr uri='tel:+1-303-555-1212'>
  169. <desc xml:lang='en'>Conference room phone</desc>
  170. </addr>
  171. <addr uri=''>
  172. <desc xml:lang='en'>In-room video system</desc>
  173. </addr>
  174. </reach>
  175. </item>
  176. </publish>
  177. </pubsub>
  178. </iq>
  179. ]]></example>
  180. <example caption='Subscriber Receives PEP Event with Payload'><![CDATA[
  181. <message from='pubsub.shakespeare.lit'
  182. to=''>
  183. <event xmlns=''>
  184. <items node='urn:xmpp:reach:0'>
  185. <item id='a1s2d3f4g5h6bjeh936'>
  186. <reach xmlns='urn:xmpp:reach:0'>
  187. <addr uri='tel:+1-303-555-1212'>
  188. <desc xml:lang='en'>Conference room phone</desc>
  189. </addr>
  190. <addr uri=''>
  191. <desc xml:lang='en'>In-room video system</desc>
  192. </addr>
  193. </reach>
  194. </item>
  195. </items>
  196. </event>
  197. </message>
  198. ]]></example>
  199. <p>As above, when leaving the conference room the user's client would publish an updated payload indicating that it no longer has any temporary reachability addresses.</p>
  200. <example caption='Entity Publishes Payload with Empty Reachability Addresses'><![CDATA[
  201. <iq type='set'
  202. from=''
  203. to='pubsub.shakespeare.example'
  204. id='publish1'>
  205. <pubsub xmlns=''>
  206. <publish node='urn:xmpp:reach:0'>
  207. <item id='a1s2d3f4g5h6bjeh936'>
  208. <reach xmlns='urn:xmpp:reach:0'/>
  209. </item>
  210. </publish>
  211. </pubsub>
  212. </iq>
  213. ]]></example>
  214. </section2>
  215. </section1>
  216. <section1 topic='Determining Support' anchor='support'>
  217. <p>If an entity supports reachability addresses, it MUST advertise that fact by returning a feature of "urn:xmpp:reach:0" &VNOTE; in response to a &xep0030; information request.</p>
  218. <example caption="Service Discovery Information Request"><![CDATA[
  219. <iq from=''
  220. id='disco1'
  221. to=''
  222. type='get'>
  223. <query xmlns=''/>
  224. </iq>
  225. ]]></example>
  226. <example caption="Service Discovery Information Response"><![CDATA[
  227. <iq from=''
  228. id='disco1'
  229. to=''
  230. type='result'>
  231. <query xmlns=''>
  232. <feature var='urn:xmpp:reach:0'/>
  233. </query>
  234. </iq>
  235. ]]></example>
  236. <p>In order for an application to determine whether an entity supports this protocol, where possible it SHOULD use the dynamic, presence-based profile of service discovery defined in &xep0115;. However, if an application has not received entity capabilities information from an entity, it SHOULD use explicit service discovery instead.</p>
  237. </section1>
  238. <section1 topic='Implementation Notes' anchor='impl'>
  239. <p>To preserve network bandwidth, the sender ought not include the &lt;desc/&gt; element unless that information is deemed necessary to enable communication.</p>
  240. <p>A recipient ought to attempt communications with reachability addresses in the order that the &lt;addr/&gt; elements appear within the &lt;reach/&gt; element.</p>
  241. </section1>
  242. <section1 topic='Internationalization Considerations' anchor='i18n'>
  243. <p>If included, the &lt;desc/&gt; element SHOULD possess an 'xml:lang' attribute specifying the language of the human-readable descriptive text for a particular address.</p>
  244. </section1>
  245. <section1 topic='Security Considerations' anchor='security'>
  246. <p>Security considerations for XMPP presence and PEP publication are described in RFC 6120, RFC 6121, XEP-0060, and XEP-0163.</p>
  247. <p>Advertising a telephone number, SIP URI, or other real-time communication address to multiple contacts in an unencrypted way (e.g., via XMPP presence or PEP in cases where not all hops are TLS-protected) introduces the possibility of information leakage and subsequent attacks such as unsolicited phone calls. Clients are advised to appropriately warn users about the dangers of such attacks. Alternatively, if the address is especially sensitive (say, a hashname &rfc6920; for use in a system that enables direct private communication outside of XMPP), then a client could send it in a message that itself is end-to-end encrypted.</p>
  248. </section1>
  249. <section1 topic='IANA Considerations' anchor='iana'>
  250. <p>This document requires no interaction with &IANA;.</p>
  251. </section1>
  252. <section1 topic='XMPP Registrar Considerations' anchor='registrar'>
  253. <section2 topic='Protocol Namespaces' anchor='registrar-ns'>
  254. <p>This specification defines the following XML namespace:</p>
  255. <ul>
  256. <li>urn:xmpp:reach:0</li>
  257. </ul>
  258. <p>Upon advancement of this specification from a status of Experimental to a status of Draft, the &REGISTRAR; shall add the foregoing namespace to the registry located at &NAMESPACES;, as described in Section 4 of &xep0053;.</p>
  259. </section2>
  260. <section2 topic='Namespace Versioning' anchor='registrar-versioning'>
  261. &NSVER;
  262. </section2>
  263. </section1>
  264. <section1 topic='XML Schema' anchor='schema'>
  265. <code><![CDATA[
  266. <?xml version='1.0' encoding='UTF-8'?>
  267. <xs:schema
  268. xmlns:xs=''
  269. targetNamespace='urn:xmpp:reach:0'
  270. xmlns='urn:xmpp:reach:0'
  271. elementFormDefault='qualified'>
  272. <xs:annotation>
  273. <xs:documentation>
  274. The protocol documented by this schema is defined in
  275. XEP-0152:
  276. </xs:documentation>
  277. </xs:annotation>
  278. <xs:element name='reach'>
  279. <xs:complexType>
  280. <xs:sequence>
  281. <xs:element name='addr'
  282. minOccurs='0'
  283. maxOccurs='unbounded'
  284. type='addrElementType'/>
  285. </xs:sequence>
  286. </xs:complexType>
  287. </xs:element>
  288. <xs:complexType name='addrElementType'>
  289. <xs:sequence>
  290. <xs:element name='desc'
  291. minOccurs='0'
  292. maxOccurs='unbounded'
  293. type='xs:string'/>
  294. </xs:sequence>
  295. <xs:attribute name='uri' use='required' type='xs:anyURI'/>
  296. </xs:complexType>
  297. </xs:schema>
  298. ]]></code>
  299. </section1>
  300. </xep>