This document is one of two proposals for digital signatures in XMPP. It is expected that only one of these proposals be progressed beyond Experimental on the Standards Track.
This document provides a technical specification for Encapsulated Digital Signatures in Extensible Messaging and Presence Protocol (XMPP ).
XMPP Digital Signatures may be used to provide signer authentication, data integrity, non-repudiation, and other security services.
This extension is intended to be highly flexible, supporting a wide range of applications. The extension not only supports signing by the originator, but by other entities which handle XMPP stanzas. Multiple entities may independently sign a stanza.
A signed manifest approach is used to allow selective signing (only select elements may be included in the manifest) and to allow flexibility in handling verification errors.
This extension is intended to support optimistic signing.
This document offers an encapsulated signature approach based upon XML Signature  (XMLDSIG). Implementations of this extension not required to fully implement the XML DSIG specification, they may implement only the minimal subset necessary to support this extension.
It is noted that a number of object-level XMPP digital signature extensions have been specified over the years. These include RFC 3923  (XMPP E2E), Encrypted Session Negotiation (XEP-0116)  (XMPP PGP), and Encapsulating Digital Signatures in XMPP (XEP-0285) . The limited applicability of encapsulating signature approaches in XMPP is discussed in Design Considerations for Digital Signatures in XMPP (XEP-0274) .
The process that a sending agent follows for securing stanzas is very similar regardless of the form of stanza (i.e., <iq/>, <message/>, or <presence/>).
The signer begins with the cleartext version of the <message/> stanza "S":
This is modified prior to signing as follows:
idattribute qualified in the
urn:xmpp:dsig:0namespace. As these attributes are used to identify the element within a manifest, they must be sufficient unique.
The signer builds a stanza description object containing a signer element, the stanza
element, and a timestamp element. The signer element value is the bare JID of the
signing entity. When the signing entity is a service entity, the JID may only contain
service domain. The stanza-desc element is the stanza prepared above with each of its
child elements replaced by an reference element. The reference element references the
child element via a "urn:xmpp:dsig:ref:0" URI with an anchor of the value of child
d:id. The value of the reference element is the digest value produced
by the digest method after the specified transforms are applied.
The signer then builds a SignedInfo element.
And then produces a Signature element:
The signer than computes the SignatureValue element, processing the Signature element as a detached signature, and replaces the empty Signature element with it. Finally, the signer inserts the Signature element into stanza and forwards the stanza as it normally would.
For referenced elements of a stanza, the referenced element is normalized (omitting comments), as detailed in Canonical XML , as a document subset of a document containing a stream element containing the appropriate jabber:client stanza element containing the stanza with the referenced elements. Note that jabber:client stanzas are used when constructing this document even when a server is signing a stanza to be sent to another server.
For the stanza in Example 2, the input document would be:
The canonical form of element referenced by
The URI 'uri:xmpp:dsig:ref:0#xxxx" refers to the child element of the stanza which contains the 'uri:xmpp:dsig:0' 'id' attribute with the value "xxxx".
Timestamps are included to help prevent replay attacks. All timestamps MUST conform to DATETIME  and be presented as UTC with no offset, always including the seconds and fractions of a second to three digits (resulting in a datetime 24 characters in length). Absent a local adjustment to the sending agent's perceived time or the underlying clock time, the sending agent MUST ensure that the timestamps it sends to the receiver increase monotonically (if necessary by incrementing the seconds fraction in the timestamp if the clock returns the same time for multiple requests). The following rules apply to the receiving application:
The foregoing timestamp checks assume that the recipient is online when the message is received. However, if the recipient is offline then the server will probably store the message for delivery when the recipient is next online (offline storage does not apply to <iq/> or <presence/> stanzas, only <message/> stanzas). As described in Best Practices for Handling Offline Messages (XEP-0160) , when sending an offline message to the recipient, the server SHOULD include delayed delivery data as specified in Delayed Delivery (XEP-0203)  so that the recipient knows that this is an offline message and also knows the original time of receipt at the server. In this case, the recipient SHOULD verify that the timestamp received in the encrypted message is within five minutes of the time stamped by the recipient's server in the <delay/> element.
All implementations MUST support the following algorithms. Implementations MAY support other algorithms as well.
To participate in end-to-end signing using the methods defined in this document, a client needs to possess an X.509 certificate. It is expected that many clients will generate their own (self-signed) certificates rather than obtain a certificate issued by a certification authority (CA). In any case the certificate MUST include an XMPP address that is represented using the ASN.1 Object Identifier "id-on-xmppAddr" as specified in Section 5.1.1 of RFC 3920bis.
A URN sub-namespace of signed content for the Extensible Messaging and Presence Protocol (XMPP) is defined as follows.
This document in other formats: XML PDF
This XMPP Extension Protocol is copyright © 1999 – 2018 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 <firstname.lastname@example.org> 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 <email@example.com>.
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".
2. XML Signature Syntax and Processing <http://www.w3.org/TR/2002/REC-xmldsig-core-20020212/>.
Note: Older versions of this specification might be available at http://xmpp.org/extensions/attic/
Merge manifest and schema-desc objects.
Initial published version.