[jitsi-dev] RFC 6120 Compatibility


#1

hello,

i have problem after upgrade from jabberd 2.2.17 to 2.3.4 (jabberd2.org)
the problem is known as "packet sent before session start, closing stream" [1]

after consultation with maintainer i have question about RFC 6120 Compatibility

he said that one of the differences in new RFC is stricter specification of session establishment protocol. Unfortunately this breaks clients using pre-XMPP Jabber session protocol.

Section 7.3.1 of http://xmpp.org/rfcs/rfc6120.html Resource binding is mandatory now. In old Jabber protocol when announcing the presence was binding the resource from presence message implicitly.

what's the status of xmpp library in jitsi?
thank you

[1] http://www.mail-archive.com/jabberd2@lists.xiaoka.com/msg02360.html

···

--
---------------------------------------
Marek Cervenka


#2

hello,

Ahoj. :wink:

i have problem after upgrade from jabberd 2.2.17 to 2.3.4 (jabberd2.org)
the problem is known as "packet sent before session start, closing
stream" [1]

after consultation with maintainer i have question about RFC 6120
Compatibility

he said that one of the differences in new RFC is stricter specification
of session establishment protocol. Unfortunately this breaks clients
using pre-XMPP Jabber session protocol.

Section 7.3.1 of http://xmpp.org/rfcs/rfc6120.html Resource binding is
mandatory now. In old Jabber protocol when announcing the presence was
binding the resource from presence message implicitly.

Actually, resource binding was effectively mandatory even in RFC 3920, published in 2004. The behavior you describe (implicit binding by sending presence from the resource) is ancient history. :slight_smile:

Peter

···

On 11/3/15 4:12 PM, Marek Červenka wrote:


#3

Dne 4.11.2015 v 0:12 Marek Červenka napsal(a):

hello,

i have problem after upgrade from jabberd 2.2.17 to 2.3.4 (jabberd2.org)
the problem is known as "packet sent before session start, closing stream" [1]

after consultation with maintainer i have question about RFC 6120 Compatibility

he said that one of the differences in new RFC is stricter specification of session establishment protocol. Unfortunately this breaks clients using pre-XMPP Jabber session protocol.

Section 7.3.1 of http://xmpp.org/rfcs/rfc6120.html Resource binding is mandatory now. In old Jabber protocol when announcing the presence was binding the resource from presence message implicitly.

what's the status of xmpp library in jitsi?

i found that jitsi is using smack library for xmpp
https://github.com/jitsi/jitsi/tree/master/lib/installer-exclude/smack.jar

but i cannot find which version is used
hint please?

···

--
---------------------------------------
Marek Cervenka


#4

i found that jitsi is using smack library for xmpp
https://github.com/jitsi/jitsi/tree/master/lib/installer-exclude/smack.ja
r

but i cannot find which version is used
hint please?

3.2.2 + some custom patches

Ingo


#5

Dne 4.11.2015 v 12:30 Ingo Bauersachs napsal(a):

i found that jitsi is using smack library for xmpp
https://github.com/jitsi/jitsi/tree/master/lib/installer-exclude/smack.ja
r

but i cannot find which version is used
hint please?

3.2.2 + some custom patches

thank you. where can i find this info?

it looks like the problem with RFC 6120 Compatibility is solved in last stable version smack 4.1
https://igniterealtime.org/issues/browse/SMACK-396

verified with spark 2.7.3

is it hard to update to the latest smack library?

···

--
---------------------------------------
Marek Cervenka


#6

Dne 4.11.2015 v 12:49 Marek Červenka napsal(a):

Dne 4.11.2015 v 12:30 Ingo Bauersachs napsal(a):

i found that jitsi is using smack library for xmpp
https://github.com/jitsi/jitsi/tree/master/lib/installer-exclude/smack.ja

r

but i cannot find which version is used
hint please?

3.2.2 + some custom patches

thank you. where can i find this info?

it looks like the problem with RFC 6120 Compatibility is solved in last stable version smack 4.1
https://igniterealtime.org/issues/browse/SMACK-396

verified with spark 2.7.3

sorry. spark 2.7.3 run on smack 3.3.1 version

···

--
---------------------------------------
Marek Cervenka


#7

but i cannot find which version is used
hint please?

3.2.2 + some custom patches

thank you. where can i find this info?

https://github.com/jitsi/jitsi/commit/5e72bec68ae102c3203edd6769bee19cf3caf518
->
https://github.com/jitsi/libsrc/tree/master/smack

it looks like the problem with RFC 6120 Compatibility is solved in last
stable version smack 4.1
https://igniterealtime.org/issues/browse/SMACK-396

verified with spark 2.7.3

is it hard to update to the latest smack library?

Yes, but contributions towards that goal would be welcome.

Ingo