[Standards-JIG] UPDATED: JEP-0191 (Simple Communications Blocking)
stpeter at jabber.org
Tue Nov 21 21:51:25 UTC 2006
> If blocking is supposed to be a front end to privacy list, then isn't
> the implementation notes taking it away from this goal ?
> Privacy lists never lead to roster changes : which is what the
> implementation notes for 191 talking about.
> If blocking could lead to roster change, then it is no longer a
> frontend to privacy list.
So I think we should add the 191 implementation note to 16.
> Also, blocking a user through privacy list always did update the
> contact about the availablity change.
Right. Is that currently different between 16 and 191?
> The way I was thinking of it simple terms was : blocking is to all
> stanzas what privacy lists was to presece-out.
> If contact gets (un)blocked through privacy list, change in status
> would get pushed (IF he was seeing user as visible earlier : through
> directed presence or roster/privacy list). Cant we not mirror that for
> blocking too ?
> If blocked -> send unavailable if contact was seeing user as
> available, and then block.
> If unblocked -> send available (if allowed) and then 'normal'.
I think 191 already specifies that behavior, no? Consider the following
When the user blocks communications with the contact, the user's server
MUST send unavailable presence information to the contact (but only if
the contact is allowed to receive presence notifications from the user
in accordance with the rules defined in RFC 3921).
When the user unblocks communications with the contact, the user's
server MUST send the user's current presence information to the contact
(but only if the contact is allowed to receive presence notifications
from the user in accordance with the rules defined in RFC 3921).
> Just for completeness sake : there is already a difference between
> privacy list and blocking for presence - you could send directed
> presence even when presence-out was disabled in privacy lists : not so
> in blocking. But this is by design for blocking.
Right. It's OK for blocking to be different from privacy lists in some
ways, because it is "simple" and doesn't provide the same level of
flexibility (but also that reduces the complexity).
Jabber Software Foundation
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 7358 bytes
Desc: S/MIME Cryptographic Signature
More information about the Standards