[Standards] Namespace Priority

[Peter Saint-Andre]

Ian Paterson wrote:

>>> Furthermore, it doesn't help anyway, since servers would still have 
>>> no way of understanding to which resource a Session Negotiation 
>>> request should be delivered (since the sender currently has no 
>>> protocol to tell the server that the request should be sent to a 
>>> client that supports, for example, Jingle).
>>
>> But we can create a RAP application (rapplication?) type for that.
> 
> We can, then you'll be duplicating the functionality in my namespace 
> priority proposal.

I looked at your mini-proposal again. I find the focus on namespaces a 
bit confusing. What exactly are we trying to accomplish here? I think we 
need to clarify the requirements. AFAICS we're not routing based on 
namespace but on relevant application type of interest. In RAP those 
application types are things like "messaging" (chat session), "audio 
chat", and "video chat". I don't think those exactly map to namespaces.

What it seems you want is the ability to initiate a session with someone 
even if you don't have information about the capabilities of their 
various resources (via presence). So let's say Alice wants to start an 
audio chat with Bob. She doesn't have Bob's presence so she doesn't know 
anything about his resources. She wants to initiate a voice chat with 
him but Jingle uses IQs. So she needs to do *something* in order to get 
the session started. What exactly are you proposing to solve that 
problem? It's not clear to me from your previous message:

http://mail.jabber.org/pipermail/standards/2007-February/014000.html

Are you suggesting that the XEP-0115 form will contain a field that 
specifies what kind of stanza session is desired (e.g., chat session, 
signalling session for Jingle audio or video chat)?

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/20070404/ed752531/smime-0001.bin