Summary: | Call: Support SDP Capability Negotiation (RFC 5939) | ||
---|---|---|---|
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: | normal | ||
Priority: | medium | CC: | david.laban |
Version: | git master | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | Call-later | ||
i915 platform: | i915 features: |
Description
Olivier Crête
2011-01-12 13:03:57 UTC
The fallback behaviour is well defined by the rfc (ignore the other offers), so we can implement the fallback behaviour for the undrafted Call spec without any extra effort. I'm marking this as later. To do full cap-neg support, the CM could add an optional interface for cap neg which contains the other possible configurations as lists of MediaDescriptionMaps (possibly with some compression with numbered descriptions like how the RFC does it). If the client supports it, then everything is peachy. Otherwise it gets ignored, and we're also good. I'm assuming here that clients are allowed to ignore MD interfaces they don't understand in MDOffers. We should probably specify that. Is this considered as a blocker for Call1? No, that's why the whiteboard says "Call-later" -- 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/104. |
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.