[rmcat] Spencer Dawkins' Yes on draft-ietf-rmcat-sbd-11: (with COMMENT)

Spencer Dawkins <spencerdawkins.ietf@gmail.com> Mon, 02 April 2018 14:49 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: rmcat@ietf.org
Delivered-To: rmcat@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E42201241FC; Mon, 2 Apr 2018 07:49:03 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-rmcat-sbd@ietf.org, Anna Brunstrom <anna.brunstrom@kau.se>, rmcat-chairs@ietf.org, anna.brunstrom@kau.se, rmcat@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.77.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152268054392.30863.14736928981691873030.idtracker@ietfa.amsl.com>
Date: Mon, 02 Apr 2018 07:49:03 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rmcat/XwNR2qlLmRvGJyOvmXFgtK-usXc>
Subject: [rmcat] Spencer Dawkins' Yes on draft-ietf-rmcat-sbd-11: (with COMMENT)
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "RTP Media Congestion Avoidance Techniques \(RMCAT\) Working Group discussion list." <rmcat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rmcat>, <mailto:rmcat-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rmcat/>
List-Post: <mailto:rmcat@ietf.org>
List-Help: <mailto:rmcat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rmcat>, <mailto:rmcat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Apr 2018 14:49:04 -0000

Spencer Dawkins has entered the following ballot position for
draft-ietf-rmcat-sbd-11: 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:


I'm somewhat confused about whether the intended scope for this mechanism is to
detect bottleneck links shared by all flows, or only what's shared by RTP media
flows. The Abstract seems clear about that, but I'm not seeing a similar
statement about scope in the Introduction, unless I'm missing it. Perhaps it's
worth repeating the statement from the Abstract in the Introduction?

I agree with the last sentence in this paragraph,

  The current Internet is unable to explicitly inform endpoints as to
   which flows share bottlenecks, so endpoints need to infer this from
   whatever information is available to them.  The mechanism described
   here currently utilizes packet loss and packet delay, but is not
   restricted to these.  As ECN becomes more prevalent it too will
   become a valuable base signal.

and I'd believe that ECN helps identify path bottlenecks, but I'm not
understanding how ECN helps identify shared bottlenecks, and I think that's the
point being made here.