Peter Saint-Andre wrote: [...]
How else would the receiving entity know to send an error? If I negotiate TLS and then just sit there and not negotiate SASL, the server shouldn't boot me (well except due to a timeout, but that's not the same thing as skipping over a required feature). The server pretty much has to wait for me to make a wrong move. Maybe you mean if I try to negotiate a stream feature out of sequence? That would be one non-stanza way of me doing something wrong.A stanza is <iq/>, <message/>, or <presence/>. If the server is expecting SASL and I try to negotiate XEP-0198 support or dialback or whatever, I haven't sent a stanza so how can the server return a stanza error to me?
In the case of dialback that is rather easy now that we have dialback errors in xep 220. The additional error conditions might be: * policy-violation: dialback without tls when tls is required by policy * forbidden: dialback with tls but invalid certificate philipp
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.