IETF Logo Mail Archive

Re: [Mops] Comments on draft-ietf-mops-streaming-opcons-07

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Sun, 02 January 2022 23:57 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 2834B3A1557; Sun, 2 Jan 2022 15:57:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 ynUmz_yoeBYm; Sun, 2 Jan 2022 15:56:56 -0800 (PST)
Received: from mail-vk1-xa2b.google.com (mail-vk1-xa2b.google.com [IPv6:2607:f8b0:4864:20::a2b]) (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 F41B33A1558; Sun, 2 Jan 2022 15:56:55 -0800 (PST)
Received: by mail-vk1-xa2b.google.com with SMTP id u1so17667924vkn.10; Sun, 02 Jan 2022 15:56:55 -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=HwBMinkq3858czVIo57iyDWvgYO2EC43aBqLetPlMvk=; b=VCfzpVCmDwyRRZbMlmT1EmlIfcvmoJF5+XewHvA8I9LzSMz/k9aUD12sa7myfHhDUh esUsIZW9Sk2j4Qxujfu+l4KNpOV16wZaa46UKPsLIL8liexNbpCdTwtPOoHYkCeQOG3/ CEdGiRk2DYrBqep8K+q3HyfuoeizrPRiPRYaa+yo3DcvKow0i7WoOvC4bYKDMUDPyP6E TC0naRwsdn4DrmBjFc/duthuMCSREi1zOXqlQ837cCEDECG2p6wAJVd5P9jlSGWKI34i TYMRynxoDRTA6sccRSH/2Jh50JUv4jw9TTuRIoH5nQAfoVoRkwBzX+2Pen5sioX2AtXS /HcA==
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=HwBMinkq3858czVIo57iyDWvgYO2EC43aBqLetPlMvk=; b=L1GXcvZ3QpmjNW4kiEBb69HRhhZTHXe6AEn2B+VHisijNonzRsjf1E3ZlxlBTe65sU QB3WmDnBNmZc+VPOkMO1rgzvVEL3Rp/XBOC5GelefgIJkJ43FB2BffnxcREyeKMcndNI IuN+Vw6dwo1GZYiBZnk5NPUB8sMpPpm/jKnE+N0pNlWAx8ysaijQAmhkyoLI0xK13gLR FCY0neP9k7ldQ6I5ytUYNWUEaH8cbYQfwqwEsYRY+dQfogw1lpdk/v8OIb8bkFQwyzIm IQ4qJnMBspoGbK4DjHlOFtobqo2Sq3fcwjnjQl6HTxg+qAvgTgCpaefhII+Uf2MKnAx8 TM1A==
X-Gm-Message-State: AOAM532XiInoLhSEdW+mzSHjZ0gtSqRHnE1NgDwoEyqj/44+akB6IvKo 4NFtQAtBnfqo+WxzPQedB4Z0VCUbx8CzJAKbBdjXp1brN0CBsw==
X-Google-Smtp-Source: ABdhPJz379CZtG5WORavM+hqdeeAWzp6PSOIB3qrBV9fonSblQb9wwR4Rt5QefnIOa1KNbsHNr8P/viS6nCIfBQP3hk=
X-Received: by 2002:a1f:5fcb:: with SMTP id t194mr11181662vkb.1.1641167814221; Sun, 02 Jan 2022 15:56:54 -0800 (PST)
MIME-Version: 1.0
References: <CAK=xEZMsVKbuuSv3AME2jVof5_bUKxoNKVgyu1R1CFzZUnt1qg@mail.gmail.com> <CAKKJt-ev_Az2wf3RgpdJ5AMvREb=ALaesUG0sGWEko8_dwD2DA@mail.gmail.com>
In-Reply-To: <CAKKJt-ev_Az2wf3RgpdJ5AMvREb=ALaesUG0sGWEko8_dwD2DA@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Sun, 2 Jan 2022 17:56:28 -0600
Message-ID: <CAKKJt-cb-xmTvr3BWoV=pdJj3cReVsh92uUgNJD=j12Lxa=aXg@mail.gmail.com>
To: mops-chairs@ietf.org
Cc: mops@ietf.org
Content-Type: multipart/alternative; boundary="0000000000009564fd05d4a228f3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mops/l6aTtzySEUAorr6EGbJArKWpKIA>
Subject: Re: [Mops] Comments on draft-ietf-mops-streaming-opcons-07
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: Sun, 02 Jan 2022 23:57:00 -0000

Just (finally!) following up ...

On Thu, Dec 16, 2021 at 7:32 AM Spencer Dawkins at IETF <
spencerdawkins.ietf@gmail.com> wrote:

> Dear Chairs (and, of course, co-editors),
>
> On Fri, Dec 10, 2021 at 1:05 PM Mike English <ietf@englishm.net> wrote:
>
>> Hello MOPS!
>>
>> I finally carved out some time this morning to re-read the draft
>> "Operational Considerations for Streaming Media" with fresh eyes.
>
>
(snip)


> I think this document contains many useful concepts and explanations
>
> relevant to IETF work exploring the development of new protocols or
>> protocol extensions, however, in my opinion, it suffers from a lack of
>> clarity of purpose, and I think that needs to be addressed.
>>
>> What do others think?
>>
> '
> After walking back through some diffs, it looks like we haven't
> touched the Introduction for more than editorials since
> https://www.ietf.org/rfcdiff?url2=draft-ietf-mops-streaming-opcons-04.txt,
> and the abstract hasn't changed significantly since the draft was adopted
> nearly two years ago.
>
> If it would be helpful to provide a PR that describes the document more
> clearly in the Abstract and Introduction, I'd be happy to do that, but
> don't want to wander off into the weeds if people think that's a bad idea.
>
> Please advise.
>

I've created
https://github.com/ietf-wg-mops/draft-ietf-mops-streaming-opcons/pull/94,
and asked Mike to let us know if this does a better job of describing the
scope of the document.

Best,

Spencer

v2.8.7 | Report a Bug | By Email