From 4a37fec1c87ed40ecda532b3b1faa683234ca461 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Thu, 29 May 2008 03:02:09 +0000 Subject: [PATCH] 0.19 git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1886 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0167.xml | 25 ++++++++++++++++++------- 1 file changed, 18 insertions(+), 7 deletions(-) diff --git a/xep-0167.xml b/xep-0167.xml index d93fcba2..93821a8d 100644 --- a/xep-0167.xml +++ b/xep-0167.xml @@ -25,6 +25,12 @@ &stpeter; &seanegan; &robmcqueen; + + 0.19 + 2008-05-28 + psa +

Specified default value for profile attribute; clarified relationship to SDP offer-answer model.

 + 0.18 2008-05-28 @@ -186,7 +192,7 @@

A Jingle audio 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:audio-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.

+ @@ -200,7 +206,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:

@@ -256,7 +262,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 audio (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 audio, each one encapsulated in a separate &PAYLOADTYPE; element (the rules specified in &rfc3264; SHOULD be followed regarding inclusion of payload types).

]]> -

If the responder wishes to accept the session, 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 session, 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.

- + @@ -1240,7 +1246,12 @@ Romeo Juliet -

Support for the Speex codec is RECOMMENDED.

+ +

For the sake of interoperability with a wide variety of free and open-source implementations as well as deployment of patent-free technologies, support for the Speex codec is RECOMMENDED.

+ + +

For the sake of interoperability with the public switched telephone network (PSTN) and most VoIP providers, support for the Pulse Code Modulation (PCM) codec defined in &ITU; recommendation G.711 is RECOMMENDED, including both the μ-law ("U-law") and A-law versions widely deployed in North America and Japan and in the rest of the world respectively.

+

If it is necessary to send Dual Tone Multi-Frequency (DTMF) tones, it is REQUIRED to use the XML format specified &xep0181;.

@@ -1303,7 +1314,7 @@ Romeo Juliet - +