[Jingle] XEP-0176 - putting many candidates in initiate/accept

Peter Saint-Andre stpeter at stpeter.im
Wed Apr 8 17:04:30 CDT 2009

On 4/7/09 6:34 PM, Justin Karneges wrote:
> There was a recent change to suggest putting all of your candidates in 
> initiate/accept.  

Not *all* your candidates -- the highest priority candidates, i.e., the
ones you know about right away.

> Peter says this was to help simplify the state machine.  
> However, transport-info is still in the XEP and expected to be supported, so 
> I don't see how this resulted in any simplification.  I just wanted to point 
> out that if anyone is planning to write a client that doesn't understand 
> transport-info (/me looks at whoever suggested this change), compatibility 
> will be lost.

Clients need to support transport-info. If they don't, we'll file bug
reports. :)

> There seems to be a way to indicate that you prefer all candidates in the 
> initiate/accept: the urn:ietf:rfc:3264 feature, originally intended for SIP 
> gateways.  I suggest simple clients advertise that feature too, then, and 
> when interacting with a client that supports it you MUST send all candidates 
> in one pass and never use transport-info (instead of the "SHOULD" wording, 
> which may imply that it cannot be relied on).

Yes, the urn:ietf:rfc:3264 feature could be used for that purpose.


Peter Saint-Andre

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 6751 bytes
Desc: S/MIME Cryptographic Signature
Url : http://mail.jabber.org/pipermail/jingle/attachments/20090408/065c300e/attachment-0001.bin 

More information about the Jingle mailing list