Re: [Standards] proposal to remove Managing Multiple IBB Sessions from XEP-0261

2016-02-24 Thread Lance Stout
I'm +1 for removing Section 2.4. After taking a glance through existing implementations I'm aware of, I'm not seeing that anyone has implemented this feature. To clarify on-list for future reference, here is why Section 2.4 is problematic: The Jingle IBB transport is limited in only being

Re: [Standards] proposal to remove Managing Multiple IBB Sessions from XEP-0261

2016-02-24 Thread Yann Leboulanger
Le 2016-02-24 04:55, Peter Saint-Andre a écrit : Lance Stout and I had a chat today about Jingle, and he noted that the multi-session feature in XEP-0261 is not consistent with the rest of IBB. To make it work properly, we'd need something like components within a session, but we don't have a way

Re: [Standards] proposal to remove Managing Multiple IBB Sessions from XEP-0261

2016-02-24 Thread Sam Whited
On Tue, Feb 23, 2016 at 9:55 PM, Peter Saint-Andre wrote: > If no one is using this feature currently, I suggest that we remove it from > XEP-0261. Agreed; I don't manage an implementation, so their voices should be heard first, but for the sake of reducing complexity I'd like to see it removed.

Re: [Standards] proposal to remove Managing Multiple IBB Sessions from XEP-0261

2016-02-24 Thread Goffi
Le mardi 23 février 2016, 20:55:41 Peter Saint-Andre a écrit : > Lance Stout and I had a chat today about Jingle, and he noted that the > multi-session feature in XEP-0261 is not consistent with the rest of > IBB. To make it work properly, we'd need something like components > within a session, but

[Standards] proposal to remove Managing Multiple IBB Sessions from XEP-0261

2016-02-23 Thread Peter Saint-Andre
Lance Stout and I had a chat today about Jingle, and he noted that the multi-session feature in XEP-0261 is not consistent with the rest of IBB. To make it work properly, we'd need something like components within a session, but we don't have a way to signal that. If no one is using this featur