Stream feature negotiation ordering. Was: Re: [jdev] S2S questions - from attribute and version support

[Ralph Meijer]

On Fri, Dec 30, 2005 at 08:57:38AM -0700, Peter Saint-Andre wrote:
> >>   12. If the TLS negotiation is successful, the initiating entity MUST
> >>       continue with SASL negotiation.
> >>
> >>So I infer from the above that any entity that would specify its
> >>version to be 1.0 would have support for TLS as well.  And if TLS is
> >>done successfully, SASL MUST be done as well.
> 
> That is correct.

I want to note here that JEP-0138, Stream Compression, should be done
after TLS negotiation. The JEP does not mention that it should also go
before SASL but that seems fairly logical.

As we may come up with more and more stream features, it might be good
to think about how to do the ordering of steps correctly, before actual
XML Stanzas can start to be communicated.

And we also seem to have at least one stream feature that works with XML
Stanzas themselves, jabber:iq:auth.

-- 
Groetjes,

ralphm