[Standards] Let's put "Instant Stream Resumption" back on Council's table
flo at geekplace.eu
Sun Jun 5 17:52:40 UTC 2016
My dear members of the XMPP Council, Hi everyone else :)
I would like to put the "Instant Stream Resumption (ISR)" XEP proposal
back on Council's table. If I'm not mistaken, all Council members said
to vote on list  in the meeting (2016-03-16) after I've re-submitted
a overworked version of ISR, but none did so far.
I'm aware that Dave suggested  to fit this into an eventually
upcoming Multi-Step-Mechanism SASL approach , but this is all in the
very early stages. I did not see much traction after  and I don't
foresee an first draft of such a specification in the near future. But
on the other hand, we need ISR now! I told people at FOSDEM 2015 that
this is one major show stopper left for XMPP on mobile, and a similar
approach to ISR came out of the industry . So there is an urgent
requirement for it.
I also do think that potential SASL changes can and should *not* be
considered a blocker for ISR. There sure will be an upgrade path on
protocol level if Multi-Step-Mechanism SASL becomes a thing.
I hope the XMPP Council also sees the need for ISR. I believe to have
addressed all security concerns, e.g., ISR offers mutual authentication
of the endpoints, and it does not replace SASL and therefore does not
weaken SASL security in any way. So I hereby ask all Council members to
submit the pending votes.
Of course I hope for +1's. Please ask if there is anything left unclear.
5: Besides: I'm not convinced (yet) that ISR should be designed like a
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 603 bytes
Desc: OpenPGP digital signature
More information about the Standards