This strange Prosody dev (not the one that added the error) fails to
understand the problem with this response, it being more specific than
"invalid-mechanism". You're making a mountain out of a molehill, over
an error that will never appear to a "correct" client. Hence I don't
particularly care whether it gets changed in Prosody - patches welcome
:)
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.