On Montag, 17. Dezember 2018 16:50:17 CET Sebastian Riese wrote: > XEP-0261 <https://xmpp.org/extensions/xep-0261.html> uses "bytestream" > for the overall Jingle session and "session" for the IBB session (at > least it does so consistently). This is *extremely* confusing. For > > example section 2.5 reads: > > Whenever a party is finished with a particular session within the > > bytestream, it SHOULD send an IBB <close/> as shown above. This applies > to all sessions, including the last one. > > > To close the bytestream itself (e.g., because the parties have > > finished using all sessions associated with the bytestream), a party > sends a Jingle session-terminate action as defined in XEP-0166. > > This nomenclature is just wrong: The Jingle session manages multiple > In-Band Bytestream sessions. If you close the Jingle session there may > be zero or more bytestream sessions that are closed (and perhaps other > transport sessions – Jingle does not prescribe uniform transports in a > session). > > If you all agree I would make a PR to fix this issue. My proposal is to > use "session" for Jingle sessions and "bytestream" for IBB sessions, if > this is deemed to be too confusing also, I could spell out "Jingle > session" and "IBB session".
I suggest you take the silence as agreement. kind regards, Jonas
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
