23
edits
Difference between revisions of "XEP-Remarks/XEP-0260: Jingle SOCKS5 Bytestreams Transport Method"
Jump to navigation
Jump to search
XEP-Remarks/XEP-0260: Jingle SOCKS5 Bytestreams Transport Method (view source)
Revision as of 20:17, 9 June 2019
, 20:17, 9 June 2019no edit summary
| Line 45: | Line 45: | ||
# Never use the same local port for 2+ candidates | # Never use the same local port for 2+ candidates | ||
# If you still want to configure your router manually then do it, but use different local ports for all other candidates. | # If you still want to configure your router manually then do it, but use different local ports for all other candidates. | ||
----- | |||
'''Fallback inconsistency''' | |||
XEP-0166 allows to send multiple contents with the same creator and name. Lets suppose we do this to provide the same file (xep-0234) with different <security> elements. Now one of sides sends such a request with duplicated creator/name and the other side wants to change the transport before content-accept. What's going to be replaced in this case if we provide just name and creator in the request? So while it's not said explicitly you should do transport-replace either after session/content-accept or including all the other content elements (description/security/etc) | |||