XSF Discussion - 2020-12-20

What

what's the point having this in xep-0166? In the session-accept stanza, the <jingle/> element MUST contain one or more <content/> elements, each of which MUST contain one <description/> element and one <transport/> element.

particularly about transport. for example if transport was already negotiated as transport-replace

We had this this discussion previously. I and remember fippo said he had some workaround somewhere sending empty transport in similar cases. But why do we need workarounds at all. Isn't it better to fix xep? I understand it may rise backward compat issues. but it looks like a bug in the xep

The problem with the empty jingle transport workaround it has to refer some transport-specific attributes which may differ depending on a use case. For example referring two different jingle-ibb streams withing one jingle content. So if we just want to accept-content with already negotiated transport, the a jingle app should care about jingle transport implementation, which looks like a bad idea (bad design).