[Standards] Re: Fwd: [kitten] Call for adoption: draft-bouchez-scram-mcf-02 (Ends 2026-06-17)

Is there any interest in the XMPP community for an MCF-based SCRAM? If so, is there any interest in working on this within the Kitten IETF Working Group? Dave. ---------- Forwarded message --------- From: Alexey Melnikov via Datatracker &lt;noreply(a)ietf.org&gt; Date: Wed, 3 Jun 2026 at 16:19 Subject: [kitten] Call for adoption: draft-bouchez-scram-mcf-02 (Ends 2026-06-17) To: &lt;kitten(a)ietf.org&gt;rg>, &lt;kitten-chairs(a)ietf.org&gt;rg>, < draft-bouchez-scram-mcf(a)ietf.org&gt; As some interest was expressed in this document, this message starts a kitten WG Call for Adoption of: draft-bouchez-scram-mcf-02. This Working Group Call for Adoption ends on 2026-06-17 Abstract: This document specifies SCRAM-MCF, an extension to the Salted Challenge Response Authentication Mechanism (SCRAM) family of SASL mechanisms ([RFC5802]) and HTTP Digest extensions ([RFC7616], [RFC7677]). The extension replaces the PBKDF2-specific iteration count attributes i= and s= in the server-first-message with a generic Modular Crypt Format (MCF) descriptor f=. This allows servers to use modern memory- hard key derivation functions such as Argon2, SCrypt, or bcrypt while preserving the full security properties and message flow of SCRAM. The change is fully backward compatible: servers can continue sending i= and s= for legacy clients and only send f= (or both) when the client advertises support. This document is intended to be discussed and potentially adopted by the KITTEN working group. Feedback from the KITTEN WG is welcome on the kitten(a)ietf.org mailing list. Please reply to this message and indicate whether or not you support adoption of this Internet-Draft by the kitten WG. Comments to explain your preference are greatly appreciated. Please reply to all recipients of this message and include this message in your response. Authors, and WG participants in general, are reminded of the Intellectual Property Rights (IPR) disclosure obligations described in BCP 79 [2]. Appropriate IPR disclosures required for full conformance with the provisions of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any. Sanctions available for application to violators of IETF IPR Policy can be found at [3]. Thank you. [1] https://datatracker.ietf.org/doc/bcp78/ [2] https://datatracker.ietf.org/doc/bcp79/ [3] https://datatracker.ietf.org/doc/rfc6701/ The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-bouchez-scram-mcf/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-bouchez-scram-mcf-02.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-bouchez-scram-mcf-02 _______________________________________________ Kitten mailing list -- kitten(a)ietf.org To unsubscribe send an email to kitten-leave(a)ietf.org