On 2014-04-29 18:12, Kim Alvefur wrote:
does not mention XEP 198, Stream Management.
198 does point to 170 however. [...] it makes sense for the server to
offer the SM feature when it will be possible for the other party to
start sending stanzas, not before. But for c2s connection that is
Hello list,
I noticed that XEP-0170 1) talks about the old RFCs and 2) does not
mention XEP 198, Stream Management. 198 doesn't use a stream restart,
so some description about that could be useful. Is it perhaps time for
an update to this XEP (or replacement)?
--
Kim Zash Alvefur
On Apr 29, 2014, at 9:12 AM, Kim Alvefur z...@zash.se wrote:
Hello list,
I noticed that XEP-0170 1) talks about the old RFCs and 2) does not
mention XEP 198, Stream Management. 198 doesn't use a stream restart,
so some description about that could be useful. Is it perhaps time for
an
FYI:
Since there is (was) conflicting recommendations in XEP-0170, Recommended Order
of Stream Feature Negotiation,
(SASL - compression)
and XEP-0138, Stream Compression, (compression - SASL),
but St Peter said 0170 is the correct one, I thought about investigating what servers say:
OpenFire
You can get sasl to provide the means to establish an encrypted channel
after authentication (digest-md5 for example) - which is the reason to
establish compression after sasl.
Since we already have tls, I dont know what sort of value add it would
provide in xmpp case ... but the order of feature
