Re: Resource Binding Means End of Stream Negotiation?

殷啟聰 | Kai-Chung Yan <[email protected]> Wed, 23 Aug 2017 14:55:14 +0800

Newsgroups	gmane.network.jabber.devel
Message-ID	<[email protected]>

Thank you guys for the comments. In that case, this part of RFC 6120 is indeed a bit confusing. Might be nice if a clearer description is added to the errata.

Kevin Smith 於 2017/8/22 下午9:36 寫道:
> On 22 Aug 2017, at 14:05, 殷啟聰 | Kai-Chung Yan <[email protected]> wrote:
>> I tried with Prosody 0.9.12 today and found that it has the same behavior as ejabberd. I guess that "Resource Binding indicating stream negotiation" has been a consensus among developers. I personally do not think this is good, because clients who strictly comply with RFC 6120 will have trouble talking to the rest of the world.
> I think in this case 4.3.5 is somewhat misleading, here (maybe it’s an artefact of trying to support clients that don’t resource bind). For the full flow, see 9.1.3 and 9.1.4, where it’s explicit that after resource binding (and without sending stream features), "Now the client is allowed to send XML stanzas over the negotiated stream."
>
> So yes, you shouldn’t expect stream features after a resource bind, at that point you’re done and can start Doing Stuff.
>
> /K
> _______________________________________________
> JDev mailing list
> Info: https://mail.jabber.org/mailman/listinfo/jdev
> Unsubscribe: [email protected]
> _______________________________________________

_______________________________________________
JDev mailing list
Info: https://mail.jabber.org/mailman/listinfo/jdev
Unsubscribe: [email protected]
_______________________________________________

signature.asc (application/pgp-signature, 862 B)