Bug 31380

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:	RESOLVED MOVED	QA Contact:	Telepathy bugs list <telepathy-bugs>
Severity:	enhancement
Priority:	medium	CC:	david.laban
Version:	git master
Hardware:	Other
OS:	All
Whiteboard:	Call-later
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.

Comment 4 GitLab Migration User 2019-12-03 20:23:02 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-spec/issues/93.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.