[Standards] Jingle: multiple candidates per transport-info?

[Peter Saint-Andre]

Olivier Crête also wondered why in Jingle ICE-UDP a transport-info
message is restricted to containing only one ICE candidate, rather than
allowing multiple candidates:

http://mail.jabber.org/pipermail/standards/2008-April/018554.html

Olivier pointed out that allowing a transport-info message to contain
multiple candidates would be more consistent with the SDP offer/answer
model, thus making it easier to write clients that support both Jingle
and SIP as well as gateways between Jingle and SIP. However, it is my
understanding that this approach would be inconsistent with the approach
taken by Google Talk as well as any existing Jingle implementations.
Therefore feedback would be appreciated regarding the implications of
such a change.

Thanks!

Peter

-- 
Peter Saint-Andre
https://stpeter.im/


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