From #24936: For ICE->rawudp fallback, we probably want to have an API "ForcedRemoteCandates" or something, that will overrides the regular remote candidates. That API should be the only one called in the case of rawudp (ie.. in rawudp mode, the ICE candidates are ignored). In the Farstream api break, I plan to have rawudp implement only force_remote_candidates() and not add_remote_candidates(), the second one will be only for ICE and ICE-like protocols. Yes, every ICE implementation needs to support rawudp fallback, otherwise its not compliant (ie, its not ICE). Also, don't confuse with SelectedCandidate, this is to tell other side how the ICE negotiation has concluded (it prevents a race in the ICE negotiation). So its unrelated to rawudp fallback.
-- 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/72.
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.