From 2cddf2836302a775c77ade9bbf29bed21eb5d192 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Wed, 14 Nov 2007 21:06:38 +0000 Subject: [PATCH] XEP-0155 clarification git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1379 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0166.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xep-0166.xml b/xep-0166.xml index e72b0230..bb5e9ff3 100644 --- a/xep-0166.xml +++ b/xep-0166.xml @@ -471,7 +471,7 @@ PENDING o---------------------+ |

  • If the intended responder shares presence with the initiator (see &xmppim;) and has only one available resource, this task SHOULD be completed using &xep0030; or the presence-based profile of service discovery specified in &xep0115;. Naturally, instead of sending service discovery requests to every contact in a user's roster, it is more efficient to use Entity Capabilities, whereby support for Jingle and various Jingle content description formats and content transport methods is determined for a client version in general (rather than on a per-JID basis) and then cached. Refer to XEP-0115 for details.

  • If the intended responder shares presence with the initiator and has more than one available resource but only one of the resources supports Jingle and the desired content description format, the initiator SHOULD initiate the Jingle signalling with that resource.

  • If the intended responder shares presence with the initiator and has more than one available resource but more than one of the resources supports Jingle and the desired content description format, the initiator SHOULD use &xep0168; in order to determine which is the best resource with which to initiate the desired Jingle session.

    • -

  • If the intended responder does not share presence with the initiator, the initiator SHOULD first send a &xep0155; request to the responder in order to initiate the exchange of XMPP stanzas. The request SHOULD include a RAP routing hint as specified in XEP-0168 and the &MESSAGE; stanza containing the request SHOULD be of type "headline" so that (typically) it is not stored offline for later delivery.

    • +

  • If the intended responder does not share presence with the initiator, the initiator SHOULD first send a &xep0155; request to the responder in order to initiate the exchange of XMPP stanzas. The request SHOULD include a RAP routing hint as specified in XEP-0168 and the &MESSAGE; stanza containing the request SHOULD be of type "headline" so that (typically) it is not stored offline for later delivery. The stanza session negotiation SHOULD result in temporary sharing of presence between the parties via the "presence" field as described in XEP-0155.