Re: [Mops] Comments on draft-ietf-mops-streaming-opscons-08

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Tue, 01 March 2022 02:47 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: mops@ietfa.amsl.com
Delivered-To: mops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B61963A1815 for <mops@ietfa.amsl.com>; Mon, 28 Feb 2022 18:47:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 Kl_FA7-I8VQH for <mops@ietfa.amsl.com>; Mon, 28 Feb 2022 18:47:06 -0800 (PST)
Received: from mail-vs1-xe31.google.com (mail-vs1-xe31.google.com [IPv6:2607:f8b0:4864:20::e31]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 21F8E3A0E03 for <mops@ietf.org>; Mon, 28 Feb 2022 18:47:06 -0800 (PST)
Received: by mail-vs1-xe31.google.com with SMTP id u10so15067300vsu.13 for <mops@ietf.org>; Mon, 28 Feb 2022 18:47:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=486B+RvUE9KW/Ci+vXx6arr85hqhmlQp8smXRVb+Ljg=; b=BMK8Ujdzwx8dLKE76Lgo5Zl8vo6zJCFSNEF2Wch+JioO5ZDvIKWqBWT/4gPsWV2Sbp /UhU0PKGshPgKmmIOPi5+hbi6ww5K9dlaqpFVlvWoAaXLzNDXImptbN3VdUqOlJtH8sZ oNnvnsUoGKtuzRJrX/qr+h10Ro6o3JCIFV4Hc9vFTm6JjSGcnpkwpJUJAqg3tbkKLEox teImgYYb8oq7zAZ7P2KjlcbWE66Xag3yi8g6LgesO0TbjWumAsiF0WkeBGsKbzEkcvWi BePqCdtNbVfeKZ+vUnWsEC1pwxJ909eOeautVVhTJ21GHjOOWiX0KHgflGhtfjYKEKWx hGjA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=486B+RvUE9KW/Ci+vXx6arr85hqhmlQp8smXRVb+Ljg=; b=6ZhH2U7InvzUsivBH3KPMqWQXyZTc+EtrEM8fAFyUgJ1ixGXqp+r17dX2UlJLdYy1/ IIl3dI9bdC3pRbHkLF5ZsXMGz6vkF4ZD+rXPPu/X7w23dOW8TL0Mdf+Hs8O+yzFNZtze ZK1gVZrS8AcmXSNK0e7aPmbi1YetMy9pcvzgYcSUhBqEojfBJWn3N85cUcYphZBHvIg1 XYnG16lGa7anKq0IEGkLp+8FtXnHiz4SAEGR+MiJdxsM+Pp//IC2AhlTd5wwjMho2C2Q AdRpG2rzVK1GMnsAa14QDkXR5Mg4qngkGnnoLhX39v9zI95f476KHNXFHK5J3GzN7nmy su0A==
X-Gm-Message-State: AOAM533YIKtbKSYVlmW1ZxV8SwpUhdh3mNbBwpg1FqKYl27bMmObGyM7 /uTPIk9XfoJmBtmUAJHOaHNxgcwoXWuW0sQjMZd80OQQ
X-Google-Smtp-Source: ABdhPJyRxKF//n5jlnMI/ahwl/GTJEG/h7QFluS6K/suKvK/xfNkqBLqgKLU7gNNhid0VTEjvBVuVCse7a1cTTqgFZQ=
X-Received: by 2002:a05:6102:3eca:b0:31b:bab5:b42d with SMTP id n10-20020a0561023eca00b0031bbab5b42dmr9836792vsv.43.1646102824738; Mon, 28 Feb 2022 18:47:04 -0800 (PST)
MIME-Version: 1.0
References: <CA+EbDtB44oeMY3AhkCvkiMYKhrRg6TTbVqkrBWMRDsZpC5_PgA@mail.gmail.com>
In-Reply-To: <CA+EbDtB44oeMY3AhkCvkiMYKhrRg6TTbVqkrBWMRDsZpC5_PgA@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Mon, 28 Feb 2022 20:46:38 -0600
Message-ID: <CAKKJt-fJMWOBoDeh8KiERWFdrxNNRMA1OHG6wqiOMiiQ6B01Aw@mail.gmail.com>
To: "Mishra, Sanjay" <sanjay.mishra@verizon.com>
Cc: jakeholland.net@gmail.com, "Ali C. Begen" <ali.begen@networked.media>, mops@ietf.org
Content-Type: multipart/alternative; boundary="00000000000021e2aa05d91f2ee3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mops/CY8qF0tXKvJCYVxaG86dsF8MN4U>
Subject: Re: [Mops] Comments on draft-ietf-mops-streaming-opscons-08
X-BeenThere: mops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: Tue, 01 Mar 2022 02:47:11 -0000

Hi, Sanjay,

On Mon, Feb 28, 2022 at 6:03 PM Mishra, Sanjay <sanjay.mishra@verizon.com>
wrote:

> Opscon authors - I have submitted a shepherd write up for the document
> earlier today.
>

Thanks for this.


> I have two follow up questions.
>
> 1. I am reconfirming that there are no IPR disclosures that should be made
> but have not been made. But, please confirm once again.
>

No IPR from me.


> 2. I have some minor knits in the document. See below:
>

I'm working on a PR now :-)

Best,

Spencer


> Comments:
>
> Pg 6: remove "." between TCP and which.
> Much of the focus of this document is on reliable media using HTTP
> over TCP. which is widely used..."
>
> Awkward transition between comma and start of another example.
>
> "wide range of operating systems, is also used in a
> wide variety of other applications, has been demonstrated to provide
> acceptable performance over the open Internet, includes state of the
> art standardized security mechanisms, and can make use of already deployed
> caching infrastructure"
>
> Consider rephrasing the start of the sentence, such as "This document also
> briefly discusses..." (or the document also briefly touches on...)
> "Some mentions of unreliable media delivery using RTP and other UDPbased
> protocols appear in..."
>
> it's -> it is (other places in the document)
>
> sec 3.4 -> re-use of "popular" twice in a sentence
> "One popular example is when popular streaming content..."
> May be re-state -> "one relevant example is when popular streaming
> content..."
>
> sec 3.5 ->  "users consume more video and videos at
> higher bitrates" reword?
> "users consume more videos and at a higher bit rate"?
>
> sec 3.6 -> '"throttle" these transfers, to mitigate the load..." Comma not
> needed
>
> sec 4.2 -> Reference to draft-pantos-hls-rfc8216bis will need update as
> this is not an RFC yet
>
> "While an LL-HLS client retrieves each chunk with a separate HTTP GET
> request, an LL-DASH client ..." replace "an" -> "a"
>
> sec 5.4 -> "Ads" -> prior to use of acronym suggest defining it when first
> referencing the word advertisements.
>
> sec 6.3 -> missing "an" before increasing -> "As noted in Section 6.2,
> there is increasing interest...."
>
> sec 7 -> comma at the end of the sentence can be removed -> "when senders
> and receivers store it,"
>
> Thank you
> Sanjay
>
>