[jdev] Resource Binding Means End of Stream Negotiation?

Peter Saint-Andre stpeter at stpeter.im
Tue Aug 15 17:42:15 UTC 2017

On 8/15/17 10:34 AM, Kai-Chung Yan (殷啟聰) wrote:
> Dear XMPP community,
> I am implementing (yet another) XMPP client library and found
> something confusing in RFC 6120: XMPP Core.
> Section 4.3.5 states that the receiving party sends either an empty
> <features/> element or one containing only optional features in order
> to indicate the completion of a stream negotiation. In fact, I
> believe the receiving party should send a <features/> element
> immediately after negotiating every single feature.
> However my client stuck after finishing Resource Binding and both
> parties are waiting for further XML data. After I changed the
> behavior to assume that Resource Binding indicates end of stream
> negotiation, everything works perfectly I can start exchanging
> stanzas.
> Does that indicate that Resource Binding means the end of a stream
> negotiation? I fail to find such policy in RFC 6120 or its errata.

It sounds to me as if the server software you're connecting to makes an
incorrect assumption. Have you tested this with multiple server


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: OpenPGP digital signature
URL: <http://mail.jabber.org/pipermail/jdev/attachments/20170815/b938ed08/attachment.sig>

More information about the JDev mailing list