2010/9/10 Peter Saint-Andre <[email protected]>: > Please read the most up-to-date specification: > > http://tools.ietf.org/html/draft-ietf-xmpp-3921bis-12 > > That document is currently in Working Group Last Call at the IETF and I > will public version -13 very soon (perhaps even today), which will be > the version that goes to IETF Last Call. After IETF Last Call the IESG > will vote on approving it, after which it will replace RFC 3921.
Good to know :) >> My question is: why does the server add "ask=subscribe" before roster >> pushing to all the other resources? Why doesn't it avoid "ask" and >> instead set "subscription=None + Pending Out"? > > Because that's the way it's been since 1999. Ok. >> When a resource receives this push it can know that other resource has >> requested subscription by inspecting the subscription 'none + prending >> out', am I wrong? which is the use case of "ask=subscribe" then? > > You're asking that we change a core part of the protocol for the sake of > syntactic hygiene. Oh no, I just ask the reason for it. Perhaps I missed something in the specs :) > That's simply not going to happen at this point, but > feel free to raise the issue on the XMPP WG list, which is the > appropriate venue for discussion of the XMPP RFCs. > > https://www.ietf.org/mailman/listinfo/xmpp Thanks for pointing it. However, as I'm not proposing a change (but just asking about the current specs), is this the appropriate maillist for a question like mine? Thanks a lot. -- Iñaki Baz Castillo <[email protected]>
