-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/23/09 8:20 AM, Philipp Hancke wrote: > 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 Correct. My only point in this context is that the server can't send you a stanza error out of the blue -- you need to send a stanza first. If you haven't sent any stanzas yet but you have sent other things over the stream before you are authenticated or cleared for sending stanzas, then the server needs to send you a stream error, not a stanza error. A very simple point. :) Peter - -- Peter Saint-Andre https://stpeter.im/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkrh2YIACgkQNL8k5A2w/vyLyACg5L9bhmnXDePi+3T7TCvFom7v JcEAn3qNcyhkUqtM0gSVZHqR7lOskxm1 =i8RN -----END PGP SIGNATURE-----
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.