Re: [AVTCORE] Call for Framemarking implementation experience

Sergio --

Did the P/U bit issue in VP9 render framemarking completely unusable with
VP9?  Or were there some set of use cases (e.g. simulcast-only, temporal
scalability only, etc.) in which it still could be useful?  If the P/U
issue had been solved, would the list of VP9 use cases be expanded?

Did you implement support for H.264/AVC with temporal scalability based on
framemarking?  If so, did you consider it usable for that purpose?

Any implementation experience with VP8?

On Sun, Nov 22, 2020 at 1:24 PM Sergio Garcia Murillo <
sergio.garcia.murillo@gmail.com> wrote:

> I implemented an slightly modified version of an earlier draft of the
> Framemarking on both my SFU and a custom libwebrtc for supporting VP9 SVC
> with perc-lite e2ee:
>
> https://codereview.webrtc.org/2954503002/
>
> https://github.com/murillo128/draft-berger-avtext-framemarking/commit/35cdb229108251f12bc1cdf77909df83a51d3994
>
> I don't think we ever got to solve the question about the P/U bits on the
> vp9 payload draft:
>
> https://mailarchive.ietf.org/arch/msg/avtext/ntfDsjMJjuruDPenp6-w0k0__Rk/
>
> I plan to remove the framemarking code soon as it is no longer needed for
> SFrame with standard VP9 packetization and not supported by libwebrtc for
> other codecs neither (h264 with temporal scalability was a nice feature
> though).
>
> Best regards
> Sergio
>
>
> On 22/11/2020 16:24, Bernard Aboba wrote:
>
> During WGLC, questions were raised about implementation experience with
> draft-IETF-AVTEXT-framemarking. If you have implemented the specification,
> please respond to this thread with your observations.
>
> Some notes relating to WebRTC.org:
>
> Frame marking support (-07) appears to have been first added to the
> WebRTC.org implementation in 2017:
> https://codereview.webrtc.org/2954503002/
> https://bugs.chromium.org/p/webrtc/issues/detail?id=7765
>
> The commits refer appears to support temporal scalability with H.264/AVC.
>
> In 2019 support was added to the H.264 receiver in Chrome M76:
> https://groups.google.com/g/discuss-webrtc/c/Y7TIuNbgP8M/m/UoXP-RuxAwAJ
>
> In March 2020, Issue 7765 on support for framemarking was closed as ‘won’t
> fix’.
>
> A security issue was found in April 8, 2020:
> https://bugs.chromium.org/p/chromium/issues/detail?id=1042933
>
> Framemarking support was removed from WebRTC.org in June, 2020 and from
> Chrome starting in M85:
> http://bugs.webrtc.org/11637
>
>
>
>
>
>
> _______________________________________________
> Audio/Video Transport Core Maintenanceavt@ietf.orghttps://www.ietf.org/mailman/listinfo/avt
>
>
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
>