On Sat, Nov 19, 2022 at 5:55 PM Florian Schmaus <[email protected]> wrote:
> Why not simply > > <stream:features> > <authentication xmlns="urn:xmpp:sasl:2"> > <mechanism>SCRAM-SHA-1-PLUS</mechanism> > <mechanism>PLAIN</mechanism> > <mechanism>SCRAM-SHA-1</mechanism> > <stream:features xmlns='"jabber:client"> > <bind xmlns="urn:xmpp:bind:0"/> > <carbons xmlns="urn:xmpp:carbons:2"/> > <csi xmlns='urn:xmpp:csi:0'/> > <sm xmlns="urn:xmpp:sm:3"/> > <fast xmlns="urn:xmpp:fast:0"/> > </inline> > </authentication> > <mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl"> > <mechanism>SCRAM-SHA-1-PLUS</mechanism> > <mechanism>PLAIN</mechanism> > <mechanism>SCRAM-SHA-1</mechanism> > </mechanisms> > <sasl-channel-binding xmlns="urn:xmpp:sasl-cb:0"> > <channel-binding type="tls-exporter"/> > </sasl-channel-binding> > <register xmlns="urn:xmpp:invite"/> > <register xmlns="urn:xmpp:ibr-token:0"/> > <register xmlns="http://jabber.org/features/iq-register"/> > </stream:features> Because this would imply that carbons and CSI can be inlined into SASL. That's not the same as the other example where they can be inlined into bind2 (Which also answers your question on why SM is there twice) _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
