I found e serious issue with FC 3921bis Managing Presence Subscriptions. Reading through section 3. Managing Presence Subscriptions, we find a requirement, that server MUST stamp every outbound (un)subscribe(d) presence stanza with bare JID of the user in the 'from' attribute of presence stanza.
We find nothing about the 'to' attribute. Now the problem: Historically Jabber allowed full JID based subscriptions. One could request full JID subscription and have full JID in the roster item. This indicates that one is interested in only one resource of the contact, not all of them. Server conforming to RFC 3921bis, when asked for [EMAIL PROTECTED]/resource subscription will accept it from [EMAIL PROTECTED], resulting in uncertainty at the requesting server side: - treat as request acceptance? but it does not match the roster item - ignore it as unrequested? this leaves the user with permanent 'ask' roster item Situation gets worse with probes. Let's assume that the receiving server was upgraded to RFC 3921bis compatible release. It now gets presence probes directed to [EMAIL PROTECTED]/resource. How should it answer when [EMAIL PROTECTED]/otherresource is connected? - send [EMAIL PROTECTED]/otherresource presence? but requestor is not interested in it - send presence unsubscribed not finding the probed item on roster? but it will send it from bare JID, the requesting server will not match it against the roster items to and just ignore it - ignore it? there is no such option in RFC I think we need to resolve this before RFC 3921bis goes "live". Let's disallow full JID based subscriptions or fully document it. Either way is OK with me, but the current, unclear situation is a no go. -- /\_./o__ Tomasz Sterna (/^/(_^^' http://www.xiaoka.com/ ._.(_.)_ im:[EMAIL PROTECTED]
