Sorry about the delayed reply. On 8/3/11 8:39 AM, Tobias Markmann wrote: > On 29.06.2011, at 17:35, XMPP Extensions Editor wrote: > >> This message constitutes notice of a Last Call for comments on >> XEP-0260 (Jingle SOCKS5 Bytestreams Transport Method). >> >> Abstract: This specification defines a Jingle transport method that >> results in sending data via the SOCKS5 Bytestreams (S5B) protocol >> defined in XEP-0065. Essentially this transport method reuses >> XEP-0065 semantics for sending the data and defines native Jingle >> methods for starting and ending an S5B session. >> >> URL: http://www.xmpp.org/extensions/xep-0260.html >> >> This Last Call begins today and shall end at the close of business >> on 2011-07-15. >> >> Please consider the following questions during this Last Call and >> send your feedback to the [email protected] discussion list: >> >> 1. Is this specification needed to fill gaps in the XMPP protocol >> stack or to clarify an existing protocol? 2. Does the specification >> solve the problem stated in the introduction and requirements? 3. >> Do you plan to implement this specification in your code? If not, >> why not? 4. Do you have any security concerns related to this >> specification? 5. Is the specification accurate and clearly >> written? >> >> Your feedback is appreciated! > > Hi, > > I'm currently implementing nearly all the Jingle File-Transfer > related XEPs for Swift(-en). Today I stumbled on the > initiator/responder attributes on the <jingle> tag. XEP-0166 talks > about those attribute at the top of section 7.1 [1]. Nearly all > examples of XEP-0260 having a <jingle> tag include the initiator > attribute, which is only RECOMMENDED (in XEP-0166) for the > session-initiate action. Additionally to that the examples for > session-accept are missing the RECOMMENDED (in XEP-0166) responder > attribute.
Fixed in my working copy. I note that XEP-0166 has these errors too, so I've fixed them there. Peter -- Peter Saint-Andre https://stpeter.im/
