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 &constraint; 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, where the XMPP &ERROR; element SHOULD also include an application-specific error condition of <resource-limit-exceeded/>, as shown in the following example:
A server implementation SHOULD enable a server administrator to limit the size of stanzas it will accept from a connected client or peer server.
-If a connected client or peer server sends a stanza that violates the upper limit, the receiving server SHOULD NOT process the stanza and instead SHOULD return a ¬allowed; stanza error, which in turn SHOULD include an application-specific error condition of <stanza-too-big/>, as shown in the following example:
+If a connected client or peer server sends a stanza that violates the upper limit, the receiving server SHOULD NOT process the stanza and instead SHOULD return a ¬allowed; stanza error, where the XMPP &ERROR; element SHOULD also include an application-specific error condition of <stanza-too-big/>, as shown in the following example:
A server implementation SHOULD enable a server administrator to limit the number of XML stanzas that a connected client may send to distinct recipients within a given time period.
-If a connected client sends too many stanzas to distinct recipients in a given time period, the receiving server SHOULD NOT process the stanza and instead SHOULD return an &unexpected; stanza error, which in turn SHOULD include an application-specific error condition of <too-many-stanzas/>, as shown in the following example:
+If a connected client sends too many stanzas to distinct recipients in a given time period, the receiving server SHOULD NOT process the stanza and instead SHOULD return an &unexpected; stanza error, where the XMPP &ERROR; element SHOULD also include an application-specific error condition of <too-many-stanzas/>, as shown in the following example:
Special thanks to Chris Mullins for calling attention to the need for a specification on this topic. Thanks also to Thiago Camargo, Bruce Campbell, Dave Cridland, Gustavo Felisberto, Justin Karneges, Pedro Melo, Kevin Smith, Michal Vaner, and Matthew Wild for their suggestions.
+Special thanks to Chris Mullins for calling attention to the need for a specification on this topic. Thanks also to Thiago Camargo, Bruce Campbell, Dave Cridland, Gustavo Felisberto, Justin Karneges, Alexey Melnikov, Pedro Melo, Kevin Smith, Michal Vaner, and Matthew Wild for their suggestions.