diff --git a/xep-0180.xml b/xep-0180.xml index bb2b3236..ee0b4611 100644 --- a/xep-0180.xml +++ b/xep-0180.xml @@ -27,6 +27,12 @@ Chen Milton.Chen@vseelab.com + + 0.7 + 2007-05-23 + psa +

More completely specified how to include SDP parameters and codec-specific parameters (same approach as in XEP-0167); added and corrected Theora examples.

+
0.6 2007-04-17 @@ -103,13 +109,18 @@

A Jingle video session is described by one or more encodings contained within a wrapper &DESCRIPTION; element. In the language of RFC 4566 these encodings are payload-types; therefore, each <payload-type/> child element specifies an encoding that can be used for the video stream. Such encodings are often used in the context of the Real-time Transfer Protocol (RTP; see RFC 3550) but may be used in other contexts as well. 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 &PAYLOADTYPE; element's 'id' attribute is REQUIRED and its 'name' attribute is RECOMMENDED. The encodings SHOULD be provided in order of preference.

+ + + + + ]]> -

The &DESCRIPTION; element is intended to be a child of a &JINGLE; element as specified in XEP-0166.

+

The &DESCRIPTION; element is intended to be a child of a &CONTENT; element as specified in XEP-0166.

The defined attributes of the &PAYLOADTYPE; element are as follows:

@@ -163,6 +174,11 @@
positiveInteger
+

Each <payload-type/> element MAY contain one or more child elements that specify particular parameters related to the payload. For example, as described in draft-ietf-avt-rtp-theora This Internet-Draft has expired; see <http://svn.xiph.org/trunk/theora/doc/draft-ietf-avt-rtp-theora-00.txt> for an archived version., the "configuration", "configuration-uri", "delivery-method", and "sampling", parameters may be specified in relation to usage of the Theora See <http://www.theora.org/>. codec. Where such parameters are encoded via the "fmtp" SDP attribute, they shall be represented in Jingle via the following format:

+ + ]]> +

Note: The parameter names are effectively guaranteed to be unique, since &IANA; maintains a registry of SDP parameters (see <http://www.iana.org/assignments/sdp-parameters>).

@@ -178,7 +194,11 @@ sid='v1d30k1ll3dth3r4d10st4r'> - + + + + + @@ -219,7 +239,11 @@ sid='v1d30k1ll3dth3r4d10st4r'> - + + + + + @@ -303,20 +327,17 @@ a=fmtp:98 width=352;height=288; ]]>

As noted, if additional parameters are to be specified, they shall be represented as attributes of the <payload-type/> element of the child <parameter/> element, as in the following example.

- - - - - - + + + + ]]>
@@ -351,7 +372,7 @@ bitrate=384000;buffer=2000;config=4e291800 -

Support for the Theora codec See <http://www.theora.org/>. is RECOMMENDED.

+

Support for the Theora codec is RECOMMENDED.