[Standards] Jingle initiate and resource determination

[Peter Saint-Andre]

Lauri Kaila wrote:
> Hi List,
> 
> I was trying to sort out Jingle initiation when someone has many
> clients (resources) online. XEP-0168 (RAP) is created for that
> situation, but does it always work so that the initiation goes where
> the receiver wants? 

We had some relevant discussion starting here:

http://mail.jabber.org/pipermail/standards/2007-March/014046.html

Ian proposed something different from RAP and we need to revisit that.

> So I have all these questions about the standards
> plus some implementation questions:
> 
> - Does XEP-0168 (RAP) status need to be updated to draft along with
> XEP-0166/167/180? If yes, shouldn't XEP-0167 and XEP-0180 include the
> app type registration entry in chapter "XMPP Registrar
> Considerations"?

Yes, if we go with RAP.

> - Could and should session receiver's clients co-operate somehow? For
> example, I'd see on PC that my PDA is ringing. Jingle seems to support
> accepting the session from a resource other than original receiver
> (responder attribute). Then the clients must be somehow in sync so
> that only one client sends session-accept and transport candidates.
> And wouldn't the initiator need to re-send all candidates that were
> sent before it received session-accept?

Yes, that sounds messy. Better to terminate at resource1 and start a new 
session from resource2, perhaps.

> - If there are old clients using old namespaces for "jingle-audio" 

I don't think so.

> and
> I wanted to be compatible with those, how does a client know which
> namespace to use in session-initiate?

The real namespaces will be urn:xmpp:jingle etc. (to be issued upon 
advancement to Draft).

> - Typo: Jingle namespaces (containing jabber.org) in XEP-0168 are not
> up to date.

I'll update XEP-0168 if we decide to move forward with it.

Peter

-- 
Peter Saint-Andre
XMPP Standards Foundation
http://www.xmpp.org/xsf/people/stpeter.shtml

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 7358 bytes
Desc: S/MIME Cryptographic Signature
Url : http://mail.jabber.org/pipermail/standards/attachments/20070604/97b94da9/smime-0001.bin