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

Magnus Westerlund <magnus.westerlund@ericsson.com> Wed, 15 January 2014 07:28 UTC

Return-Path: <magnus.westerlund@ericsson.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 EC0611AE317 for <rtcweb@ietfa.amsl.com>; Tue, 14 Jan 2014 23:28:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.24
X-Spam-Level:
X-Spam-Status: No, score=-1.24 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001] autolearn=no
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 mMHUz0gYkV2A for <rtcweb@ietfa.amsl.com>; Tue, 14 Jan 2014 23:28:34 -0800 (PST)
Received: from sessmg20.mgmt.ericsson.se (sessmg20.ericsson.net [193.180.251.50]) by ietfa.amsl.com (Postfix) with ESMTP id 2CB1F1AE314 for <rtcweb@ietf.org>; Tue, 14 Jan 2014 23:28:33 -0800 (PST)
X-AuditID: c1b4fb32-b7f2b8e0000073bf-1d-52d63895decf
Received: from ESESSHC012.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg20.mgmt.ericsson.se (Symantec Mail Security) with SMTP id 66.83.29631.59836D25; Wed, 15 Jan 2014 08:28:21 +0100 (CET)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.56) with Microsoft SMTP Server id 14.2.347.0; Wed, 15 Jan 2014 08:26:39 +0100
Message-ID: <52D63823.4070900@ericsson.com>
Date: Wed, 15 Jan 2014 08:26:27 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>, Tim Panton <tim@phonefromhere.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>
In-Reply-To: <BLU181-W5294EB8A20C840137C1D793BF0@phx.gbl>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrCLMWRmVeSWpSXmKPExsUyM+Jvje5Ui2tBBlemyFvsX3KZ2WL5yxOM Fmv/tbNbXNx+i9GBxWPa/ftsHo97zrB5LFnyk8ljyaRGtgCWKC6blNSczLLUIn27BK6MNQen MRZ8E6rYfPE/SwPjCv4uRk4OCQETiRO/e9kgbDGJC/fWA9lcHEICJxglem59gXKWM0rsb/zA 0sXIwcEroC1xpkUNpIFFQFXi0ekLrCA2m4CFxM0fjWCDRAWCJW5Ne8AOYvMKCEqcnPmEBcQW AYovf/KFEcRmFvCSePjtDFi9sICvxKT3F8HmCAncZ5KY+dsQZBWngKXEhYkmIKaEgLhET2MQ RKeexJSrLVBT5CWat85mhujUlmho6mCdwCg0C8niWUhaZiFpWcDIvIpRsji1uDg33chALzc9 t0QvtSgzubg4P0+vOHUTIzDkD275bbSD8eQe+0OM0hwsSuK811lrgoQE0hNLUrNTUwtSi+KL SnNSiw8xMnFwSjUwlixP+LZNK8104163K3WndtrO+en+4MrRqSXGWccLtRlrO1IcvhxzarGb oneDe/7xf+oWayf8U+iInrxUTXriba4/ZdLbs24pLpsrNLHUc01Y28MJ56zMLuQd/Fd2/uSh tm3mNe9vOr+c/LZJ9L/2uzTJfdMqruicbxVf3FgtHhu4Ovr1hxDuNiWW4oxEQy3mouJEAL6O 0wVHAgAA
Cc: "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 07:28:36 -0000

On 2014-01-14 17:55, Bernard Aboba wrote:
> I'd prefer choice A.  It makes sense to me for all fb message
> recommendations to be handled within the same document.  Right now RPSI
> and SLI are discussed in the RTP usage document, but are OPTIONAL, 
> Since there will be substantial benefits in terms of interoperability, 
> I'd like to see commonly used fb messages RECOMMENDED for implementation
> (since implementation is not required in the codec documents a MUST is
> probably too much).

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.

>  
> It might also be appropriate to include a general statement that WebRTC
> implementations supporting a particular video codec need to conform to
> the requirements of the codec specification with respect to fb messages. 

This, I don't see a problem with such a statement. Do you have a text
proposal?

>  
> I am indifferent to whether the RTP usage document includes a reference
> to the VP8 or H265 payload specifications or not (I'd suggest that
> either reference be non-normative). RFC 6184 does not have a section on
> fb messages similar to the ones in the VP8 and H265 payload specs, so
> that will not be of much help.

I would like to avoid these and let these be part of the
draft-ietf-rtcweb-audio and draft-ietf-rtcweb-video documents. The
intention with this structure was to enable piece wise revisioning if
required without needing to open up questions of all the media formats
at the same time. And that RTP usage changes would not require having to
deal with media format changes unless required.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------