RFC 3921:Extensible Messaging and Presence Protoco...
RFC-Ref

Route


Click on the red underlined text to get to the source

... having sent initial presence and before sending unavailable presence broadcast, the user's server MUST route or deliver the full XML of that presence stanza ...
... after having sent initial presence and before sending unavailable presence broadcast, the user's server MUST route or deliver the full XML of that presence stanza ...


... resource identifier). If the contact is served by a different host than the user, the user's server MUST route the presence stanza to the contact's server for delivery ...
... return an IQ result to the sending resource indicating the success of the roster set; (3) MUST route the presence stanza of type "subscribed" to the user, first stamping the 'from' address ...
... server MUST silently ignore the presence stanza of type "subscribed" (i.e., it MUST NOT route it to the user, modify the user's roster, or generate a roster push to the user's available resources). If the contact is in the user's roster with either ...
... unsubscribed'/> 2. As a result, the contact's server MUST route the presence stanza of type "unsubscribed ...
... by the inclusion of the ask='subscribe' attribute in the roster item; and (2) MUST route the presence stanza of type "subscribe" ...
... roster, containing a roster item for the contact with the 'subscription' attribute set to a value of "both"; (2) MUST route the presence stanza of type "subscribed" to the contact, first ...
... server MUST silently ignore the presence stanza of type "subscribed" (i.e., it MUST NOT route it to the contact, modify the contact's roster, or generate a roster push to the contact's available resources). If the user is in the contact's roster ...
... unsubscribed'/> 2. As a result, the user's server MUST route the presence stanza of type "unsubscribed ...
... roster item for the contact with the 'subscription' attribute set to a value of "none"; and (2) MUST route the presence stanza of type "unsubscribe" to the contact, ...
... roster item for the contact with the 'subscription' attribute set to a value of "from"; and (2) MUST route the presence stanza of type "unsubscribe" to the contact, ...
... roster, containing an updated roster item for the user with the 'subscription' attribute set to a value of "none"; (2) MUST route the presence stanza of type "unsubscribed ...
... roster, containing an updated roster item for the user with the 'subscription' attribute set to a value of "to"; (2) MUST route the presence stanza of type "unsubscribed ...


... to lose synchronization regarding subscription states, the user's server MUST without exception route all outbound presence stanzas of type "subscribe ...
... presence information if needed. The user's server SHOULD NOT route a presence stanza of type "subscribed" or "unsubscribed ...
... stanza results in a subscription state change, the user's server MUST route the stanza to the contact and MUST make the appropriate state change ...
... +----------------------------------------------------------------+ | EXISTING STATE | ROUTE? | NEW STATE | +----------------------------------------------------------------+ ...
... +----------------------------------------------------------------+ | EXISTING STATE | ROUTE? | NEW STATE | +----------------------------------------------------------------+ ...


... contained in the 'to' attribute of an outbound stanza does not match a hostname of the server itself, the server MUST attempt to route the stanza to the foreign domain ...



Google
Web
RFC-Ref