Hi, I would appreciate clarification about section "3.2.3. Server
Processing of Inbound Subscription Cancellation":
2. Initiate a roster push to all of the user's interested resources,
containing an updated roster item for the contact with the
'subscription' attribute set to a value of "none" (if the
subscription state was "To" or "To + Pending In") or "from" (if
the subscription state was "Both").
So, imagine the case in which Alice was already subscribed to Bob, and
Bob has asked subscription to Alice. In Alice's roster Bob has
"subscription = To + Pending In". Later Bob cancells Alice's
subscription.
According to step 2 above, Alice's server should set "subscription =
none" for Bob contact. Why? What about the pending incoming
subscription request from Bob to Alice? shouldn't the new state of Bob
in Alice's roster be "none + pending in"?
Thanks a lot.
--
Iñaki Baz Castillo
<[email protected]>
