mirror of https://github.com/moparisthebest/xeps
0.27
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@2749 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre
parent
dadf4a5741
commit
f6f3a1c967
292
xep-0167.xml
292
xep-0167.xml
|
|
@ -28,6 +28,12 @@
|
|||
&seanegan;
|
||||
&robmcqueen;
|
||||
&diana;
|
||||
<revision>
|
||||
<version>0.27</version>
|
||||
<date>2009-02-17</date>
|
||||
<initials>psa</initials>
|
||||
<remark><p>Added ssrc attribute to description element; clarified handling with streaming transports; in accordance with list consensus, moved zrtp-hash to a separate specification; updated examples to reflect changes to XEP-0176.</p></remark>
|
||||
</revision>
|
||||
<revision>
|
||||
<version>0.26</version>
|
||||
<date>2009-02-16</date>
|
||||
|
|
@ -240,12 +246,13 @@
|
|||
<li><p>The application format negotiation process is defined in the <link url='#negotiation'>Negotiating a Jingle RTP Session</link> section of this document.</p></li>
|
||||
<li><p>The semantics of the &DESCRIPTION; element are defined in the <link url='#format'>Application Format</link> section of this document.</p></li>
|
||||
<li><p>A mapping of Jingle semantics to the Session Description Protocol is provided in the <link url='#sdp'>Mapping to Session Description Protocol</link> section of this document.</p></li>
|
||||
<li><p>A Jingle RTP session SHOULD use a datagram transport method such as &xep0177; or the "ice-udp" method specified in &xep0176;, but MAY use a streaming transport such as "ice-tcp" if a low-bandwidth codec is employed and the media negotiated is not unduly heavy (e.g., it might be possible to use a streaming transport for audio, but not for video).</p></li>
|
||||
<li><p>A Jingle RTP session SHOULD use a datagram transport method (e.g. &xep0177; or the "ice-udp" method specified in &xep0176;), but MAY use a streaming transport if a low-bandwidth codec is employed and the media negotiated is not unduly heavy (e.g., it might be possible to use a streaming transport for audio, but not for video).</p></li>
|
||||
<li><p>If multiple components are to be communicated over the chosen transport, the component numbered "1" shall be associated with RTP and the component numbered "2" shall be associated with the Real Time Control Protocol (RTCP).</p></li>
|
||||
<li>
|
||||
<p>Content is to be sent and received as follows:</p>
|
||||
<ul>
|
||||
<li><p>For datagram transports, outbound content shall be encoded into RTP packets and each packet shall be sent individually over the transport. Each inbound packet received over the transport is an RTP packet.</p></li>
|
||||
<li><p>For streaming transports, outbound content shall be encoded into RTP packets and each packet data shall be sent in succession over the transport. Incoming data received over the transport shall be processed as a stream of RTP packets, where each RTP packet boundary marks the location of the next packet.</p></li>
|
||||
<li><p>For streaming transports, outbound content shall be encoded into RTP packets, framed in accordance with &rfc4571;, and sent in succession over the transport. Incoming data received over the transport shall be processed as a stream of RTP packets, where each RTP packet boundary marks the location of the next packet.</p></li>
|
||||
</ul>
|
||||
</li>
|
||||
</ol>
|
||||
|
|
@ -270,6 +277,7 @@
|
|||
]]></code>
|
||||
<p>The &DESCRIPTION; element is intended to be a child of a Jingle &CONTENT; element as specified in <cite>XEP-0166</cite>.</p>
|
||||
<p>The &DESCRIPTION; element MUST possess a 'media' attribute that specifies the media type, such as "audio" or "video", where the media type SHOULD be as registered at &ianamedia;.</p>
|
||||
<p>The &DESCRIPTION; element MAY possess a 'ssrc' attribute that specifies the 32-bit synchronization source for this media stream, as defined in <cite>RFC 3550</cite>.</p>
|
||||
<p>After inclusion of one or more &PAYLOADTYPE; child elements, the &DESCRIPTION; element MAY also contain a <bandwidth/> element that specifies the allowable or preferred bandwidth for use by this application type. The 'type' attribute of the <bandwidth/> element SHOULD be a value for the SDP "bwtype" parameter as listed in the &ianasdp;. For RTP sessions, often the <bandwidth/> element will specify the "session bandwidth" as described in Section 6.2 of <cite>RFC 3550</cite>, measured in kilobits per second as described in Section 5.2 of <cite>RFC 4566</cite>.</p>
|
||||
<p>The encodings SHOULD be provided in order of preference by placing the most-preferred payload type as the first &PAYLOADTYPE; child of the &DESCRIPTION; element and the least-preferred payload type as the last child.</p>
|
||||
<p>The allowable attributes of the &PAYLOADTYPE; element are as follows:</p>
|
||||
|
|
@ -364,7 +372,32 @@ Initiator Responder
|
|||
<payload-type id='103' name='L16' clockrate='16000' channels='2'/>
|
||||
<payload-type id='98' name='x-ISAC' clockrate='8000'/>
|
||||
</description>
|
||||
<transport xmlns='urn:xmpp:jingle:transports:ice-udp:0'/>
|
||||
<transport xmlns='urn:xmpp:jingle:transports:ice-udp:1'
|
||||
pwd='asd88fgpdd777uzjYhagZg'
|
||||
ufrag='8hhy'>
|
||||
<candidate component='1'
|
||||
foundation='1'
|
||||
generation='0'
|
||||
id='el0747fg11'
|
||||
ip='10.0.1.1'
|
||||
network='1'
|
||||
port='8998'
|
||||
priority='2130706431'
|
||||
protocol='udp'
|
||||
type='host'/>
|
||||
<candidate component='1'
|
||||
foundation='2'
|
||||
generation='0'
|
||||
id='y3s2b30v3r'
|
||||
ip='192.0.2.3'
|
||||
network='1'
|
||||
port='45664'
|
||||
priority='1694498815'
|
||||
protocol='udp'
|
||||
rel-addr='10.0.1.1'
|
||||
rel-port='8998'
|
||||
type='srflx'/>
|
||||
</transport>
|
||||
</content>
|
||||
</jingle>
|
||||
</iq>
|
||||
|
|
@ -377,7 +410,7 @@ Initiator Responder
|
|||
to='romeo@montague.lit/orchard'
|
||||
type='result'/>
|
||||
]]></example>
|
||||
<p>After successful transport negotiation (not shown here), the responder accepts the session by sending a session-accept action to the initiator. The session-accept SHOULD include a subset of the payload types sent by the initiator, i.e., a list of the offered payload types that the responder can send and/or receive. The list that the responder sends SHOULD retain the ID numbers specified by the initiator. The order of the &PAYLOADTYPE; elements indicates the responder's preferences, with the most-preferred type first.</p>
|
||||
<p>Depending on user preferences or client configuration, a user agent controlled by a human user might need to wait for the user to affirm a desire to proceed with the session before continuing. When the user agent has received such affirmation (or if the user agent can automatically proceed for any reason, e.g. because no human intervention is expected or because a human user has configured the user agent to automatically accept sessions with a given entity), it returns a Jingle session-accept message. The session-accept SHOULD include a subset of the payload types sent by the initiator, i.e., a list of the offered payload types that the responder can send and/or receive. The list that the responder sends SHOULD retain the ID numbers specified by the initiator. The order of the &PAYLOADTYPE; elements indicates the responder's preferences, with the most-preferred type first.</p>
|
||||
<p>In the following example, we imagine that the responder supports Speex at clockrate of 8000 but not 16000, G729, and PCMA but not PMCU. Therefore the responder returns only two payload types (since PMCA was not offered).</p>
|
||||
<example caption="Responder definitively accepts the session"><![CDATA[
|
||||
<iq from='juliet@capulet.lit/balcony'
|
||||
|
|
@ -394,18 +427,17 @@ Initiator Responder
|
|||
<payload-type id='97' name='speex' clockrate='8000'/>
|
||||
<payload-type id='18' name='G729'/>
|
||||
</description>
|
||||
<transport xmlns='urn:xmpp:jingle:transports:ice-udp:0'>
|
||||
<transport xmlns='urn:xmpp:jingle:transports:ice-udp:1'>
|
||||
<candidate component='1'
|
||||
foundation='1'
|
||||
generation='0'
|
||||
ip='192.0.2.3'
|
||||
network='1'
|
||||
port='45664'
|
||||
priority='1678246398'
|
||||
id='or2ii2syr1'
|
||||
ip='192.0.2.1'
|
||||
network='0'
|
||||
port='3478'
|
||||
priority='2130706431'
|
||||
protocol='udp'
|
||||
pwd='asd88fgpdd777uzjYhagZg'
|
||||
type='srflx'
|
||||
ufrag='8hhy'/>
|
||||
type='host'/>
|
||||
</transport>
|
||||
</content>
|
||||
</jingle>
|
||||
|
|
@ -587,27 +619,6 @@ delivery-method=inline; configuration=somebase16string;
|
|||
]]></example>
|
||||
</section1>
|
||||
|
||||
<section1 topic='Negotiation of ZRTP' anchor='zrtp'>
|
||||
<p>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>
|
||||
<code>
|
||||
a=zrtp-hash:zrtp-version zrtp-hash-value
|
||||
</code>
|
||||
<p>An example follows.</p>
|
||||
<code>
|
||||
a=zrtp-hash:1.10 fe30efd02423cb054e50efd0248742ac7a52c8f91bc2df881ae642c371ba46df
|
||||
</code>
|
||||
<p>This SDP attribute has been translated into Jingle as a <zrtp-hash/> element, as shown below.</p>
|
||||
<code><![CDATA[
|
||||
<zrtp-hash version='zrtp-version'>zrtp-hash-value</zrtp-hash>
|
||||
]]></code>
|
||||
<p>An example follows.</p>
|
||||
<code><![CDATA[
|
||||
<zrtp-hash version='1.10'>fe30efd02423cb054e50efd0248742ac7a52c8f91bc2df881ae642c371ba46df</zrtp-hash>
|
||||
]]></code>
|
||||
<p>Therefore, if the initiator wishes to use ZRTP, the session-initiate stanza shall include an <encryption/> element, which MUST contain one and only one <zrtp-hash/> element. Note: The <encryption/> element MUST include only 1+ <crypto/> elements (for SRTP) or 1 <zrtp-hash/> element (for ZRTP), but not both.</p>
|
||||
</section1>
|
||||
|
||||
<section1 topic='Informational Messages' anchor='info'>
|
||||
<section2 topic='Format' anchor='info-format'>
|
||||
<p>Informational messages can be sent by either party within the context of Jingle to communicate the status of a Jingle RTP session, device, or principal. The informational message MUST be an IQ-set containing a &JINGLE; element of type "session-info", where the informational message is a payload element qualified by the 'urn:xmpp:jingle:apps:rtp:info:1' namespace; the following payload elements are defined: <note>A <trying/> element (equivalent to the SIP 100 Trying response code) is not necessary, since each session-level action is acknowledged via XMPP IQ semantics.</note></p>
|
||||
|
|
@ -793,7 +804,30 @@ Romeo Juliet
|
|||
<payload-type id='103' name='L16' clockrate='16000' channels='2'/>
|
||||
<payload-type id='98' name='x-ISAC' clockrate='8000'/>
|
||||
</description>
|
||||
<transport xmlns='urn:xmpp:jingle:transports:ice-udp:0'/>
|
||||
<transport xmlns='urn:xmpp:jingle:transports:ice-udp:1'>
|
||||
<candidate component='1'
|
||||
foundation='1'
|
||||
generation='0'
|
||||
id='el0747fg11'
|
||||
ip='10.0.1.1'
|
||||
network='1'
|
||||
port='8998'
|
||||
priority='2130706431'
|
||||
protocol='udp'
|
||||
type='host'/>
|
||||
<candidate component='1'
|
||||
foundation='2'
|
||||
generation='0'
|
||||
id='y3s2b30v3r'
|
||||
ip='192.0.2.3'
|
||||
network='1'
|
||||
port='45664'
|
||||
priority='1694498815'
|
||||
protocol='udp'
|
||||
rel-addr='10.0.1.1'
|
||||
rel-port='8998'
|
||||
type='srflx'/>
|
||||
</transport>
|
||||
</content>
|
||||
</jingle>
|
||||
</iq>
|
||||
|
|
@ -897,7 +931,32 @@ Romeo Juliet
|
|||
<payload-type id='103' name='L16' clockrate='16000' channels='2'/>
|
||||
<payload-type id='98' name='x-ISAC' clockrate='8000'/>
|
||||
</description>
|
||||
<transport xmlns='urn:xmpp:jingle:transports:ice-udp:0'/>
|
||||
<transport xmlns='urn:xmpp:jingle:transports:ice-udp:1'
|
||||
pwd='asd88fgpdd777uzjYhagZg'
|
||||
ufrag='8hhy'>
|
||||
<candidate component='1'
|
||||
foundation='1'
|
||||
generation='0'
|
||||
id='el0747fg11'
|
||||
ip='10.0.1.1'
|
||||
network='1'
|
||||
port='8998'
|
||||
priority='2130706431'
|
||||
protocol='udp'
|
||||
type='host'/>
|
||||
<candidate component='1'
|
||||
foundation='2'
|
||||
generation='0'
|
||||
id='y3s2b30v3r'
|
||||
ip='192.0.2.3'
|
||||
network='1'
|
||||
port='45664'
|
||||
priority='1694498815'
|
||||
protocol='udp'
|
||||
rel-addr='10.0.1.1'
|
||||
rel-port='8998'
|
||||
type='srflx'/>
|
||||
</transport>
|
||||
</content>
|
||||
</jingle>
|
||||
</iq>
|
||||
|
|
@ -943,22 +1002,17 @@ Romeo Juliet
|
|||
<payload-type id='97' name='speex' clockrate='8000'/>
|
||||
<payload-type id='18' name='G729'/>
|
||||
</description>
|
||||
<transport xmlns='urn:xmpp:jingle:transports:ice-udp:0'>
|
||||
<transport xmlns='urn:xmpp:jingle:transports:ice-udp:1'>
|
||||
<candidate component='1'
|
||||
foundation='1'
|
||||
generation='0'
|
||||
ip='192.0.2.3'
|
||||
network='1'
|
||||
port='45664'
|
||||
priority='1694498815'
|
||||
id='or2ii2syr1'
|
||||
ip='192.0.2.1'
|
||||
network='0'
|
||||
port='3478'
|
||||
priority='2130706431'
|
||||
protocol='udp'
|
||||
pwd='asd88fgpdd777uzjYhagZg'
|
||||
rel-addr='10.0.1.1'
|
||||
rel-port='8998'
|
||||
rem-addr='192.0.2.1'
|
||||
rem-port='3478'
|
||||
type='srflx'
|
||||
ufrag='8hhy'/>
|
||||
type='host'/>
|
||||
</transport>
|
||||
</content>
|
||||
</jingle>
|
||||
|
|
@ -1056,7 +1110,32 @@ Romeo Juliet
|
|||
tag='1'/>
|
||||
</encryption>
|
||||
</description>
|
||||
<transport xmlns='urn:xmpp:jingle:transports:ice-udp:0'/>
|
||||
<transport xmlns='urn:xmpp:jingle:transports:ice-udp:1'
|
||||
pwd='asd88fgpdd777uzjYhagZg'
|
||||
ufrag='8hhy'>
|
||||
<candidate component='1'
|
||||
foundation='1'
|
||||
generation='0'
|
||||
id='el0747fg11'
|
||||
ip='10.0.1.1'
|
||||
network='1'
|
||||
port='8998'
|
||||
priority='2130706431'
|
||||
protocol='udp'
|
||||
type='host'/>
|
||||
<candidate component='1'
|
||||
foundation='2'
|
||||
generation='0'
|
||||
id='y3s2b30v3r'
|
||||
ip='192.0.2.3'
|
||||
network='1'
|
||||
port='45664'
|
||||
priority='1694498815'
|
||||
protocol='udp'
|
||||
rel-addr='10.0.1.1'
|
||||
rel-port='8998'
|
||||
type='srflx'/>
|
||||
</transport>
|
||||
</content>
|
||||
</jingle>
|
||||
</iq>
|
||||
|
|
@ -1112,22 +1191,17 @@ Romeo Juliet
|
|||
tag='1'/>
|
||||
</encryption>
|
||||
</description>
|
||||
<transport xmlns='urn:xmpp:jingle:transports:ice-udp:0'>
|
||||
<transport xmlns='urn:xmpp:jingle:transports:ice-udp:1'>
|
||||
<candidate component='1'
|
||||
foundation='1'
|
||||
generation='0'
|
||||
ip='192.0.2.3'
|
||||
network='1'
|
||||
port='45664'
|
||||
priority='1694498815'
|
||||
id='or2ii2syr1'
|
||||
ip='192.0.2.1'
|
||||
network='0'
|
||||
port='3478'
|
||||
priority='2130706431'
|
||||
protocol='udp'
|
||||
pwd='asd88fgpdd777uzjYhagZg'
|
||||
rel-addr='10.0.1.1'
|
||||
rel-port='8998'
|
||||
rem-addr='192.0.2.1'
|
||||
rem-port='3478'
|
||||
type='srflx'
|
||||
ufrag='8hhy'/>
|
||||
type='host'/>
|
||||
</transport>
|
||||
</content>
|
||||
</jingle>
|
||||
|
|
@ -1228,7 +1302,32 @@ Romeo Gateway Juliet
|
|||
<payload-type id='103' name='L16' clockrate='16000' channels='2'/>
|
||||
<payload-type id='98' name='x-ISAC' clockrate='8000'/>
|
||||
</description>
|
||||
<transport xmlns='urn:xmpp:jingle:transports:ice-udp:0'/>
|
||||
<transport xmlns='urn:xmpp:jingle:transports:ice-udp:1'
|
||||
pwd='asd88fgpdd777uzjYhagZg'
|
||||
ufrag='8hhy'>
|
||||
<candidate component='1'
|
||||
foundation='1'
|
||||
generation='0'
|
||||
id='el0747fg11'
|
||||
ip='10.0.1.1'
|
||||
network='1'
|
||||
port='8998'
|
||||
priority='2130706431'
|
||||
protocol='udp'
|
||||
type='host'/>
|
||||
<candidate component='1'
|
||||
foundation='2'
|
||||
generation='0'
|
||||
id='y3s2b30v3r'
|
||||
ip='192.0.2.3'
|
||||
network='1'
|
||||
port='45664'
|
||||
priority='1694498815'
|
||||
protocol='udp'
|
||||
rel-addr='10.0.1.1'
|
||||
rel-port='8998'
|
||||
type='srflx'/>
|
||||
</transport>
|
||||
</content>
|
||||
</jingle>
|
||||
</iq>
|
||||
|
|
@ -1292,13 +1391,7 @@ Romeo Gateway Juliet
|
|||
<description xmlns='urn:xmpp:jingle:apps:rtp:1' media='audio'>
|
||||
<payload-type id='18' name='G729'/>
|
||||
</description>
|
||||
<transport xmlns='urn:xmpp:jingle:transports:raw-udp:1'>
|
||||
<candidate component='1'
|
||||
generation='0'
|
||||
id='a9j3mnbtu1'
|
||||
ip='10.1.1.104'
|
||||
port='13540'/>
|
||||
</transport>
|
||||
<transport xmlns='urn:xmpp:jingle:transports:raw-udp:1'/>
|
||||
</content>
|
||||
</jingle>
|
||||
</iq>
|
||||
|
|
@ -1327,22 +1420,17 @@ Romeo Gateway Juliet
|
|||
<payload-type id='97' name='speex' clockrate='8000'/>
|
||||
<payload-type id='18' name='G729'/>
|
||||
</description>
|
||||
<transport xmlns='urn:xmpp:jingle:transports:ice-udp:0'>
|
||||
<transport xmlns='urn:xmpp:jingle:transports:ice-udp:1'>
|
||||
<candidate component='1'
|
||||
foundation='1'
|
||||
generation='0'
|
||||
ip='192.0.2.3'
|
||||
network='1'
|
||||
port='45664'
|
||||
priority='1694498815'
|
||||
id='or2ii2syr1'
|
||||
ip='192.0.2.1'
|
||||
network='0'
|
||||
port='3478'
|
||||
priority='2130706431'
|
||||
protocol='udp'
|
||||
pwd='asd88fgpdd777uzjYhagZg'
|
||||
rel-addr='10.0.1.1'
|
||||
rel-port='8998'
|
||||
rem-addr='192.0.2.1'
|
||||
rem-port='3478'
|
||||
type='srflx'
|
||||
ufrag='8hhy'/>
|
||||
type='host'/>
|
||||
</transport>
|
||||
</content>
|
||||
</jingle>
|
||||
|
|
@ -1536,22 +1624,17 @@ Romeo Juliet
|
|||
<payload-type id='97' name='speex' clockrate='8000'/>
|
||||
<payload-type id='18' name='G729'/>
|
||||
</description>
|
||||
<transport xmlns='urn:xmpp:jingle:transports:ice-udp:0'>
|
||||
<transport xmlns='urn:xmpp:jingle:transports:ice-udp:1'>
|
||||
<candidate component='1'
|
||||
foundation='1'
|
||||
generation='0'
|
||||
ip='192.0.2.3'
|
||||
network='1'
|
||||
port='45664'
|
||||
priority='1694498815'
|
||||
id='or2ii2syr1'
|
||||
ip='192.0.2.1'
|
||||
network='0'
|
||||
port='3478'
|
||||
priority='2130706431'
|
||||
protocol='udp'
|
||||
pwd='asd88fgpdd777uzjYhagZg'
|
||||
rel-addr='10.0.1.1'
|
||||
rel-port='8998'
|
||||
rem-addr='192.0.2.1'
|
||||
rem-port='3478'
|
||||
type='srflx'
|
||||
ufrag='8hhy'/>
|
||||
type='host'/>
|
||||
</transport>
|
||||
</content>
|
||||
</jingle>
|
||||
|
|
@ -1758,7 +1841,8 @@ Romeo Juliet
|
|||
</section1>
|
||||
|
||||
<section1 topic='Security Considerations' anchor='security'>
|
||||
<p>In order to secure the data stream, implementations SHOULD use encryption methods appropriate to the RTP data transport; the use of SRTP is recommended.</p>
|
||||
<p>In order to secure the data stream, implementations SHOULD use encryption methods appropriate to the RTP data transport. It is RECOMMENDED to use SRTP as defined in the <link url='#srtp'>Negotiation of SRTP</link> section of this document. The SRTP keying material SHOULD (1) be tied to a separate, secure connection such as provided by DTLS (&rfc4347;) where the keys are established as described in &dtlssrtp; and/or (2) protected by sending the Jingle signalling over a secure channel that protects the confidentiality and integrity of the SRTP-related signalling data.</p>
|
||||
<p>While it is also possible to use native RTP methods, such as &zrtp; as described at <<link url='http://xmpp.org/extensions/inbox/jingle-zrtp.html'>http://xmpp.org/extensions/inbox/jingle-zrtp.html</link>>, this specification does not actively encourage or discourage the use of such methods.</p>
|
||||
</section1>
|
||||
|
||||
<section1 topic='IANA Considerations' anchor='iana'>
|
||||
|
|
@ -1837,6 +1921,12 @@ Romeo Juliet
|
|||
minOccurs='0'
|
||||
maxOccurs='1'/>
|
||||
</xs:sequence>
|
||||
<xs:attribute name='media'
|
||||
type='xs:NCName'
|
||||
use='required'/>
|
||||
<xs:attribute name='ssrc'
|
||||
type='xs:string'
|
||||
use='optional'/>
|
||||
</xs:complexType>
|
||||
</xs:element>
|
||||
|
||||
|
|
@ -1862,16 +1952,12 @@ Romeo Juliet
|
|||
</xs:complexType>
|
||||
|
||||
<xs:complexType name='encryptionElementType'>
|
||||
<xs:choice>
|
||||
<xs:sequence>
|
||||
<xs:element name='crypto'
|
||||
type='cryptoElementType'
|
||||
minOccurs='0'
|
||||
maxOccurs='unbounded'/>
|
||||
<xs:element name='zrtp-hash'
|
||||
type='zrtpElementType'
|
||||
minOccurs='0'
|
||||
maxOccurs='1'/>
|
||||
</xs:choice>
|
||||
</xs:sequence>
|
||||
</xs:complexType>
|
||||
|
||||
<xs:complexType name='payloadElementType'>
|
||||
|
|
@ -1898,14 +1984,6 @@ Romeo Juliet
|
|||
</xs:simpleContent>
|
||||
</xs:complexType>
|
||||
|
||||
<xs:complexType name='zrtpElementType'>
|
||||
<xs:simpleContent>
|
||||
<xs:extension base='xs:string'>
|
||||
<xs:attribute name='version' type='xs:string' use='required'/>
|
||||
</xs:extension>
|
||||
</xs:simpleContent>
|
||||
</xs:complexType>
|
||||
|
||||
<xs:simpleType name='empty'>
|
||||
<xs:restriction base='xs:string'>
|
||||
<xs:enumeration value=''/>
|
||||
|
|
|
|||
Loading…
Reference in New Issue