0.4

xep-0152.xml

@@ -21,8 +21,14 @@
   <supersedes/>
   <supersededby/>
   <shortname>reach</shortname>
-  &hildjj;
   &stpeter;
+  &hildjj;
+  <revision>
+    <version>0.4</version>
+    <date>2013-02-05</date>
+    <initials>psa</initials>
+    <remark><p>Updated to reflect new XMPP RFCs; strengthened security considerations.</p></remark>
+  </revision>
   <revision>
     <version>0.3</version>
     <date>2008-10-06</date>
@@ -46,7 +52,7 @@
     <version>0.1</version>
     <date>2005-06-16</date>
     <initials>psa</initials>
-    <remark><p>Initial version.</p></remark>
+    <remark><p>Initial published version.</p></remark>
   </revision>
   <revision>
     <version>0.0.1</version>
@@ -57,11 +63,11 @@
 </header>
 
 <section1 topic='Introduction' anchor='intro'>
-  <p>Sometimes it is desirable or necessary to switch from instant messaging (IM) to another real-time communications medium, such as a telephone conversation conducted over the traditional public switched telephone network (PSTN) or more recent Voice over Internet Protocol (VoIP) applications. In order to facilitate switching from IM to telephony or some other medium, a user needs to advertise the address(es) at which they can be reached. There are several possible ways to do this:</p>
+  <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 more recent 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>
   <ul>
-    <li><p>Publish the reachability address(es) in the user's vCard (see &xep0054;); 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>
+    <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>
-    <li><p>Send the reachability address(es) within a &PRESENCE; stanza; this option is described in the <link url='#transport-presence'>Presence Broadcast</link> section of this document and is consistent with &rfc6121; since reachability is one aspect of a user's availability for communication.</p></li>
+    <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>
-    <li><p>Send reachability address(es) to the appropriate &xep0163; node; this option is described in the <link url='#transport-pep'>PEP Transport</link> section of this document but may not be available at all service providers.</p></li>
+    <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>
   </ul>
 </section1>
 
@@ -74,15 +80,15 @@
 </section1>
 
 <section1 topic='Data Format' anchor='format'>
-  <p>The following is an example of the basic data format for reachability addresses:</p>
+  <p>The following is an example of the data format for reachability addresses:</p>
-  <example caption="Basic Data Format for Reachability Addresses"><![CDATA[
+  <example caption="Data Format for Reachability Addresses"><![CDATA[
 <reach xmlns='urn:xmpp:reach:0'>
   <addr uri='tel:+1-303-555-1212'/>
   <addr uri='sip:romeo@sipspeare.lit'/>
 </reach>
   ]]></example>
   <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>
-  <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 reachbility data via presence broadcast, but MAY be included when using the personal eventing protocol.</p>
+  <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 reachbility data via presence broadcast, but MAY be included when using directed presence or the personal eventing protocol.</p>
   <example caption="Reachability Addresses With Descriptions"><![CDATA[
 <reach xmlns='urn:xmpp:reach:0'>
   <addr uri='tel:+1-303-555-1212'>
@@ -96,16 +102,16 @@
 </section1>
 
 <section1 topic='Data Transport' anchor='transport'>
-  <p>As described below, this document specifies two methods of advertising reachability addresses:</p>
+  <p>This document specifies two methods of advertising reachability addresses:</p>
   <ul>
-    <li>Presence broadcast</li>
+    <li>Presence</li>
-    <li>Personal eventing via publish-subscribe (PEP)</li>
+    <li>&xep0163; (PEP)</li>
   </ul>
   <p>This document does not recommend one transport method over the other.</p>
-  <p>In addition, a contact MAY request a user's reachability addresses using an &IQ; request-response sequence.</p>
+  <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>
-  <section2 topic='Presence Broadcast' anchor='transport-presence'>
+  <section2 topic='Presence Transport' anchor='transport-presence'>
-    <p>In order 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>
+    <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>
-    <example caption="User&apos;s Client Includes Reachability Addresses in Presence Broadcast"><![CDATA[
+    <example caption="User&apos;s Client Includes Reachability Addresses in Presence"><![CDATA[
 <presence from='romeo@montague.net'>
   <reach xmlns='urn:xmpp:reach:0'>
     <addr uri='tel:+1-303-555-1212'/>
@@ -122,10 +128,11 @@
   </reach>
 </presence>
     ]]></example>
+    <p>Naturally, a reachability address MAY alternatively be included in directed presence.</p>
   </section2>
   <section2 topic='Personal Eventing Protocol' anchor='transport-pep'>
-    <p>In order to publish reachability addresses via the personal eventing protocol (<cite>XEP-0163</cite>), the entity simply publishes data to the "urn:xmpp:reach:0" node.</p>
+    <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>
-    <example caption='Entity publishes reachability addresses'><![CDATA[
+    <example caption='Entity Publishes Reachability Addresses via PEP'><![CDATA[
 <iq type='set'
     from='romeo@montague.net'
     to='pubsub.shakespeare.lit'
@@ -146,7 +153,7 @@
   </pubsub>
 </iq>
     ]]></example>
-    <example caption='Subscriber receives event with payload'><![CDATA[
+    <example caption='Subscriber Receives PEP Event with Payload'><![CDATA[
 <message from='pubsub.shakespeare.lit'
          to='juliet@capulet.com'>
   <event xmlns='http://jabber.org/protocol/pubsub#event'>
@@ -169,7 +176,7 @@
 </section1>
 
 <section1 topic='Determining Support' anchor='support'>
-  <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. The response MUST also include features for the application formats and transport methods supported by the responding entity, as described in the relevant specifications.</p>
+  <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>
   <example caption="Service Discovery Information Request"><![CDATA[
 <iq from='juliet@capulet.com/balcony' 
     id='disco1'
@@ -201,7 +208,8 @@
 </section1>
 
 <section1 topic='Security Considerations' anchor='security'>
-  <p>This document introduces no security considerations above and beyond those described in RFC 6120, RFC 6121, and (for the personal eventing transport) XEP-0163.</p>
+  <p>Security considerations for XMPP presence and PEP publication are described in RFC 6120, RFC 6121, XEP-0060, and XEP-0163.</p>
+  <t>Advertising a telephone number, SIP URI, or other real-time communication address to one contact or to multiple contacts introduces the possibility of information leakage and subsequent attacks (e.g., unsolicited phone calls). Clients are advised to appropriately warn users about the dangers of such attacks.</t>
 </section1>
 
 <section1 topic='IANA Considerations' anchor='iana'>