Actually, I think that the problem of incomplete ICE implementation in WebRTC is a bigger problem in XMPP<->WebRTC interoperability (http://code.google.com/p/webrtc/issues/detail?id=345).
I have found one discussion about backwards compatibility between AVPF and AVP: http://www.ietf.org/mail-archive/web/rtcweb/current/msg01145.html but it seems that we have to have AVPF support. It's really sad that we have a big lag in Jingle development: even if we get ability to negotiate profile in XEP, implementations will not support this for a long time (judging by, for example, SRTP/SDES support). On 05/30/2012 01:50 PM, Michael Weibel wrote: > Hi, > > I'm currently trying to map SDP (from WebRTC) to Jingle and noticed that the > current chrome canary build does give me a RTP/SAVPF profiles which is > currently not in the XEP 167: > Quote from XEP 167, 4. Application Format: > " > • Future versions of this specification might define how to use other RTP > profiles, such as "RTP/AVPF" and "RTP/SAVPF" as defined in RFC 4585 [9] and > RFC 5124 [10] respectively. > " > > Does anyone know what's the current state about this? Is this planned to be > updated in the spec or not? > > - Michael -- With best regards, Sergey Dobrov, XMPP Developer and JRuDevels.org founder.
