[Telepathy-commits] [telepathy-spec/master] Media.StreamHandler.RelayInfo: Add some rationale
Simon McVittie
simon.mcvittie at collabora.co.uk
Tue Mar 24 09:53:42 PDT 2009
---
spec/Media_Stream_Handler.xml | 15 ++++++++++++++-
1 files changed, 14 insertions(+), 1 deletions(-)
diff --git a/spec/Media_Stream_Handler.xml b/spec/Media_Stream_Handler.xml
index c45c7d8..1a68532 100644
--- a/spec/Media_Stream_Handler.xml
+++ b/spec/Media_Stream_Handler.xml
@@ -151,9 +151,22 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.</
<dt><code>component</code></dt>
<dd>The component number to use this relay server for, as an
ASCII unsigned integer; if not included, this relay server
- may be used for any or all components</dd>
+ may be used for any or all components.
+
+ <tp:rationale>
+ In ICE draft 6, as used by Google Talk, credentials are only
+ valid once, so each component needs relaying separately.
+ </tp:rationale>
+ </dd>
</dl>
+ <tp:rationale>
+ <p>An equivalent of the gtalk-p2p-relay-token property on
+ MediaSignalling channels is not included here. The connection
+ manager should be responsible for making the necessary HTTP
+ requests to turn the token into a username and password.</p>
+ </tp:rationale>
+
<p>The type of relay server that this represents depends on
the value of the <tp:member-ref>NATTraversal</tp:member-ref>
property. If NATTraversal is ice-udp, this is a TURN server;
--
1.5.6.5
More information about the telepathy-commits
mailing list