diff --git a/xep-0167.xml b/xep-0167.xml index fba35f7d..3d5c2530 100644 --- a/xep-0167.xml +++ b/xep-0167.xml @@ -10,7 +10,7 @@ This document defines a content description format for Jingle audio sessions. &LEGALNOTICE; 0167 - Proposed + Experimental Standards Track Standards JIG Council @@ -20,10 +20,16 @@ - jingle-audio + TO BE ASSIGNED &scottlu; &stpeter; &seanegan; + + 0.7 + 2006-12-21 + psa +

Modified spec to use provisional namespace before advancement to Draft (per XEP-0053).

 + 0.6 2006-10-31 @@ -93,7 +99,7 @@

A Jingle audio 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/> element specifies an encoding that can be used for the audio stream. In Jingle Audio, these 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 allowable attributes are as follows:

- +
@@ -132,7 +138,7 @@
Attribute Description

The encodings SHOULD be provided in order of preference.

+ @@ -145,7 +151,7 @@ ]]> -

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 &JINGLE; element as specified in XEP-0166. (See Protocol Namespaces regarding issuance of a permanent namespace.)

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-speex This Internet-Draft has expired; see <http://www.watersprings.org/pub/id/draft-ietf-avt-rtp-speex-00.txt> for an archived version., the "ebw", "eng", "mode", "sr", 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:

@@ -164,16 +170,16 @@

Following is an example of this negotiation:

- - + - + ... @@ -187,12 +193,12 @@

It then offers the new content description in a 'description-modify' action:

- - + @@ -204,10 +210,10 @@ - - + @@ -256,7 +262,7 @@ a=fmtp:96 vbr=on;cng=on ]]> -

If an entity supports the Jingle audio content description format, it MUST advertise that fact by returning a feature of "http://jabber.org/protocol/jingle/description/audio" in response to &xep0030; information requests.

+

If an entity supports the Jingle audio content description format, it MUST advertise that fact by returning a feature of "http://www.xmpp.org/extensions/xep-0167.html#ns" (see Protocol Namespaces) in response to &xep0030; information requests.

... - - + + ... @@ -281,7 +287,7 @@ a=fmtp:96 vbr=on;cng=on -

Informational messages may be sent by either party within the context of Jingle to communicate the status of a Jingle audio session, device, or principal. The informational message MUST be an IQ-set containing a &JINGLE; element of type "description-info", where the informational message is a payload element qualified by the 'http://jabber.org/protocol/jingle/info/audio' namespace; the following payload elements are defined: A <trying/> element (equivalent to the SIP 100 Trying response code) is not necessary, since each session-level action is acknowledged via XMPP IQ semantics.

+

Informational messages may be sent by either party within the context of Jingle to communicate the status of a Jingle audio session, device, or principal. The informational message MUST be an IQ-set containing a &JINGLE; element of type "description-info", where the informational message is a payload element qualified by the 'http://www.xmpp.org/extensions/xep-0167.html#ns-info' namespace; the following payload elements are defined: A <trying/> element (equivalent to the SIP 100 Trying response code) is not necessary, since each session-level action is acknowledged via XMPP IQ semantics.

@@ -312,11 +318,11 @@ a=fmtp:96 vbr=on;cng=on to='romeo@montague.net/orchard' id='busy1' type='set'> - - + ]]> @@ -325,11 +331,11 @@ a=fmtp:96 vbr=on;cng=on to='romeo@montague.net/orchard' id='hold1' type='set'> - - + ]]> @@ -338,11 +344,11 @@ a=fmtp:96 vbr=on;cng=on to='romeo@montague.net/orchard' id='mute1' type='set'> - - + ]]> @@ -351,11 +357,11 @@ a=fmtp:96 vbr=on;cng=on to='romeo@montague.net/orchard' id='ringing1' type='set'> - - + ]]> @@ -400,11 +406,11 @@ The Jingle Audio-specific error conditions are as follows: - -

The ®ISTRAR; shall include 'http://jabber.org/protocol/jingle/description/audio' and 'http://jabber.org/protocol/jingle/info/audio' in its registry of protocol namespaces.

+ +

Until this specification advances to a status of Draft, its associated namespaces shall be "http://www.xmpp.org/extensions/xep-0167.html#ns" and "http://www.xmpp.org/extensions/xep-0167.html#ns-info"; upon advancement of this specification, the ®ISTRAR; shall issue permanent namespaces in accordance with the process defined in Section 4 of &xep0053;.

 -

The XMPP Registrar shall include the name "audio" in its registry of Jingle content description formats. The registration is as follows:

+

The XMPP Registrar shall include "audio" in its registry of Jingle content description formats. The registry submission is as follows:

audio @@ -422,8 +428,8 @@ The Jingle Audio-specific error conditions are as follows: @@ -474,8 +480,8 @@ The Jingle Audio-specific error conditions are as follows:
Element