[Standards] PR #793 - XEP-0166: Relax transport element requirement

Sergey Ilinykh rion4ik at gmail.com
Sat Jun 22 15:18:15 UTC 2019


In response to  Council Minutes 2019-06-19

quote from
https://wiki.xmpp.org/web/XEP-Remarks/XEP-0260:_Jingle_SOCKS5_Bytestreams_Transport_Method


Another problem with early (before accept) transport replace is the fact we
have to send the same offer twice. For example we have S5B and IBB. The
lousy s5b implementation can only gather s5b proxy candidates so it may
fail before we sent initial offer (session/content accept). So after proxy
discovery failure we may want to send transport-replace request to IBB
which will contain everything needed for IBB negotiation (at least block
size). Then we have to repeat transport offer with session/content-accept
which will force the remote party to reinitialize IBB transport what looks
like a bad practice, which may be even worse with other transports. To make
things right it has to be allowed to send session/content-accept without
transport element if it was accepted earlier.

To solve this we have https://github.com/xsf/xeps/pull/793 but may be it
require more actions.
Let's discuss.

Best Regards,
Sergey
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/standards/attachments/20190622/d82c93da/attachment.html>


More information about the Standards mailing list