Skip to content

Commit

Permalink
[skip ci] Update MUC Light specs on legacy Blocking feature (#1166)
Browse files Browse the repository at this point in the history
  • Loading branch information
fenek authored and michalwski committed Jan 24, 2017
1 parent db197d6 commit e3afbe1
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions doc/open-extensions/muc_light.md
Original file line number Diff line number Diff line change
Expand Up @@ -1299,7 +1299,7 @@ next to MUC Light one, or completely replace it, which is RECOMMENDED behaviour.

### 8.1.2 Discovering Occupied Rooms

The room list MUST not include room versions.
The room list MUST NOT include room versions.

**Service Returns Disco Items Result**

Expand Down Expand Up @@ -1491,9 +1491,9 @@ and MUST include status code 321 (i.e. user leaving due to affiliation change).
### 8.1.8 Blocking functionality

Blocking functionality uses small subset of Privacy Lists protocol.
Stanzas MUST be addressed to the server JID.
Stanzas MUST be addressed to the sender's bare JID (`to` attribute may be skipped).
The privacy list name MUST be equal to "urn:xmpp:muclight:0".
Obviously, this method won't work properly in XMPP Server Federation.
Obviously, this method won't work properly in XMPP Server Federation, because privacy stanzas are handled by sender's server and MUC Light Blocking functionality is handled by MUC Light service server.
As opposed to XEP-0016, it is allowed to send "delta" privacy lists.

#### 8.1.8.1 Request blocking list
Expand Down

0 comments on commit e3afbe1

Please sign in to comment.