0.5

git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@315 4b5297f7-1745-476d-ba37-a9c6900126ab

xep-0157.xml

@@ -27,6 +27,12 @@
     <email>[email protected]</email>
     <jid>[email protected]</jid>
   </author>
+  <revision>
+    <version>0.5</version>
+    <date>2007-01-06</date>
+    <initials>psa</initials>
+    <remark><p>Changed XMPP address from domain.tld/admin to [email protected].</p></remark>
+  </revision>
   <revision>
     <version>0.4</version>
     <date>2007-01-05</date>
@@ -68,11 +74,23 @@
   &RFC3920BISNOTE;
   <p>&rfc2142; specifies conventional electronic mailbox names for common services, roles, and functions related to SMTP, NNTP, and HTTP (such as [email protected], [email protected], and [email protected]). However, no such conventional email address or XMPP address (JID) has been specified for XMPP services. This document remedies that oversight.</p>
 </section1>
+<section1 topic='Email Address' anchor='email'>
+  <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>
+</section1>
 <section1 topic='XMPP Address' anchor='xmpp'>
-  <p>Many existing Jabber/XMPP server implementations use the bare domain of the server (e.g., "domain.tld") as an alias for the server administrator(s), such that a &MESSAGE; stanza addressed to that domain name (e.g., "jabber.org") is delivered to the JIDs of the server administrator(s). <note>This does not apply to &IQ; or &PRESENCE; stanzas.</note> Unfortunately, this 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). Therefore, it is RECOMMENDED to instead support a special address of &lt;domain.tld/admin&gt; for this functionality. A domain that provides such functionality MAY also advertise the service through an XMPP URI (see &rfc4622;) of &lt;xmpp:domain.tld/admin&gt; or (per &xep0147;) &lt;xmpp:domain.tld/admin?message&gt;.</p>
+  <p>Many existing Jabber/XMPP server implementations use the bare domain (&DOMAIN;) 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. <note>Currently, this functionality does not apply to &IQ; or &PRESENCE; stanzas.</note> 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 a reserved address of &lt;[email protected]&gt; for this functionality.</p>
+  <p>In particular, it is RECOMMENDED for a service provider to handle XML stanzas with a 'to' address of &lt;[email protected]&gt; as follows:</p>
+  <ol start='1'>
+    <li><p>For &MESSAGE; stanzas, deliver them to the administrators of the XMPP service.</p></li>
+    <li><p>For &PRESENCE; stanzas, ignore them.</p></li>
+    <li><p>For &IQ; stanzas, respond with a &unavailable; error.</p></li>
+  </ol>
+  <p>A service provider MAY aggregate presence from the server administrators so that the presence associated with &lt;[email protected]&gt; reflects the presence of the server administrators (e.g., if at least one of the server administrators is online, then the alias &lt;[email protected]&gt; will also appear to be online); alternatively, the service provider MAY refuse all requests for presence information about the &lt;[email protected]&gt; address.</p>
 </section1>
-<section1 topic='Email Address' anchor='email'>
-  <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. A domain that provides such functionality MAY also advertise the service through a Mailto URI (see &rfc2368;) of &lt;mailto:[email protected]&gt;.</p>
+<section1 topic='Deployment Notes' anchor='deploy'>
+  <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 "[email protected]"), that similarity is not necessary.</p>
+  <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>
+   <p>A service provider that supports the functionality specified herein may advertise the service through an XMPP URI (see &rfc4622;) of &lt;xmpp:[email protected]&gt; or (per &xep0147;) &lt;xmpp:[email protected]?message&gt;, and through a Mailto URI (see &rfc2368;) of &lt;mailto:[email protected]&gt;.</p>
 </section1>
 <section1 topic='Security Considerations' anchor='security'>
   <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>