The SCRAM (RFC 5802 ) family of SASL (RFC 4422 ) mechanisms is widely used in XMPP. SCRAM supports channel binding to the underlying security layer to prevent replay attacks, but does not provide a means of negotiating the type of channel binding performed. Normally this means that XMPP defaults to the tls-unique channel binding method defined in RFC 5929 .
This specification provides servers with a way to advertise what forms of channel binding they support, and for clients to choose a channel binding mechanism to use.
As a server operator I want to support different channel bindings depending on what version of TLS was negotiated.
As a client I want to know if the server supports tls-server-end-point channel binding to verify that the server's certificate has not changed between negotiation attempts.
The SCRAM based mechanisms advertise their channel binding support by listing themselves with an added suffix, "-PLUS". This advertises that channel binding is possible, but not the actual channel binding types supported by the server. The "SCRAM-SHA-1-PLUS" mechanism is the same as the "SCRAM-SHA-1" mechanism, the "-PLUS" suffix does not fundamentally change the mechanisms behavior. This concept of a "pseudomechanism", a mechanism that is implemented in terms of another mechanism with minor changes to the name and behavior, can be extended to allow for the advertising of specific channel binding types in addition to whether channel binding is supported or not.
To create such a pseudomechanism the server MUST concatenate the name of any "-PLUS" suffixed mechanism that it supports from the IANA SASL SCRAM Family Mechanisms Subregistry of the IANA SASL Mechanisms Registry  with a colon (":") followed by the name of any channel binding data that it supports with the currently negotiated security layer from the IANA Channel-Binding Types Registry . For example, if a TLS connection has been established and the server wants to advertise that it supports the SCRAM-SHA-1-PLUS and SCRAM-SHA-256-PLUS mechanisms with the tls-unique and tls-server-end-point channel binding types, it would list the following mechanisms:
While the channel binding variants of SCRAM are registered in the IANA SASL Mechanisms Registry , the pseudomechanisms described in this document depend on values in the registry themselves and so are explicitly not meant to be listed. A mechanism with a conflicting name cannot be registered because these pseudomechanisms are deliberately in violation of the naming convention of the SCRAM family of mechanisms as defined in RFC 7677  to prevent such conflicts. Because they are not meant to represent full mechanisms for use outside of XMPP, they do not require registration or the issuance of a GSS-API mechanism OID.
The original "-PLUS" suffixed mechanisms SHOULD continue to be listed and function as they did before (likely by defaulting to tls-unique) for the purpose of backwards compatibility.
The Security Considerations sections from RFC 4422 , RFC 5802 , and RFC 7677  apply to this document.
This document has no actions for IANA.
This document has no actions for the XMPP Registrar .
This document in other formats: XML PDF
This XMPP Extension Protocol is copyright © 1999 – 2020 by the XMPP Standards Foundation (XSF).
Permission is hereby granted, free of charge, to any person obtaining a copy of this specification (the "Specification"), to make use of the Specification without restriction, including without limitation the rights to implement the Specification in a software program, deploy the Specification in a network service, and copy, modify, merge, publish, translate, distribute, sublicense, or sell copies of the Specification, and to permit persons to whom the Specification is furnished to do so, subject to the condition that the foregoing copyright notice and this permission notice shall be included in all copies or substantial portions of the Specification. Unless separate permission is granted, modified works that are redistributed shall not contain misleading information regarding the authors, title, number, or publisher of the Specification, and shall not claim endorsement of the modified works by the authors, any organization or project to which the authors belong, or the XMPP Standards Foundation.
## NOTE WELL: This Specification is provided on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. ##
In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall the XMPP Standards Foundation or any author of this Specification be liable for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising from, out of, or in connection with the Specification or the implementation, deployment, or other use of the Specification (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if the XMPP Standards Foundation or such author has been advised of the possibility of such damages.
This XMPP Extension Protocol has been contributed in full conformance with the XSF's Intellectual Property Rights Policy (a copy of which can be found at <https://xmpp.org/about/xsf/ipr-policy> or obtained by writing to XMPP Standards Foundation, P.O. Box 787, Parker, CO 80134 USA).
The Extensible Messaging and Presence Protocol (XMPP) is defined in the XMPP Core (RFC 6120) and XMPP IM (RFC 6121) specifications contributed by the XMPP Standards Foundation to the Internet Standards Process, which is managed by the Internet Engineering Task Force in accordance with RFC 2026. Any protocol defined in this document has been developed outside the Internet Standards Process and is to be understood as an extension to XMPP rather than as an evolution, development, or modification of XMPP itself.
The primary venue for discussion of XMPP Extension Protocols is the <email@example.com> discussion list.
Discussion on other xmpp.org discussion lists might also be appropriate; see <http://xmpp.org/about/discuss.shtml> for a complete list.
Errata can be sent to <firstname.lastname@example.org>.
The following requirements keywords as used in this document are to be interpreted as described in RFC 2119: "MUST", "SHALL", "REQUIRED"; "MUST NOT", "SHALL NOT"; "SHOULD", "RECOMMENDED"; "SHOULD NOT", "NOT RECOMMENDED"; "MAY", "OPTIONAL".
5. IANA registry of channel binding types <https://www.iana.org/assignments/channel-binding-types>.
7. The XMPP Registrar maintains a list of reserved protocol namespaces as well as registries of parameters used in the context of XMPP extension protocols approved by the XMPP Standards Foundation. For further information, see <https://xmpp.org/registrar/>.
Note: Older versions of this specification might be available at http://xmpp.org/extensions/attic/