> 1. Is this specification needed to fill gaps in the XMPP protocol stack or to > clarify an existing protocol?
This is a feature that has received a lot of end-user requests, and we have no other good way to do it, so yes. If anyone is going to ever implement this feature, let's have a thought out approach for them instead of horrible hacks. > 2. Does the specification solve the problem stated in the introduction and > requirements? Yes, it does. > 3. Do you plan to implement this specification in your code? If not, why not? I've implemented this twice already on the client side - in SleekXMPP and stanza.io. However, I'm not aware of any server-side implementation to use those with. > 4. Do you have any security concerns related to this specification? As mentioned in the XEP, it's still very easy to expose the fact that you're online, but any method of accomplishing presence invisibility will have that issue. One thing I notice not mentioned in the XEP is client handling of bookmarks set to auto join. > 5. Is the specification accurate and clearly written? Yes. - Lance
signature.asc
Description: Message signed with OpenPGP using GPGMail
