moparisthebest
/
xeps
mirror of https://github.com/moparisthebest/xeps
1
0
Fork 0
Code Issues Releases Wiki Activity

listed namespaces to be requested

Browse Source 
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1429 4b5297f7-1745-476d-ba37-a9c6900126ab
xep-0352-v0.2
Peter Saint-Andre 16 years ago
parent 83e1feb27e
commit 5d2ef2784f
7 changed files with 78 additions and 11 deletions
Show Stats Download Patch File Download Diff File

14
xep-0166.xml
Unescape Escape View File

@ -816,8 +816,18 @@ PENDING o---------------------+ |
</section1>
<section1 topic='XMPP Registrar Considerations' anchor='registrar'>
<section2 topic='Protocol Namespaces' anchor='registrar-ns'>
<p>Until this specification advances to a status of Draft, its associated namespaces shall be "http://www.xmpp.org/extensions/xep-0166.html#ns" and "http://www.xmpp.org/extensions/xep-0166.html#ns-errors"; upon advancement of this specification, the &REGISTRAR; shall issue permanent namespaces in accordance with the process defined in Section 4 of &xep0053;.</p>
<section2 topic='Protocol Namespaces' anchor='ns'>
<p>Until this specification advances to a status of Draft, its associated namespaces shall be:</p>
<ul>
<li>http://www.xmpp.org/extensions/xep-0166.html#ns</li>
<li>http://www.xmpp.org/extensions/xep-0166.html#ns-errors</li>
</ul>
<p>Upon advancement of this specification, the &REGISTRAR; shall issue permanent namespaces in accordance with the process defined in Section 4 of &xep0053;.</p>
<p>The following namespaces are requested, and are thought to be unique per the XMPP Registrar's requirements:</p>
<ul>
<li>urn:xmpp:jingle</li>
<li>urn:xmpp:jingle:errors</li>
</ul>
</section2>
<section2 topic='Jingle Application Formats Registry' anchor='registrar-apps'>
<p>The XMPP Registrar shall maintain a registry of Jingle application formats. All application format registrations shall be defined in separate specifications (not in this document). Application types defined within the XEP series MUST be registered with the XMPP Registrar, resulting in protocol URNs of the form "urn:xmpp:jingle:app:name" (where "name" is the registered name of the application format).</p>

14
xep-0167.xml
Unescape Escape View File

@ -1322,7 +1322,19 @@ Romeo Juliet
<section1 topic='XMPP Registrar Considerations' anchor='registrar'>
<section2 topic='Protocol Namespaces' anchor='ns'>
<p>Until this specification advances to a status of Draft, its associated namespaces shall be "http://www.xmpp.org/extensions/xep-0167.html#ns" and "http://www.xmpp.org/extensions/xep-0167.html#ns-info"; upon advancement of this specification, the &REGISTRAR; shall issue permanent namespaces in accordance with the process defined in Section 4 of &xep0053;.</p>
<p>Until this specification advances to a status of Draft, its associated namespaces shall be:</p>
<ul>
<li>http://www.xmpp.org/extensions/xep-0167.html#ns</li>
<li>http://www.xmpp.org/extensions/xep-0167.html#ns-errors</li>
<li>http://www.xmpp.org/extensions/xep-0167.html#ns-info</li>
</ul>
<p>Upon advancement of this specification, the &REGISTRAR; shall issue permanent namespaces in accordance with the process defined in Section 4 of &xep0053;.</p>
<p>The following namespaces are requested, and are thought to be unique per the XMPP Registrar's requirements:</p>
<ul>
<li>urn:xmpp:jingle:app:audio-rtp</li>
<li>urn:xmpp:jingle:app:audio-rtp:errors</li>
<li>urn:xmpp:jingle:app:audio-rtp:info</li>
</ul>
</section2>
<section2 topic='Jingle Application Formats' anchor='registrar-content'>
<p>The XMPP Registrar shall include "audio-rtp" in its registry of Jingle application formats. The registry submission is as follows:</p>

7
xep-0168.xml
Unescape Escape View File

@ -338,13 +338,18 @@
<p>This document requires no interaction with &IANA;.</p>
</section1>
<section1 topic='XMPP Registrar Considerations' anchor='registrar'>
<section2 topic='Protocol Namespaces' anchor='registrar-ns'>
<section2 topic='Protocol Namespaces' anchor='ns'>
<p>Until this specification advances to a status of Draft, its associated namespaces shall be:</p>
<ul>
<li>http://www.xmpp.org/extensions/xep-0168.html#ns</li>
<li>http://www.xmpp.org/extensions/xep-0168.html#ns-route</li>
</ul>
<p>Upon advancement of this specification, the &REGISTRAR; shall issue permanent namespaces in accordance with the process defined in Section 4 of &xep0053;.</p>
<p>The following namespaces are requested, and are thought to be unique per the XMPP Registrar's requirements:</p>
<ul>
<li>urn:xmpp:rap</li>
<li>urn:xmpp:rap:route</li>
</ul>
</section2>
</section1>
<section1 topic='XML Schemas' anchor='schema'>

14
xep-0176.xml
Unescape Escape View File

@ -642,10 +642,20 @@
<section1 topic='XMPP Registrar Considerations' anchor='registrar'>
<section2 topic='Protocol Namespaces' anchor='ns'>
<p>Until this specification advances to a status of Draft, its associated namespaces shall be "http://www.xmpp.org/extensions/xep-0176.html#ns-udp" and "http://www.xmpp.org/extensions/xep-0176.html#ns-tcp"; upon advancement of this specification, the &REGISTRAR; shall issue permanent namespaces in accordance with the process defined in Section 4 of &xep0053;.</p>
<p>Until this specification advances to a status of Draft, its associated namespaces shall be:</p>
<ul>
<li>http://www.xmpp.org/extensions/xep-0176.html#ns-tcp</li>
<li>http://www.xmpp.org/extensions/xep-0176.html#ns-udp</li>
</ul>
<p>Upon advancement of this specification, the &REGISTRAR; shall issue permanent namespaces in accordance with the process defined in Section 4 of &xep0053;.</p>
<p>The following namespaces are requested, and are thought to be unique per the XMPP Registrar's requirements:</p>
<ul>
<li>urn:xmpp:jingle:transport:ice-tcp</li>
<li>urn:xmpp:jingle:transport:ice-udp</li>
</ul>
</section2>
<section2 topic='Jingle Transport Methods' anchor='registrar-transports'>
<p>The XMPP Registrar shall include "ice-udp" and "ice-tcp" in its registry of Jingle transport methods. The registry submission is as follows:</p>
<p>The XMPP Registrar shall include "ice-tcp" and "ice-udp" in its registry of Jingle transport methods. The registry submission is as follows:</p>
<code><![CDATA[
<transport>
<name>ice-tcp</name>

12
xep-0177.xml
Unescape Escape View File

@ -289,7 +289,17 @@
<section1 topic='XMPP Registrar Considerations' anchor='registrar'>
<section2 topic='Protocol Namespaces' anchor='ns'>
<p>Until this specification advances to a status of Draft, its associated namespaces shall be "http://www.xmpp.org/extensions/xep-0177.html#ns" and "http://www.xmpp.org/extensions/xep-0177.html#ns-info"; upon advancement of this specification, the &REGISTRAR; shall issue permanent namespaces in accordance with the process defined in Section 4 of &xep0053;.</p>
<p>Until this specification advances to a status of Draft, its associated namespaces shall be:</p>
<ul>
<li>http://www.xmpp.org/extensions/xep-0177.html#ns</li>
<li>http://www.xmpp.org/extensions/xep-0177.html#ns-info</li>
</ul>
<p>Upon advancement of this specification, the &REGISTRAR; shall issue permanent namespaces in accordance with the process defined in Section 4 of &xep0053;.</p>
<p>The following namespaces are requested, and are thought to be unique per the XMPP Registrar's requirements:</p>
<ul>
<li>urn:xmpp:jingle:transport:raw-udp</li>
<li>urn:xmpp:jingle:transport:raw-udp:info</li>
</ul>
</section2>
<section2 topic='Jingle Transport Methods' anchor='registrar-transports'>
<p>The XMPP Registrar shall include "raw-udp" in its registry of Jingle transport methods. The registry submission is as follows:</p>

12
xep-0180.xml
Unescape Escape View File

@ -447,7 +447,17 @@ delivery-method=inline; configuration=somebase16string;
<section1 topic='XMPP Registrar Considerations' anchor='registrar'>
<section2 topic='Protocol Namespaces' anchor='ns'>
<p>Until this specification advances to a status of Draft, its associated namespaces shall be "http://www.xmpp.org/extensions/xep-0180.html#ns" and "http://www.xmpp.org/extensions/xep-0180.html#ns-errors"; upon advancement of this specification, the &REGISTRAR; shall issue permanent namespaces in accordance with the process defined in Section 4 of &xep0053;.</p>
<p>Until this specification advances to a status of Draft, its associated namespaces shall be:</p>
<ul>
<li>http://www.xmpp.org/extensions/xep-0180.html#ns</li>
<li>http://www.xmpp.org/extensions/xep-0180.html#ns-errors</li>
</ul>
<p>Upon advancement of this specification, the &REGISTRAR; shall issue permanent namespaces in accordance with the process defined in Section 4 of &xep0053;.</p>
<p>The following namespaces are requested, and are thought to be unique per the XMPP Registrar's requirements:</p>
<ul>
<li>urn:xmpp:jingle:app:video-rtp</li>
<li>urn:xmpp:jingle:app:video-rtp:errors</li>
</ul>
</section2>
<section2 topic='Jingle Application Formats' anchor='registrar-content'>
<p>The XMPP Registrar shall include "video-rtp" in its registry of Jingle application formats. The registry submission is as follows:</p>

16
xep-0181.xml
Unescape Escape View File

@ -161,7 +161,7 @@
<section1 topic='Determining Support' anchor='disco'>
<p>If an entity supports Jingle DTMF (which natively includes sending of DTMF in the XMPP signalling channel), it MUST return a &xep0030; feature of "http://www.xmpp.org/extensions/xep-0181.html#ns" in response to service discovery information requests.</p>
<p>If an entity also supports sending of DTMF in the content channel, it MUST also return a service discovery feature of "http://www.xmpp.org/extensions/xep-0181.html#ns-rtp" in response to service discovery information requests.</p>
<p>If an entity also supports sending of DTMF in the content channel, it MUST also return a service discovery feature of "urn:xmpp:jingle:dtmf:rtp" in response to service discovery information requests.</p>
<p>Naturally, support MAY also be determined via the dynamic, presence-based profile of Service Discovery defined in &xep0115;.</p>
</section1>
@ -175,10 +175,20 @@
<section1 topic='XMPP Registrar Considerations' anchor='registrar'>
<section2 topic='Protocol Namespaces' anchor='ns'>
<p>Until this specification advances to a status of Draft, its associated namespaces shall be "http://www.xmpp.org/extensions/xep-0181.html#ns" and "http://www.xmpp.org/extensions/xep-0181.html#ns-errors"; upon advancement of this specification, the &REGISTRAR; shall issue permanent namespaces in accordance with the process defined in Section 4 of &xep0053;.</p>
<p>Until this specification advances to a status of Draft, its associated namespaces shall be:</p>
<ul>
<li>http://www.xmpp.org/extensions/xep-0181.html#ns</li>
<li>http://www.xmpp.org/extensions/xep-0181.html#ns-errors</li>
</ul>
<p>Upon advancement of this specification, the &REGISTRAR; shall issue permanent namespaces in accordance with the process defined in Section 4 of &xep0053;.</p>
<p>The following namespaces are requested, and are thought to be unique per the XMPP Registrar's requirements:</p>
<ul>
<li>urn:xmpp:jingle:dtmf</li>
<li>urn:xmpp:jingle:dtmf:errors</li>
</ul>
</section2>
<section2 topic='Service Discovery Features' anchor='registrar-disco'>
<p>The XMPP Registrar shall include 'http://www.xmpp.org/extensions/xep-0181.html#ns-rtp' in its registry of service discovery features.</p>
<p>The XMPP Registrar shall include "urn:xmpp:jingle:dtmf:rtp" in its registry of service discovery features (see &DISCOFEATURES;).</p>
</section2>
</section1>

Write Preview
Loading…
Cancel
Save