[Bug 738319] rtpsession: fix Early Feedback Transmission

GStreamer (bugzilla.gnome.org) bugzilla at gnome.org
Thu Jan 22 14:55:47 PST 2015


https://bugzilla.gnome.org/show_bug.cgi?id=738319
  GStreamer | gst-plugins-good | 1.4.1

--- Comment #21 from Miguel París Díaz <mparisdiaz at gmail.com> 2015-01-22 22:55:42 UTC ---
Hello,
the point here is that the RFC might be written in a better way xD. We also had
the same feelings than you Sebastian ;).

Kurento team studied  the RFC and GStreamer code some months ago (we were
focused on the point-to-point case). We got our own conclusions, but the most
relevant is the related with this question:
How many RTCP packets can be sent between two Regular RTCP packets?
  - Following the RFC only one: the early packet (point-to-point case).
  - GStreamer allowed sent all app requests (because did not follow Part 6 (see
comment #1)

For our use cases, both cases did not match with a useful way to sent NACKs.
Why?
  - Following the RFC only a NACK can be sent.
  - GStreamer sent each NACK in a independent packet wasting a lot of bandwidth
(if the max_delay used for scheduling and set by jitterbuffer is too small).

We have our own patches (out of the RFC) that work fine for us. These changes
are in the "middle" of both last cases.

I have to say that I can have forgotten some detail, but anyway I think that we
could work together to improve GStreamer source and do some suggestion to
change the RFC if we consider it suitable ;).

Regards!!

-- 
Configure bugmail: https://bugzilla.gnome.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.


More information about the gstreamer-bugs mailing list