Adrian Chan wrote: > We have just made available our latest free web service to use XMPP for > backend message routing. If you are interested, feel free to visit > http://www.apowertouch.com and give us feedback.
Cool. > Per my understanding of XMPP spec, user (or server ??) can select privacy > policy such that only the designated sender(s) can send messages to the > user. All others will be blocked (or messages dropped) by the server. I think you're talking about the jabber:iq:privacy namespace as defined in Section 10 of RFC 3921: http://www.xmpp.org/specs/rfc3921.html#privacy > My > questions are: > > (1) has anyone had experience implementing this policy? As we discovered at the interop event recently, there are very few server-side implementations of that protocol, and we will probably move it from rfc3291bis back to JEP-0016 (where it originally came from), then define a much simpler blocking protocol that we will add to rfc3921bis (I hope to write a JEP for that soon). Basically I think we mis-read the privacy requirement in RFC 2779 -- we could have met the requirement with simple blocking rather than the much more complex privacy lists. Peter -- Peter Saint-Andre Jabber Software Foundation http://www.jabber.org/people/stpeter.shtml
smime.p7s
Description: S/MIME Cryptographic Signature
