On Wed, 12 Jun 2013, Peter Saint-Andre wrote:
On 6/12/13 11:23 AM, Philipp Hancke wrote:
old thread alert...
Am 18.02.2011 17:37, schrieb XMPP Extensions Editor:
XEP-0215 (External Service Discovery) has been Deferred because
of inactivity.

Oh, I wrote a prosody module for this recently, covering the stuff
in 3.1 (and 3.3 when time permits me to clean things up a litte).
Primary use-case was handing out time-limited turn credentials for
webrtc clients. Works like charm, also for provisioning stun.

Yes, that was the idea.

http://www.ietf.org/id/draft-uberti-rtcweb-turn-rest-00.txt describes it fully. Ignore the "REST" part, XEP-0215 solves way more usecases (such as deploying stun servers, removing servers going down for maintenance via services push, ...)

One remark: Having a format which uses the same terminology as
http://www.w3.org/TR/webrtc/#rtciceserver-type (url, credential and
due to recent consensus username) would be handy, but as long as
there is a straightforward mapping...

There were no 'stun' or 'turn' URIs back in 2007. :-) If there's a URI
scheme available, as there is now for STUN and TURN, I suppose you can
put the type, host, and port in one string. But what do we do if we
want to advertise external services for which no URI scheme exists
(say, a SOCK5 Bytestreams proxy or a Jingle Nodes service)?

As far as I'm concerned this could go to draft without any
changes.

Cool.

Is the attached patch a sufficient reason to update this, getting it back to experimental and then to draft? :-)

And guess what, there is even a prosody module for this.
diff --git a/extensions/xep-0215.xml b/extensions/xep-0215.xml
index 1d33982..48113f6 100644
--- a/extensions/xep-0215.xml
+++ b/extensions/xep-0215.xml
@@ -285,6 +285,7 @@
   </credentials>
 </iq>
     ]]></example>
+    <p>For TURN, the server might construct time-limited credentials as described in <span class='ref'><link url='http://tools.ietf.org/html/draft-uberti-rtcweb-turn-rest-00'>draft-uberti-rtcweb-turn-rest-00</link></span><note>draft-uberti-rtcweb-turn-rest-00: A REST API For Access To TURN Services &lt;<link url='http://tools.ietf.org/html/draft-uberti-rtcweb-turn-rest-00'>http://tools.ietf.org/html/draft-uberti-rtcweb-turn-rest-00</link>&gt;. Work in progress.</note></p>
     <p>If the server cannot obtain credentials at the service, it returns an appropriate stanza error, such as &notfound;, &remoteserver;, &timeout;, or &notauthorized;.</p>
   </section2>
 </section1>
@@ -374,7 +375,7 @@
 <service>
   <name>turn</name>
   <desc>a server that provides Traversal Using Relays around NAT (TURN)</desc>
-  <doc>draft-ietf-behave-turn</doc>
+  <doc>RFC 5766</doc>
 </service>
       ]]></code>
     </section3>

Reply via email to