jdev - 2023-01-18

How is webrtc used in jingle A/V calls? The XEPs necessary are the one mentionned at https://xmpp.org/extensions/xep-0459.html#av right?

You know this is being discussed in xsf@ right now? :)

Mid of month - Newsletter time! ✉️ Add your news since dec 2022: https://github.com/xsf/xmpp.org/milestone/3 https://yopad.eu/p/xmpp-newsletter-365days

MattJ: yeah but it's talking about specific issues, and I don't know yet those xeps and mecanisms good enough to participate, that's why I'm asking here to not pollute the debate.

Yeah, it's about the XEPs there

So, when can I merge this ? https://github.com/movim/movim/pull/1128

So, it's globally the XEPs mentioned in compliance suit right? All of them are necessary (beside quality/perfs section)?

Because what I get from xsf@ is that there is a lot of obsolete stuff.

The problem is that modern A/V stacks are quite complex, and WebRTC has "won". But XMPP is using Jingle, so there is a lot of mapping to do between the two.

And a lot of XMPP implementations are using WebRTC, and mapping it to specific behaviour in Jingle that afaik isn't documented well or at all

I've not worked directly on any of these implementations, so this is just my assessment of the situation

Alright thanks. And for the documented mapping, where is that mostly happening? XEP-0167 I guess? The trick is that the only reference to webrtc that I see is for datachannel in XEP-0343

Are you planning to use WebRTC in your implementation?

Yes

But I'm mostly evaluating the amount of work for now, and what is mandatory to implement and in which order, that's why I'm trying to understand it better.

Also I'm not sure if I will use only webrtc or not, will depend of the existing ecosystem I guess.