-
Notifications
You must be signed in to change notification settings - Fork 122
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@314 4b5297f7-1745-476d-ba37-a9c6900126ab
- Loading branch information
Peter Saint-Andre
committed
Jan 6, 2007
1 parent
87b9844
commit ebc04d4
Showing
1 changed file
with
7 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -27,6 +27,12 @@ | |
<email>[email protected]</email> | ||
<jid>[email protected]</jid> | ||
</author> | ||
<revision> | ||
<version>0.4</version> | ||
<date>2007-01-05</date> | ||
<initials>psa</initials> | ||
<remark><p>Changed XMPP address from domain.tld to domain.tld/admin to prevent overloading.</p></remark> | ||
</revision> | ||
<revision> | ||
<version>0.3</version> | ||
<date>2006-07-31</date> | ||
|
@@ -63,7 +69,7 @@ | |
<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='XMPP Address' anchor='xmpp'> | ||
<p>Many existing Jabber/XMPP server implementations use the bare domain of the server 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> An XMPP server implementation SHOULD support this functionality. A domain that provides such functionality MAY also advertise the service through an XMPP URI (see &rfc4622;) of <xmpp:domain.tld> or (per &xep0147;) <xmpp:domain.tld?message>.</p> | ||
<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 <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>.</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 <mailto:[email protected]>.</p> | ||
|