[Bug 28686] Call needs to be able to support RTCP XR signalling (RFC 3611)

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=28686

--- Comment #3 from David Laban <david.laban at collabora.co.uk> 2011-04-06 04:13:59 PDT ---
(In reply to comment #2)
> I think you mean
> http://git.collabora.co.uk/?p=user/alsuren/telepathy-spec.git;a=shortlog;h=refs/heads/rtcp-xr
> 
> I'm sure if having one property per type of report is good or not, since this
> is extension (and we only have the basic ones int here).

This is why I have added the "as" property "ExtendedFormats". I would prefer it
if the streaming implementation could avoid having to do SDP parsing (because
it makes life hard for other protocols).

Since ExtendedFormats is defined to always contain all sdp strings not defined
in the core XR RFC 3611 for sip, we have the following upgrade path:

1) Implement it in farstream without changing rakia
2) Implement a new property in rakia without changing farstream
("ExtendedFormats" still contains the unparsed string for backwards
compatibility)
3) Use the new property in farstream
4) Implement the new property in gabble
5) Take over the world.

We should probably define what a CM should do if a client calls Accept() with a
property that it doesn't understand though. Should Accept return a list of
invalid fully-qualified property names on error or something?

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.