moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-21 16:55:07 -05:00
Code Issues Releases Wiki Activity

0.27

Browse Source 
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1913 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2008-06-04 21:49:49 +00:00
parent 0fda9f93a7
commit 197da78ece
1 changed files with 11 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
xep-0166.xml
View File

@ -26,6 +26,12 @@
&robmcqueen;
&seanegan;
&hildjj;
<revision>
<version>0.27</version>
<date>2008-06-04</date>
<initials>psa</initials>
<remark><p>Updated examples to track changes to XEP-0167 and retraction of XEP-0180; corrected definition of name attribute to allow semantic meaning.</p></remark>
</revision>
<revision>
<version>0.26</version>
<date>2008-05-28</date>
@ -346,7 +352,7 @@ Romeo Juliet
</ol>
<p>This document defines the signalling protocol only. Additional documents specify the following:</p>
<ul>
<li><p>Various application formats (audio, video, etc.) and, where possible, mapping of those types to the Session Description Protocol (SDP; see &rfc4566;); examples include <cite>Jingle Audio via RTP</cite> and <cite>Jingle Video via RTP</cite>.</p></li>
<li><p>Various application formats (audio, video, etc.) and, where possible, mapping of those types to the Session Description Protocol (SDP; see &rfc4566;); examples include <cite>Jingle RTP Sessions</cite> and <cite>Jingle Video via RTP</cite>.</p></li>
<li><p>Various transport methods; examples include &xep0176; and <cite>Raw UDP Transport</cite>.</p></li>
<li><p>Procedures for mapping the Jingle signalling protocol to existing signalling standards such as the IETF's Session Initiation Protocol (SIP) and the ITU's H.323 protocol (see &h323;); these documents are forthcoming.</p></li>
</ul>
@ -479,7 +485,7 @@ PENDING o---------------------+ |
</tr>
<tr>
<td>session-info</td>
<td>Send session-level information, such as (for Jingle audio) a ringing message.</td>
<td>Send session-level information, such as (for Jingle RTP sessions) a ringing message.</td>
</tr>
<tr>
<td>session-initiate</td>
@ -743,7 +749,7 @@ PENDING o---------------------+ |
action='session-info'
initiator='romeo@montague.net/orchard'
sid='a73sjjvkla37jfea'>
<ringing xmlns='urn:xmpp:tmp:jingle:apps:audio-rtp:info'/>
<ringing xmlns='urn:xmpp:tmp:jingle:apps:rtp:info'/>
</jingle>
</iq>
]]></example>
@ -811,7 +817,7 @@ PENDING o---------------------+ |
</tr>
<tr>
<td>name</td>
<td>A unique name or identifier for the content type (this identifier is opaque and does not have semantic meaning).</td>
<td>A unique name or identifier for the content type, which MAY have semantic meaning in order to differentiate this content type from other content types (e.g., two content types containing video media could differentiate between "room-pan" and "slides").</td>
<td>REQUIRED</td>
</tr>
<tr>
@ -932,7 +938,7 @@ PENDING o---------------------+ |
<section1 topic='Conformance by Using Protocols' anchor='conformance'>
<section2 topic='Application Formats' anchor='conformance-apps'>
<p>A document that specifies a Jingle application format (e.g., audio via RTP) MUST define:</p>
<p>A document that specifies a Jingle application format (e.g., RTP sessions) MUST define:</p>
<ol>
<li>How successful application format negotiation occurs for encapsulation into Jingle.</li>
<li>A &DESCRIPTION; element and associated semantics for representing the application format.</li>