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 RFC 3551. The payload IDs are represented in the 'id' attribute.
-
Each <payload-type/> 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 See <http://www.speex.org/>. codec. Where such parameters are encoded via the "fmtp" SDP attribute, they shall be represented in Jingle via the following format:
+
Each <payload-type/> 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 See <http://www.speex.org/>. codec. Where such parameters are encoded via the "fmtp" SDP attribute, they shall be represented in Jingle via the following format:
Good quality; optimized for voice; can be used for wide-band audio.
-
See &rtpspeex;.
+
See &rfc5574;.
Freely downloadable under a revised BSD license at <http://speex.org/> and commonly deployed on Internet (VoIP) systems; not commonly deployed on non-Internet systems.
Designed to be patent-clear.
diff --git a/xep.ent b/xep.ent
index 3c409019..91eeb9e5 100644
--- a/xep.ent
+++ b/xep.ent
@@ -574,6 +574,7 @@ THE SOFTWARE.
RFC 5246 RFC 5246: The Transport Layer Security (TLS) Protocol Version 1.2 <http://tools.ietf.org/html/rfc5246>." >
RFC 5389 RFC 5389: Session Traversal Utilities for NAT (STUN) <http://tools.ietf.org/html/rfc5389>." >
RFC 5391 RFC 5391: RTP Payload Format for ITU-T Recommendation G.711.1 <http://tools.ietf.org/html/rfc5391>." >
+RTP Payload Format for the Speex Codec RTP Payload Format for the Speex Codec <http://tools.ietf.org/html/rfc5574>. Work in progress." >
@@ -589,7 +590,6 @@ THE SOFTWARE.
Multicast DNS Multicast DNS <http://tools.ietf.org/html/draft-cheshire-dnsext-multicastdns>. Work in progress." >
Presence Information Data Format (PIDF) RFC 3863: Presence Information Data Format (PIDF) <http://tools.ietf.org/html/rfc3863>." >
Application Mechanism for maintaining alive the Network Address Translator (NAT) mappings associated to RTP flows Application Mechanism for maintaining alive the Network Address Translator (NAT) mappings associated to RTP flows <http://tools.ietf.org/html/draft-ietf-avt-app-rtp-keepalive>. Work in progress." >
-RTP Payload Format for the Speex Codec RTP Payload Format for the Speex Codec <http://tools.ietf.org/html/draft-ietf-avt-rtp-speex>. Work in progress." >
RTP Payload Format for Theora Encoded Video RTP Payload Format for Theora Encoded Video <http://tools.ietf.org/html/draft-barbato-avt-rtp-theora>. Work in progress." >
draft-ietf-sasl-gssapi The Kerberos V5 (GSSAPI) SASL mechanism <http://tools.ietf.org/html/draft-ietf-sasl-gssapi>. Work in progress." >
draft-cridland-sasl-tls-sessions On the use of TLS Session resumption and SASL EXTERNAL <http://tools.ietf.org/html/draft-cridland-sasl-tls-sessions>. Work in progress." >