initial published version

git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@2789 4b5297f7-1745-476d-ba37-a9c6900126ab
Peter Saint-Andre 2009-02-25 21:36:01 +00:00
parent d934e87fd4
commit b86dcd415f
1 changed files with 165 additions and 0 deletions

xep-0262.xml 100644
View File

@ -0,0 +1,165 @@
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE xep SYSTEM 'xep.dtd' [
<!ENTITY % ents SYSTEM 'xep.ent'>
<?xml-stylesheet type='text/xsl' href='xep.xsl'?>
<title>Use of ZRTP in Jingle RTP Sessions</title>
<abstract>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.</abstract>
<type>Standards Track</type>
<spec>XMPP Core</spec>
<remark><p>Initial published version.</p></remark>
<remark><p>Defined dedicated namespace for the zrtp-hash element to improve service discovery and handling of session-info message; clarified protocol flow and security considerations.</p></remark>
<remark><p>First draft, copied from XEP-0167.</p></remark>
<section1 topic='Protocol' anchor='protocol'>
<p>&xep0167; recommends the use of the Secure Real-time Transport Protocol (SRTP) for end-to-end encryption of RTP sessions negotiated using &xep0166;. An alternative approach to end-to-end encryption of RTP traffic is provided by &zrtp;. 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).</p>
<p>The SDP format is shown below.</p>
a=zrtp-hash:zrtp-version zrtp-hash-value
<p>An example follows.</p>
a=zrtp-hash:1.10 fe30efd02423cb054e50efd0248742ac7a52c8f91bc2df881ae642c371ba46df
<p>This SDP attribute can be translated into Jingle as a &lt;zrtp-hash/&gt; element, as shown below.</p>
<zrtp-hash version='zrtp-version'>zrtp-hash-value</zrtp-hash>
<p>An example follows.</p>
<zrtp-hash version='1.10'>fe30efd02423cb054e50efd0248742ac7a52c8f91bc2df881ae642c371ba46df</zrtp-hash>
<p>If either party to a Jingle RTP session wishes to use ZRTP, the party SHOULD send a Jingle session-info message that includes a &lt;zrtp-hash/&gt; element qualified by the 'urn:xmpp:jingle:apps:rtp:zrtp:0' namespace, as shown in the following example.</p>
<example caption="Initiator sends session-info message with zrtp-hash"><![CDATA[
<iq from='romeo@montague.lit/orchard'
<jingle xmlns='urn:xmpp:jingle:0'
<zrtp-hash xmlns='urn:xmpp:jingle:apps:rtp:zrtp:0'
<p>In accordance with <cite>XEP-0166</cite>, if the receiving party does not understand the payload of the session-info message then it MUST return a &feature; error.</p>
<example caption="Receiver returns feature-not-implemented error"><![CDATA[
<iq from='juliet@capulet.lit/balcony'
<error type='modify'>
<feature-not-implemented xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/>
<unsupported-info xmlns='urn:xmpp:jingle:errors:0'/>
<p>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.</p>
<section1 topic='Determining Support' anchor='disco'>
<p>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":</p>
<example caption='A disco#info query'><![CDATA[
<iq type='get'
<query xmlns=''/>
<example caption='A disco#info response'><![CDATA[
<iq type='result'
<query xmlns=''>
<feature var='urn:xmpp:jingle:apps:rtp:zrtp:0'/>
<p>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 &xep0115;. However, if an application has not received entity capabilities information from an entity, it SHOULD use explicit service discovery instead.</p>
<section1 topic='Security Considerations' anchor='security'>
<p>Security considerations for ZRTP itself are provided in <cite>draft-zimmermann-avt-zrtp</cite>.</p>
<p>XMPP stanzas such as Jingle session-info 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.</p>
<section1 topic='IANA Considerations' anchor='iana'>
<p>This document requires no interaction with &IANA;.</p>
<section1 topic='XMPP Registrar Considerations' anchor='registrar'>
<section2 topic='Protocol Namespaces' anchor='registrar-ns'>
<p>This specification defines the following XML namespace:</p>
<p>Upon advancement of this specification from a status of Experimental to a status of Draft, the &REGISTRAR; shall add the foregoing namespace to the registry located at &NAMESPACES;, as described in Section 4 of &xep0053;.</p>
<section2 topic='Protocol Versioning' anchor='registrar-versioning'>
<section1 topic='XML Schemas' anchor='schema'>
<?xml version='1.0' encoding='UTF-8'?>
<xs:element name='zrtp-hash'>
<xs:extension base='xs:string'>
<xs:attribute name='version' type='xs:string' use='required'/>