SASL authentication doesn't support "abort" stanza

I’ve been testing a new client I’m writing against Openfire 3.6.2. According to RFC 3920, the initiator in a SASL exchange can terminate the exchange by sending an stanza. However, when I try to do this with the Openfire server, it stops accepting further messages from my client and logs the following warning to its logs:

Unexpected packet tag (not message,iq,presence)

If I leave out the and just send a second stanza instead with a different mechanism, things seem to work fine, but that doesn’t feel correct to me if I want to abort after receiving a but without sending a or getting back a . I think the Openfire server should be properly handling to clear the current auth exchange in progress and then still allow another after that from the client. Am I missing something?