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 Extensible Messaging and Presence Protocol (XMPP) <https://xmpp.org/>.).

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 XML Signature Syntax and Processing <http://www.w3.org/TR/2002/REC-xmldsig-core-20020212/>. (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 RFC 3923: End-to-End Signing and Object Encryption for the Extensible Messaging and Presence Protocol (XMPP) <http://tools.ietf.org/html/rfc3923>. (XMPP E2E), Encrypted Session Negotiation (XEP-0116) XEP-0116: Encrypted Session Negotiation <https://xmpp.org/extensions/xep-0116.html>. (XMPP PGP), and Encapsulating Digital Signatures in XMPP (XEP-0285) XEP-0285: Encapsulating Digital Signatures in XMPP <https://xmpp.org/extensions/xep-0285.html>.. The limited applicability of encapsulating signature approaches in XMPP is discussed in Design Considerations for Digital Signatures in XMPP (XEP-0274) XEP-0274: Design Considerations for Digital Signatures in XMPP <https://xmpp.org/extensions/xep-0274.html>..

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:

• Default attribute values are added. (Namespace declarations are not modified.)
• Each child element of the stanza is augmented by a id attribute qualified in the urn:xmpp:dsig:0 namespace. 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 element's 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 Canonical XML 1.0 <http://www.w3.org/TR/xml-c14n>., 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 urn:xmpp:dsig:ref:0#xxx-1 would be:

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 RFC 3339: Date and Time on the Internet: Timestamps <http://tools.ietf.org/html/rfc3339>. 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:

• It MUST verify that the timestamp received is within five minutes of the current time, except as described below for offline messages.
• If the foregoing check fails, the timestamp SHOULD be presented to the receiving entity (human or application) marked with descriptive text indicating "old timestamp" or "future timestamp" and the receiving entity MAY return a stanza error to the sender (except as precluded in the protocol).

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) XEP-0160: Best Practices for Handling Offline Messages <https://xmpp.org/extensions/xep-0160.html>., when sending an offline message to the recipient, the server SHOULD include delayed delivery data as specified in Delayed Delivery (XEP-0203) XEP-0203: Delayed Delivery <https://xmpp.org/extensions/xep-0203.html>. 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.

• TBD

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.

TBD.