Skip to content

Commit ac8e9b9

Browse files
edhelasedhelas
committed
New ProtoXEP: Jingle Content Category
1 parent 4730566 commit ac8e9b9

File tree

1 file changed

+182
-0
lines changed

1 file changed

+182
-0
lines changed

‎inbox/jingle-content-category.xml‎

Lines changed: 182 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,182 @@
1+
<?xml version='1.0' encoding='UTF-8'?>
2+
<!DOCTYPE xep SYSTEM 'xep.dtd' [
3+
<!ENTITY % ents SYSTEM 'xep.ent'>
4+
<!ENTITY namespace "urn:xmpp:jingle:apps:category:0">
5+
<!ENTITY rfc4796 "<span class='ref'><link url='http://tools.ietf.org/html/rfc4796'>RFC 4796</link></span> <note>RFC 4796: The Session Description Protocol (SDP) Content Attribute &lt;<link url='http://tools.ietf.org/html/rfc4796'>http://tools.ietf.org/html/rfc4796</link>&gt;.</note>" >
6+
%ents;
7+
]>
8+
<?xml-stylesheet type='text/xsl' href='xep.xsl'?>
9+
<xep>
10+
<header>
11+
<title>Jingle Content Category</title>
12+
<abstract>This specification defines an XMPP extension to negotiate the use of Session Description Protocol (SDP) media-
13+
level attribute 'content' as defined by RFC 4796 with Jingle RTP sessions</abstract>
14+
&LEGALNOTICE;
15+
<number>xxxx</number>
16+
<status>ProtoXEP</status>
17+
<type>Standards Track</type>
18+
<sig>Standards</sig>
19+
<approver>Council</approver>
20+
<dependencies>
21+
<spec>XMPP Core</spec>
22+
<spec>XEP-0001</spec>
23+
<spec>XEP-0166</spec>
24+
<spec>XEP-0167</spec>
25+
<spec>RFC 4796</spec>
26+
</dependencies>
27+
<supersedes/>
28+
<supersededby/>
29+
<shortname>NOT_YET_ASSIGNED</shortname>
30+
&edhelas;
31+
<revision>
32+
<version>0.0.1</version>
33+
<date>2025-09-19</date>
34+
<initials>psa</initials>
35+
<remark>
36+
<p>First draft.</p>
37+
</remark>
38+
</revision>
39+
</header>
40+
<section1 topic='Introduction' anchor='intro'>
41+
<p>The &xep0167; already defines a way to map SDP medias to Jingle RTP sessions. This mapping is also defined through several other XEPs. Jingle allows several medias to be negotiated through 'content' elements, each content is mapped to one specific SDP media. When negotiating a Jingle sessions some of its content can be similar in the sense that their medias cannot be distinguished just by examining their description lines (e.g., two video streams).</p>
42+
<p>This document defines a new element 'category', based on the &rfc4796; SDP 'content' attribute, that allows applications to treat each of those contents differently.</p>
43+
</section1>
44+
<section1 topic='Protocol' anchor='protocol'>
45+
<p>When an entity wishes to negotiate a new Jingle 'content' in a session it may want to categorize that content to help the other entities to understand how they should display it and adapt their interface in an appropriate manner.</p>
46+
47+
<p>For example, if a user wants to share simultaneously its webcam and screen with a contact the applications involved may want to automatically adapt their interface to display those different types of content accordingly, e.g., putting the screencast in full-screen and displaying the contact's webcam in the corner.</p>
48+
49+
<p>To categorize accordingly those different kinds of contents each entity SHOULD add one or several &lt;category/&gt; elements in the &lt;description/&gt; section qualified by the '&namespace;' having a 'name' attribute that MUST map to the &rfc4796; SDP 'content' attribute.</p>
50+
51+
<table caption="The category 'name' attribute values as defined from the RFC 4796">
52+
<tr>
53+
<td>
54+
<strong>Name</strong>
55+
</td>
56+
<td>
57+
<strong>Description</strong>
58+
</td>
59+
</tr>
60+
<tr>
61+
<td>slides</td>
62+
<td>The media stream includes presentation slides</td>
63+
</tr>
64+
<tr>
65+
<td>speaker</td>
66+
<td>The media stream contains the image of the speaker</td>
67+
</tr>
68+
<tr>
69+
<td>sl</td>
70+
<td>The media stream contains sign language</td>
71+
</tr>
72+
<tr>
73+
<td>main</td>
74+
<td>The media stream is taken from the main source</td>
75+
</tr>
76+
<tr>
77+
<td>alt</td>
78+
<td>The media stream is taken from the alternative source</td>
79+
</tr>
80+
</table>
81+
</section1>
82+
83+
<section1 topic='Mapping to Session Description Protocol' anchor='sdp'>
84+
<p>The SDP extract bellow.</p>
85+
86+
<code>
87+
v=0
88+
o=Stuart 292742730 29277831 IN IP4 138.143.71.89
89+
s=Showing of my skills
90+
c=IN IP4 138.143.71.2
91+
t=0 0
92+
m=video 52886 RTP/AVP 31
93+
a=rtpmap:31 H261/9000
94+
a=content:slides,alt
95+
m=video 53334 RTP/AVP 31
96+
a=rtpmap:31 H261/9000
97+
a=content:speaker
98+
m=video 54132 RTP/AVP 31
99+
a=rtpmap:31 H261/9000
100+
a=content:sl
101+
</code>
102+
103+
<p>Should then map to:</p>
104+
105+
<example caption='Server return the list of bookmarks'><![CDATA[
106+
<iq from='[email protected]/main'
107+
id='rg6s5134'
108+
to='[email protected]/living'
109+
type='set'>
110+
<jingle xmlns='urn:xmpp:jingle:1'
111+
action='session-initiate'
112+
initiator='[email protected]/main'
113+
sid='a73sjjvkla37jfea'>
114+
<content creator="initiator" name='video0'>
115+
<transport xmlns="urn:xmpp:jingle:transports:ice-udp:1"/>
116+
<description xmlns="urn:xmpp:jingle:apps:rtp:1" media="video">
117+
<category xmlns=']]>&namespace;<![CDATA[' name='slides'/>
118+
<category xmlns=']]>&namespace;<![CDATA[' name='alt'/>
119+
<payload-type id="31" name="H261" clockrate="9000"/>
120+
</description>
121+
</content>
122+
<content creator="initiator" name='video1'>
123+
<transport xmlns="urn:xmpp:jingle:transports:ice-udp:1"/>
124+
<description xmlns="urn:xmpp:jingle:apps:rtp:1" media="video">
125+
<category xmlns=']]>&namespace;<![CDATA[' name='speaker'/>
126+
<payload-type id="31" name="H261" clockrate="9000"/>
127+
</description>
128+
</content>
129+
<content creator="initiator" name='video2'>
130+
<transport xmlns="urn:xmpp:jingle:transports:ice-udp:1"/>
131+
<description xmlns="urn:xmpp:jingle:apps:rtp:1" media="video">
132+
<category xmlns=']]>&namespace;<![CDATA[' name='sl'/>
133+
<payload-type id="31" name="H261" clockrate="9000"/>
134+
</description>
135+
</content>
136+
</jingle>
137+
</iq>
138+
]]></example>
139+
</section1>
140+
<section1 topic='Requirements' anchor='reqs'>
141+
<p>The motivations for this document are to:</p>
142+
<ul>
143+
<li>Allow entities to map &rfc4796; to Jingle when initiating or answering a session</li>
144+
<li>Allow applications to categorize Jingle contents medias and adapt their interface accordingly</li>
145+
</ul>
146+
</section1>
147+
<section1 topic='Security Considerations' anchor='security'>
148+
<p>Related to the XEPs using this document.</p>
149+
</section1>
150+
<section1 topic='IANA Considerations' anchor='iana'>
151+
<p>This document requires no interaction with &IANA;.</p>
152+
</section1>
153+
<section1 topic='XMPP Registrar Considerations' anchor='registrar'>
154+
<p>The &REGISTRAR; is requested to issue an initial namespace of "&namespace;".</p>
155+
</section1>
156+
<section1 topic='XML Schema' anchor='schema'>
157+
<code><![CDATA[
158+
<?xml version='1.0' encoding='UTF-8'?>
159+
160+
<xs:schema
161+
xmlns:xs='http://www.w3.org/2001/XMLSchema'
162+
targetNamespace=']]>&namespace;<![CDATA['
163+
xmlns=']]>&namespace;<![CDATA['
164+
elementFormDefault='qualified'>
165+
166+
<xs:element name='category'>
167+
<xs:complexType>
168+
<xs:attribute name='name'>
169+
<xs:restriction base='xs:NCName'>
170+
<xs:enumeration value='slides'/>
171+
<xs:enumeration value='speaker'/>
172+
<xs:enumeration value='sl'/>
173+
<xs:enumeration value='main'/>
174+
<xs:enumeration value='alt'/>
175+
</xs:restriction>
176+
</xs:attribute>
177+
</xs:complexType>
178+
</xs:element>
179+
</xs:schema>
180+
]]></code>
181+
</section1>
182+
</xep>

0 commit comments

Comments
 (0)