[rtcweb] Ben Campbell's Yes on draft-ietf-rtcweb-fec-08: (with COMMENT)

Ben Campbell <ben@nostrum.com> Wed, 20 February 2019 17:56 UTC

Return-Path: <ben@nostrum.com>
X-Original-To: rtcweb@ietf.org
Delivered-To: rtcweb@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 453A0130DD3; Wed, 20 Feb 2019 09:56:19 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Ben Campbell <ben@nostrum.com>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-rtcweb-fec@ietf.org, Ted Hardie <ted.ietf@gmail.com>, rtcweb-chairs@ietf.org, ted.ietf@gmail.com, rtcweb@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.91.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <155068537927.31452.11334457138991637471.idtracker@ietfa.amsl.com>
Date: Wed, 20 Feb 2019 09:56:19 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/2iiRwaK0Ig8C068pvJU6Rca7PJk>
Subject: [rtcweb] Ben Campbell's Yes on draft-ietf-rtcweb-fec-08: (with COMMENT)
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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, 20 Feb 2019 17:56:19 -0000

Ben Campbell has entered the following ballot position for
draft-ietf-rtcweb-fec-08: Yes

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-rtcweb-fec/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thanks for this effort. I am balloting "yes", but have some minor comments:

§8:
- "Given this, WebRTC implementations SHOULD consider using RTX or
flexfec retransmissions instead of FEC when RTT is low,"

"consider" seems vague for a normative requirement. Can you describe concrete
requirements? Otherwise I suggest descriptive language.

Can you give guidance on what RTT would be reasonable to consider as "low"?

- "Note that when probing bandwidth, i.e., speculatively sending extra
data to determine if additional link capacity exists, FEC SHOULD be
used in all cases."

I assume the point of this is the redundant FEC data should _be_ that extra
data. But one could read this to mean that, if you are already sending extra
data, you should also use FEC.

§9, 2nd paragraph:

I'm by no means an expert in this, and leave it to the crypto experts to know
if this matters, but does the additional redundancy of FEC have any impact on
SRTP encryption?