moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-12-21 23:28:51 -05:00
Code Issues Releases Wiki Activity

tracking other XEPs

Browse Source 
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@2751 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2009-02-18 02:40:56 +00:00
parent b836fbc640
commit ddcb924cef
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
xep-0177.xml
View File

@ -152,7 +152,7 @@
<li><p>The transport negotiation process is defined in the <link url='#protocol'>Protocol Description</link> section of this document.</p></li>
<li><p>The semantics of the &TRANSPORT; element are defined in the <link url='#initiate'>Transport Initiation</link> section of this document.</p></li>
<li><p>Successful negotiation of the Raw UDP method results in use of a datagram transport that is suitable for applications where some packet loss is tolerable, such as audio and video.</p></li>
<li><p>If multiple components are to be communicated over the transport in the context of the Real-time Transport Protocol (RTP; see &rfc3550;), the component numbered "1" shall be associated with RTP and the component numbered "2" shall be associated with the Real Time Control Protocol (RTCP).</p></li>
<li><p>If multiple components are to be communicated by the application type that uses the transport, the transport shall support those components and assign identifiers for them as described in the specification that defines the application type.</p></li>
</ol>
</section1>
@ -232,7 +232,7 @@ INITIATOR RESPONDER
to='romeo@montague.lit/orchard'
type='result'/>
]]></example>
<p>As soon as the responding user agrees to proceed with the session, the responding client MUST send a Jingle session-accept to the initiator. This session-accept message MAY include a candidate that is generated by the responder.</p>
<p>As soon as the responding user agrees to proceed with the session, the responding client MUST send a Jingle session-accept to the initiator. This session-accept message MAY include one or more candidates generated by the responder.</p>
<example caption="Responder definitively accepts the session"><![CDATA[
<iq from='juliet@capulet.lit/balcony'
id='accept1'