diff --git a/xep-0262.xml b/xep-0262.xml index c699eeaa..a81714e4 100644 --- a/xep-0262.xml +++ b/xep-0262.xml @@ -10,7 +10,7 @@ This specification defines a Jingle application type for negotiating one or more sessions that use the Real-time Transport Protocol (RTP) to exchange media such as voice or video. The application type includes a straightforward mapping to Session Description Protocol (SDP) for interworking with SIP media endpoints. &LEGALNOTICE; 0262 - Deferred + Experimental Standards Track Standards Council @@ -25,6 +25,12 @@ jingle-zrtp jingle &stpeter; + + 0.2 + 2010-08-09 + psa +

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.1 2009-02-25 @@ -55,46 +61,113 @@ a=zrtp-hash:zrtp-version zrtp-hash-value a=zrtp-hash:1.10 fe30efd02423cb054e50efd0248742ac7a52c8f91bc2df881ae642c371ba46df -

This SDP attribute can be translated into Jingle as a <zrtp-hash/> element, as shown below.

+

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.

zrtp-hash-value +zrtp-hash-value ]]>

An example follows.

fe30efd02423cb054e50efd0248742ac7a52c8f91bc2df881ae642c371ba46df + + fe30efd02423cb054e50efd0248742ac7a52c8f91bc2df881ae642c371ba46df + ]]> -

If either party to a Jingle RTP session wishes to use ZRTP, the party SHOULD send a Jingle session-info message that includes a <zrtp-hash/> element qualified by the 'urn:xmpp:jingle:apps:rtp:zrtp:0' namespace, as shown in the following example.

- The <zrtp-hash/> element is sent as a child of the <encryption/> element defined in &xep0167;.

+

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).

+ - - fe30efd02423cb054e50efd0248742ac7a52c8f91bc2df881ae642c371ba46df + + + + + + + + + + fe30efd02423cb054e50efd0248742ac7a52c8f91bc2df881ae642c371ba46df + + + + + + + + ]]> -

In accordance with XEP-0166, if the receiving party does not understand the payload of the session-info message then it MUST return a &feature; error.

- 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).

+ - - - - + type='set'> + + + + + + + + badfbe66ff87fe135750377509b09b0babd1c3ec25fa4314565e2bf7ccc30299 + + + + + + + + ]]> -

However, if the receiving party also supports and wishes to use ZRTP, it too SHOULD send a session-info message containing a zrtp-hash element.

-

If an entity supports the zrtp-hash session-info message, it MUST advertise that fact in its responses to &xep0030; information ("disco#info") requests by returning a feature of "urn:xmpp:jingle:apps:rtp:zrtp:0":

+

If an entity supports the zrtp-hash session-info message, it MUST advertise that fact in its responses to &xep0030; information ("disco#info") requests by returning a feature of "urn:xmpp:jingle:apps:rtp:zrtp:1":

- + ]]> @@ -125,11 +198,15 @@ a=zrtp-hash:1.10 fe30efd02423cb054e50efd0248742ac7a52c8f91bc2df881ae642c371ba46d

This document requires no interaction with &IANA;.

 + +

Thanks to Werner Dittmann and Emil Ivov for their implementation feedback.

+ +

This specification defines the following XML namespace:

    -
  • urn:xmpp:jingle:apps:rtp:zrtp:0
    • +
  • urn:xmpp:jingle:apps:rtp:zrtp:1

Upon advancement of this specification from a status of Experimental to a status of Draft, the ®ISTRAR; shall add the foregoing namespace to the registry located at &NAMESPACES;, as described in Section 4 of &xep0053;.

 @@ -144,8 +221,8 @@ a=zrtp-hash:1.10 fe30efd02423cb054e50efd0248742ac7a52c8f91bc2df881ae642c371ba46d