mirror of
https://github.com/moparisthebest/xeps
synced 2024-11-21 16:55:07 -05:00
1.1rc3
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@3664 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
parent
aa71b2c9c8
commit
2d3695a6ae
@ -42,10 +42,10 @@
|
||||
&robmcqueen;
|
||||
&diana;
|
||||
<revision>
|
||||
<version>1.1rc2</version>
|
||||
<date>in progress, last updated 2009-11-19</date>
|
||||
<version>1.1rc3</version>
|
||||
<date>in progress, last updated 2009-12-02</date>
|
||||
<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 <failed-application/> 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 <failed-application/> 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>
|
||||
<version>1.0</version>
|
||||
@ -514,12 +514,13 @@ Initiator Responder
|
||||
|
||||
<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 Jingle <bandwidth/> element SHALL be mapped to an SDP b= line; in particular, the value of the 'type' attribute shall be mapped to the SDP <bwtype> parameter and the XML character data of the Jingle <bandwidth/> element shall be mapped to the SDP <bandwidth> parameter.</p>
|
||||
<p>The Jingle <bandwidth/> element SHALL be mapped to an SDP b= line; in particular, the value of the 'type' attribute SHALL be mapped to the SDP <bwtype> parameter and the XML character data of the Jingle <bandwidth/> element SHALL be mapped to the SDP <bandwidth> 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>
|
||||
<code><![CDATA[
|
||||
m=<media> <port> <transport> <fmt list>
|
||||
]]></code>
|
||||
<p>The SDP <media> parameter is "audio" or "video" or some other media type as specified by the Jingle 'media' attribute, the <port> parameter is the preferred port for such communications (which might be determined dynamically), and the <fmt list> parameter is the payload-type ID.</p>
|
||||
<p>By default the SDP <transport> MUST be considered "RTP/AVP" as defined in <cite>RFC 3550</cite>. If the initiation request contains a <security/> element to specify security preconditions for the session, then the SDP <transport> 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>
|
||||
<code><![CDATA[
|
||||
<description xmlns='urn:xmpp:jingle:apps:rtp:1' media='audio'>
|
||||
|
Loading…
Reference in New Issue
Block a user