This document defines a method for specifying contact addresses related to an XMPP service.
NOTICE: This document is currently within Last Call or under consideration by the XMPP Council for advancement to the next stage in the XSF standards process.
Publisher: XMPP Standards Foundation
Last Updated: 2007-01-25
Approving Body: XMPP Council
Dependencies: XMPP Core
Superseded By: None
Short Name: N/A
Wiki Page: <http://wiki.jabber.org/index.php/Contact Addresses for XMPP Services (XEP-0157)>
This XMPP Extension Protocol is copyright 1999 - 2007 by the XMPP Standards Foundation (XSF) and is in full conformance with the XSF's Intellectual Property Rights Policy <http://www.xmpp.org/extensions/ipr-policy.shtml>. This material may be distributed only subject to the terms and conditions set forth in the Creative Commons Attribution License (<http://creativecommons.org/licenses/by/2.5/>).
The preferred venue for discussion of this document is the Standards discussion list: <http://mail.jabber.org/mailman/listinfo/standards>.
The Extensible Messaging and Presence Protocol (XMPP) is defined in the XMPP Core (RFC 3920) and XMPP IM (RFC 3921) specifications contributed by the XMPP Standards Foundation to the Internet Standards Process, which is managed by the Internet Engineering Task Force in accordance with RFC 2026. Any protocol defined in this document has been developed outside the Internet Standards Process and is to be understood as an extension to XMPP rather than as an evolution, development, or modification of XMPP itself.
The following keywords as used in this document are to be interpreted as described in RFC 2119: "MUST", "SHALL", "REQUIRED"; "MUST NOT", "SHALL NOT"; "SHOULD", "RECOMMENDED"; "SHOULD NOT", "NOT RECOMMENDED"; "MAY", "OPTIONAL".
Note: This document describes a protocol or best practice that is intended for incorporation into the specification that will supersede RFC 3920  within the Internet Standards Process, i.e., rfc3920bis . This document is provided only for the purpose of open community discussion of the potential modification and will be obsoleted as soon as the relevant RFC is published.
RFC 2142  specifies conventional electronic mailbox names for common services, roles, and functions related to SMTP, NNTP, and HTTP (such as email@example.com, firstname.lastname@example.org, and email@example.com). However, no such conventional email address or XMPP address (JID) has been specified for XMPP services. This document remedies that oversight.
Consistent with RFC 2142, a domain that offers a Jabber/XMPP service SHOULD provide an Internet mailbox of "XMPP" for inquiries related to that service.
The administrators of an XMPP service may desire to advertise contact information related to that service.  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 RFC 2142. 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 Service Discovery . To make such discovery possible, we specify a Service Discovery Extensions  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 XEP-0128) and data form fields registered for this purpose as defined in the XMPP Registrar Considerations section of this document.
To illustrate this usage, consider the following example of a disco#info request sent to the mythical shakespeare.lit XMPP server:
<iq firstname.lastname@example.org/chamber' to='shakespeare.lit' id='disco1' type='get'> <query xmlns='http://jabber.org/protocol/disco#info'/> </iq>
<iq from='shakespeare.lit' email@example.com/chamber' id='disco1' type='result'> <query xmlns='http://jabber.org/protocol/disco#info'> <identity category='server' type='im'/> <feature var='http://jabber.org/protocol/disco'/> <x xmlns='jabber:x:data' type='result'> <field var='FORM_TYPE' type='hidden'> <value>http://jabber.org/network/serverinfo</value> </field> <field var='abuse-addresses'> <value>mailto:firstname.lastname@example.org</value> <value>xmpp:email@example.com</value> </field> <field var='admin-addresses'> <value>mailto:firstname.lastname@example.org</value> <value>xmpp:email@example.com</value> </field> <field var='feedback-addresses'> <value>http://shakespeare.lit/feedback.php</value> <value>mailto:firstname.lastname@example.org</value> <value>xmpp:email@example.com</value> </field> <field var='sales-addresses'> <value>xmpp:firstname.lastname@example.org</value> </field> <field var='security-addresses'> <value>xmpp:email@example.com</value> </field> <field var='support-addresses'> <value>http://shakespeare.lit/support.php</value> <value>xmpp:firstname.lastname@example.org</value> </field> </x> </query> </iq>
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@example.com"), that similarity is not necessary.
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.
A service provider that supports the functionality specified herein may advertise the service through a Mailto URI (see RFC 2368 ) of <mailto:firstname.lastname@example.org> and through appropriate XMPP URIs (see RFC 4622 ) such as <xmpp:email@example.com> or (per XMPP URI Query Components ) <xmpp:firstname.lastname@example.org?message>.
It is a matter of service policy whether the XMPP addresses provided are dedicated accounts or aliases that redirect communications to the appropriate accounts.
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.
This document requires no interaction with the Internet Assigned Numbers Authority (IANA) .
The XMPP Registrar  shall include the following information in its registries.
Field Standardization for Data Forms  defines a process for standardizing the fields used within Data Forms qualified by a particular namespace, and XEP-0128 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.
<form_type> <name>http://jabber.org/network/serverinfo</name> <doc>XEP-0157</doc> <desc> Forms enabling the communication of contact addresses and other server information. </desc> <field var='abuse-addresses' type='list-multi' label='One or more addresses for communication related to abusive traffic'/> <field var='feedback-addresses' type='list-multi' label='One or more addresses for customer feedback'/> <field var='sales-addresses' type='list-multi' label='One or more addresses for communication related to sales and marketing'/> <field var='security-addresses' type='list-multi' label='One or more addresses for communication related to security concerns'/> <field var='support-addresses' type='list-multi' label='One or more addresses for customer support'/> </form_type>
2. rfc3921bis: proposed revisions to Extensible Messaging and Presence Protocol (XMPP): Core <http://www.ietf.org/internet-drafts/draft-saintandre-rfc3920bis-00.txt>. (work in progress)
4. Many existing Jabber/XMPP server implementations use the bare domain (<domain.tld>) 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 Publish-Subscribe  service). Therefore, it is instead RECOMMENDED to support service discovery of contact addresses as specified herein.
11. The Internet Assigned Numbers Authority (IANA) is the central coordinator for the assignment of unique parameter values for Internet protocols, such as port numbers and URI schemes. For further information, see <http://www.iana.org/>.
12. The XMPP Registrar maintains a list of reserved protocol namespaces as well as registries of parameters used in the context of XMPP extension protocols approved by the XMPP Standards Foundation. For further information, see <http://www.xmpp.org/registrar/>.
Per Council feedback, restored service discovery of XMPP contact addresses from version 0.1 of spec.(psa)
Changed XMPP address from domain.tld/admin to email@example.com.(psa)
Changed XMPP address from domain.tld to domain.tld/admin to prevent overloading.(psa)
Recommended support for RFC2142-style mailbox in addition to XMPP address.(psa)
Removed extended addressing recommendations pending further review.(psa)
Added security considerations and XMPP Registrar considerations.(psa)