Hi, I have some new found interest in Instant Stream Resumption and after reading the XEP again I find myself agreeing with a lot of what Dave said 4.5 years ago especially with regard to decoupling the HT-* family of authentication from ISR itself. One might argue that more XEPs means more complexity but to the contrary I think it would actually reduce complexity because one could - theoretically - implement ISR with PLAIN and then not having to worry about HT-* and channel binding. (Don’t get me wrong I like channel binding and I like HT-* but if one is in the market for some quick and easy stream resumption being able to do it with PLAIN would help a lot.)
What Dave outlined in his comment to §4 seems sensible enough to me?! Minor stuff: I’m also agreeing with the feedback on location and compression. However the above (allowing multiple SASL mechanisms) is the urgent one for me right now. cheers Daniel On Mon, Jan 22, 2018 at 1:18 PM Dave Cridland <[email protected]> wrote: > Not ready for Draft, but actually surprisingly close for a newly > adopted XEP. The main thing preventing me from implementing this in > Openfire today is actually the overhead of implementing HT-* properly, > which'd take me a little longer. I think this is very likely to be a > general problem for implementors, and removing the hard dependency > between them (even if it remains a SHOULD, which seems sensible) would > improve deployment. _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
