From 756e38b9c2c9b7eff8edde6bfa3da789e2dd7d99 Mon Sep 17 00:00:00 2001 From: "Matthew A. Miller" Date: Mon, 24 Aug 2015 08:36:34 -0600 Subject: [PATCH] Update revision and fix typos --- xep-0280.xml | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/xep-0280.xml b/xep-0280.xml index d2bae197..f1d8b79b 100644 --- a/xep-0280.xml +++ b/xep-0280.xml @@ -40,6 +40,15 @@ linuxwolf@outer-planes.net linuxwolf@outer-planes.net + + 0.10 + 2015-08-24 + mm (editor) + +

Removed distinction between full-JID and bare-JID when receiving messages (Georg Lukas).

+

Define rules around "elible messages", and provide reasonable default guidelines (Kevin Smith).

+ + 0.9 2013-10-17 @@ -341,7 +350,7 @@

Note: if the private &MESSAGE; stanza is addressed to a bare JID, the receiving server still delivers it according to RFC 6121. This might result in a copy being delivered to each resource for the recipient, which effectively negates the behavior of the <private/> element for recipients.

- +

If a client is permitted to enable Carbons during its login session, the server MUST allow the client to enable and disable the protocol multiple times within a session. The server SHOULD NOT treat multiple enable requests (without an intermediate disable request) as an error; it SHOULD simply return an IQ-result (if the protocol is already enabled) or an IQ-error (if the client is not permitted to enable Carbons) for any subsequent requests after the first. Similarly, the server SHOULD NOT treat multiple disable requests (without an intermediate enable request) as an error; it SHOULD return an IQ-result (if the protocols is already disabled) or an IQ-error (if the client's request failed previously) for any subsequent requests after the first.