[Mops] Opsdir last call review of draft-ietf-mops-streaming-opcons-10
Linda Dunbar via Datatracker <noreply@ietf.org> Sat, 07 May 2022 03:54 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: mops@ietf.org
Delivered-To: mops@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 71853C159499; Fri, 6 May 2022 20:54:36 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Linda Dunbar via Datatracker <noreply@ietf.org>
To: ops-dir@ietf.org
Cc: draft-ietf-mops-streaming-opcons.all@ietf.org, last-call@ietf.org, mops@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 8.1.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <165189567644.21964.10604921190599956677@ietfa.amsl.com>
Reply-To: Linda Dunbar <linda.dunbar@futurewei.com>
Date: Fri, 06 May 2022 20:54:36 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mops/fC8-l5curUXlkkQd5nOibajBF04>
Subject: [Mops] Opsdir last call review of draft-ietf-mops-streaming-opcons-10
X-BeenThere: mops@ietf.org
X-Mailman-Version: 2.1.34
List-Id: Media OPerationS <mops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mops>, <mailto:mops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mops/>
List-Post: <mailto:mops@ietf.org>
List-Help: <mailto:mops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mops>, <mailto:mops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 07 May 2022 03:54:36 -0000
Reviewer: Linda Dunbar Review result: Has Nits I have reviewed this document as part of the Ops area directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments were written primarily for the benefit of the Ops area directors. Document editors and WG chairs should treat these comments just like any other last-call comments. Summary: the document describes many issues associated with streaming video. The description is very clear and it is very useful to have those problems documented. Some questions for the description of Section 3.2 The first bullet describes the Media server's adjusting bandwidth in responding to the application-level feedback that indicates a bottleneck link somewhere along the path. Question 1: is the "Link" in the sentence referring to the physical link between two routers along the path? How can application know the all the links along the path from the server to itself? let alone detecting which link is the bottleneck? The second bullet describes the Media servers adjusting bandwidth by implementing some forms of congestion control that probe for bandwidth. The conclusion says that the QoE is poorer when the two methods don't coordinate. Question 2: Both methods are implemented on the Media server, they should coordinate by nature, aren't they? Thank you very much, Linda Dunbar
- [Mops] Opsdir last call review of draft-ietf-mops… Linda Dunbar via Datatracker
- Re: [Mops] Opsdir last call review of draft-ietf-… Spencer Dawkins at IETF
- Re: [Mops] Opsdir last call review of draft-ietf-… Linda Dunbar
- Re: [Mops] Opsdir last call review of draft-ietf-… Spencer Dawkins at IETF