Am Samstag, 19. November 2022, 18:15:17 CET schrieb Daniel Gultsch:
> On Sat, Nov 19, 2022 at 5:55 PM Florian Schmaus <f...@geekplace.eu> 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)

Or, to explain it in more detail: with traditional xmpp you'd have two places 
in the xmpp stream to do something: 1. after auth and 2. after bind.
Because inlining squeezes it all together, these two points in the xmpp stream 
no longer exist. The two <inline/> elements therefore correspond exactly to 
this two traditional points in the xmpp stream.

XEP-0198 can be enabled after bind and can be used to resume a stream without 
bind directly after authentication. It can also be used to do only one of 
these two.
That's the reason why it's mentioned in both inline blocks.
The occurrence in the SASL2 <inline/> element means "resume" and the 
occurrence in the bind2 <inline/> means "enable".

-tmolitor



_______________________________________________
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
_______________________________________________

Reply via email to