On Mon, 27 Nov 2023 at 12:48, Nicolas George wrote:
> Michael Riedl (12023-11-27):
> > Regardless, this will only test the implementation against itself. If
> that makes
> > sense and sounds reasonable, I will add the server support to this patch
> series.
>
> Thanks. It will not be enough in a p
Michael Riedl (12023-11-27):
> Regardless, this will only test the implementation against itself. If that
> makes
> sense and sounds reasonable, I will add the server support to this patch
> series.
Thanks. It will not be enough in a perfect world, but it still is a very
good start and much bett
On 11/15/23 22:45, Michael Niedermayer wrote:
> On Tue, Nov 14, 2023 at 01:59:48PM +0100, Michael Riedl wrote:
>> On 11/14/23 11:05, Tomas Härdin wrote:
>>> This patchset is missing tests. I know that we for some reason don't
>>> really have tests for protocols, but I feel the issue is worthwhile t
On Tue, Nov 14, 2023 at 01:59:48PM +0100, Michael Riedl wrote:
> On 11/14/23 11:05, Tomas Härdin wrote:
> > This patchset is missing tests. I know that we for some reason don't
> > really have tests for protocols, but I feel the issue is worthwhile to
> > bring up. I've worked a bit with WebRTC rec
tis 2023-11-14 klockan 13:59 +0100 skrev Michael Riedl:
> Another option is an external project for WebRTC testing, but the
> challenge is
> keeping it maintained and compatible with changes in implementations.
Perhaps there are funds to raise for such an effort? I can imagine
Google et al have an
On 11/14/23 11:05, Tomas Härdin wrote:
> This patchset is missing tests. I know that we for some reason don't
> really have tests for protocols, but I feel the issue is worthwhile to
> bring up. I've worked a bit with WebRTC recently and it's fiddly, so
> it'd be nice to have some automated thing t
This patchset is missing tests. I know that we for some reason don't
really have tests for protocols, but I feel the issue is worthwhile to
bring up. I've worked a bit with WebRTC recently and it's fiddly, so
it'd be nice to have some automated thing that keeps track of which
WebRTC implementations
This patch series adds support for WHIP and WHEP (WebRTC-HTTP ingestion protocol
and WebRTC-HTTP egress protocol). It supersedes the previous patch series. Thank
you all for your feedback and suggestions!
The WHIP and WHEP are defined in the following draft RFCs:
- WHIP: https://datatracker.ietf.o
