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

initial version of XEP-0294

Browse Source
This commit is contained in:
stpeter 2011-03-24 11:47:00 -06:00
parent 1c13444a83
commit e8f8de2743
1 changed files with 18 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

34
inbox/rtp-hdrext.xml → xep-0294.xml
View File

@ -11,14 +11,14 @@
the use of the use of RTP Header Extension as defined by RFC 5285
with Jingle RTP sessions</abstract>
&LEGALNOTICE;
<number>xxxx</number>
<status>ProtoXEP</status>
<type>Standard</type>
<number>0294</number>
<status>Experimental</status>
<type>Standards Track</type>
<sig>Standards</sig>
<approver>Council</approver>
<dependencies>
<spec>XEP-0167</spec>
<spec>RFC 85</spec>
<spec>RFC 5285</spec>
</dependencies>
<author>
<firstname>Olivier</firstname>
@ -27,7 +27,13 @@
<jid>olivier.crete@collabora.co.uk</jid>
</author>
<discuss>jingle</discuss>
<revision>
<revision>
<version>0.1</version>
<date>2011-03-24</date>
<initials>psa</initials>
<remark><p>Initial published version.</p></remark>
</revision>
<revision>
<version>0.0.1</version>
<date>2011-01-10</date>
<initials>oc</initials>
@ -37,7 +43,7 @@
<section1 topic='Introduction' anchor='introduction'>
<p>This documents specifies how to negotiate the use of the RTP
Header Extensions as defined by RFC 5285 with Jingle RTP
Header Extensions as defined by &rfc5285; with Jingle RTP
sessions.</p>
</section1>
@ -45,7 +51,7 @@
<p>The Jingle extension defined herein is designed to meet the following requirements:</p>
<ol>
<li>Enable negotiations of the RTP Header extensions as defined in
RFC 5285.</li>
<cite>RFC 5285</cite>.</li>
<li>Map these parameters to Session Description Protocol (SDP; see
&rfc4566;) to enable interoperability.</li>
</ol>
@ -110,8 +116,8 @@ inside the &lt;rtp-hdrext/&gt; element.</p>
if it is "initator" or "responder".</p>
<p>Example negotiation where the initiator offers to use the
timestamp offset header extension as defined in RFC 5450 and also
the requests synchronisation metadata header extension (RFC 6051)
timestamp offset header extension as defined in &rfc5450; and also
the requests synchronisation metadata header extension (&rfc6051;)
with either the 56-bit or the 64-bit format.</p>
<example caption='Initiator sends description inside session-initiate'>
@ -159,11 +165,11 @@ inside the &lt;rtp-hdrext/&gt; element.</p>
<section1 topic='Mapping to Session Description Protocol' anchor='sdp-mapping'>
<p>The &lt;rtp-hdrext/&gt; element maps to the "a:extmap=" SDP line
defined in RFC 5285. The ID is mapped to the 'id' attribute, the
defined in <cite>RFC 5285</cite>. The ID is mapped to the 'id' attribute, the
direction to the 'senders' attribute and the URI to the 'uri'
attribute.</p>
<p>Example conversion of a incomplete sample fragment of a SDP taken from RFC 5285 section 6 into equivalent XMPP:</p>
<p>Example conversion of a incomplete sample fragment of a SDP taken from <cite>RFC 5285</cite> section 6 into equivalent XMPP:</p>
<example caption='SDP fragment'><![CDATA[
m=video
a=sendrecv
@ -239,11 +245,7 @@ a=extmap:3 URI-frametype
registry at &NAMESPACES;, as governed by &xep0053;.</p>
</section2>
<section2 topic='Namespace Versioning' anchor='registrar-versioning'>
<p>If the protocol defined in this specification undergoes a
revision that is not fully backwards-compatible with an older
version, the XMPP Registrar shall increment the protocol version
number found at the end of the XML namespaces defined herein, as
described in Section 4 of XEP-0053.</p>
&NSVER;
</section2>
</section1>
<section1 topic='XML Schemas'>