[telepathy-spec/master] MediaSignalling/video/h264: clients MAY lack codec caps completely

[Simon McVittie]

Gatewaying between connections requires this.
---
 spec/Channel_Interface_Media_Signalling.xml |   16 ++++++++++------
 1 files changed, 10 insertions(+), 6 deletions(-)

diff --git a/spec/Channel_Interface_Media_Signalling.xml b/spec/Channel_Interface_Media_Signalling.xml
index 0df05f9..004df5b 100644
--- a/spec/Channel_Interface_Media_Signalling.xml
+++ b/spec/Channel_Interface_Media_Signalling.xml
@@ -208,12 +208,6 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.</
             <code>video/h264</code> on StreamedMedia channels.</p>
         </tp:rationale>
 
-        <p>[FIXME: should we say the next paragraph, for completeness?]</p>
-
-        <p>Clients supporting video MUST advertise support for at least
-          one video codec, while clients supporting audio MUST advertise
-          support for at least one audio codec.</p>
-
         <p>For example, a client could advertise support for
           Speex, Theora and H264 by having three
           handler capability tokens,
@@ -223,6 +217,16 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.</
           in its <tp:dbus-ref
             namespace="org.freedesktop.Telepathy.Client.Handler">Capabilities</tp:dbus-ref>
           property.</p>
+
+        <p>Clients MAY have media signalling abilities without explicitly
+          supporting any particular codec, and connection managers SHOULD
+          support this usage.</p>
+
+        <tp:rationale>
+          <p>This is necessary to support gatewaying between two Telepathy
+            connections, in which case the available codecs might not be
+            known to the gatewaying process.</p>
+        </tp:rationale>
       </tp:docstring>
     </tp:handler-capability-token>
 
-- 
1.5.6.5