Re: [rtcweb] Feedback messages (and problem with RTP usage document)

Martin Thomson <martin.thomson@gmail.com> Wed, 15 January 2014 17:13 UTC

Return-Path: <martin.thomson@gmail.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6E591AE1B6 for <rtcweb@ietfa.amsl.com>; Wed, 15 Jan 2014 09:13:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 IhiszJMZMRQX for <rtcweb@ietfa.amsl.com>; Wed, 15 Jan 2014 09:13:16 -0800 (PST)
Received: from mail-we0-x233.google.com (mail-we0-x233.google.com [IPv6:2a00:1450:400c:c03::233]) by ietfa.amsl.com (Postfix) with ESMTP id DCDA41AE1AA for <rtcweb@ietf.org>; Wed, 15 Jan 2014 09:13:15 -0800 (PST)
Received: by mail-we0-f179.google.com with SMTP id w62so2058133wes.38 for <rtcweb@ietf.org>; Wed, 15 Jan 2014 09:13:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=hMzd8htXbf+/C/AGOPmZvLKO/5uuRJ66EFu8UPnG4pw=; b=UXcNCl37yqM5g313AaaPZxpspgcl/GkUQvRg1mTnLrd+pjvETeayn0PPe0QKq3c2AA 4G6nZtMs/HNxSSPsr5WCGupsM2DNzddRhdS5ejiiMtUbGxw0cw+lkUUQMIcY9A12fD4K CU/VIprcLABgNQ4mH8rSLNRjGL/M+1yfEtipHMvwXLH7CbD7tLddKfmII6qTitpFmrRW 7LsxbTiyqAE/rhq2VL6HzqElnr+8QH7IEtwVJkDkqhrkq99jo+iYZJcGHfDcSBHiUyhk 3q/h4pFZZDq0kNqeWSQVgSEkcvKh+N0MsFGOu6N9kh831FCUdmNb27/jz4v2kXMY1DRB 7/mA==
MIME-Version: 1.0
X-Received: by 10.194.236.9 with SMTP id uq9mr3509244wjc.31.1389805983520; Wed, 15 Jan 2014 09:13:03 -0800 (PST)
Received: by 10.227.105.132 with HTTP; Wed, 15 Jan 2014 09:13:03 -0800 (PST)
In-Reply-To: <52D63823.4070900@ericsson.com>
References: <CA+9kkMBSpDLJBBbPxgyMUi+bi3aw3D8zpSXcAvQ4koi115QqBg@mail.gmail.com> <67AD498F-4E6D-48FD-9067-B4491BE3FC16@phonefromhere.com> <52BF083C.7050308@googlemail.com> <7684BF01-C9F6-49F6-8B6A-A262EE3B08C0@phonefromhere.com> <BLU181-W70C92547315D630BF0312F93CE0@phx.gbl> <52D50957.2090202@ericsson.com> <BLU181-W5294EB8A20C840137C1D793BF0@phx.gbl> <52D63823.4070900@ericsson.com>
Date: Wed, 15 Jan 2014 09:13:03 -0800
Message-ID: <CABkgnnV36+2dFFLhjeLVRXs0A0kQM_mu2Y8KDPuTf2w=CHE3Qg@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Content-Type: text/plain; charset="UTF-8"
Cc: Bernard Aboba <bernard_aboba@hotmail.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>, Colin Perkins <csp@csperkins.org>
Subject: Re: [rtcweb] Feedback messages (and problem with RTP usage document)
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 17:13:18 -0000

On 14 January 2014 23:26, Magnus Westerlund
<magnus.westerlund@ericsson.com> wrote:
> I definitely wants more feedback on this. But, I think I am not
> disagreeing with your view. Most of the video codecs that there exist
> RTP payload formats today can use SLI and RPSI. RPSI don't make sense
> for Motion JPEG and the video/raw or video/SMPTE292M that don't use
> reference structures and SLI should be possible to use with also the RAW
> formats so that has even wider applicability.

Those formats that don't need SLI/RPSI can just ignore this guidance,
or you can add a specific exception clause if you feel magnanimous,
i.e., "The SLI and RPSI feedback messages MUST be supported and acted
upon for video streams unless the codec does not support the concept
of macroblocks or reference frames (respectively)."  Or a statement to
that effect.

Basically, SLI and RPSI make sense for the codecs we actually care
about, so let's require them.  If people want to do raw video, then
they are either smart enough to know that SLI/RPSI can't help them, or
nothing an RFC says will help fix their issues.