From 3620d2d2bb7100a050b2092e6e520ea9e5d6c372 Mon Sep 17 00:00:00 2001
From: Xavier Claessens <xclaesse@gmail.com>
Date: Mon, 7 Nov 2011 16:07:31 +0100
Subject: Call1: Add rational explaining why Content could have multiple
 streams

---
 spec/Call_Content.xml | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/spec/Call_Content.xml b/spec/Call_Content.xml
index 12061a29..ef08acc3 100644
--- a/spec/Call_Content.xml
+++ b/spec/Call_Content.xml
@@ -31,6 +31,17 @@
       and one video content. Each content has one or more <tp:dbus-ref
       namespace="ofdT.Call1">Stream</tp:dbus-ref> objects which
       represent the actual transport to one or more remote contacts.</p>
+      <tp:rationale>
+        There are two cases where multiple streams may happen:
+        <ul>
+          <li>Calls with more than two participants, if the protocol does not
+          support multicast, and does not have mixer proxy.</li>
+          <li>With jingle, when calling a contact connected from multiple
+          resources, a stream is created for each resource. Once the remote
+          contact answered from one of its resources, all other streams get
+          removed.</li>
+        </ul>
+      </tp:rationale>
       <p>For protocols that support muting all streams of a given content
       separately, this object MAY also implement the <tp:dbus-ref
       namespace="ofdT.Call1.Interface">Mute</tp:dbus-ref> interface</p>
-- 
cgit v1.2.3