Greetings. I would advise to substitute the word "kitten" with a descriptive word; or, otherwise, remove it. I think that these words do not contribute to further the engagement with XMPP and related technologies; especially amongst academics and adults from Africa, Asia, Australia, and South America. Kind regards, Schimon On Tue, 12 May 2026 13:28:55 +0200 Florian Schmaus <flo@geekplace.eu> wrote:
[cc to standards@xmpp.org since it is of interest to the xmpp ecosystem]
I've uploaded draft-ietf-kitten-sasl-ht-01. The major changes since the adoption by the Kitten WG are
- the introduction of a response status byte to indicate success or failure responses - the capability to transmit authenticated key/value pairs in the exchanged messages (e.g., for XEP-0474 [1])
SASL-HT is already deployed using an older and incompatible version of the I-D in some parts of the XMPP ecosystem. Therefore, we probably need to adjust the SASL Mechanism Name to avoid interoperability issues. For example, from
HT-SHA-512-ENDP
to
HT2-SHA-512-ENDP
Please forgive my lack of creativity regarding the new name. Suggestions on a more creative naming schema that is in-line with the constraints of SASL Mechanism names are appreciated.
And, of course, feedback in general is welcomed.
- Florian