git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@3273 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2009-06-23 01:52:58 +00:00
parent b18a9bf29c
commit 9fed543977
3 changed files with 3 additions and 3 deletions

View File

@ -368,7 +368,7 @@
</tr>
</table>
<p>In Jingle RTP, the encodings are used in the context of RTP. The most common encodings for the Audio/Video Profile (AVP) of RTP are listed in &rfc3551; (these "static" types are reserved from payload ID 0 through payload ID 95), although other encodings are allowed (these "dynamic" types use payload IDs 96 to 127) in accordance with the dynamic assignment rules described in Section 3 of <cite>RFC 3551</cite>. The payload IDs are represented in the 'id' attribute.</p>
<p>Each &lt;payload-type/&gt; element MAY contain one or more child elements that specify particular parameters related to the payload. For example, as described in &rtpspeex;, the "cng", "mode", and "vbr" parameters can be specified in relation to usage of the Speex <note>See &lt;<link url='http://www.speex.org/'>http://www.speex.org/</link>&gt;.</note> codec. Where such parameters are encoded via the "fmtp" SDP attribute, they shall be represented in Jingle via the following format:</p>
<p>Each &lt;payload-type/&gt; element MAY contain one or more child elements that specify particular parameters related to the payload. For example, as described in &rfc5574;, the "cng", "mode", and "vbr" parameters can be specified in relation to usage of the Speex <note>See &lt;<link url='http://www.speex.org/'>http://www.speex.org/</link>&gt;.</note> codec. Where such parameters are encoded via the "fmtp" SDP attribute, they shall be represented in Jingle via the following format:</p>
<code><![CDATA[
<parameter name='foo' value='bar'/>
]]></code>

View File

@ -92,7 +92,7 @@
</tr>
<tr>
<td>Good quality; optimized for voice; can be used for wide-band audio.</td>
<td>See &rtpspeex;.</td>
<td>See &rfc5574;.</td>
<td>Freely downloadable under a revised BSD license at &lt;<link url='http://speex.org/'>http://speex.org/</link>&gt; and commonly deployed on Internet (VoIP) systems; not commonly deployed on non-Internet systems.</td>
<td>Designed to be patent-clear.</td>
</tr>

View File

@ -574,6 +574,7 @@ THE SOFTWARE.
<!ENTITY rfc5246 "<span class='ref'><link url='http://tools.ietf.org/html/rfc5246'>RFC 5246</link></span> <note>RFC 5246: The Transport Layer Security (TLS) Protocol Version 1.2 &lt;<link url='http://tools.ietf.org/html/rfc5246'>http://tools.ietf.org/html/rfc5246</link>&gt;.</note>" >
<!ENTITY rfc5389 "<span class='ref'><link url='http://tools.ietf.org/html/rfc5389'>RFC 5389</link></span> <note>RFC 5389: Session Traversal Utilities for NAT (STUN) &lt;<link url='http://tools.ietf.org/html/rfc5389'>http://tools.ietf.org/html/rfc5389</link>&gt;.</note>" >
<!ENTITY rfc5391 "<span class='ref'><link url='http://tools.ietf.org/html/rfc5391'>RFC 5391</link></span> <note>RFC 5391: RTP Payload Format for ITU-T Recommendation G.711.1 &lt;<link url='http://tools.ietf.org/html/rfc5391'>http://tools.ietf.org/html/rfc5391</link>&gt;.</note>" >
<!ENTITY rfc5574 "<span class='ref'><link url='http://tools.ietf.org/html/rfc5574'>RTP Payload Format for the Speex Codec</link></span> <note>RTP Payload Format for the Speex Codec &lt;<link url='http://tools.ietf.org/html/rfc5574'>http://tools.ietf.org/html/rfc5574</link>&gt;. Work in progress.</note>" >
<!-- Internet-Drafts -->
@ -589,7 +590,6 @@ THE SOFTWARE.
<!ENTITY mdns "<span class='ref'><link url='http://tools.ietf.org/html/draft-cheshire-dnsext-multicastdns'>Multicast DNS</link></span> <note>Multicast DNS &lt;<link url='http://tools.ietf.org/html/draft-cheshire-dnsext-multicastdns'>http://tools.ietf.org/html/draft-cheshire-dnsext-multicastdns</link>&gt;. Work in progress.</note>" >
<!ENTITY pidf "<span class='ref'><link url='http://tools.ietf.org/html/rfc3863'>Presence Information Data Format (PIDF) </link></span> <note>RFC 3863: Presence Information Data Format (PIDF) &lt;<link url='http://tools.ietf.org/html/rfc3863'>http://tools.ietf.org/html/rfc3863</link>&gt;.</note>" >
<!ENTITY rtpkeepalive "<span class='ref'><link url='http://tools.ietf.org/html/draft-ietf-avt-app-rtp-keepalive'>Application Mechanism for maintaining alive the Network Address Translator (NAT) mappings associated to RTP flows</link></span> <note>Application Mechanism for maintaining alive the Network Address Translator (NAT) mappings associated to RTP flows &lt;<link url='http://tools.ietf.org/html/draft-ietf-avt-app-rtp-keepalive'>http://tools.ietf.org/html/draft-ietf-avt-app-rtp-keepalive</link>&gt;. Work in progress.</note>" >
<!ENTITY rtpspeex "<span class='ref'><link url='http://tools.ietf.org/html/draft-ietf-avt-rtp-speex'>RTP Payload Format for the Speex Codec</link></span> <note>RTP Payload Format for the Speex Codec &lt;<link url='http://tools.ietf.org/html/draft-ietf-avt-rtp-speex'>http://tools.ietf.org/html/draft-ietf-avt-rtp-speex</link>&gt;. Work in progress.</note>" >
<!ENTITY rtptheora "<span class='ref'><link url='http://tools.ietf.org/html/draft-barbato-avt-rtp-theora'>RTP Payload Format for Theora Encoded Video</link></span> <note>RTP Payload Format for Theora Encoded Video &lt;<link url='http://tools.ietf.org/html/draft-barbato-avt-rtp-theora'>http://tools.ietf.org/html/draft-barbato-avt-rtp-theora</link>&gt;. Work in progress.</note>" >
<!ENTITY saslkrb5 "<span class='ref'><link url='http://tools.ietf.org/html/draft-ietf-sasl-gssapi'>draft-ietf-sasl-gssapi</link></span> <note>The Kerberos V5 (GSSAPI) SASL mechanism &lt;<link url='http://tools.ietf.org/html/draft-ietf-sasl-gssapi'>http://tools.ietf.org/html/draft-ietf-sasl-gssapi</link>&gt;. Work in progress.</note>" >
<!ENTITY sasltls "<span class='ref'><link url='http://tools.ietf.org/html/draft-cridland-sasl-tls-sessions'>draft-cridland-sasl-tls-sessions</link></span> <note>On the use of TLS Session resumption and SASL EXTERNAL &lt;<link url='http://tools.ietf.org/html/draft-cridland-sasl-tls-sessions'>http://tools.ietf.org/html/draft-cridland-sasl-tls-sessions</link>&gt;. Work in progress.</note>" >