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-0157.xml 10KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196
  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>Contact Addresses for XMPP Services</title>
  10. <abstract>This document defines a method for specifying contact addresses related to an XMPP service.</abstract>
  11. &LEGALNOTICE;
  12. <number>0157</number>
  13. <status>Active</status>
  14. <type>Informational</type>
  15. <sig>Standards</sig>
  16. <approver>Council</approver>
  17. <dependencies>
  18. <spec>XMPP Core</spec>
  19. </dependencies>
  20. <supersedes/>
  21. <supersededby/>
  22. <shortname>N/A</shortname>
  23. &stpeter;
  24. <author>
  25. <firstname>Jacek</firstname>
  26. <surname>Konieczny</surname>
  27. <email>jajcus@jajcus.net</email>
  28. <jid>jajcus@jabber.bnet.pl</jid>
  29. </author>
  30. <revision>
  31. <version>1.0</version>
  32. <date>2007-01-31</date>
  33. <initials>psa</initials>
  34. <remark><p>Per a vote of the XMPP Council, advanced specification to Active.</p></remark>
  35. </revision>
  36. <revision>
  37. <version>0.6</version>
  38. <date>2007-01-25</date>
  39. <initials>psa</initials>
  40. <remark><p>Per Council feedback, restored service discovery of XMPP contact addresses from version 0.1 of spec.</p></remark>
  41. </revision>
  42. <revision>
  43. <version>0.5</version>
  44. <date>2007-01-06</date>
  45. <initials>psa</initials>
  46. <remark><p>Changed XMPP address from domain.tld/admin to xmpp@domain.tld.</p></remark>
  47. </revision>
  48. <revision>
  49. <version>0.4</version>
  50. <date>2007-01-05</date>
  51. <initials>psa</initials>
  52. <remark><p>Changed XMPP address from domain.tld to domain.tld/admin to prevent overloading.</p></remark>
  53. </revision>
  54. <revision>
  55. <version>0.3</version>
  56. <date>2006-07-31</date>
  57. <initials>psa</initials>
  58. <remark><p>Recommended support for RFC2142-style mailbox in addition to XMPP address.</p></remark>
  59. </revision>
  60. <revision>
  61. <version>0.2</version>
  62. <date>2006-07-18</date>
  63. <initials>psa</initials>
  64. <remark><p>Removed extended addressing recommendations pending further review.</p></remark>
  65. </revision>
  66. <revision>
  67. <version>0.1</version>
  68. <date>2005-09-08</date>
  69. <initials>psa</initials>
  70. <remark><p>Initial version.</p></remark>
  71. </revision>
  72. <revision>
  73. <version>0.0.2</version>
  74. <date>2005-09-06</date>
  75. <initials>psa</initials>
  76. <remark><p>Added security considerations and XMPP Registrar considerations.</p></remark>
  77. </revision>
  78. <revision>
  79. <version>0.0.1</version>
  80. <date>2005-08-27</date>
  81. <initials>psa/jk</initials>
  82. <remark><p>First draft.</p></remark>
  83. </revision>
  84. </header>
  85. <section1 topic='Introduction' anchor='intro'>
  86. <p>&rfc2142; specifies conventional electronic mailbox names for common services, roles, and functions related to SMTP, NNTP, and HTTP (such as hostmaster@domain.tld, usenet@domain.tld, and abuse@domain.tld). However, no such conventional email address or XMPP address has been specified for XMPP services (e.g., in &rfc3920;). This document remedies that oversight, and the email recommendation specified here has been incorporated into &rfc6120;.</p>
  87. </section1>
  88. <section1 topic='Email Address' anchor='email'>
  89. <p>Consistent with <cite>RFC 2142</cite>, a domain that offers a Jabber/XMPP service SHOULD provide an Internet mailbox of "XMPP" for inquiries related to that service.</p>
  90. </section1>
  91. <section1 topic='XMPP Addresses' anchor='xmpp'>
  92. <p>The administrators of an XMPP service may desire to advertise contact information related to that service.
  93. <note>Many existing Jabber/XMPP server implementations use the bare domain &DOMAINBARE; of the server (e.g., "example.org") as an alias for the server administrators, such that a &MESSAGE; stanza addressed to that domain name is delivered to the JIDs of the server administrators. (Currently, this functionality does not apply to &IQ; or &PRESENCE; stanzas.) Unfortunately, using the "domain.tld" address as a way to direct messages to the server administrators may result in overloading of the bare domain address (i.e., it may be desirable to send messages to the server's address without having those messages delivered to the server admins, for example if the server doubles as a &xep0060; service). Therefore, it is instead RECOMMENDED to support service discovery of contact addresses as specified herein.</note>
  94. This contact information may include email addresses, web URLs, and JabberIDs for specific roles and functions such as the service administrators, abuse reports, customer feedback, sales inquiries, technical support, and security concerns. For this purpose, domains SHOULD support the electronic mailboxes required by <cite>RFC 2142</cite>. However, additional contact mechanisms may be desirable, and it would be helpful if those who want to initiate contact could discover the contact information using standard XMPP extensions, specifically &xep0030;. To make such discovery possible, we specify a &xep0128; mechanism that a server SHOULD return in response to service discovery information ("disco#info") requests sent to the bare domain of the server. This information MUST be scoped using a FORM_TYPE of "http://jabber.org/network/serverinfo" (as already specified in <cite>XEP-0128</cite>) and data form fields registered for this purpose as defined in the <link url='#registrar'>XMPP Registrar Considerations</link> section of this document.</p>
  95. <p>To illustrate this usage, consider the following example of a disco#info request sent to the mythical shakespeare.lit XMPP server:</p>
  96. <example caption='Entity queries server for information'><![CDATA[
  97. <iq from='juliet@capulet.com/chamber'
  98. to='shakespeare.lit'
  99. id='disco1'
  100. type='get'>
  101. <query xmlns='http://jabber.org/protocol/disco#info'/>
  102. </iq>
  103. ]]></example>
  104. <example caption='Server communicates information'><![CDATA[
  105. <iq from='shakespeare.lit'
  106. to='juliet@capulet.com/chamber'
  107. id='disco1'
  108. type='result'>
  109. <query xmlns='http://jabber.org/protocol/disco#info'>
  110. <identity category='server' type='im'/>
  111. <feature var='http://jabber.org/protocol/disco'/>
  112. <x xmlns='jabber:x:data' type='result'>
  113. <field var='FORM_TYPE' type='hidden'>
  114. <value>http://jabber.org/network/serverinfo</value>
  115. </field>
  116. <field var='abuse-addresses'>
  117. <value>mailto:abuse@shakespeare.lit</value>
  118. <value>xmpp:abuse@shakespeare.lit</value>
  119. </field>
  120. <field var='admin-addresses'>
  121. <value>mailto:xmpp@shakespeare.lit</value>
  122. <value>xmpp:admins@shakespeare.lit</value>
  123. </field>
  124. <field var='feedback-addresses'>
  125. <value>http://shakespeare.lit/feedback.php</value>
  126. <value>mailto:feedback@shakespeare.lit</value>
  127. <value>xmpp:feedback@shakespeare.lit</value>
  128. </field>
  129. <field var='sales-addresses'>
  130. <value>xmpp:bard@shakespeare.lit</value>
  131. </field>
  132. <field var='security-addresses'>
  133. <value>xmpp:security@shakespeare.lit</value>
  134. </field>
  135. <field var='support-addresses'>
  136. <value>http://shakespeare.lit/support.php</value>
  137. <value>xmpp:support@shakespeare.lit</value>
  138. </field>
  139. </x>
  140. </query>
  141. </iq>
  142. ]]></example>
  143. </section1>
  144. <section1 topic='Deployment Notes' anchor='deploy'>
  145. <p>The "domain.tld" at which the XMPP service is hosted need not be the same as the "domain.tld" at which the email service is hosted. For example, it is common for a service provider to host its XMPP service at a hostname such as "jabber.example.org" whereas email related to the service provider is sent to a hostname of "example.org". Thus while the XMPP address and email address may be the same for some service providers (e.g., both "xmpp@example.com"), that similarity is not necessary.</p>
  146. <p>Although some service providers that use the same address for both XMPP and email messaging may integrate delivery of messages sent by those mechanisms (e.g., XMPP messages sent while a user is offline are redirected to email delivery), XMPP and email remain separate messaging systems.</p>
  147. <p>A service provider that supports the functionality specified herein may advertise the service through a Mailto URI (see &rfc2368;) of &lt;mailto:xmpp@domain.tld&gt; and through appropriate XMPP URIs (see &rfc5122;) such as &lt;xmpp:admins@domain.tld&gt; or (per &xep0147;) &lt;xmpp:admins@domain.tld?message&gt;.</p>
  148. <p>It is a matter of service policy whether the XMPP addresses provided are dedicated accounts or aliases that redirect communications to the appropriate accounts.</p>
  149. </section1>
  150. <section1 topic='Security Considerations' anchor='security'>
  151. <p>Providing or advertising contact addresses may open those addresses to unwanted communication. Server administrators should balance the need for openness with the desire for control over communication with customers and peers.</p>
  152. </section1>
  153. <section1 topic='IANA Considerations' anchor='iana'>
  154. <p>This document requires no interaction with &IANA;.</p>
  155. </section1>
  156. <section1 topic='XMPP Registrar Considerations' anchor='registrar'>
  157. <p>The &REGISTRAR; includes the following information in its registries.</p>
  158. <section2 topic='Field Standardization' anchor='registrar-formtype'>
  159. <p>&xep0068; defines a process for standardizing the fields used within Data Forms qualified by a particular namespace, and <cite>XEP-0128</cite> describes how to use field standardization in the context of service discovery. This section registers fields for server information scoped by the "http://jabber.org/network/serverinfo" FORM_TYPE.</p>
  160. <code caption='Registry Submission'><![CDATA[
  161. <form_type>
  162. <name>http://jabber.org/network/serverinfo</name>
  163. <doc>XEP-0157</doc>
  164. <desc>
  165. Forms enabling the communication of contact addresses
  166. and other server information.
  167. </desc>
  168. <field
  169. var='abuse-addresses'
  170. type='list-multi'
  171. label='One or more addresses for communication related to abusive traffic'/>
  172. <field
  173. var='admin-addresses'
  174. type='list-multi'
  175. label='One or more addresses for communication with the service administrators'/>
  176. <field
  177. var='feedback-addresses'
  178. type='list-multi'
  179. label='One or more addresses for customer feedback'/>
  180. <field
  181. var='sales-addresses'
  182. type='list-multi'
  183. label='One or more addresses for communication related to sales and marketing'/>
  184. <field
  185. var='security-addresses'
  186. type='list-multi'
  187. label='One or more addresses for communication related to security concerns'/>
  188. <field
  189. var='support-addresses'
  190. type='list-multi'
  191. label='One or more addresses for customer support'/>
  192. </form_type>
  193. ]]></code>
  194. </section2>
  195. </section1>
  196. </xep>