diff --git a/xep-0205.xml b/xep-0205.xml index d2b67b45..621604e2 100644 --- a/xep-0205.xml +++ b/xep-0205.xml @@ -90,18 +90,18 @@

If an entity attempts to connect but the maximum number of connections has been reached, the receiving server MUST NOT allow the new connection to proceed. There are no XMPP errors associated with this behavior, since it occurs at the binding (TCP or HTTP) level before an XML stream is initiated.

-

In accordance with RFC 3920, a server MUST NOT process XML stanzas from clients that have not provided appropriate authentication credentials, and MUST NOT process XML stanzas from peer servers whose identity it has not either authenticated via SASL (see &rfc4422;) or verified via server dialback.

+

In accordance with RFC 3920, a server MUST NOT process XML stanzas (i.e., &MESSAGE;, &PRESENCE;, or &IQ;) from clients that have not provided appropriate authentication credentials, and MUST NOT process XML stanzas from peer servers whose identity it has not either authenticated via SASL (see &rfc4422;) or verified via server dialback.

A server implementation SHOULD enable a server administrator to limit the number of resources it will allow an account to bind at any one time.

-

If a connected client attempts to bind a resource but has already reached the configured number of allowable resources, the receiving server MUST return a ¬allowed; stanza error, which in turn SHOULD include an application-specific error condition of <resource-limit-exceeded/>, as shown in the following example:

+

If a connected client attempts to bind a resource but has already reached the configured number of allowable resources, the receiving server MUST return a &constraint; stanza error, which in turn SHOULD include an application-specific error condition of <resource-limit-exceeded/>, as shown in the following example:

someresource - - + +