|Summary:||Call: Contents with FEC repair data|
|Product:||Telepathy||Reporter:||Olivier Crête <olivier.crete>|
|Component:||tp-spec||Assignee:||Telepathy bugs list <telepathy-bugs>|
|Status:||NEW ---||QA Contact:||Telepathy bugs list <telepathy-bugs>|
|i915 platform:||i915 features:|
Description Olivier Crête 2010-11-04 05:41:29 UTC
There are some RFCs (RFC 5109 and the fecframe draft) which allow (force) the FEC data to be carried in its own m= line (ie Content). We should keep that in mind while thinking about the design... That said, this also means having a way to group contents. We should make sure Call is extensible in that direction.
Comment 1 David Laban 2011-04-04 04:27:57 UTC
The Content as viewed by the UI would not exactly map onto a singe m= section in this case. This could be solved using a separate interface on the Content a la C.I.MediaMixing (proposed for #28718 but left as "later").
Comment 2 Guillaume Desmottes 2012-02-16 09:19:19 UTC
Is this considered as a blocker for Call1?
Comment 3 Olivier Crête 2012-02-16 09:42:06 UTC
No, it's not a regression.. And we can add it as a further interface on MD later.