moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-22 01:02:17 -05:00
Code Issues Releases Wiki Activity

1.1rc3

Browse Source 
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@3664 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2009-12-02 18:53:48 +00:00
parent aa71b2c9c8
commit 2d3695a6ae
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
xep-0167.xml
View File

@ -42,10 +42,10 @@
&robmcqueen; &robmcqueen;
&diana; &diana;
<revision> <revision>
<version>1.1rc2</version> <version>1.1rc3</version>
<date>in progress, last updated 2009-11-19</date> <date>in progress, last updated 2009-12-02</date>
<initials>psa</initials> <initials>psa</initials>
<remark><p>Added creator attribute to mute and unmute elements so that these events can be correlated with a particular content type; clarified use of the reason element in cases other than termination; defined handling of content-add when none of the offered payload-types are supported, where the signalling uses a content-reject message with a Jingle reason of &lt;failed-application/&gt; and a list of the supported codecs.</p></remark> <remark><p>Added creator attribute to mute and unmute elements so that these events can be correlated with a particular content type; clarified use of the reason element in cases other than termination; defined handling of content-add when none of the offered payload-types are supported, where the signalling uses a content-reject message with a Jingle reason of &lt;failed-application/&gt; and a list of the supported codecs; clarified that the SDP transport is RTP/AVP by default, that the transport is RTP/SAVP if security preconditions are present, and that additional transports such as RTP/AVPF and RTP/SAVPF might be supported in a future version of this specification.</p></remark>
</revision> </revision>
<revision> <revision>
<version>1.0</version> <version>1.0</version>
@ -514,12 +514,13 @@ Initiator Responder
<section1 topic='Mapping to Session Description Protocol' anchor='sdp'> <section1 topic='Mapping to Session Description Protocol' anchor='sdp'>
<p>The SDP media type for Jingle RTP is "audio" (see Section 8.2.1 of <cite>RFC 4566</cite>) for audio media, "video" (see Section 8.2.1 of <cite>RFC 4566</cite>) for video media, etc. The media type is reflected in the Jingle 'media' attribute.</p> <p>The SDP media type for Jingle RTP is "audio" (see Section 8.2.1 of <cite>RFC 4566</cite>) for audio media, "video" (see Section 8.2.1 of <cite>RFC 4566</cite>) for video media, etc. The media type is reflected in the Jingle 'media' attribute.</p>
<p>The Jingle &lt;bandwidth/&gt; element SHALL be mapped to an SDP b= line; in particular, the value of the 'type' attribute shall be mapped to the SDP &lt;bwtype&gt; parameter and the XML character data of the Jingle &lt;bandwidth/&gt; element shall be mapped to the SDP &lt;bandwidth&gt; parameter.</p> <p>The Jingle &lt;bandwidth/&gt; element SHALL be mapped to an SDP b= line; in particular, the value of the 'type' attribute SHALL be mapped to the SDP &lt;bwtype&gt; parameter and the XML character data of the Jingle &lt;bandwidth/&gt; element SHALL be mapped to the SDP &lt;bandwidth&gt; parameter.</p>
<p>If the payload type is static (payload-type IDs 0 through 95 inclusive), it MUST be mapped to an m= line as defined in <cite>RFC 4566</cite>. The generic format for this line is as follows:</p> <p>If the payload type is static (payload-type IDs 0 through 95 inclusive), it MUST be mapped to an m= line as defined in <cite>RFC 4566</cite>. The generic format for this line is as follows:</p>
<code><![CDATA[ <code><![CDATA[
m=<media> <port> <transport> <fmt list> m=<media> <port> <transport> <fmt list>
]]></code> ]]></code>
<p>The SDP &lt;media&gt; parameter is "audio" or "video" or some other media type as specified by the Jingle 'media' attribute, the &lt;port&gt; parameter is the preferred port for such communications (which might be determined dynamically), and the &lt;fmt list&gt; parameter is the payload-type ID.</p> <p>The SDP &lt;media&gt; parameter is "audio" or "video" or some other media type as specified by the Jingle 'media' attribute, the &lt;port&gt; parameter is the preferred port for such communications (which might be determined dynamically), and the &lt;fmt list&gt; parameter is the payload-type ID.</p>
<p>By default the SDP &lt;transport&gt; MUST be considered "RTP/AVP" as defined in <cite>RFC 3550</cite>. If the initiation request contains a &lt;security/&gt; element to specify security preconditions for the session, then the SDP &lt;transport&gt; MUST instead be considered "RTP/SAVP" as defined in <cite>RFC 3711</cite>. Future versions of this specification might define how to use other SDP transports, such as "RTP/AVPF" and "RTP/SAVPF" as defined in &rfc4585; and &rfc5124; respectively.</p>
<p>For example, consider the following static payload-type:</p> <p>For example, consider the following static payload-type:</p>
<code><![CDATA[ <code><![CDATA[
<description xmlns='urn:xmpp:jingle:apps:rtp:1' media='audio'> <description xmlns='urn:xmpp:jingle:apps:rtp:1' media='audio'>