Per a vote of the XMPP Council, advanced specification to Draft.
0.32011-04-12psa
Updated reference to reflect publication of RFC 6189; clarified that inclusion of the hash is optional.
0.22010-08-09psa
In harmony with the ZRTP spec, moved communication of <zrtp-hash/> element from Jingle session-info message to jingle-invite, specifically as a child of the <encryption/> element from XEP-0167; increased protocol version from zero to one.
0.12009-02-25psa
Initial published version.
0.0.22009-02-24psa
Defined dedicated namespace for the zrtp-hash element to improve service discovery and handling of session-info message; clarified protocol flow and security considerations.
0.0.12009-02-17psa
First draft, copied from XEP-0167.
Jingle RTP Sessions (XEP-0167)XEP-0167: Jingle RTP Sessions <https://xmpp.org/extensions/xep-0167.html>. recommends the use of the Secure Real-time Transport Protocol (SRTP) for end-to-end encryption of RTP sessions negotiated using Jingle (XEP-0166)XEP-0166: Jingle <https://xmpp.org/extensions/xep-0166.html>.. An alternative approach to end-to-end encryption of RTP traffic is provided by RFC 6189RFC 6189: ZRTP: Media Path Key Agreement for Unicast Secure RTP <http://tools.ietf.org/html/rfc6189>., developed by Phil Zimmermann, the inventor of "Pretty Good Privacy" (PGP). Although negotiation of ZRTP mainly occurs in the media channel rather than the signalling channel, the ZRTP specification defines one SDP attribute called "zrtp-hash" (this communicates the ZRTP version supported as well as a hash of the Hello message). Inclusion of this information is OPTIONAL in both SIP/SDP and Jingle.
This SDP attribute can be translated into Jingle as a <zrtp-hash/> element qualified by the 'urn:xmpp:jingle:apps:rtp:zrtp:1' namespace, as shown below.
The <zrtp-hash/> element is sent as a child of the <encryption/> element defined in Jingle RTP Sessions (XEP-0167)XEP-0167: Jingle RTP Sessions <https://xmpp.org/extensions/xep-0167.html>..
If the Jingle initiator wishes to use ZRTP, it includes the <zrtp-hash/> element in its session invitation (where it hashes over its own Hello message as described in the ZRTP specification).
If the receiving party wishes to proceed with ZRTP negotiation, it also includes the <zrtp-hash/> element in its session-accept message (where it hashes over its own Hello message as described in the ZRTP specification).
Note that a unique zrtp-hash is needed for each media stream, since the hash for each stream is computed from a different ZRTP Hello message (e.g., if a session includes both audio and video then the value of the <zrtp-hash/> element included in the <description/> element for the audio stream will be different from the value for the video stream).
If an entity supports the use of ZRTP in Jingle as described in this document, it MUST advertise that fact in its responses to Service Discovery (XEP-0030)XEP-0030: Service Discovery <https://xmpp.org/extensions/xep-0030.html>. information ("disco#info") requests by returning a feature of "urn:xmpp:jingle:apps:rtp:zrtp:1":
]]>
]]>
In order for an application to determine whether an entity supports this protocol, where possible it SHOULD use the dynamic, presence-based profile of service discovery defined in Entity Capabilities (XEP-0115)XEP-0115: Entity Capabilities <https://xmpp.org/extensions/xep-0115.html>.. However, if an application has not received entity capabilities information from an entity, it SHOULD use explicit service discovery instead.
Security considerations for ZRTP itself are provided in RFC 6189.
XMPP stanzas such as Jingle invite messages and service discovery exchanges are not encrypted or signed. As a result, it is possible for an attacker to intercept these stanzas and modify them, thus convincing one party that the other party does not support ZRTP and therefore denying the parties an opportunity to use ZRTP. However, because the zrtp-hash is mostly advisory, the parties could still use ZRTP even if the signalling channel is compromised.
This document requires no interaction with the Internet Assigned Numbers Authority (IANA)The Internet Assigned Numbers Authority (IANA) is the central coordinator for the assignment of unique parameter values for Internet protocols, such as port numbers and URI schemes. For further information, see <http://www.iana.org/>..
Thanks to Werner Dittmann and Emil Ivov for their implementation feedback.
This specification defines the following XML namespace:
urn:xmpp:jingle:apps:rtp:zrtp:1
The XMPP RegistrarThe 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/>. includes the foregoing namespace to the registry located at <https://xmpp.org/registrar/namespaces.html>, as described in Section 4 of XMPP Registrar Function (XEP-0053)XEP-0053: XMPP Registrar Function <https://xmpp.org/extensions/xep-0053.html>..
If the protocol defined in this specification undergoes a revision that is not fully backwards-compatible with an older version, the XMPP Registrar shall increment the protocol version number found at the end of the XML namespaces defined herein, as described in Section 4 of XEP-0053.
The protocol documented by this schema is defined in
XEP-0262: http://www.xmpp.org/extensions/xep-0262.html
]]>