From 02462c6e4ca320c62a6475e3adb89f7961b90a30 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Thu, 29 May 2008 03:02:20 +0000 Subject: [PATCH] 0.12 git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1887 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0180.xml | 83 ++++++++++++++++++---------------------------------- 1 file changed, 28 insertions(+), 55 deletions(-) diff --git a/xep-0180.xml b/xep-0180.xml index 56f1b444..ff9cc346 100644 --- a/xep-0180.xml +++ b/xep-0180.xml @@ -20,13 +20,19 @@ - TO BE ASSIGNED + NOT_YET_ASSIGNED &stpeter; Milton Chen Milton.Chen@vseelab.com + + 0.12 + 2008-05-28 + psa +

Specified default value for profile attribute; clarified relationship to SDP offer-answer model; moved some attributes from payload-type element to optional parameter elements.

 + 0.11 2008-02-28 @@ -133,7 +139,9 @@

A Jingle video session is described by a content type that contains one application format and one transport method. The application format consists of one or more encodings contained within a wrapper <description/> element qualified by the 'urn:xmpp:tmp:jingle:apps:video-rtp' namespace &NSNOTE;. In the language of RFC 4566 each encoding is a payload-type; therefore, each <payload-type/> element specifies an encoding that can be used for the audio stream, as illustrated in the following example.

- + + + @@ -144,7 +152,7 @@ ]]>

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

-

The &DESCRIPTION; element SHOULD possess a 'profile' attribute that specifies the profile of RTP in use as would be encapsulated in SDP (e.g., "RTP/AVP" or "UDP/TLS/RTP/SAVP").

+

The &DESCRIPTION; element SHOULD possess a 'profile' attribute that specifies the profile of RTP in use as would be encapsulated in SDP (e.g., "RTP/AVP" or "UDP/TLS/RTP/SAVP"). If not included, the default value of "RTP/AVP" MUST be assumed.

The encodings SHOULD be provided in order of preference by placing the most-preferred &PAYLOADTYPE; element as the first child of the &DESCRIPTION; element (etc.).

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

@@ -166,57 +174,21 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
positiveInteger RECOMMENDED
heightThe vertical extent of the displayed video, in pixelspositiveIntegerRECOMMENDED
id A unique identifier for the payload type positiveInteger REQUIRED
layerThe relationship of a layer to the "bottom" of the stack, where 0 = bottom (the first layer)nonNegativeIntegerOPTIONAL
name A name for the payload type string RECOMMENDED for static payload types, REQUIRED for dynamic payload types
transparentWhether or not a layer is transparentbooleanOPTIONAL
widthThe horizontal extent of the displayed video, in pixelspositiveIntegerRECOMMENDED
xThe horizontal starting point of a tile, in pixels from the origin pointpositiveIntegerOPTIONAL
yThe vertical starting point of a tile, in pixels from the origin pointpositiveIntegerOPTIONAL

In Jingle Video, 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 may 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 &rtptheora;, the "configuration", "configuration-uri", "delivery-method", "height", "sampling", and "width" 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:

]]> @@ -224,7 +196,7 @@ -

When the initiator sends a session-initiate stanza to the responder, the &DESCRIPTION; element includes all of the payload types that the initiator can receive for Jingle video (each one encapsulated in a separate &PAYLOADTYPE; element):

+

When the initiator sends a session-initiate stanza to the responder, the &DESCRIPTION; element includes all of the payload types that the initiator can send and/or receive for Jingle video, each one encapsulated in a separate &PAYLOADTYPE; element (the rules specified in &rfc3264; SHOULD be followed regarding inclusion of payload types).

- + + + @@ -269,7 +243,7 @@ to='romeo@montague.net/orchard' type='result' /> ]]> -

If the responder wishes to accept the content definition, it MUST send a content-accept action to the initiator, which SHOULD include a list of the payload types that it can receive. The list that the responder sends MAY include any payload types (not a subset of the payload types sent by the initiator) but SHOULD retain the ID numbers specified by the initiator. The order of the &PAYLOADTYPE; elements indicates the responder's preferences, with the most-preferred types first.

+

If the responder wishes to accept the content definition, it MUST send a content-accept action to the initiator, which SHOULD include a list of the payload types that it can send and/or receive. The list that the responder sends MAY include any payload types (not a subset of the payload types sent by the initiator) but SHOULD retain the ID numbers specified by the initiator. The order of the &PAYLOADTYPE; elements indicates the responder's preferences, with the most-preferred types first.

- + + + @@ -314,7 +290,9 @@ sid='v1d30k1ll3dth3r4d10st4r'> - + + + @@ -371,17 +349,18 @@ m=video 9000 RTP/AVP 28

If the payload type is dynamic (payload-type IDs 96 through 127 inclusive), it SHOULD be mapped to an SDP media field plus an SDP attribute field named "rtpmap".

For example, consider a VC-1 payload such as that described in &rfc4425;:

+ ]]>

That Jingle-formatted information would be mapped to SDP as follows:

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

+ + + @@ -499,7 +478,7 @@ delivery-method=inline; configuration=somebase16string; - + @@ -510,14 +489,8 @@ delivery-method=inline; configuration=somebase16string; - - - - - -