Re: [Standards] Confusing Language in XEP-0261 (Jingle In-Band Bytestreams Transport Method)

Hi Larry, I don't think that this mailinglist is the right place to discuss your questions. Although I'm not familiar with your issue, I think you should address them at Google, not the XMPP standards mailinglist. I suggest that you start at https://support.google.com/ and see where that gets you

Re: [Standards] Confusing Language in XEP-0261 (Jingle In-Band Bytestreams Transport Method)

I have a couple questions... While looking into my Google account after a factory reset I was asked to choose what phone I Wanted to restore. But my options were exactly the same. In addition Google didn't recognize my phone number, I had changed my password the week before but the old one was the

Re: [Standards] Confusing Language in XEP-0261 (Jingle In-Band Bytestreams Transport Method)

On 1/12/19 1:01 PM, Jonas Schäfer wrote: > On Montag, 17. Dezember 2018 16:50:17 CET Sebastian Riese wrote: >> XEP-0261 uses "bytestream" >> for the overall Jingle session and "session" for the IBB session (at >> least it does so consistently). This is *e

Re: [Standards] Confusing Language in XEP-0261 (Jingle In-Band Bytestreams Transport Method)

On Montag, 17. Dezember 2018 16:50:17 CET Sebastian Riese wrote: > XEP-0261 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

[Standards] Confusing Language in XEP-0261 (Jingle In-Band Bytestreams Transport Method)

XEP-0261 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