&rfc2142; specifies conventional electronic mailbox names for common services, roles, and functions related to SMTP, NNTP, and HTTP (such as postmaster@domain.tld, usenet@domain.tld, and webmaster@domain.tld). However, no such conventional email address or XMPP address (JID) has been specified for XMPP services. This document remedies that oversight.

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). This does not apply to &IQ; or &PRESENCE; stanzas. 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 <domain.tld/admin> for this functionality. A domain that provides such functionality MAY also advertise the service through an XMPP URI (see &rfc4622;) of <xmpp:domain.tld/admin> or (per &xep0147;) <xmpp:domain.tld/admin?message>.

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. A domain that provides such functionality MAY also advertise the service through a Mailto URI (see &rfc2368;) of <mailto:xmpp@domain.tld>.

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 &IANA;.

This document requires no interaction with the ®ISTRAR;.