IETF Logo Mail Archive

Re: [AVTCORE] Call for Framemarking implementation experience

Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com> Sun, 22 November 2020 21:24 UTC

Return-Path: <sergio.garcia.murillo@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 701D93A0DBE for <avt@ietfa.amsl.com>; Sun, 22 Nov 2020 13:24:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.187
X-Spam-Level:
X-Spam-Status: No, score=-0.187 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QOIXCtxTfQ53 for <avt@ietfa.amsl.com>; Sun, 22 Nov 2020 13:24:25 -0800 (PST)
Received: from mail-wr1-x42e.google.com (mail-wr1-x42e.google.com [IPv6:2a00:1450:4864:20::42e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 80AB93A0DBF for <avt@ietf.org>; Sun, 22 Nov 2020 13:24:25 -0800 (PST)
Received: by mail-wr1-x42e.google.com with SMTP id l1so16646705wrb.9 for <avt@ietf.org>; Sun, 22 Nov 2020 13:24:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=ijyQVLI0iSPL0yIAPDOyRHfadCpwLTcCKIAe601QRR8=; b=Y9HWE59394E0C6fR+LYIjxm36xMYVqbcC5mY8b3rR46GHCZZOGXLXiiojkTkBj191I 47N3jm/sp8Pc+dlMoBSqMTs36J+XO+Tfv3Vp+7DJrNNNovoJc5A6d/5jPFHNU3s3X9AR cC0Kr5ho2KgpY9BpIk5k09anfTu8truKlADRiUWB7ROHNYA890t8l9eG2w351TkDtbH7 waVttGChLDXZieG2tRRRYRDQLUsZO0+/TcVTtkPl3/fgf2+EGqu8MVhdmFh8q5zi7djb VCD49o9ynfZi+pUGFKj/Rj7YQm84DvOiBNF43cw3E1xlylVH3Zec8G9tPIOVkhHv7Ol3 9HFw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=ijyQVLI0iSPL0yIAPDOyRHfadCpwLTcCKIAe601QRR8=; b=I0EBDIb5idNmrlynf2V22L91Tu62M8eU3+5QL79aocoVf/5N31VXs+fObVEyE/tN1+ AcjYifFbxB/kTZkvYxZPKvj3zp/djBVXT2+2kdlCRfUtGKpgDEg2wxoINX2kOuLsExRQ Q8eMpz5ehnyaXClDmh/DcYhBY+BKwtO+wb1AsAjQ4VCOKFUhhsVVnMwA5HvNFdSYAJpx KCLGwsvEh8AkVUgPqzMYSFboqO0CdViis+XBV2CyMLvSfCsSud8FRm/ysFX0SN6/Blqu /MKSDVS2qW1pJDk033WdQXDnqhl6uWBz8Px4foxO2eH6nr5N95p4Te70otUsk/pTU6Z7 gFdg==
X-Gm-Message-State: AOAM531cYV4aHAQ4D4qYlZQkR7x7qD49VhpTUtZyRfsCgGi0oBndBFOh l2nuhYCk9bLiWKsPKexNZtLSVjls0EJfIw==
X-Google-Smtp-Source: ABdhPJwOuE1IcK300gU3BzYF+D4dzjMY3aFK/UCZosnJyyI8xNo7PcCZFVswk+8TKe0MZ0ZE9tZubg==
X-Received: by 2002:a5d:4703:: with SMTP id y3mr28186021wrq.416.1606080263653; Sun, 22 Nov 2020 13:24:23 -0800 (PST)
Received: from [192.168.0.11] (79.108.125.160.dyn.user.ono.com. [79.108.125.160]) by smtp.googlemail.com with ESMTPSA id e5sm14555305wrs.84.2020.11.22.13.24.22 for <avt@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 22 Nov 2020 13:24:23 -0800 (PST)
To: avt@ietf.org
References: <E0140570-4164-43C9-9202-2C3C85B8AA69@gmail.com>
From: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
Message-ID: <aa038039-18f3-a662-b934-8438d639161e@gmail.com>
Date: Sun, 22 Nov 2020 22:24:22 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0
MIME-Version: 1.0
In-Reply-To: <E0140570-4164-43C9-9202-2C3C85B8AA69@gmail.com>
Content-Type: multipart/alternative; boundary="------------A144B472F8615DB64E610CA6"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/aPDA76O1UOc2UtFmxW6Gq8eFnwg>
Subject: Re: [AVTCORE] Call for Framemarking implementation experience
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Nov 2020 21:24:31 -0000

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://codereview.webrtc.org/2954503002/>
> https://bugs.chromium.org/p/webrtc/issues/detail?id=7765 
> <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 
> <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 
> <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 Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt

v2.23.0 | Report a Bug | By Email