On 05/29/2008 9:39 AM, Tim Julien wrote: > Peter Saint-Andre wrote: >> On 05/21/2008 1:18 PM, Tim Julien wrote: >>> So, I'm confused about some of the transport negotiation stuff. >> >> It was sketched out rather quickly and probably needs more work. >> >>> In first scenario (section 3.1) the negotiation occurs after >>> session-accept - which is counter to every Jingle spec that has come out >>> so far: typically both <description> and <transport> are negotiated as a >>> pre-requisite to session-accept and going into ACTIVE. (I'll bet it was >>> done this way because content-replace isn't currently allowed in >>> PENDING, even though the other specs are using it there). >> >> The other specs have been corrected. >> >> In file transfer especially you might want fallback because SOCKS5 >> Bytestreams does not provide reliable NAT traversal, unlike ICE. So you >> might try XEP-0065 first but then it fails, so you fall back to In-Band >> Bytestreams because you know that will always get through (well, almost >> always: you might run into rate limiting from your server). > > The fallback makes alot of sense - I'm glad its being added. > > But do you envision that happening pre or post session-accept (i.e., > during PENDING or ACTIVE). I guess I'll wait for your updated flows. :)
I'm working on that right now and will post an updated version shortly. However, the flows will be consistent with what's in XEP-0166 and the various other Jingle specs. Whatever that ends up meaning... :) Peter -- Peter Saint-Andre https://stpeter.im/
smime.p7s
Description: S/MIME Cryptographic Signature
