moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-24 10:12:19 -05:00
Code Issues Releases Wiki Activity

xep-0294: add mapping for a=extmap-allow-mixed

Browse Source
This commit is contained in:
Philipp Hancke 2021-03-05 21:58:28 +01:00
parent 2b5ee06703
commit be6bc3a1e0
2 changed files with 51 additions and 34 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
xep-0294.xml
View File

@ -19,6 +19,7 @@
<dependencies>
<spec>XEP-0167</spec>
<spec>RFC 5285</spec>
<spec>RFC 8285</spec>
</dependencies>
<supersedes/>
<supersededby/>
@ -61,7 +62,7 @@
<section1 topic='Introduction' anchor='introduction'>
<p>This documents specifies how to negotiate the use of the RTP
Header Extensions as defined by &rfc5285; with Jingle RTP
Header Extensions as defined by &rfc5285; and &rfc8285; with Jingle RTP
sessions.</p>
</section1>
@ -69,13 +70,13 @@
<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
<cite>RFC 5285</cite>.</li>
<cite>RFC 5285</cite> and <cite>RFC 8285</cite>.</li>
<li>Map these parameters to Session Description Protocol (SDP; see
&rfc4566;) to enable interoperability.</li>
</ol>
</section1>
<section1 topic='New element' anchor='element'>
<section1 topic='New elements' anchor='element'>
<p>This specification defines a new element, &lt;rtp-hdrext/&gt;,
that can be inserted in the &lt;description/&gt; element of a
XEP-0167 RTP session.</p>
@ -112,6 +113,10 @@
parameters in the a=b form can embed &lt;parameter/&gt; elements to
describe it. Any other form of parameter can be stored as the 'key' attribute in a parameter element with an empty value.</p>
<p>This specification defines a new element, &lt;extmap-allow-mixed/&gt;,
that can be inserted in the &lt;description/&gt; element of a
XEP-0167 RTP session. The element has no attributes.</p>
</section1>
<section1 topic='Negotiation' anchor='negotiation'>
@ -132,6 +137,9 @@ describe it. Any other form of parameter can be stored as the 'key' attribute in
field from "both" to "initator" or "responder", but MUST NOT modify it
if it is "initator" or "responder".</p>
<p>The usage of the &lt;extmap-allow-mixed/&gt; is governed by the
SDP Offer/Answer mechanism as well.</p>
<p>Example negotiation where the initiator offers to use the
timestamp offset header extension as defined in &rfc5450; and also
the requests synchronisation metadata header extension (&rfc6051;)
@ -150,11 +158,13 @@ describe it. Any other form of parameter can be stored as the 'key' attribute in
uri='urn:ietf:params:rtp-hdrext:ntp-56'
id='4907'/>
<payload-type id='96' name='THEORA' clockrate='90000'/>
<extmap-allow-mixed xmlns='urn:xmpp:jingle:apps:rtp:rtp-hdrext:0'/>
</description>
]]></example>
<p>Example reply where the responder accepts the timestamp offset
and the 56-bit synchronisation metadata header extensions.</p>
and the 56-bit synchronisation metadata header extensions as well as the
&lt;extmap-allow-mixed/&gt;.</p>
<example caption='Reponder sends description inside session-accept'><![CDATA[
<description xmlns='urn:xmpp:jingle:apps:rtp:1' media='video'>
@ -186,6 +196,10 @@ describe it. Any other form of parameter can be stored as the 'key' attribute in
direction to the 'senders' attribute and the URI to the 'uri'
attribute.</p>
<p>The &lt;extmap-allow-mixed/&gt; element maps to the "a=extmap-allow-mixed" SDP line
defined in <cite>RFC 8285</cite>. Note that a session-level line might need to be mapped
to all &lt;description/&gt; elements.</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
@ -193,6 +207,7 @@ a=sendrecv
a=extmap:1 URI-toffset
a=extmap:2/recvonly URI-gps-string
a=extmap:3 URI-frametype
a=extmap-allow-mixed
]]></example>
<example caption='The same description in XMPP format'><![CDATA[
<description xmlns='urn:xmpp:jingle:apps:rtp:1' media='video'>
@ -206,6 +221,7 @@ a=extmap:3 URI-frametype
<rtp-hdrext xmlns='urn:xmpp:jingle:apps:rtp:rtp-hdrext:0'
id='3'
uri='URI-frametype'/>
<extmap-allow-mixed xmlns='urn:xmpp:jingle:apps:rtp:rtp-hdrext:0'/>
</description>
]]></example>
</section1>

1
xep.ent
View File

@ -702,6 +702,7 @@ THE SOFTWARE.
<!ENTITY rfc8446 "<span class='ref'><link url='http://tools.ietf.org/html/rfc8446'>RFC 8446</link></span> <note>RFC 8446: The Transport Layer Security (TLS) Protocol Version 1.3 &lt;<link url='http://tools.ietf.org/html/rfc8446'>http://tools.ietf.org/html/rfc8446</link>&gt;.</note>" >
<!ENTITY rfc8467 "<span class='ref'><link url='http://tools.ietf.org/html/rfc8467'>RFC 8467</link></span> <note>RFC 8467: Padding Policies for Extension Mechanisms for DNS (EDNS(0)) &lt;<link url='http://tools.ietf.org/html/rfc8467'>http://tools.ietf.org/html/rfc8467</link>&gt;.</note>" >
<!ENTITY rfc8484 "<span class='ref'><link url='http://tools.ietf.org/html/rfc8484'>RFC 8484</link></span> <note>RFC 8484: DNS Queries over HTTPS (DoH) &lt;<link url='http://tools.ietf.org/html/rfc8484'>http://tools.ietf.org/html/rfc8484</link>&gt;.</note>" >
<!ENTITY rfc8285 "<span class='ref'><link url='http://tools.ietf.org/html/rfc8285'>RFC 8285</link></span> <note>RFC 8285: A General Mechanism for RTP Header Extensions &lt;<link url='http://tools.ietf.org/html/rfc8285'>http://tools.ietf.org/html/rfc8285</link>&gt;.</note>" >
<!-- Internet-Drafts -->