
From nobody Sun Jan  2 15:57:01 2022
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

--0000000000009564fd05d4a228f3
Content-Type: text/plain; charset="UTF-8"

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

--0000000000009564fd05d4a228f3
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">Just (finally!) following=C2=A0up ...=C2=
=A0</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_att=
r">On Thu, Dec 16, 2021 at 7:32 AM Spencer Dawkins at IETF &lt;<a href=3D"m=
ailto:spencerdawkins.ietf@gmail.com">spencerdawkins.ietf@gmail.com</a>&gt; =
wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0=
px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=
=3D"ltr"><div dir=3D"ltr">Dear Chairs (and, of course, co-editors),=C2=A0</=
div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On=
 Fri, Dec 10, 2021 at 1:05 PM Mike English &lt;<a href=3D"mailto:ietf@engli=
shm.net" target=3D"_blank">ietf@englishm.net</a>&gt; wrote:<br></div><block=
quote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1=
px solid rgb(204,204,204);padding-left:1ex">Hello MOPS!<br>
<br>
I finally carved out some time this morning to re-read the draft<br>
&quot;Operational Considerations for Streaming Media&quot; with fresh eyes.=
</blockquote></div></div></blockquote><div><br></div><div>(snip)=C2=A0</div=
><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px=
 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div di=
r=3D"ltr"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddin=
g-left:1ex">I think this document contains many useful concepts and explana=
tions</blockquote></div></div></blockquote><blockquote class=3D"gmail_quote=
" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);=
padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_quote"><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px soli=
d rgb(204,204,204);padding-left:1ex">
relevant to IETF work exploring the development of new protocols or<br>
protocol extensions, however, in my opinion, it suffers from a lack of<br>
clarity of purpose, and I think that needs to be addressed.<br>
<br>
What do others think?<br></blockquote><div>&#39;</div><div>After walking ba=
ck through some diffs, it looks like we haven&#39;t touched=C2=A0the Introd=
uction for more than editorials since=C2=A0<a href=3D"https://www.ietf.org/=
rfcdiff?url2=3Ddraft-ietf-mops-streaming-opcons-04.txt" target=3D"_blank">h=
ttps://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mops-streaming-opcons-04.txt<=
/a>, and the abstract hasn&#39;t changed significantly since the draft was =
adopted nearly two years ago.=C2=A0</div><div><br></div><div>If it would be=
 helpful to provide a PR that describes the document more clearly in the Ab=
stract and Introduction, I&#39;d be happy to do that, but don&#39;t want to=
 wander off into the weeds if people think that&#39;s a bad idea.=C2=A0</di=
v><div><br></div><div>Please advise.</div></div></div></blockquote><div><br=
></div><div>I&#39;ve created=C2=A0<a href=3D"https://github.com/ietf-wg-mop=
s/draft-ietf-mops-streaming-opcons/pull/94">https://github.com/ietf-wg-mops=
/draft-ietf-mops-streaming-opcons/pull/94</a>, and asked Mike to let us kno=
w if this does a better job of describing the scope of the document.=C2=A0<=
/div><div><br></div><div>Best,</div><div><br></div><div>Spencer=C2=A0</div>=
</div></div>

--0000000000009564fd05d4a228f3--


From nobody Fri Jan  7 04:16:59 2022
Return-Path: <Renan.Krishna@interdigital.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 53A503A1A06 for <mops@ietfa.amsl.com>; Fri,  7 Jan 2022 04:16:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 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, HTML_MESSAGE=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=interdigital.com header.b=AvvkHsOA; dkim=pass (1024-bit key) header.d=interdigital.onmicrosoft.com header.b=LyGgLoSP
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 bHf4DC8upmVK for <mops@ietfa.amsl.com>; Fri,  7 Jan 2022 04:16:52 -0800 (PST)
Received: from esa2.hc3352-98.iphmx.com (esa2.hc3352-98.iphmx.com [216.71.148.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C1F4F3A1A04 for <mops@ietf.org>; Fri,  7 Jan 2022 04:16:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=interdigital.com; i=@interdigital.com; q=dns/txt; s=esa; t=1641557812; x=1673093812; h=from:to:cc:subject:date:message-id:mime-version; bh=GOlVfRaTYOGbAiH20MIphuRcNiGD8Mfi2sO/uIpfsVs=; b=AvvkHsOA19xGHYFnr1rDnkBzAxAhtj6+fSqRUbk7McCM3PFNo4PQnYss cCtUv/AIuXXOPHakpJh6ok3unJ9LGIYd4U35WL97oQP3GKwMDeCt2gswa NPSAT0EZmW9PnEToj8F4ruB3qZsi+9mwm8lQay/s2wRm2DWCdLYLCHPf1 Vc6fgoDUUOvvpf0xVcRXIKxfBaISPmVF3bQm+z6ugSq1MNvsMMzYGjJdp BnQ+5Aig8zoheRGBs6EdJtOUA9g4WSNf6LJg8sCMKHV362IheCVct3SDI AIG5ynJmJy87oRjtHgItBj/cuGjKcUwaHpdrWMQvtwyHwyeXqJUktyEkc Q==;
Received: from mail-dm6nam11lp2176.outbound.protection.outlook.com (HELO NAM11-DM6-obe.outbound.protection.outlook.com) ([104.47.57.176]) by ob1.hc3352-98.iphmx.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 07 Jan 2022 07:16:51 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=OsY85Vxaeej/V3aLtMCOTno+Od7JmizRgj3o/NmqYU07dbYH7XAmEciPkcywjuPo0nFUxUOZDMJxfFYVCcBcmzXEAzRSygI5M6Ud5/fI3ytfmsq3wFf1K0Xa6XUCLeyK1AyJdbpgbEqV/K3MQSxzz9q7YVEl2vzI5N+TKSDDq9xRYu2XF2OYK4DajsRdeQWw0WZQ66Qu8ZLQff+Wybs3Vg2N8cN1oOLxgFU/DaoG3iCEt7aSDnDYXFXF+xB2thhMIVodlmZHgZbtA4UMvQDPdshiHpgWOUn2l88AYLWAWCyo1mj+lPpDxvecCLGqvPl6VyvSRkyOJCYSihsFdOqWPg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=xy2TOB6TUWozYh3zztGgCWNXCbW2ZCdnsSMzMGUiPa0=; b=ajEWvM68d8dAFImNgfbOkhqDRLBmYPWEgPmqXq6tQusaeOkupFy+Tf8UDZb23UkIQPtx8T00TTP5d0svQ4fLfYSTBJOKp1dmg0q8Ci2hx/UJOKxV+whFUsQ46s2REp7NmXfdbfyaIouIP47Te52NHt8YpLuWvMf9BE1/2e9pQqIRxraM8O+bRKqytKlcqlkhJGZw/DpBRsiKfoeCpAu+9NsiWAWCRE1jvNr1w5JrjfR+VtAMsLWne6Aa9hqRj5oOfVTG0mkGQ8JgMaxGLIdbiiEsSq6BruNq1BHnngLiXRq1KTHI0kP2YeuQh7RjVMY/JTEZ2LpIMirqI79fgtQOWA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=interdigital.com; dmarc=pass action=none header.from=interdigital.com; dkim=pass header.d=interdigital.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=interdigital.onmicrosoft.com; s=selector2-interdigital-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=xy2TOB6TUWozYh3zztGgCWNXCbW2ZCdnsSMzMGUiPa0=; b=LyGgLoSPTqJaxgL3GRyInDZPrlKT/N+aBmkWSU3L8MiQrZH9uVHWSrnZKEJAXm2hrBfWkeFsRTWKqu/lPZe4RBX6jwsWuSEFiotVZ9DBjUVZBntyqWZricAVaAKJ+wIP0CNnSZPGD06HCAIMh/grjftmUTkt6gW398hbVhqav4Y=
Received: from DM6PR10MB4316.namprd10.prod.outlook.com (2603:10b6:5:21d::23) by DM5PR10MB1244.namprd10.prod.outlook.com (2603:10b6:4:5::23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4867.11; Fri, 7 Jan 2022 12:16:47 +0000
Received: from DM6PR10MB4316.namprd10.prod.outlook.com ([fe80::c80d:7814:d47e:56ec]) by DM6PR10MB4316.namprd10.prod.outlook.com ([fe80::c80d:7814:d47e:56ec%5]) with mapi id 15.20.4867.009; Fri, 7 Jan 2022 12:16:46 +0000
From: Renan Krishna <Renan.Krishna@InterDigital.com>
To: "mops@ietf.org" <mops@ietf.org>
CC: Leslie Daigle <ldaigle@thinkingcat.com>, Kyle Rose <krose@krose.org>
Thread-Topic: My comments on draft-ietf-mops-streaming-opcons-07
Thread-Index: AdgDv7vVOulo4Eu9TwSmjJOYFYWwkw==
Date: Fri, 7 Jan 2022 12:16:46 +0000
Message-ID: <DM6PR10MB43168B871B59F701E2818E6D974D9@DM6PR10MB4316.namprd10.prod.outlook.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=InterDigital.com;
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 4d0480ae-439d-4667-8a56-08d9d1d79353
x-ms-traffictypediagnostic: DM5PR10MB1244:EE_
x-microsoft-antispam-prvs: <DM5PR10MB12444971356ADD536C65D3CF974D9@DM5PR10MB1244.namprd10.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 9vVWd9PZXyYW6kdfnPM3E0anYiXDUQwzRhl01DsTP112sgUJufNAjDmQ1KgLrj9ZsTOiJU4LVmjw/ewrR7JXkVl64fuUP8SwMDVhXeHsuO6Y/XkjhZzuXYXDnMmGuwyvPw2Q+k1JQnoNebkBIr5up1SNvGeURUkiMtMLbKbuU+PKrn9bzZYqbEE2/1KeN8TG9XPUCaZGnkvRjifkShplgbn67VG+ibBAGaw+GEC1WFnFcwaQj8XmcEqTGLYNDVCJfYPErmuS9r2AS/MUHI8wIdl2FbMRZHFrm+A0ORKDymFzja0wvc93PvL/IawKBEHa76thbKYZ9OknmBwXASZGsrrcVwgihyIenyYqmkbezlNO1wS3hUYrrZD/uak7l6k2VmBTPNZm8CijCIS0J8OolJk0BYJo5yQ2jU0DHKwpcVgjlI+vgZWNtYzDjgVheM81QCWy60XhLztnv+HJMPi0/EP+F+gaaJupYvwXDxU21FvJPnWun0R2Q8E8YzmwcEg14/6bmNtgki3L26SvLbqo4SY4TspQUkFjD943pjkWTitnDJrxcanMhn3RYb+1eNs5kUuf5GUnUplQBXj/JP0hleA+XiXn3pRrw7wt4WvB/SEGRLlDZMplZyQG4EK7cUctk5++nOkiUOb3Spqne1UlsMIrLX5KGl3BxXlxac/mRZ2muF4LOJ+F5z1nLE4ycaouhdkzOaM4Rs0YYHGyhTygxPAWHeFlRwrV6WmxQk19yi0=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:DM6PR10MB4316.namprd10.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(366004)(66946007)(76116006)(52536014)(2906002)(122000001)(64756008)(66556008)(66446008)(38100700002)(66476007)(55016003)(33656002)(508600001)(5660300002)(8936002)(7696005)(86362001)(186003)(26005)(8676002)(38070700005)(6506007)(9686003)(9326002)(54906003)(71200400001)(316002)(6916009)(107886003)(4326008)(85282002); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: =?us-ascii?Q?wOARnKvg6Kmv4cUBu99WJRkqBgZwV6hOrzdNidhbhZdaYzdTs2bHHkqY62ES?= =?us-ascii?Q?EMPyPZvlphYcS/OjzRzPvHp0kslnVhljUDLzEW5mFhy/JUh141gYARCkkd2Q?= =?us-ascii?Q?q7/E957KppADx5feMeLonBjgdd7jxe7w8WtXbD9oFzggSw1+J75iTMRw4jLj?= =?us-ascii?Q?DxFl0axHSSL/ZM7OIGHzvm+bWNZXbo4WlNdeP5sHIaXCyzz2pDHXy6G7Lo/S?= =?us-ascii?Q?qc3ANvSOVQrRt+8bbHNTIleYqW/5cOZl0+Aq5HG+GqFTjAbhxrDuNU9y2f/b?= =?us-ascii?Q?ubvCyDytiCeojVuyFe63ZAYOUHvFjrjtl6jJ3GOLcwcRM+LtLNYvjiEvQYh9?= =?us-ascii?Q?g1Tr3a5shyYHTDiaCBTUe5m5mH4m915aXIdfjaqMzxsKN6+6nnVT35FCHEzC?= =?us-ascii?Q?IsPN6pZrQ7wCtOX0VjdFQUAoYY3M4AVOSORkw6+nUo56aQV0CXX4UQiSYZJw?= =?us-ascii?Q?bjNqB3jpFEFC36nHKH/NVv6XTreFelXk/kkbFEb2DlxquTVtcmVsd4DTzQzh?= =?us-ascii?Q?ORqxYyyne54Bu1Vs4lOogubM/d7bcYK3jKUBA7hXwDioJe3Uy/G4FvztROUz?= =?us-ascii?Q?3wKJZhKPrBDVY/hF2cDLAa5Ga7KwepHyqxQRQplKHvBqY8kM2ypifzbbMJLR?= =?us-ascii?Q?9YPoBGxwVd6DIPtbMqxH1AkIKpEJ4slbN6sHqOgu+5/4400kq1BDyWYgikFh?= =?us-ascii?Q?wNTpOKmXCXoUZeToGtcbcUhnoWPX1lHIZsePA77F0f2lIJTdPQiC5vm1t0VD?= =?us-ascii?Q?NwcyeBogzeOcfMeyJcAavXuwMpwC0dsoSa/shYvbS89DZenqHkQEORIUHbMD?= =?us-ascii?Q?01imyEH3oQYMrI/p6DJ4fmP0eX3X/IcIq8NcCHvQg0eLAdxGHN/uXF4IQrD3?= =?us-ascii?Q?ionlaQLxWX5+BCDcsY+YWWiP3oiUFAtxUw8n0Kf7mzZ4iHVeWG45xT08qSIv?= =?us-ascii?Q?TEvqDUlvzIt0ecy1Ho5+/seLgbr5NkIoDZMkxZWqdCn9kdhGlWOd6+CnYrGU?= =?us-ascii?Q?xFqx7lpYs+GwJ84AB1QDyY4rXVo+7d64kY9uyOUrKY0lu7PRsKggCoGOrJFh?= =?us-ascii?Q?Gy5hrFojWPntWKyb0M3drWLKcuAAC3dS1jVhP8T7yKodsB61YQnJnJB+NYL+?= =?us-ascii?Q?sj7ScjeLuEe67YiJrY0G9x608ZcpbQKUOJWDnRhxGRPd5EhfQ3q0KbJ5N+jY?= =?us-ascii?Q?2gB5UJYWJ2Qd70SE3q5SOn+548jYvOkuVrWx2GgpK9LqaPDeKoAYxYq5huSd?= =?us-ascii?Q?T7TKbkpWc2Jfnrr3LJvxyhSeRfgD2e5lPcbq4AasTg+e5Nb3c5+LYB2YKwmc?= =?us-ascii?Q?tboLixZ2rTNitO0kPH+tU9+rIMMv9PqM5qm1K+GCklZadIiwvd6gCBvOVwgr?= =?us-ascii?Q?gVWp9+Oqp20zJEHB4EHTC7JosuVwus/brpdIIlx0CEvQyFaTjdP2CCpUA8DD?= =?us-ascii?Q?QWG9wl7v2Z3hSjDUAfekSv3zppOpJ65XWbS50229+QkRiqyPAVDBMjYXUWaM?= =?us-ascii?Q?91VmEFtR6AGCiRMzoicIMpCdrZVZ0/lgYLl+qa7QEnaq/jVRW/bU7ZtA+JOa?= =?us-ascii?Q?Vqp74i3l4VADosSaHlZVRprI/DaiPXDeaLxGThAQ4D4elrv3ImX8+IoWBeIM?= =?us-ascii?Q?bPmNwFyX8a3Qz9Hbwtgowa0iYiNZUbdqdLJQuzX4ucfmVBE9chI6vPY2mROV?= =?us-ascii?Q?m5fJ7g=3D=3D?=
Content-Type: multipart/alternative; boundary="_000_DM6PR10MB43168B871B59F701E2818E6D974D9DM6PR10MB4316namp_"
MIME-Version: 1.0
X-OriginatorOrg: interdigital.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DM6PR10MB4316.namprd10.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 4d0480ae-439d-4667-8a56-08d9d1d79353
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Jan 2022 12:16:46.8911 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: e351b779-f6d5-4e50-8568-80e922d180ae
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 2i5L1M9pJdHp7LBuUmReYXgVhd9Y7CbMVrjpSyXQEmiTRRb7NxRMySCJJPGZE0qRZCxqbwpSVL/hHDh6tt2FjhkjbLflEuRuXpjQMEDUMLo=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR10MB1244
Archived-At: <https://mailarchive.ietf.org/arch/msg/mops/HBiZXEwepsUs1TA0QeIowSw4s68>
Subject: [Mops] My 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: Fri, 07 Jan 2022 12:16:58 -0000

--_000_DM6PR10MB43168B871B59F701E2818E6D974D9DM6PR10MB4316namp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Everyone,
Apologies for the delay in providing this feedback. My comments on draft-ie=
tf-mops-streaming-opcons-07 follow:

Overall comments: The draft provides a timely and comprehensive snapshot of=
 the current operational issues that network operators, service providers, =
and protocol designers must consider when dealing with streaming video traf=
fic.
These operational issues are not obvious to those without specific video ex=
pertise. Therefore, the draft will prove useful for providing such a list o=
f issues against which engineering solutions could be evaluated for standar=
dization at the IETF.  Additionally, Section 7 provides a comprehensive lis=
t of references and pointers for anyone interested in a deeper exploration =
of the operational issues.
I therefore support this draft.

Some minor issues:
1) The scope of the document could be expressed more clearly in the abstrac=
t and introduction.
2) Section 2.1.2: Is it possible to provide a reference/explanation for the=
 following line:
"The typical multiplication factor is 8 to 10"
3) Section 2.6:
Suggested change : "faiils" -> "fails"
4) Section 4.6: The text "In addition to measurements....... is providing t=
he best experience for viewers." is repeated.
5) Section 4.6.2:
Suggested change: "assumes" -> "assume"
6) Section 5.3
Suggested change: "....congestion hooks that can be use" -> "....congestion=
 hooks that can be used"
Suggested change: "...congestion controllers in use for TCP base" -> "...co=
ngestion controllers in use for TCP based"
7) Section 6.3: The hyperlink for the reference "[RFC7258]" is not working.
8) Section 7.2.4
Presumably,  the following is not meant to be a bullet point but a heading =
for the bullet points that follow?
" * Low-Latency Live Streaming: The following papers describe the peculiari=
ties of adaptive streaming in low-latency live streaming scenarios."

Regards,
Renan



Dr. Renan Krishna
Staff Engineer | InterDigital
T: +44-20-39221788
E:  Renan.Krishna@InterDigital.com<mailto:Renan.Krishna@InterDigital.com>


--_000_DM6PR10MB43168B871B59F701E2818E6D974D9DM6PR10MB4316namp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi Everyone,<o:p></o:p></p>
<p class=3D"MsoNormal">Apologies for the delay in providing this feedback. =
My comments on draft-ietf-mops-streaming-opcons-07 follow:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Overall comments: The draft provides a timely and co=
mprehensive snapshot of the current operational issues that network operato=
rs, service providers, and protocol designers must consider when dealing wi=
th streaming video traffic.<o:p></o:p></p>
<p class=3D"MsoNormal">These operational issues are not obvious to those wi=
thout specific video expertise. Therefore, the draft will prove useful for =
providing such a list of issues against which engineering solutions could b=
e evaluated for standardization at
 the IETF.&nbsp; Additionally, Section 7 provides a comprehensive list of r=
eferences and pointers for anyone interested in a deeper exploration of the=
 operational issues.
<o:p></o:p></p>
<p class=3D"MsoNormal">I therefore support this draft.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Some minor issues:<o:p></o:p></p>
<p class=3D"MsoNormal">1) The scope of the document could be expressed more=
 clearly in the abstract and introduction.<o:p></o:p></p>
<p class=3D"MsoNormal">2) Section 2.1.2: Is it possible to provide a refere=
nce/explanation for the following line:<o:p></o:p></p>
<p class=3D"MsoNormal">&#8220;The typical multiplication factor is 8 to 10&=
#8221;<o:p></o:p></p>
<p class=3D"MsoNormal">3) Section 2.6: <o:p></o:p></p>
<p class=3D"MsoNormal">Suggested change : &#8220;faiils&#8221; -&gt; &#8220=
;fails&#8221;<o:p></o:p></p>
<p class=3D"MsoNormal">4) Section 4.6: The text &#8220;In addition to measu=
rements&#8230;&#8230;. is providing the best experience for viewers.&#8221;=
 is repeated.<o:p></o:p></p>
<p class=3D"MsoNormal">5) Section 4.6.2: <o:p></o:p></p>
<p class=3D"MsoNormal">Suggested change: &#8220;assumes&#8221; -&gt; &#8220=
;assume&#8221;<o:p></o:p></p>
<p class=3D"MsoNormal">6) Section 5.3<o:p></o:p></p>
<p class=3D"MsoNormal">Suggested change: &#8220;&#8230;.congestion hooks th=
at can be use&#8221; -&gt; &#8220;&#8230;.congestion hooks that can be used=
&#8221;<o:p></o:p></p>
<p class=3D"MsoNormal">Suggested change: &#8220;&#8230;congestion controlle=
rs in use for TCP base&#8221; -&gt; &#8220;&#8230;congestion controllers in=
 use for TCP based&#8221;<o:p></o:p></p>
<p class=3D"MsoNormal">7) Section 6.3: The hyperlink for the reference &#82=
20;[RFC7258]&#8221; is not working.<o:p></o:p></p>
<p class=3D"MsoNormal">8) Section 7.2.4<o:p></o:p></p>
<p class=3D"MsoNormal">Presumably, &nbsp;the following is not meant to be a=
 bullet point but a heading for the bullet points that follow?<o:p></o:p></=
p>
<p class=3D"MsoNormal">&#8220; * Low-Latency Live Streaming: The following =
papers describe the peculiarities of adaptive streaming in low-latency live=
 streaming scenarios.&#8221;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Regards,<o:p></o:p></p>
<p class=3D"MsoNormal">Renan<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div style=3D"mso-element:para-border-div;border:none;border-bottom:solid w=
indowtext 1.0pt;padding:0in 0in 1.0pt 0in">
<p class=3D"MsoNormal" style=3D"border:none;padding:0in"><o:p>&nbsp;</o:p><=
/p>
</div>
<p class=3D"MsoNormal"><b><span style=3D"color:#00B0F0"><o:p>&nbsp;</o:p></=
span></b></p>
<p class=3D"MsoNormal"><b><span style=3D"color:#00B0F0">Dr. Renan Krishna</=
span></b><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Staff E=
ngineer&nbsp;|&nbsp;InterDigital</span><o:p></o:p></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.5pt;color:#00B0F0">T:=
</span></b><span style=3D"font-size:10.5pt;color:#00B0F0">&nbsp;</span><spa=
n style=3D"font-size:10.5pt;color:black">+44-20-39221788</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.5pt;color:#00B0F0">E:=
</span></b><span style=3D"font-size:10.5pt;color:#00B0F0">&nbsp;&nbsp;</spa=
n><u><span lang=3D"FR" style=3D"font-size:10.5pt;color:#4472C4"><a href=3D"=
mailto:Renan.Krishna@InterDigital.com"><span lang=3D"EN-US">Renan.Krishna@I=
nterDigital.com</span></a></span></u><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_DM6PR10MB43168B871B59F701E2818E6D974D9DM6PR10MB4316namp_--


From nobody Sat Jan  8 23:56:22 2022
Return-Path: <do_not_reply@mnot.net>
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 CE5313A0C0A for <mops@ietfa.amsl.com>; Sat,  8 Jan 2022 23:56:14 -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, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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=mnot.net header.b=DtHrZKA+; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=MyJLu4FS
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 ZVBItu7F11Cj for <mops@ietfa.amsl.com>; Sat,  8 Jan 2022 23:56:09 -0800 (PST)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 481143A0C07 for <mops@ietf.org>; Sat,  8 Jan 2022 23:56:09 -0800 (PST)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 3C8AC3200D25 for <mops@ietf.org>; Sun,  9 Jan 2022 02:40:06 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Sun, 09 Jan 2022 02:40:06 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:from:to:subject; s=fm1; bh=CCTMilTrvGp x36/W6zHsczeesTdQ/l/ebvFaQYd07v0=; b=DtHrZKA+Nxn4VEoUr93Rd61JM16 NAn+XxemfrbxXNSFjnbG6jPk8Vvr7xj2nX1N7He2b4OE1CRBFUf62mgLidSQedC7 lCf+bJpDYgc38I8p+i8BfFDikdt9h8ZgIqjeQr/YRh5EQzgMAzAZGl4Ri5kiZOHu CoSZOtQlAQkQ5RQAKe0ZVrKAdq5PwHe7oRl0toNKZiMXLas7DUmOHu1KSAofC7wx iNJsSk+E7zAnj2PPs6Hdm1MpQ9qfpZWwvOzzl6LeM6S9jMOceQgOP/9LnVpoTUzQ T0aMsPak6yOZZhAQ3aTLAzxlU0k75y9kucL8d9WKSXYWmaDMVZx4MSVtxnw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:from:mime-version:subject:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; bh=CCTMilTrvGpx36/W6zHsczeesTdQ/l/ebvFaQYd07v0=; b=MyJLu4FS Ef/L0cOuNLp/vL43DK8YSsoWGvoGuDpVLxTU8MZ/vg14L9P0DJNdud3sL/JcosXJ MQb810AEHGHy1uON7kle798vHnTErEdg3JsfUx7KXls51zDJ+YMxSrdhjZZf5Icl qFKzgA9uBRJdBxy2ZMWXhqXvJNEvf4eKOaIi/7e54PcYOQ/Og9jE6TyarY2RaJaQ ATzKP+62MwMtE10qfr29nX9mtbf8tNWl8x4G+q/4xFAgAbsNrYml7rGhMGsWupXq Oh7E0gcvQdWDM85QMOHMkGJQ2Aftx0LNvWjIQ+RWXDYbOT/3I1IqmcSBV39tUBXw zuQCuGvPrZtv8Q==
X-ME-Sender: <xms:VZHaYfMDDL9yknFT-YB46k_IP-vw_7nRM_DsnsR2B-7IdKT_60TCyg> <xme:VZHaYZ8cpMnI60ONCbFqNWhUsWsYtAc1pqmduRCj3so-ptpX4uoBVaMXJBMSTIZkE IGZsu3-UYisvE9J0A>
X-ME-Received: <xmr:VZHaYeRhi4ht988T-wfCOBoXdbcuFHLZS23kx3ottwA5-BtVocp2KFYTaMNVdGC6oT6Fe5Te3czIChFxMni9gizrifp9FGoq7sztEVqR-IeM7DfM1X5Vvus9P-NAr7D9cY25>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrudegjedgtdejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucfpohcuuggrthgvuchfihgvlhguucdlgeelmdenuc fjughrpegtggfhvffusegrtddtredttdejnecuhfhrohhmpeftvghpohhsihhtohhrhicu tegtthhivhhithihucfuuhhmmhgrrhihuceuohhtuceoughopghnohhtpghrvghplhihse hmnhhothdrnhgvtheqnecuggftrfgrthhtvghrnhepkeefvdduteejvdefkeehieevuefg fefhteetveegffekffefteffvdelheduieetnecuffhomhgrihhnpehgihhthhhusgdrtg homhenucevlhhushhtvghrufhiiigvpedunecurfgrrhgrmhepmhgrihhlfhhrohhmpegu ohgpnhhothgprhgvphhlhiesmhhnohhtrdhnvght
X-ME-Proxy: <xmx:VZHaYTvyXpjCIYLMfvT7cM6UqDz61euGvt3lj6A5tDkOUx9dOiObXQ> <xmx:VZHaYXfpteJCpyIDtxbuFXZ7DmkFXHWyGyZBIDBWsya9WbgXBaksCw> <xmx:VZHaYf3tz-MYiL34TyzBxoVIAHA1N0xFJ-6V_7PBQVP4V4irKFYsCg> <xmx:VZHaYYoOcplAZo46qlSSVsadEBhGm1d3jKAtF8YYzpycROo957MYcA>
Received: by mail.messagingengine.com (Postfix) with ESMTPA for <mops@ietf.org>; Sun, 9 Jan 2022 02:40:05 -0500 (EST)
Content-Type: multipart/alternative; boundary="===============1393372600380571705=="
MIME-Version: 1.0
From: Repository Activity Summary Bot <do_not_reply@mnot.net>
To: mops@ietf.org
Message-Id: <20220109075609.481143A0C07@ietfa.amsl.com>
Date: Sat,  8 Jan 2022 23:56:09 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mops/6mYVVUyIyO5nCBXs_RXYe9RNcaY>
Subject: [Mops] Weekly github digest (MOPS Activity Summary)
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, 09 Jan 2022 07:56:15 -0000

--===============1393372600380571705==
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"; format="flowed"




Events without label "editorial"



Pull requests
-------------
* ietf-wg-mops/draft-ietf-mops-streaming-opcons (+2/-0/=F0=9F=92=AC7)
  2 pull requests submitted:
  - Updating acknowledgements section (by SpencerDawkins)
    https://github.com/ietf-wg-mops/draft-ietf-mops-streaming-opcons/pull/9=
5=20
  - Update for Mike English WGLC comments on Introduction (by SpencerDawkin=
s)
    https://github.com/ietf-wg-mops/draft-ietf-mops-streaming-opcons/pull/9=
4=20

  1 pull requests received 7 new comments:
  - #94 Update for Mike English WGLC comments on Introduction (7 by GrumpyO=
ldTroll, SpencerDawkins, acbegen, englishm-ietf)
    https://github.com/ietf-wg-mops/draft-ietf-mops-streaming-opcons/pull/9=
4=20


Repositories tracked by this digest:
-----------------------------------
* https://github.com/ietf-wg-mops/draft-ietf-mops-streaming-opcons

--===============1393372600380571705==
Content-Type: text/html; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

<!doctype html>
<html lang=3D"en">
<head>
<meta charset=3D"utf-8">
<title>Weekly github digest (MOPS Activity Summary)</title>
<style>
body { font-family: Gotham, "Helvetica Neue", Helvetica, Arial, sans-serif;=
 font-size: 14px; }
h2 { margin-top: 3em; color: #A52A2A; font-style: italic; font-weight: norm=
al; }
h3 { margin-bottom:0; margin-top: 2em; font-size: 1.2em; }
h1+h2 { margin-top: 1em; }
a { color: #bb6219; text-decoration: none; }
li { margin-bottom: .35em; }
.repos { margin-bottom: 0; margin-top:0; line-height: 1.2; }
.new { color: red; }
.label { display: inline;
	padding: .2em .6em .3em;
	font-size: 75%;
	font-weight: 700;
	line-height: 1;
	color: #fff;
	text-align: center;
	white-space: nowrap;
	vertical-align: baseline;
	border-radius: .25em;
}
details {
	margin-top: 8em;
	}
summary {
	margin-bottom: 1em;
	cursor: pointer;
}
</style>
</head>

<body>
<h1>Sunday January 09, 2022</h1>

<p>Events without label "editorial"</p>



<h2>Pull requests</h2>
<h3>ietf-wg-mops/draft-ietf-mops-streaming-opcons (+2/-0/=F0=9F=92=AC7)</h3>
  <p class=3D"new">2 pull requests submitted:</p>
  <ul>
  <li>#95 <a href=3D"https://github.com/ietf-wg-mops/draft-ietf-mops-stream=
ing-opcons/pull/95">Updating acknowledgements section</a> (by SpencerDawkin=
s) </li>
 =20
  <li>#94 <a href=3D"https://github.com/ietf-wg-mops/draft-ietf-mops-stream=
ing-opcons/pull/94">Update for Mike English WGLC comments on Introduction</=
a> (by SpencerDawkins) </li>
  </ul>

  <p>1 pull requests received 7 new comments:</p>
  <ul>
  <li>#94 <a href=3D"https://github.com/ietf-wg-mops/draft-ietf-mops-stream=
ing-opcons/pull/94">Update for Mike English WGLC comments on Introduction</=
a> (7 by GrumpyOldTroll, SpencerDawkins, acbegen, englishm-ietf) </li>
  </ul>



  <details>
    <summary>Repositories tracked by this digest:</summary>
<ul class=3D"repos">
  <li><a href=3D"https://github.com/ietf-wg-mops/draft-ietf-mops-streaming-=
opcons">https://github.com/ietf-wg-mops/draft-ietf-mops-streaming-opcons</a=
></li>
</ul>
</details>
</body>
</html>

--===============1393372600380571705==--


From nobody Mon Jan 10 11:16:34 2022
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 9120D3A0B82 for <mops@ietfa.amsl.com>; Mon, 10 Jan 2022 11:16:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.097
X-Spam-Level: 
X-Spam-Status: No, score=-7.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, RCVD_IN_DNSWL_HI=-5, 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 cR7GL2cKz2ze for <mops@ietfa.amsl.com>; Mon, 10 Jan 2022 11:16:28 -0800 (PST)
Received: from mail-ua1-x92b.google.com (mail-ua1-x92b.google.com [IPv6:2607:f8b0:4864:20::92b]) (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 103283A0B80 for <mops@ietf.org>; Mon, 10 Jan 2022 11:16:28 -0800 (PST)
Received: by mail-ua1-x92b.google.com with SMTP id p37so25372445uae.8 for <mops@ietf.org>; Mon, 10 Jan 2022 11:16:27 -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=13zOVfXeptLm27vWFUubDr32sPRaSgDRdJbcL0pmjeY=; b=lFwRRCp90uYw99pWHThT6UE0vhKKFAX4I90uN/uIsnQYIUgviX6i/490BEltMC1MQl Cr0bmrc+0ldWHYjlFLmNBAGeKRjTM1DYEaLboD7jM3v/pGLyRuRoAIPecudE65CL+ZyO GY8OakGSrriPeAZiwgExgmuucDI6FWemYm17wKr1LIOB5aMnIrbgMawNWFX8q8CzpdIH vvOozLo4HnSru1SeBMBpSquHO/Oh/ViraTToG5GMO4uovVnbyL5qq5f7GXoKPBclvwTo qR283PKiptv1ckuklm7Ufw50z5POuRDNtRaOGhAwuVjgq0+2hh2gMyVWRwYwjt1T6jE9 3HBQ==
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=13zOVfXeptLm27vWFUubDr32sPRaSgDRdJbcL0pmjeY=; b=iAH9gS3akcGbUUBWf99b6SCE3PrY/C46FMaYBHgmucCqgZPXQIq5Q2U7HulLLOUOHn HRem9Ky0uwNz4jne4gDHsvVkTWvKfi+mQ2OsB0EU8nBb6vEFXHDy0kp7zQrVu9897f3x kWyjNqdpk1lh+wzWofpbfe2JfixFcBUPmaiJRZGQzskF+McQqZ6S8+W2UtFC4acyr464 DUa1vnshWJbJ0RmKwDBb85esRPZjPN646Vkqy8VxzUrl/FBOSHZxvf4J32pJrcjPYced 4N5kugouphc0HnK2OP19LKz0r1IAb1vOmaNjR/GqETSThrZ2XOGXKir+D/RJtBkN9aP1 GDXg==
X-Gm-Message-State: AOAM533VC1VUJ68FOtOUg3nz5ZBXt8+hebFtkByRvTt3gtMNWgpCzSgQ YVuVbvnxB41NujK/2ELo4z71vi2lXZxf97JMM1I=
X-Google-Smtp-Source: ABdhPJy6DVKnc885ht9oy4enkKn08m6M1nCuozRczpXfaByUx6nZkHhgwmP3pZY0TjnmGZIp4DEyEfX6yo7lPccC0sk=
X-Received: by 2002:a67:be18:: with SMTP id x24mr503282vsq.43.1641842185437; Mon, 10 Jan 2022 11:16:25 -0800 (PST)
MIME-Version: 1.0
References: <DM6PR10MB43168B871B59F701E2818E6D974D9@DM6PR10MB4316.namprd10.prod.outlook.com>
In-Reply-To: <DM6PR10MB43168B871B59F701E2818E6D974D9@DM6PR10MB4316.namprd10.prod.outlook.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Mon, 10 Jan 2022 13:15:59 -0600
Message-ID: <CAKKJt-c97ppb4GkC-K4e0=oo=E1Cx9fRrXtf4We4WLz31NCmYA@mail.gmail.com>
To: Renan Krishna <Renan.Krishna@interdigital.com>
Cc: "mops@ietf.org" <mops@ietf.org>, Leslie Daigle <ldaigle@thinkingcat.com>,  Kyle Rose <krose@krose.org>
Content-Type: multipart/alternative; boundary="0000000000003d847c05d53f2c51"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mops/yLlOJ8sD-4ZOiCTurcsJgevC9QA>
Subject: Re: [Mops] My 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: Mon, 10 Jan 2022 19:16:33 -0000

--0000000000003d847c05d53f2c51
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi, Renan, (plus Ali and Jake),

Thank you for these comments (and I've added you to the Acknowledgements
section). Details below, but only the ones highlighted in yellow are worth
looking at before I commit the changes in Github.

On Fri, Jan 7, 2022 at 6:17 AM Renan Krishna <Renan.Krishna@interdigital.co=
m>
wrote:

> Hi Everyone,
>
> Apologies for the delay in providing this feedback. My comments on
> draft-ietf-mops-streaming-opcons-07 follow:
>
>
>
> Overall comments: The draft provides a timely and comprehensive snapshot
> of the current operational issues that network operators, service
> providers, and protocol designers must consider when dealing with streami=
ng
> video traffic.
>
> These operational issues are not obvious to those without specific video
> expertise. Therefore, the draft will prove useful for providing such a li=
st
> of issues against which engineering solutions could be evaluated for
> standardization at the IETF.  Additionally, Section 7 provides a
> comprehensive list of references and pointers for anyone interested in a
> deeper exploration of the operational issues.
>
> I therefore support this draft.
>
>
>
> Some minor issues:
>
> 1) The scope of the document could be expressed more clearly in the
> abstract and introduction.
>

Agreed.

I'm working on improvements for the abstract and Introduction, based on
Mike English's review comments, and I'll keep your thoughts in mind. Please
check that the next submitted version of the draft seems clearter to you,
OK? And if you're following the work in
https://github.com/ietf-wg-mops/draft-ietf-mops-streaming-opcons, you can
provide comments on
https://github.com/ietf-wg-mops/draft-ietf-mops-streaming-opcons/pull/94 as
I add commits.

I also made an editorial pass with your minor issues under that same PR.
I'll do a commit soon.


> 2) Section 2.1.2: Is it possible to provide a reference/explanation for
> the following line:
>
> =E2=80=9CThe typical multiplication factor is 8 to 10=E2=80=9D
>

I don't actually remember where that statement comes from. I'll ask for
help from my co-editors (or anyone else). *Ali and Jake,* the context is

Even basic virtual reality (360-degree) videos that allow users to look
around freely (referred to as "three degrees of freedom", or 3DoF) require
substantially larger bitrates when they are captured and encoded as such
videos require multiple fields of view of the scene. *The typical
multiplication factor is 8 to 10. *Yet, due to smart delivery methods such
as viewport-based or tiled-based streaming, we do not need to send the
whole scene to the user. Instead, the user needs only the portion
corresponding to its viewpoint at any given time.


Honestly, I'm not sure that sentence is even needed ("substantially larger
bitrates" seems to cover a multiplication factor of 8 to 10). But let's try
to do the right thing, either way.

3) Section 2.6:
>
> Suggested change : =E2=80=9Cfaiils=E2=80=9D -> =E2=80=9Cfails=E2=80=9D
>

(I'm not seeing this word in -07)


> 4) Section 4.6: The text =E2=80=9CIn addition to measurements=E2=80=A6=E2=
=80=A6. is providing the
> best experience for viewers.=E2=80=9D is repeated.
>

Fixed


> 5) Section 4.6.2:
>
> Suggested change: =E2=80=9Cassumes=E2=80=9D -> =E2=80=9Cassume=E2=80=9D
>

Fixed.


> 6) Section 5.3
>
> Suggested change: =E2=80=9C=E2=80=A6.congestion hooks that can be use=E2=
=80=9D -> =E2=80=9C=E2=80=A6.congestion
> hooks that can be used=E2=80=9D
>

Fixed.


> Suggested change: =E2=80=9C=E2=80=A6congestion controllers in use for TCP=
 base=E2=80=9D ->
> =E2=80=9C=E2=80=A6congestion controllers in use for TCP based=E2=80=9D
>

Fixed.


> 7) Section 6.3: The hyperlink for the reference =E2=80=9C[RFC7258]=E2=80=
=9D is not working.
>

Weird. I see what you mean - actually, there is no hyperlink at all in the
third usage/last paragraph.

I'm using the same markdown string - {{RFC7258}} - and it's processed
correctly when the markdown string is used in other places.

I cut and pasted the markdown string from a place where it's processed
correctly into this usage. If that doesn't help, it looks like a tools
issue, which I can report.

Thanks for mentioning this.


> 8) Section 7.2.4
>
> Presumably,  the following is not meant to be a bullet point but a headin=
g
> for the bullet points that follow?
>
> =E2=80=9C * Low-Latency Live Streaming: The following papers describe the
> peculiarities of adaptive streaming in low-latency live streaming
> scenarios.=E2=80=9D
>
>
Good catch! I think I see why this was included as a bullet (because it's
part of the ABR material), but I agree it should be a heading.

This is now

### Low-Latency Live Adaptive Streaming

The following papers describe the peculiarities of adaptive streaming in
low-latency live streaming scenarios.


Best,

Spencer

--0000000000003d847c05d53f2c51
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">Hi, Renan, (plus Ali and Jake),</div><div=
 dir=3D"ltr"><br></div><div dir=3D"ltr"><div>Thank you for these comments (=
and I&#39;ve added you to the Acknowledgements section). Details below, but=
 only the ones highlighted in yellow are worth looking at before I commit t=
he changes in Github.=C2=A0</div><div><br></div><div>On Fri, Jan 7, 2022 at=
 6:17 AM Renan Krishna &lt;<a href=3D"mailto:Renan.Krishna@interdigital.com=
" target=3D"_blank">Renan.Krishna@interdigital.com</a>&gt; wrote:<br></div>=
</div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex">





<div lang=3D"EN-US">
<div>
<p class=3D"MsoNormal">Hi Everyone,<u></u><u></u></p>
<p class=3D"MsoNormal">Apologies for the delay in providing this feedback. =
My comments on draft-ietf-mops-streaming-opcons-07 follow:<u></u><u></u></p=
>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Overall comments: The draft provides a timely and co=
mprehensive snapshot of the current operational issues that network operato=
rs, service providers, and protocol designers must consider when dealing wi=
th streaming video traffic.<u></u><u></u></p>
<p class=3D"MsoNormal">These operational issues are not obvious to those wi=
thout specific video expertise. Therefore, the draft will prove useful for =
providing such a list of issues against which engineering solutions could b=
e evaluated for standardization at
 the IETF.=C2=A0 Additionally, Section 7 provides a comprehensive list of r=
eferences and pointers for anyone interested in a deeper exploration of the=
 operational issues.
<u></u><u></u></p>
<p class=3D"MsoNormal">I therefore support this draft.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Some minor issues:<u></u><u></u></p>
<p class=3D"MsoNormal">1) The scope of the document could be expressed more=
 clearly in the abstract and introduction.</p></div></div></blockquote><div=
><br></div><div>Agreed.=C2=A0</div><div><br></div><div>I&#39;m working on i=
mprovements for the abstract and Introduction, based on Mike English&#39;s =
review comments, and I&#39;ll keep your thoughts in mind. Please check that=
 the next submitted version of the draft seems clearter to you, OK? And if =
you&#39;re following the work in=C2=A0<a href=3D"https://github.com/ietf-wg=
-mops/draft-ietf-mops-streaming-opcons" target=3D"_blank">https://github.co=
m/ietf-wg-mops/draft-ietf-mops-streaming-opcons</a>, you can provide commen=
ts on=C2=A0<a href=3D"https://github.com/ietf-wg-mops/draft-ietf-mops-strea=
ming-opcons/pull/94" target=3D"_blank">https://github.com/ietf-wg-mops/draf=
t-ietf-mops-streaming-opcons/pull/94</a> as I add commits.</div><div><br></=
div><div>I also made an editorial pass with your minor issues under that sa=
me PR. I&#39;ll do a commit soon.<br></div><div>=C2=A0</div><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex"><div lang=3D"EN-US"><div><p class=3D"Mso=
Normal"><span style=3D"background-color:rgb(255,255,0)"><u></u><u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"background-color:rgb(255,255,0)">2) S=
ection 2.1.2: Is it possible to provide a reference/explanation for the fol=
lowing line:<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"background-color:rgb(255,255,0)">=E2=
=80=9CThe typical multiplication factor is 8 to 10=E2=80=9D</span></p></div=
></div></blockquote><div><br></div><div>I don&#39;t actually remember where=
 that statement comes from.<span style=3D"background-color:rgb(255,255,0)">=
 I&#39;ll ask for help from my co-editors (or anyone else). <b>Ali and Jake=
,</b> the context is=C2=A0</span></div><div><br></div></div><blockquote sty=
le=3D"margin:0 0 0 40px;border:none;padding:0px"><div class=3D"gmail_quote"=
><div>Even basic virtual reality (360-degree) videos that allow users to lo=
ok around freely (referred to as &quot;three degrees of freedom&quot;, or 3=
DoF) require substantially larger bitrates when they are captured and encod=
ed as such videos require multiple fields of view of the scene.<span style=
=3D"background-color:rgb(255,255,0)"> </span><b><span style=3D"background-c=
olor:rgb(255,255,0)">The typical multiplication factor is 8 to 10</span>. <=
/b>Yet, due to smart delivery methods such as viewport-based or tiled-based=
 streaming, we do not need to send the whole scene to the user. Instead, th=
e user needs only the portion corresponding to its viewpoint at any given t=
ime.</div></div></blockquote><div class=3D"gmail_quote"><div>=C2=A0</div><d=
iv>Honestly, I&#39;m not sure that sentence is even needed (&quot;substanti=
ally larger bitrates&quot; seems to cover a multiplication factor of 8 to 1=
0). But let&#39;s try to do the right thing, either way.</div><div><br></di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex"><div lang=3D"EN-US"><di=
v><p class=3D"MsoNormal"><u></u><u></u></p>
<p class=3D"MsoNormal">3) Section 2.6: <u></u><u></u></p>
<p class=3D"MsoNormal">Suggested change : =E2=80=9Cfaiils=E2=80=9D -&gt; =
=E2=80=9Cfails=E2=80=9D</p></div></div></blockquote><div><br></div><div>(I&=
#39;m not seeing this word in -07)</div><div>=C2=A0</div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex"><div lang=3D"EN-US"><div><p class=3D"MsoNo=
rmal"><u></u><u></u></p>
<p class=3D"MsoNormal">4) Section 4.6: The text =E2=80=9CIn addition to mea=
surements=E2=80=A6=E2=80=A6. is providing the best experience for viewers.=
=E2=80=9D is repeated.</p></div></div></blockquote><div><br></div><div>Fixe=
d=C2=A0</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
1ex"><div lang=3D"EN-US"><div><p class=3D"MsoNormal"><u></u><u></u></p>
<p class=3D"MsoNormal">5) Section 4.6.2: <u></u><u></u></p>
<p class=3D"MsoNormal">Suggested change: =E2=80=9Cassumes=E2=80=9D -&gt; =
=E2=80=9Cassume=E2=80=9D</p></div></div></blockquote><div><br></div><div>Fi=
xed.=C2=A0</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex"><div lang=3D"EN-US"><div><p class=3D"MsoNormal"><u></u><u></u></p>
<p class=3D"MsoNormal">6) Section 5.3<u></u><u></u></p>
<p class=3D"MsoNormal">Suggested change: =E2=80=9C=E2=80=A6.congestion hook=
s that can be use=E2=80=9D -&gt; =E2=80=9C=E2=80=A6.congestion hooks that c=
an be used=E2=80=9D</p></div></div></blockquote><div><br></div><div>Fixed.=
=C2=A0</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1=
ex"><div lang=3D"EN-US"><div><p class=3D"MsoNormal"><u></u><u></u></p>
<p class=3D"MsoNormal">Suggested change: =E2=80=9C=E2=80=A6congestion contr=
ollers in use for TCP base=E2=80=9D -&gt; =E2=80=9C=E2=80=A6congestion cont=
rollers in use for TCP based=E2=80=9D</p></div></div></blockquote><div><br>=
</div><div>Fixed.=C2=A0</div><div>=C2=A0</div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,20=
4);padding-left:1ex"><div lang=3D"EN-US"><div><p class=3D"MsoNormal"><u></u=
><u></u></p>
<p class=3D"MsoNormal">7) Section 6.3: The hyperlink for the reference =E2=
=80=9C[RFC7258]=E2=80=9D is not working.</p></div></div></blockquote><div><=
br></div><div>Weird. I see what you mean - actually, there is no hyperlink =
at all in the third usage/last paragraph.=C2=A0</div><div><br></div><div>I&=
#39;m using the same markdown string -=C2=A0{{RFC7258}} - and it&#39;s proc=
essed correctly when the markdown string is used in other places.</div><div=
><br></div><div>I cut and pasted the markdown string from a place where it&=
#39;s processed correctly into this usage. If that doesn&#39;t help, it loo=
ks like a tools issue, which I can report.=C2=A0</div><div><br></div><div>T=
hanks for mentioning this.=C2=A0</div><div>=C2=A0</div><blockquote class=3D=
"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(2=
04,204,204);padding-left:1ex"><div lang=3D"EN-US"><div><p class=3D"MsoNorma=
l"><u></u><u></u></p>
<p class=3D"MsoNormal">8) Section 7.2.4<u></u><u></u></p>
<p class=3D"MsoNormal">Presumably, =C2=A0the following is not meant to be a=
 bullet point but a heading for the bullet points that follow?<u></u><u></u=
></p>
<p class=3D"MsoNormal">=E2=80=9C * Low-Latency Live Streaming: The followin=
g papers describe the peculiarities of adaptive streaming in low-latency li=
ve streaming scenarios.=E2=80=9D<u></u><u></u></p></div></div><br></blockqu=
ote><div><br></div><div>Good catch! I think I see why this was included as =
a bullet (because it&#39;s part of the ABR material), but I agree it should=
 be a heading.=C2=A0</div><div><br></div><div>This is now</div><div><br></d=
iv></div><blockquote style=3D"margin:0 0 0 40px;border:none;padding:0px"><d=
iv class=3D"gmail_quote"><div>### Low-Latency Live Adaptive Streaming<br><b=
r>The following papers describe the peculiarities of adaptive streaming in =
low-latency live streaming scenarios.</div></div></blockquote><div class=3D=
"gmail_quote"><div><br></div><div>Best,</div><div><br></div><div>Spencer=C2=
=A0</div></div></div>

--0000000000003d847c05d53f2c51--


From nobody Mon Jan 10 12:20:41 2022
Return-Path: <ali.begen@networked.media>
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 259293A11B9 for <mops@ietfa.amsl.com>; Mon, 10 Jan 2022 12:20:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 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, 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=networked.media
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 nQMPJMGtLVWc for <mops@ietfa.amsl.com>; Mon, 10 Jan 2022 12:20:36 -0800 (PST)
Received: from mail-ed1-x52c.google.com (mail-ed1-x52c.google.com [IPv6:2a00:1450:4864:20::52c]) (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 F0A603A122E for <mops@ietf.org>; Mon, 10 Jan 2022 12:20:27 -0800 (PST)
Received: by mail-ed1-x52c.google.com with SMTP id u25so58414983edf.1 for <mops@ietf.org>; Mon, 10 Jan 2022 12:20:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networked.media; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=aiYSCrxB+aGOQQp5wUXh4pxFza5f5LiuYj5wDPUJL70=; b=FaHhMW1BYaJSZRufCo7MbdEdU9ZLWdhxNIv1PEE9WHW8sS0bZGIm5oh/oI0RU9D+Ye uC99OVhnY+kp8X5sC82GfwhM1qfuFgaL2ouTF8TFMe5CV3ryQIGM/Q0YBxv5USnvfYoD VG9ldwZAu9ESqDgCVlFkNPX79ypfs0Fhbnwt6hZmw1p0wsTDJQ4H06nd0Fb0nf3DqA6v py2Df8yp3oeyiw1smLZr1UpOjIEoSMbS6tmzmBa8ZX7rISUJpxotYAzXhUCrW3a+z9W9 3YF5sTIwgHIzvOajRVbziaDMbWf+JouxlSABZbEfLFoai0Mukq6AHlMgLMrir2K1SWJQ ExGA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=aiYSCrxB+aGOQQp5wUXh4pxFza5f5LiuYj5wDPUJL70=; b=lwmN1G3GnFaVQ6WHMJWgmkogT28hpq9EfAYbP+TAgUUTSYAoqJ/CCcucgDD85Q+jU/ VnzBrHqV6JkycGhKGKn1oI0dcGNEoVCSFiI5kXriSz6RDHf6+FsNdMDgwYy0O7/jZBzS m98ODEuKcJVic326Eg4Z8vRHLsUKG4bcnVNbjzuVPbJnr21nDN13dWq7gTyivHgvPf9x 2/LsiVfrkhtd4envlvQ/frbhtPVqvvvA88Xhwd6uS75g6rjNu8Mu/B+dXHqhfjY5Meyp bKxBg0MedHmawphoVz5VpEHHld0qVHsdrKRZ67hjG+wEWXGj2DfBX2NUVLXrTYHHbW73 tTQg==
X-Gm-Message-State: AOAM533ookflc8eq+mGrXb3GN8b1bCQmBmpSW4dm2IlK2PZPYp2z5Ffu BBwKH7BGhAkqbveBcZSpGbUeNw==
X-Google-Smtp-Source: ABdhPJwyGgBT6VwPJlTk+e68rIw3w84EAHaMt8/hrEj0ZI5u6NLuqJNuuR09JVXmoA30mui9R4rmlA==
X-Received: by 2002:a17:907:6d9f:: with SMTP id sb31mr1077533ejc.86.1641846025639;  Mon, 10 Jan 2022 12:20:25 -0800 (PST)
Received: from smtpclient.apple ([85.105.47.236]) by smtp.gmail.com with ESMTPSA id o6sm4044501eds.35.2022.01.10.12.20.24 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 10 Jan 2022 12:20:25 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
From: "Ali C. Begen" <ali.begen@networked.media>
In-Reply-To: <CAKKJt-c97ppb4GkC-K4e0=oo=E1Cx9fRrXtf4We4WLz31NCmYA@mail.gmail.com>
Date: Mon, 10 Jan 2022 23:20:23 +0300
Cc: Renan Krishna <Renan.Krishna@interdigital.com>, Leslie Daigle <ldaigle@thinkingcat.com>, Kyle Rose <krose@krose.org>, "mops@ietf.org" <mops@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <E39E0E5B-951D-4BFA-809B-F0CC0A9BD17B@networked.media>
References: <DM6PR10MB43168B871B59F701E2818E6D974D9@DM6PR10MB4316.namprd10.prod.outlook.com> <CAKKJt-c97ppb4GkC-K4e0=oo=E1Cx9fRrXtf4We4WLz31NCmYA@mail.gmail.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mops/Q8P2dO-jSep539tiPr6MpWTBAP4>
Subject: Re: [Mops] My 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: Mon, 10 Jan 2022 20:20:40 -0000

> On Jan 10, 2022, at 10:15 PM, Spencer Dawkins at IETF =
<spencerdawkins.ietf@gmail.com> wrote:
>=20
> 2) Section 2.1.2: Is it possible to provide a reference/explanation =
for the following line:
>=20
> =E2=80=9CThe typical multiplication factor is 8 to 10=E2=80=9D
>=20
>=20
> I don't actually remember where that statement comes from. I'll ask =
for help from my co-editors (or anyone else). Ali and Jake, the context =
is=20
>=20
> Even basic virtual reality (360-degree) videos that allow users to =
look around freely (referred to as "three degrees of freedom", or 3DoF) =
require substantially larger bitrates when they are captured and encoded =
as such videos require multiple fields of view of the scene. The typical =
multiplication factor is 8 to 10. Yet, due to smart delivery methods =
such as viewport-based or tiled-based streaming, we do not need to send =
the whole scene to the user. Instead, the user needs only the portion =
corresponding to its viewpoint at any given time.
> =20
> Honestly, I'm not sure that sentence is even needed ("substantially =
larger bitrates" seems to cover a multiplication factor of 8 to 10). But =
let's try to do the right thing, either way.

Yeah, we don=E2=80=99t need to give a specific number, "substantially =
larger bitrates=E2=80=9D is safer and we could cite the following paper =
as a reference:
A Survey on Adaptive 360o Video Streaming: Solutions, Challenges and =
Opportunities (https://ieeexplore.ieee.org/document/9133103) which is =
already listed in 7.2.7.

-acbegen=


From nobody Tue Jan 11 06:20:36 2022
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 5B85F3A1224 for <mops@ietfa.amsl.com>; Tue, 11 Jan 2022 06:20:35 -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 VqceBmFzFCqU for <mops@ietfa.amsl.com>; Tue, 11 Jan 2022 06:20:30 -0800 (PST)
Received: from mail-ua1-x935.google.com (mail-ua1-x935.google.com [IPv6:2607:f8b0:4864:20::935]) (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 9F84D3A1222 for <mops@ietf.org>; Tue, 11 Jan 2022 06:20:30 -0800 (PST)
Received: by mail-ua1-x935.google.com with SMTP id v12so29982083uar.7 for <mops@ietf.org>; Tue, 11 Jan 2022 06:20:30 -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=f9p6p4caXKjiLo8SVV+GRiafVAG8yq9mXXDUQU+g+Xc=; b=WfM9pHGVHSht+V92UV0YeGSLZGHXzH5zpg5av4iO97DjQLIcHQ5717xG75r9FQSHzk siQipVsYNP0hohHBa90riRZAStFbN/uLWG6yFImQfJf6lauySVVi1lumDLPiJ3hd3MNJ e36HG3RCbC/5tVTiBshgG+v5vv65D2poCUe1r6ZPeQx/71rOjWZvEi7JyOG6qZEDnVhC W8AK8iS2d24izyZhXPZXQUL9HTcfip34DZryY1XrZSb0j7bvGM1z2owCCiawJrCYw4wT 7FA0ZFODy99qMxzPOFwU6XMb49zAg/wFus3yBtrIIRGN5eXXwSBKHjiiKSMG4r9TrckE 4Vpw==
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=f9p6p4caXKjiLo8SVV+GRiafVAG8yq9mXXDUQU+g+Xc=; b=Oipb5QPaH2hd1rrMdr2yDggxQy0qE4FetF9QT5dW7xrXKxSJXG7npZkILLtP3Ag3A6 XXHAr805IP/4RE8H24Xn0GMcnlF3f/3HnHX552y26sWSGDV6ctOnB/LtKCeQ+Vvye13F NLHH7TCJe/NSqUj8EA2rvtpgt9x9QIrBD95NkasTWnOehRV6aR4mfidN6bQUMfkG7AmG WL7FgRjODUDJg55OMT1KguoGRIdwLzup2AEt8NMS6PvRthb0kQOO3ICCFFHP/fwxeOTo RVBxhf6UhW6G6fTcoSMyMrO1gkPyBGmnYDncQ+sRNziT3vNKeSYylp+XzGpiTPAiIpcI t9sA==
X-Gm-Message-State: AOAM531Oir8ueQKun8LqvV2+we1kgHXUg/dDJIng6LsTfOTohgsoXu5H GjDp1H6qWyw5WcRGjfAnxPMszjOZ12zyjqsIvvE=
X-Google-Smtp-Source: ABdhPJz8AIDKCcERvaqalYmdiB9fvjGqKQmwJdrebosyDMxdUDzUQjHOMBGLnsX90CyPFCU/ESp0Tjg5U1txMB+/Y+8=
X-Received: by 2002:ab0:c2:: with SMTP id 60mr1958276uaj.118.1641910827891; Tue, 11 Jan 2022 06:20:27 -0800 (PST)
MIME-Version: 1.0
References: <DM6PR10MB43168B871B59F701E2818E6D974D9@DM6PR10MB4316.namprd10.prod.outlook.com> <CAKKJt-c97ppb4GkC-K4e0=oo=E1Cx9fRrXtf4We4WLz31NCmYA@mail.gmail.com> <E39E0E5B-951D-4BFA-809B-F0CC0A9BD17B@networked.media>
In-Reply-To: <E39E0E5B-951D-4BFA-809B-F0CC0A9BD17B@networked.media>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Tue, 11 Jan 2022 08:20:01 -0600
Message-ID: <CAKKJt-c8cRNX0LiMhVjcPjWZSmEyi94CZu8b7YJSyqdbK7ALrQ@mail.gmail.com>
To: "Ali C. Begen" <ali.begen@networked.media>
Cc: Renan Krishna <Renan.Krishna@interdigital.com>, Leslie Daigle <ldaigle@thinkingcat.com>,  Kyle Rose <krose@krose.org>, "mops@ietf.org" <mops@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a640c705d54f27c7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mops/Fy6jAT8CfQavYPtVeD_0PvQOfDI>
Subject: Re: [Mops] My 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: Tue, 11 Jan 2022 14:20:35 -0000

--000000000000a640c705d54f27c7
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi, Ali,

On Mon, Jan 10, 2022 at 2:20 PM Ali C. Begen <ali.begen@networked.media>
wrote:

>
>
> > On Jan 10, 2022, at 10:15 PM, Spencer Dawkins at IETF <
> spencerdawkins.ietf@gmail.com> wrote:
> >
> > 2) Section 2.1.2: Is it possible to provide a reference/explanation for
> the following line:
> >
> > =E2=80=9CThe typical multiplication factor is 8 to 10=E2=80=9D
> >
> >
> > I don't actually remember where that statement comes from. I'll ask for
> help from my co-editors (or anyone else). Ali and Jake, the context is
> >
> > Even basic virtual reality (360-degree) videos that allow users to look
> around freely (referred to as "three degrees of freedom", or 3DoF) requir=
e
> substantially larger bitrates when they are captured and encoded as such
> videos require multiple fields of view of the scene. The typical
> multiplication factor is 8 to 10. Yet, due to smart delivery methods such
> as viewport-based or tiled-based streaming, we do not need to send the
> whole scene to the user. Instead, the user needs only the portion
> corresponding to its viewpoint at any given time.
> >
> > Honestly, I'm not sure that sentence is even needed ("substantially
> larger bitrates" seems to cover a multiplication factor of 8 to 10). But
> let's try to do the right thing, either way.
>
> Yeah, we don=E2=80=99t need to give a specific number, "substantially lar=
ger
> bitrates=E2=80=9D is safer and we could cite the following paper as a ref=
erence:
> A Survey on Adaptive 360o Video Streaming: Solutions, Challenges and
> Opportunities (https://ieeexplore.ieee.org/document/9133103) which is
> already listed in 7.2.7.
>

I LOVE it when you and I agree on the right thing to do!

Now in my working copy.

Best,

Spencer


> -acbegen

--000000000000a640c705d54f27c7
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">Hi, Ali,=C2=A0</div><br><div class=3D"gma=
il_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jan 10, 2022 at 2:2=
0 PM Ali C. Begen &lt;ali.begen@networked.media&gt; wrote:<br></div><blockq=
uote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1p=
x solid rgb(204,204,204);padding-left:1ex"><br>
<br>
&gt; On Jan 10, 2022, at 10:15 PM, Spencer Dawkins at IETF &lt;<a href=3D"m=
ailto:spencerdawkins.ietf@gmail.com" target=3D"_blank">spencerdawkins.ietf@=
gmail.com</a>&gt; wrote:<br>
&gt; <br>
&gt; 2) Section 2.1.2: Is it possible to provide a reference/explanation fo=
r the following line:<br>
&gt; <br>
&gt; =E2=80=9CThe typical multiplication factor is 8 to 10=E2=80=9D<br>
&gt; <br>
&gt; <br>
&gt; I don&#39;t actually remember where that statement comes from. I&#39;l=
l ask for help from my co-editors (or anyone else). Ali and Jake, the conte=
xt is <br>
&gt; <br>
&gt; Even basic virtual reality (360-degree) videos that allow users to loo=
k around freely (referred to as &quot;three degrees of freedom&quot;, or 3D=
oF) require substantially larger bitrates when they are captured and encode=
d as such videos require multiple fields of view of the scene. The typical =
multiplication factor is 8 to 10. Yet, due to smart delivery methods such a=
s viewport-based or tiled-based streaming, we do not need to send the whole=
 scene to the user. Instead, the user needs only the portion corresponding =
to its viewpoint at any given time.<br>
&gt;=C2=A0 <br>
&gt; Honestly, I&#39;m not sure that sentence is even needed (&quot;substan=
tially larger bitrates&quot; seems to cover a multiplication factor of 8 to=
 10). But let&#39;s try to do the right thing, either way.<br>
<br>
Yeah, we don=E2=80=99t need to give a specific number, &quot;substantially =
larger bitrates=E2=80=9D is safer and we could cite the following paper as =
a reference:<br>
A Survey on Adaptive 360o Video Streaming: Solutions, Challenges and Opport=
unities (<a href=3D"https://ieeexplore.ieee.org/document/9133103" rel=3D"no=
referrer" target=3D"_blank">https://ieeexplore.ieee.org/document/9133103</a=
>) which is already listed in 7.2.7.<br></blockquote><div><br></div><div>I =
LOVE it when you and I agree on the right thing to do!</div><div><br></div>=
<div>Now in my working copy.=C2=A0</div><div><br></div><div>Best,</div><div=
><br></div><div>Spencer</div><div>=C2=A0</div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,20=
4);padding-left:1ex">-acbegen</blockquote></div></div>

--000000000000a640c705d54f27c7--


From nobody Tue Jan 11 11:26:17 2022
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 195823A0B0D; Tue, 11 Jan 2022 11:26:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.098
X-Spam-Level: 
X-Spam-Status: No, score=-7.098 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_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-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 BMXngh-OPjpo; Tue, 11 Jan 2022 11:26:14 -0800 (PST)
Received: from mail-vk1-xa2d.google.com (mail-vk1-xa2d.google.com [IPv6:2607:f8b0:4864:20::a2d]) (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 C04383A0B1C; Tue, 11 Jan 2022 11:26:14 -0800 (PST)
Received: by mail-vk1-xa2d.google.com with SMTP id h16so175535vkp.5; Tue, 11 Jan 2022 11:26:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;  h=mime-version:from:date:message-id:subject:to:cc; bh=sntOQwPfD72IktWphoG6pG+/mgSCWnanNhAUDBWgWNw=; b=YcSilKKOl12ml/WTz74lsNug1p0I5xYAmVwe28i+dpXfqj+IH+Eqns1V65OlKDBm1H aWPNcEJ2YdbVX/ML54f/qFen2vpZek+Up0fOUXLan0PJw+h/ZShvnhI9qLd3tYOJWd+E FqXfUDBtHRxjr33yrYkiZxSf33xk3HYcquekHzHvaY03M8v0KZXhJLaLTv93U6rpot31 EVSjDs/iKIsZjaHomLXkmuxPf/DjNa8OCmL7KugJQ9CZWNlufhRdgtBMJqhVkvmA3+E1 aN7aXfPNFSMwNl38nDhCehxofnZlU49SNW+E1A1rr1SzyDoHIlffMRHL9uv38ahm7wax 47/A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=sntOQwPfD72IktWphoG6pG+/mgSCWnanNhAUDBWgWNw=; b=zX+kKU1NnCtcUipC285LWFEKZc0Lt9/pGS4vMjUc46Bd2pFteNlkYur7vJYMeIk36P tHeDu0vE6rvJj4laMTpc07CLSeVZepzeRpSm/vz+U+eqQ4XfSPS3vRXQsdGj7RtFLxUZ BAIfOomJEJFwCw1NPkeXR20WGejrYuA76cLAYgHqaoPX3ggn1UKnyV93aAkhz85bgQzG 5J/+0pDZrs0X8+UpM1dMLUVyphEP2ByEWvo0pFfVwYeU70NTg8idc0UJ7m+WOVm6XtPu Ngqwm2Yu1tpiK6+O84pz05KRpdXIn0NjZ0/H2fUSeATVqNsU0G/OxZwFEa/YbZv014SM 1dSg==
X-Gm-Message-State: AOAM532wiLmHh38MrzS5SyyRn+esZ6zu2eFDGWCWUrRw3IOwNiD8Ijan /4Lu/KfSlbOJMpNido1pEZUgoLFfxD5wxTGGUthP8yweRXg=
X-Google-Smtp-Source: ABdhPJx8Fn6um4K2w1W8jJlLnkko/xwARXmnI5YAB6xUHqcOTywapBzEI0dm0Q67KD8LlzJ211Gxr4oAzTADYsKuUZI=
X-Received: by 2002:a1f:4b07:: with SMTP id y7mr2815287vka.34.1641929172547; Tue, 11 Jan 2022 11:26:12 -0800 (PST)
MIME-Version: 1.0
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Tue, 11 Jan 2022 13:25:46 -0600
Message-ID: <CAKKJt-cpPCyX43BNLR=cAQ_egR9u2LLNNOFeCsLPstNNWt3vuQ@mail.gmail.com>
To: mops@ietf.org
Cc: mops-chairs@ietf.org
Content-Type: multipart/alternative; boundary="000000000000137b8e05d5536d2f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mops/SAUi51DV1GTloTxyD9BUCY0QwGk>
Subject: [Mops] Further updates on WGLC comments
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, 11 Jan 2022 19:26:16 -0000

--000000000000137b8e05d5536d2f
Content-Type: text/plain; charset="UTF-8"

Dear MOPS,

I think I've completed all the review comments from Mike, Chris, and Renan
on draft-ietf-mops-streaming-opcons-07. we've been discussing.

The best way to see these changes right now is at
https://github.com/ietf-wg-mops/draft-ietf-mops-streaming-opcons/pull/94/files
.

Please let me know if further changes are needed, but in the absence of
additional comments, I think this draft may be ready for Publication
Requested.

Best,

Spencer

--000000000000137b8e05d5536d2f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Dear MOPS,<br><div><br></div><div>I think I&#39;ve complet=
ed all the review=C2=A0comments from Mike, Chris, and Renan on=C2=A0draft-i=
etf-mops-streaming-opcons-07.=C2=A0we&#39;ve been discussing.</div><div><br=
></div><div>The best way to see these changes right now is at=C2=A0<a href=
=3D"https://github.com/ietf-wg-mops/draft-ietf-mops-streaming-opcons/pull/9=
4/files">https://github.com/ietf-wg-mops/draft-ietf-mops-streaming-opcons/p=
ull/94/files</a>.</div><div><br></div><div>Please let me know if further ch=
anges are needed, but in the absence of additional comments, I think this d=
raft may be ready for Publication Requested.=C2=A0</div><div><br></div><div=
>Best,</div><div><br></div><div>Spencer</div></div>

--000000000000137b8e05d5536d2f--


From nobody Tue Jan 11 13:05:10 2022
Return-Path: <internet-drafts@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 B88C13A0AA7; Tue, 11 Jan 2022 13:05:04 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: mops@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.42.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: mops@ietf.org
Message-ID: <164193510460.24681.7567031849577194163@ietfa.amsl.com>
Date: Tue, 11 Jan 2022 13:05:04 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/mops/lfGmI5jSuk_L6nltn-u1_rVVaYc>
Subject: [Mops] I-D Action: draft-ietf-mops-streaming-opcons-08.txt
X-BeenThere: mops@ietf.org
X-Mailman-Version: 2.1.29
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, 11 Jan 2022 21:05:05 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Media OPerationS WG of the IETF.

        Title           : Operational Considerations for Streaming Media
        Authors         : Jake Holland
                          Ali Begen
                          Spencer Dawkins
	Filename        : draft-ietf-mops-streaming-opcons-08.txt
	Pages           : 48
	Date            : 2022-01-11

Abstract:
   This document provides an overview of operational networking issues
   that pertain to quality of experience when streaming video and other
   high-bitrate media over the Internet.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mops-streaming-opcons/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-mops-streaming-opcons-08.html

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-mops-streaming-opcons-08


Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts



From nobody Tue Jan 11 13:09:36 2022
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 293C63A003E; Tue, 11 Jan 2022 13:09:35 -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 C1rSzKfpV5y7; Tue, 11 Jan 2022 13:09:30 -0800 (PST)
Received: from mail-ua1-x936.google.com (mail-ua1-x936.google.com [IPv6:2607:f8b0:4864:20::936]) (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 A346F3A0029; Tue, 11 Jan 2022 13:09:30 -0800 (PST)
Received: by mail-ua1-x936.google.com with SMTP id c36so938959uae.13; Tue, 11 Jan 2022 13:09:30 -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=p7IV9e2LGzU2Ws96usNXplcXjgoSZAXI10hX2y2TncM=; b=n6qzHxafwAx7tCdl2GgJnbjegIh4JK2awzPuu1kvUq8opLueUwnBhldZpOf7C9v2NW S6VilbvT1LslvWVguG+gxltiuz+vOcw8akVMZJXRG1N9YI+ToRIYwIB/VxYsWFAPY1QM UjjMoR/a6GoSAIgZaAkUz6wUJ9LrBg4yLmLXO4j9Zy0GVyhuXzQe4IRkKQQtpwRKUDQs 6L7DM2qDb7g/blUKzBzfXFQma1oGRTXy0jqhYnk/cm/vLtCZ8wsLBl+ChEs0xDofmKIr 4MDJKQ8dXhi/FYLMkWAmt+5h1mae76n/PK5RTrKMfr8Zk9j2UhyTA2bmmTSdjar83ali nthg==
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=p7IV9e2LGzU2Ws96usNXplcXjgoSZAXI10hX2y2TncM=; b=mun2gYEpPeuLlwJSW/8/s9mkrsItcHxaVhboj/fnjUc/wkaOq6276gaVg99D5wCaSY OX9/TPAxTN6ILbbbGZaG1Ar74WxPk07SPXnXbxK5UB/8DLzb9ZDkxJ6L2mCEUMNRhIAi XvADyP8HakuYhXi1cg94xFViiL8cKtshx8b21jTkNL3T4E6ehpWW5wZSy+R+PMVvWG8u iLnj59esmizTqRMrY42Pt8741DPBblWBDfPpXcn+sN2QVmJGbbNMRCuaBcbO5xsSUEGp N0UiO9cd7CI7db4+V3z4baPAcDwlTo1WDkuULjpGbZ3p2dspz33DFnNpXNhHdxoJLVS9 Sd9A==
X-Gm-Message-State: AOAM530RKp46dn1ClbEnCyKLSX3tKrJWRPeVje/EdGzaNRH3J8PsiLn6 WtYhGOIg5GgJtj/OEXagasWX1mSMXpixICcI5RnChEI9
X-Google-Smtp-Source: ABdhPJx5sNL04FuEalVoDSCz222oxFH9W5JpFWDAUjDNj6GDSuMpq6FuazZIAGpFztgaFKUyAmn45abR3ebK1Ikm9s4=
X-Received: by 2002:ab0:5a46:: with SMTP id m6mr2919338uad.104.1641935368349;  Tue, 11 Jan 2022 13:09:28 -0800 (PST)
MIME-Version: 1.0
References: <164193510460.24681.7567031849577194163@ietfa.amsl.com>
In-Reply-To: <164193510460.24681.7567031849577194163@ietfa.amsl.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Tue, 11 Jan 2022 15:09:02 -0600
Message-ID: <CAKKJt-e8tuKn4jkER+VyTayivsUXjXQxVPwQMFwM8WTFL7rwnA@mail.gmail.com>
To: mops@ietf.org
Cc: mops-chairs@ietf.org
Content-Type: multipart/alternative; boundary="0000000000005feacb05d554dedc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mops/KTNQUsoi3InN_UbK3kqrnSxmSh4>
Subject: Re: [Mops] I-D Action: draft-ietf-mops-streaming-opcons-08.txt
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, 11 Jan 2022 21:09:35 -0000

--0000000000005feacb05d554dedc
Content-Type: text/plain; charset="UTF-8"

Dear MOPS,

I've submitted -08 of this draft. I believe it addresses the review
comments we received since IETF 112, and subsequent discussion about those
comments.

I believe this version is ready for Publication Requested.

Best,

Spencer

On Tue, Jan 11, 2022 at 3:05 PM <internet-drafts@ietf.org> wrote:

>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Media OPerationS WG of the IETF.
>
>         Title           : Operational Considerations for Streaming Media
>         Authors         : Jake Holland
>                           Ali Begen
>                           Spencer Dawkins
>         Filename        : draft-ietf-mops-streaming-opcons-08.txt
>         Pages           : 48
>         Date            : 2022-01-11
>
> Abstract:
>    This document provides an overview of operational networking issues
>    that pertain to quality of experience when streaming video and other
>    high-bitrate media over the Internet.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-mops-streaming-opcons/
>
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-mops-streaming-opcons-08.html
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-mops-streaming-opcons-08
>
>
> Internet-Drafts are also available by rsync at rsync.ietf.org:
> :internet-drafts
>
>
> --
> Mops mailing list
> Mops@ietf.org
> https://www.ietf.org/mailman/listinfo/mops
>

--0000000000005feacb05d554dedc
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Dear MOPS,=C2=A0<div><br></div><div>I&#39;ve submitted -08=
 of this draft. I believe it addresses the review comments we received sinc=
e IETF 112, and subsequent discussion about those comments.=C2=A0</div><div=
><br></div><div>I believe this version is ready for Publication Requested.=
=C2=A0</div><div><br></div><div>Best,</div><div><br></div><div>Spencer</div=
></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr"=
>On Tue, Jan 11, 2022 at 3:05 PM &lt;<a href=3D"mailto:internet-drafts@ietf=
.org">internet-drafts@ietf.org</a>&gt; wrote:<br></div><blockquote class=3D=
"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(2=
04,204,204);padding-left:1ex"><br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
This draft is a work item of the Media OPerationS WG of the IETF.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 Operational Considerations for Streaming Media<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Authors=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: Jake=
 Holland<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Ali Begen<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Spencer Dawkins<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-iet=
f-mops-streaming-opcons-08.txt<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 48<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 :=
 2022-01-11<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0This document provides an overview of operational networking i=
ssues<br>
=C2=A0 =C2=A0that pertain to quality of experience when streaming video and=
 other<br>
=C2=A0 =C2=A0high-bitrate media over the Internet.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-mops-streaming-opcon=
s/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/doc/d=
raft-ietf-mops-streaming-opcons/</a><br>
<br>
There is also an HTML version available at:<br>
<a href=3D"https://www.ietf.org/archive/id/draft-ietf-mops-streaming-opcons=
-08.html" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/archive=
/id/draft-ietf-mops-streaming-opcons-08.html</a><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mops-streaming-op=
cons-08" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/rfcdiff?=
url2=3Ddraft-ietf-mops-streaming-opcons-08</a><br>
<br>
<br>
Internet-Drafts are also available by rsync at rsync.ietf.org::internet-dra=
fts<br>
<br>
<br>
-- <br>
Mops mailing list<br>
<a href=3D"mailto:Mops@ietf.org" target=3D"_blank">Mops@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mops" rel=3D"noreferrer" t=
arget=3D"_blank">https://www.ietf.org/mailman/listinfo/mops</a><br>
</blockquote></div>

--0000000000005feacb05d554dedc--


From nobody Sat Jan 15 08:14:51 2022
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 5FA393A16C1; Sat, 15 Jan 2022 08:14:49 -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 uUHDAlc-p4BD; Sat, 15 Jan 2022 08:14:44 -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 8BF2D3A16BE; Sat, 15 Jan 2022 08:14:44 -0800 (PST)
Received: by mail-vk1-xa2b.google.com with SMTP id bj47so7653177vkb.13; Sat, 15 Jan 2022 08:14:44 -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=wbeWoWgnWPiyYkvX2jcOm+cok+ouQYMYdNHX/McjVmM=; b=Ub9JUtvoA5KxmjRFbjiYhxv/SlfeY+seaEG8lXNUzoHPdpVQUIs5pu9lNJF8Is4lkJ Up2AfHqddm++4oZCz+UTe390wCOde4ooqlpMEhd7ECVF08yNEKzo5e/ZJrtopLAOwStW S75behusW+i64bNTmgqemcFt6EE5HsM19QJlOunXMt7Eg0WPSX+LHNKWmhoDNhsPh0t7 YRaSY/uUEOZIqXg3GiTPV2dNpUH+w/itUD3tshkfrc7Y9zoXYS6Hkmi6FEk52K6kUjrE K7dmTGg8uB+rQSjA/uFYKIHxkNU9BYoAEZYarkmOBM4fgtTi0zkhbdu9ds/tzdBbb3YY U+tQ==
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=wbeWoWgnWPiyYkvX2jcOm+cok+ouQYMYdNHX/McjVmM=; b=5qAtWGF18XbUbgweiEAWsQR4ZdFuNWs/L9ugwcmsu+wsCtIBM30G91oYKDKnCILTJt h7JoPIcFlOA+cYOhOOXuZ0tWPaphvi+1q+3lzqflPx2UftyOcokBZaMxipmdxWBmrrOt /xYQ1SjsxGYGwo6QjweVifO8AOd7hRCw4ojx6ZDG9j3XLMiyFqCCqSGUWFHltLYnv/Qf 4SZzknzAy5lh9hyirVBNwCuIjI29C4XLUpvrFZW6iyo1VcZAAbxEhBar8y/lJxIXrG59 7k/IyAtNC65Jum3mNhhy5GqTWpttakwLortGj6UN6q/X2ZJdf5iNNdtDZDKDEqdS9bQM hBjg==
X-Gm-Message-State: AOAM5300qxArN8yrWpclg1+RdgYyIjHsge1ZMK6OEi1/7XJuwcz6GVj0 HmK6o14Xid/FtERKLa01rNLOdpnSoPW0bT9+4+cvV9DR
X-Google-Smtp-Source: ABdhPJwGnr21PTipFBxIjxTo6Y9BlZ4ULzslz5p8P3/FaeTgeXvqL3Q5xiqJFxqx5s/2PN4hO1E+pWPeF7xtXv9N/fE=
X-Received: by 2002:a1f:734f:: with SMTP id o76mr5879542vkc.25.1642263282711;  Sat, 15 Jan 2022 08:14:42 -0800 (PST)
MIME-Version: 1.0
References: <CAKKJt-doYaJ5XFKJiDdrcuUb8d+hNoV4jvWa7H8Fe2Jp0hqhAw@mail.gmail.com> <BY5PR13MB293439577AE2F73AA5599E7FF3919@BY5PR13MB2934.namprd13.prod.outlook.com>
In-Reply-To: <BY5PR13MB293439577AE2F73AA5599E7FF3919@BY5PR13MB2934.namprd13.prod.outlook.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Sat, 15 Jan 2022 10:14:16 -0600
Message-ID: <CAKKJt-e78BMmKQ2nWr18z8WiCtnOFba2xLsPvwyFT9Wwrx1CmQ@mail.gmail.com>
To: "mops@ietf.org" <mops@ietf.org>
Cc: mops-chairs@ietf.org
Content-Type: multipart/alternative; boundary="00000000000098000f05d5a137ec"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mops/9YHIG1WeFapoOq_MLSnLbBbkuKA>
Subject: Re: [Mops] [Internet] My notes on draft-ietf-mops-ar-use-case-03
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: Sat, 15 Jan 2022 16:14:50 -0000

--00000000000098000f05d5a137ec
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Dear MOPS,

Just following up here - I know that the draft authors thanked Rohit and I
for our reviews during the MOPS session at IETF 112, but is anyone else
sending review comments to the working group?

Best,

Spencer

On Tue, Nov 9, 2021 at 8:45 AM Rohit Abhishek <rabhishek@rabhishek.com>
wrote:

> Some comments below for the authors on section 3.
>
>
>
> Best Regards,
>
> Rohit
>
>
>
> *From: *Mops <mops-bounces@ietf.org> on behalf of Spencer Dawkins at IETF
> <spencerdawkins.ietf@gmail.com>
> *Date: *Saturday, November 6, 2021 at 3:24 PM
> *To: *"mops@ietf.org" <mops@ietf.org>
> *Cc: *"mops-chairs@ietf.org" <mops-chairs@ietf.org>
> *Subject: *[Internet][Mops] My notes on draft-ietf-mops-ar-use-case-03
>
>
>
> Dear MOPS,
>
>
>
> Leslie reminded me that I had volunteered to send comments on this draft
> at IETF 111. My apologies for getting distracted since July!
>
>
>
> This draft was updated to -03 a couple of weeks ago, so I'm reviewing the
> current version. I can't stress enough that I'm not an AR expert, althoug=
h
> I have co-workers who are, so I'm commenting on the draft as a generalist=
.
> Please read these comments as if I had ended each of them with "does that
> make sense?"
>
>
>
> Here are my thoughts.
>
> =C2=B7         I think it's definitely worth thinking about AR in MOPS. T=
he
> material on the use case in Section 3 seems useful for operators seeking =
to
> better understand AR..
>
> =C2=B7         It's worth thinking about what the scope of this document =
is -
> the title says "Augmented Reality", but there are scattered references to
> AR/VR and 360 degree streaming  in Section 4. I suspect that most of what
> section 3 and section 4 are saying about AR would be increasingly true
> about VR and 360-degree streaming, and a variety of other applications.
> Perhaps this document should be something like "reasons to deploy edge
> computing", with the reasons not being about specific applications, but
> about the characteristics that make edge computing useful, or even
> critical, for successful application usage.
>
> =C2=B7         It's worth thinking about who the intended audience for th=
is
> document is. From the MOPS charter: "The focus of MOPS is on identifying
> areas where existing protocols and/or networks are challenged by updated
> requirements". Again, if the scope of this document is to explain why
> deploying edge computing to support high-bandwidth ultra-low latency
> applications that need to use network computing resources, that seems
> squarely within the MOPS charter, and Section 3 seems headed the right
> direction, but Sections 3.1, 3.2, and 4 contain a lot of details that are
> only relevant to network operators to the extent that that those details
> affect the application's demands on the network. I don't think it matters
> WHY AR headsets place additional demands on networking and computing
> resources within the operator domain, it only matters that they do place
> those demands.
>
> Rohit : From what I understand, the AR headset identifies objects in
> real-time and then overlays a historical 3D scene on top of the identifie=
d
> object. As the user moves, the view of the 3D scene changes. So, when you
> say =E2=80=9Chistorical scenes in 3D=E2=80=9D what exactly does it mean ?=
. Does it mean a
> 3D video is overlaid, and it is pre-created and stored somewhere in a
> server?. As the AR headset points to specific object in a scene, the
> respective 3D video is streamed onto the user=E2=80=99s headset from the =
database.
> If this is not the case, then how are the 3D videos generated and what
> would be its content?
>
> =C2=B7         Section 5, on "AR Network Traffic and Interaction with TCP=
"
> isn't WRONG, but I don't think it fits in a MOPS document. The choice of
> transport protocols is still (sadly) up to application developers, and
> Section 5 would make sense if AR application developers were the target
> audience for this document. By the time an AR application arrives in a
> network, the choice to use TCP, or not to use TCP, has already been made,
> and is largely/completely outside the operator's control.
>
> =C2=B7
>
> =C2=B7         This draft definitely needs more working group input, so I=
 hope
> I'm not the only one who sends comments!. Our experience with putting
> https://www.ietf.org/archive/id/draft-ietf-mops-streaming-opcons-07.html
> in Github definitely made it easier for people to contribute comments and
> text for that draft. I hope it does so for the AR draft as well.
>
> =C2=B7         The statement that [I-D.ietf-mops-streaming-opcons] doesn'=
t
> cover AR applications was certainly true when that text was written (the
> first paragraph of the Introduction hasn't changed since
> draft-krishna-mops-ar-use-case-01 was submitted in October 2020, when
> draft-ietf-mops-streaming-opcons was still at -02. It's definitely worth
> revisiting how this document fits with
> https://datatracker.ietf.org/doc/draft-ietf-mops-streaming-opcons/, now
> at -07 and in WGLC.
>
> I hope this is helpful to the working group. If there are questions about
> my comments, please ask on this list - I'm at IETF 112 all week =F0=9F=99=
=82.
>
>
>
> Best,
>
>
>
> Spencer
> --
> Mops mailing list
> Mops@ietf.org
> https://www.ietf.org/mailman/listinfo/mops
>

--00000000000098000f05d5a137ec
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Dear MOPS,=C2=A0</div><div><br></div><div>Just follow=
ing up here - I know that the draft authors thanked Rohit and I for our rev=
iews during the MOPS session at IETF 112, but is anyone else sending review=
 comments to the working group?</div><div><br></div><div>Best,</div><div><b=
r></div><div>Spencer</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" c=
lass=3D"gmail_attr">On Tue, Nov 9, 2021 at 8:45 AM Rohit Abhishek &lt;<a hr=
ef=3D"mailto:rabhishek@rabhishek.com">rabhishek@rabhishek.com</a>&gt; wrote=
:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.=
8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">





<div lang=3D"EN-US" style=3D"overflow-wrap: break-word;">
<div class=3D"gmail-m_-1833884109856934390WordSection1">
<p class=3D"MsoNormal">Some comments below for the authors on section 3. <u=
></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Best Regards,<u></u><u></u></p>
<p class=3D"MsoNormal">Rohit<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(181,196,223);padding:3pt 0in 0in">
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><b><span style=3D"font-s=
ize:12pt;color:black">From:
</span></b><span style=3D"font-size:12pt;color:black">Mops &lt;<a href=3D"m=
ailto:mops-bounces@ietf.org" target=3D"_blank">mops-bounces@ietf.org</a>&gt=
; on behalf of Spencer Dawkins at IETF &lt;<a href=3D"mailto:spencerdawkins=
.ietf@gmail.com" target=3D"_blank">spencerdawkins.ietf@gmail.com</a>&gt;<br=
>
<b>Date: </b>Saturday, November 6, 2021 at 3:24 PM<br>
<b>To: </b>&quot;<a href=3D"mailto:mops@ietf.org" target=3D"_blank">mops@ie=
tf.org</a>&quot; &lt;<a href=3D"mailto:mops@ietf.org" target=3D"_blank">mop=
s@ietf.org</a>&gt;<br>
<b>Cc: </b>&quot;<a href=3D"mailto:mops-chairs@ietf.org" target=3D"_blank">=
mops-chairs@ietf.org</a>&quot; &lt;<a href=3D"mailto:mops-chairs@ietf.org" =
target=3D"_blank">mops-chairs@ietf.org</a>&gt;<br>
<b>Subject: </b>[Internet][Mops] My notes on draft-ietf-mops-ar-use-case-03=
<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><u></u>=C2=A0<u></u></p>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">Dear MOPS,<u></u><u></u>=
</p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">Leslie reminded me that =
I had volunteered to send comments on this draft at IETF 111. My apologies=
=C2=A0for getting distracted since July!=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">This draft was updated t=
o -03 a couple of=C2=A0weeks ago, so I&#39;m reviewing=C2=A0the current ver=
sion. I can&#39;t=C2=A0stress enough that I&#39;m not an AR expert, althoug=
h I have co-workers who are, so I&#39;m commenting on the draft as a
 generalist. Please read these comments as if I had ended each of them with=
 &quot;does that make=C2=A0sense?&quot;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">Here are my thoughts.=C2=
=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
<u></u><span style=3D"font-size:10pt;font-family:Symbol"><span>=C2=B7<span =
style=3D"font:7pt &quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0
</span></span></span><u></u>I think it&#39;s definitely worth thinking abou=
t AR in MOPS. The material on the use case in Section 3 seems useful for op=
erators seeking to better understand AR..=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
<u></u><span style=3D"font-size:10pt;font-family:Symbol"><span>=C2=B7<span =
style=3D"font:7pt &quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0
</span></span></span><u></u>It&#39;s worth thinking about what the scope of=
 this=C2=A0document is - the title says &quot;Augmented Reality&quot;, but =
there are scattered references to AR/VR and 360 degree streaming=C2=A0 in S=
ection 4. I suspect that most of what section 3 and section
 4 are saying about AR would be increasingly true about VR and 360-degree s=
treaming, and a variety of other applications. Perhaps this document should=
 be something like &quot;reasons to deploy edge computing&quot;, with the r=
easons not being about specific applications,
 but about the characteristics that make edge computing useful, or even cri=
tical, for successful application usage.=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
<u></u><span style=3D"font-size:10pt;font-family:Symbol"><span>=C2=B7<span =
style=3D"font:7pt &quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0
</span></span></span><u></u>It&#39;s worth thinking about who the intended =
audience for this document is. From the MOPS charter: &quot;The focus of MO=
PS is on=C2=A0identifying areas where existing protocols and/or networks ar=
e challenged by=C2=A0updated requirements&quot;. Again,
 if the scope of this document is to explain why deploying edge computing t=
o support high-bandwidth ultra-low latency applications that need to use ne=
twork computing resources, that seems squarely within the MOPS charter, and=
 Section 3 seems headed the right
 direction, but Sections 3.1, 3.2, and 4 contain a lot of details that are =
only relevant to network operators to the extent that that those details af=
fect the application&#39;s demands on the network. I don&#39;t think it mat=
ters WHY AR headsets place additional demands
 on networking and computing resources within the operator domain, it only =
matters that they do place those demands.=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"color:rgb(47,85,151)">Rohit : From wh=
at I understand, the AR headset identifies objects in real-time and then ov=
erlays a historical 3D scene on top of the
 identified object. As the user moves, the view of the 3D scene changes. So=
, when you say =E2=80=9Chistorical scenes in 3D=E2=80=9D what exactly does =
it mean ?. Does it mean a 3D video is overlaid, and it is pre-created and s=
tored somewhere in a server?. As the AR headset
 points to specific object in a scene, the respective 3D video is streamed =
onto the user=E2=80=99s headset from the database. If this is not the case,=
 then how are the 3D videos generated and what would be its content?<u></u>=
<u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
<u></u><span style=3D"font-size:10pt;font-family:Symbol"><span>=C2=B7<span =
style=3D"font:7pt &quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0
</span></span></span><u></u>Section 5, on &quot;AR Network Traffic and Inte=
raction with TCP&quot; isn&#39;t WRONG, but I=C2=A0don&#39;t think it=C2=A0=
fits in a=C2=A0MOPS document. The choice of transport protocols is still (s=
adly) up to application developers,=C2=A0and Section 5 would make sense
 if AR application developers were the target audience for this document. B=
y the time an=C2=A0AR application arrives in=C2=A0a network, the choice to =
use TCP,=C2=A0or not to use TCP, has already been made, and is largely/comp=
letely outside the operator&#39;s control.=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
<u></u><span style=3D"font-size:10pt;font-family:Symbol"><span>=C2=B7<span =
style=3D"font:7pt &quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0
</span></span></span><u></u><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
<u></u><span style=3D"font-size:10pt;font-family:Symbol"><span>=C2=B7<span =
style=3D"font:7pt &quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0
</span></span></span><u></u>This draft definitely needs more working group=
=C2=A0input, so I hope I&#39;m not the only one who sends comments!. Our ex=
perience with putting=C2=A0<a href=3D"https://www.ietf.org/archive/id/draft=
-ietf-mops-streaming-opcons-07.html" target=3D"_blank">https://www.ietf.org=
/archive/id/draft-ietf-mops-streaming-opcons-07.html</a>
 in Github definitely made it easier for people to contribute comments and =
text for that draft. I hope it does so for the AR draft as well.=C2=A0<u></=
u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:1in">
<u></u><span style=3D"font-size:10pt;font-family:Symbol"><span>=C2=B7<span =
style=3D"font:7pt &quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0
</span></span></span><u></u>The statement that=C2=A0[I-D.ietf-mops-streamin=
g-opcons] doesn&#39;t cover AR applications was certainly true when that te=
xt was written (the first paragraph of the Introduction hasn&#39;t changed =
since draft-krishna-mops-ar-use-case-01 was
 submitted in October 2020, when draft-ietf-mops-streaming-opcons was still=
 at -02. It&#39;s definitely worth revisiting how this document fits with=
=C2=A0<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-mops-streaming=
-opcons/" target=3D"_blank">https://datatracker.ietf.org/doc/draft-ietf-mop=
s-streaming-opcons/</a>,
 now at -07 and in WGLC.=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">I hope this is helpful t=
o the working group. If there are questions about my comments, please=C2=A0=
ask on this=C2=A0list - I&#39;m at IETF 112 all week=C2=A0<span style=3D"fo=
nt-family:&quot;Apple Color Emoji&quot;">=F0=9F=99=82</span>.<u></u><u></u>=
</p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">Best,=C2=A0<u></u><u></u=
></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">Spencer<u></u><u></u></p=
>
</div>
</div>
</div>
</div>

-- <br>
Mops mailing list<br>
<a href=3D"mailto:Mops@ietf.org" target=3D"_blank">Mops@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mops" rel=3D"noreferrer" t=
arget=3D"_blank">https://www.ietf.org/mailman/listinfo/mops</a><br>
</blockquote></div></div>

--00000000000098000f05d5a137ec--


From nobody Sun Jan 16 00:31:07 2022
Return-Path: <do_not_reply@mnot.net>
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 34EF63A0901 for <mops@ietfa.amsl.com>; Sun, 16 Jan 2022 00:31:05 -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, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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=mnot.net header.b=IPopFdMO; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Ct45G7v9
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 PpDXXX1wOG84 for <mops@ietfa.amsl.com>; Sun, 16 Jan 2022 00:31:00 -0800 (PST)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D8B93A08F6 for <mops@ietf.org>; Sun, 16 Jan 2022 00:31:00 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id B736D3200E42 for <mops@ietf.org>; Sun, 16 Jan 2022 02:40:25 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Sun, 16 Jan 2022 02:40:25 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:from:to:subject; s=fm1; bh=m3NlVZCnNDp q9aOgky20rXHHBaIfWRe8N7QCGyGaFFo=; b=IPopFdMOTIQDGzRou6H0vGJqYXv 17pQi6hkQzerlVAPxP6r35MbZzS1z8gnIVjHZpC7EPYhgfgsuTm71/LTGdVJrLBR cM+pwvLgaaKWlmdTz3xIZv7VCqXc5hZ9H/zKjzuYQBj/6Mnt3gXLoaXJLvztDO9J ir6gSLPveVT04/K39hEXBpWKXOGjLtEDh2rB5SpO7Z8ffw45xXNHXPONGHL14lsQ D7zpiFwKL2niFHhElNSKwAsyCISC98RBO5DaTa+ksfQxfClbGdImHSW7geg0LFSR VnkFOsdo/BbTZTMzogIPx5/o6RPET0pTQy3W44nf9Af5BoSXhXl8+RfA6rQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:from:mime-version:subject:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; bh=m3NlVZCnNDpq9aOgky20rXHHBaIfWRe8N7QCGyGaFFo=; b=Ct45G7v9 wC9nb+m2bplw47BoEDzmUreqJ4sWC8aOHLuLSQcZ/uVCIPTWnffl9wL7fY7zL63n tUEo77h3ygHYTiH/vwDpw+fGDXQv0FDQiVFqDq0/eWRk4orR4Z3lKdEXjjljp11o dUH2/Ak/uK/pLDYoPTxjlyjuGVQSW19OoLT1M/LeQDgEnpbqWazTO02pRc2fZR05 lVJNm9Fmj90Ej/+1fkd1/+BzMqkr21xYYYiB9SHntLLpW88Jc97JIrgBIzZOv7R6 YOhm0pfZ/WWIytHrHK7q2vPSuM/TL7xrzQQhuJn3CG+8qyg2qqiYeuN4FN4AohdU YofF9MOviyV6kA==
X-ME-Sender: <xms:6cvjYevyiYfZ3PpdOy_X27_mfInzCCT8A_k6Cy216LNJlaHHH7gMRA> <xme:6cvjYTeslajuQPYvxxt6C8b611HnyYMhVYBqF7Y4JpxP1g-THiL_vAroz7-RnJF-k KH1Qmz2jKzDHln0fw>
X-ME-Received: <xmr:6cvjYZwViKw2NW62SOTTx1qtJ9Ju-d8ANOW6RYe-kH7d_0zjNioft5hRBFONSMsGccnAtv2lPQHgP3sECEyjS0q6j4cv8zMo5Hst8hfgWrHTubSchxs2du5TLwBntjRP1w>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrtdekgddutdelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucfpohcuuggrthgvuchfihgvlhguucdlgeelmdenuc fjughrpegtggfhvffusegrtddtredttdejnecuhfhrohhmpeftvghpohhsihhtohhrhicu tegtthhivhhithihucfuuhhmmhgrrhihuceuohhtuceoughopghnohhtpghrvghplhihse hmnhhothdrnhgvtheqnecuggftrfgrthhtvghrnhepkeefvdduteejvdefkeehieevuefg fefhteetveegffekffefteffvdelheduieetnecuffhomhgrihhnpehgihhthhhusgdrtg homhenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegu ohgpnhhothgprhgvphhlhiesmhhnohhtrdhnvght
X-ME-Proxy: <xmx:6cvjYZPHDjK1siSkrWsbDw3JNgOw04yCH3R1WAzTu_MERQ07Ci3xxQ> <xmx:6cvjYe_PYEkHwE_T3o8Nx5lRRxfZuj8PDkAo9LSZYVEdBtvqOlfaNw> <xmx:6cvjYRXfQ6wtu0Z4ppwpu74y7YdnE6luK_oV4aoeA16nNVuj_pUsQA> <xmx:6cvjYQJM9tFIY5gXp9dEJJfP7nunemMl3ym1A5paLlb6etUFIBn1sQ>
Received: by mail.messagingengine.com (Postfix) with ESMTPA for <mops@ietf.org>; Sun, 16 Jan 2022 02:40:24 -0500 (EST)
Content-Type: multipart/alternative; boundary="===============4266363556644465561=="
MIME-Version: 1.0
From: Repository Activity Summary Bot <do_not_reply@mnot.net>
To: mops@ietf.org
Message-Id: <20220116083100.6D8B93A08F6@ietfa.amsl.com>
Date: Sun, 16 Jan 2022 00:31:00 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mops/e-icPXFtutNyFkWFsZvhJ8hqWT8>
Subject: [Mops] Weekly github digest (MOPS Activity Summary)
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, 16 Jan 2022 08:31:05 -0000

--===============4266363556644465561==
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"; format="flowed"




Events without label "editorial"



Pull requests
-------------
* ietf-wg-mops/draft-ietf-mops-streaming-opcons (+0/-1/=F0=9F=92=AC2)
  2 pull requests received 2 new comments:
  - #95 Updating acknowledgements section (1 by SpencerDawkins)
    https://github.com/ietf-wg-mops/draft-ietf-mops-streaming-opcons/pull/9=
5=20
  - #94 Update for Mike English WGLC comments on Introduction (1 by Spencer=
Dawkins)
    https://github.com/ietf-wg-mops/draft-ietf-mops-streaming-opcons/pull/9=
4=20

  1 pull requests merged:
  - Update for Mike English WGLC comments on Introduction
    https://github.com/ietf-wg-mops/draft-ietf-mops-streaming-opcons/pull/9=
4=20


Repositories tracked by this digest:
-----------------------------------
* https://github.com/ietf-wg-mops/draft-ietf-mops-streaming-opcons

--===============4266363556644465561==
Content-Type: text/html; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

<!doctype html>
<html lang=3D"en">
<head>
<meta charset=3D"utf-8">
<title>Weekly github digest (MOPS Activity Summary)</title>
<style>
body { font-family: Gotham, "Helvetica Neue", Helvetica, Arial, sans-serif;=
 font-size: 14px; }
h2 { margin-top: 3em; color: #A52A2A; font-style: italic; font-weight: norm=
al; }
h3 { margin-bottom:0; margin-top: 2em; font-size: 1.2em; }
h1+h2 { margin-top: 1em; }
a { color: #bb6219; text-decoration: none; }
li { margin-bottom: .35em; }
.repos { margin-bottom: 0; margin-top:0; line-height: 1.2; }
.new { color: red; }
.label { display: inline;
	padding: .2em .6em .3em;
	font-size: 75%;
	font-weight: 700;
	line-height: 1;
	color: #fff;
	text-align: center;
	white-space: nowrap;
	vertical-align: baseline;
	border-radius: .25em;
}
details {
	margin-top: 8em;
	}
summary {
	margin-bottom: 1em;
	cursor: pointer;
}
</style>
</head>

<body>
<h1>Sunday January 16, 2022</h1>

<p>Events without label "editorial"</p>



<h2>Pull requests</h2>
<h3>ietf-wg-mops/draft-ietf-mops-streaming-opcons (+0/-1/=F0=9F=92=AC2)</h3>

  <p>2 pull requests received 2 new comments:</p>
  <ul>
  <li>#95 <a href=3D"https://github.com/ietf-wg-mops/draft-ietf-mops-stream=
ing-opcons/pull/95">Updating acknowledgements section</a> (1 by SpencerDawk=
ins) </li>
 =20
  <li>#94 <a href=3D"https://github.com/ietf-wg-mops/draft-ietf-mops-stream=
ing-opcons/pull/94">Update for Mike English WGLC comments on Introduction</=
a> (1 by SpencerDawkins) </li>
  </ul>

  <p>1 pull requests merged:</p>
  <ul>
  <li>#94 <a href=3D"https://github.com/ietf-wg-mops/draft-ietf-mops-stream=
ing-opcons/pull/94">Update for Mike English WGLC comments on Introduction</=
a> </li>
  </ul>


  <details>
    <summary>Repositories tracked by this digest:</summary>
<ul class=3D"repos">
  <li><a href=3D"https://github.com/ietf-wg-mops/draft-ietf-mops-streaming-=
opcons">https://github.com/ietf-wg-mops/draft-ietf-mops-streaming-opcons</a=
></li>
</ul>
</details>
</body>
</html>

--===============4266363556644465561==--


From nobody Mon Jan 17 23:09:46 2022
Return-Path: <kiran.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 E996E3A0AB8; Mon, 17 Jan 2022 23:09:43 -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 rbzI66H5mSCi; Mon, 17 Jan 2022 23:09:39 -0800 (PST)
Received: from mail-pg1-x535.google.com (mail-pg1-x535.google.com [IPv6:2607:f8b0:4864:20::535]) (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 6D9403A0AB9; Mon, 17 Jan 2022 23:09:39 -0800 (PST)
Received: by mail-pg1-x535.google.com with SMTP id p125so1919870pga.2; Mon, 17 Jan 2022 23:09:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;  h=date:from:to:cc:message-id:in-reply-to:references:subject :mime-version; bh=CNy7RGrwRUpMnYtGbvum2x7EGNVcMmMYe/PSHGVWXZ4=; b=JHeEt1Z375ajqJh9t6urcD9PCi6KYcbmoOWyaEzQrV6TRyeRNZKNX6G1kdbHjt1Fop 0JzNaJH1whGInfY62/7hLtkKh+3xRahtuLVIXQEw1eq2T/RBZyFGhPSMVJ8pE/hHFu+a H0ENR6gBVhsH8X1NQYdUeGZLNAWeh7TKrUfQwQABqHV17HvDzIwfIxv6vmwhu7SMv2U6 1WQbGjkByCq/04hruNqii/WaeiR174jpIEeBvn+HxPSuxQaD/f0aspxg0fRyShqdZnwl L07iN1nYP9LO2k5w5CySn60PTfkKxeTn1DKckL95t6PkrOZn+6LmjN7KT/qKF3ajyKA7 +Trg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:message-id:in-reply-to :references:subject:mime-version; bh=CNy7RGrwRUpMnYtGbvum2x7EGNVcMmMYe/PSHGVWXZ4=; b=dZL/Q3l0Au2xiCf1+TXI1qGK2J+N/PetKPUUFgF73vQ5EAZl8t1NFxFs2+Gmvqupa9 teXw47piZPYYZ7J1OIFDz8StW+lz3D0CuWFPtoO19GXP+MILGpjFVfYqR13xUK2xSs7V UeGUjPAntQRkfFSvQJ4jjZknmie9QlknW53TZpClqywj79TMApinV6QvhE07t9F4zdc3 lcEz/jGATb3gnbVSB5mjbXNgdbBWbnJa72Ej/0luc+yvD3IJBtO9gbaZMIKmgIMLLAkx F/CAWcg4a0Smk+tdobOYO6ZH6cPNNfspDXBzXdrBnrocZNAwibm5vsQTyNwNDhoCclX3 M7Aw==
X-Gm-Message-State: AOAM532b5b46lIFOwWJFnIbDejzTp4aeNRcyOZkm+N9Gu4l3CEwNLDea 9BqmVafU2ku8D5QG7u91NY83InAeDmY=
X-Google-Smtp-Source: ABdhPJwO1Wf51lHNbz+hPDBtT3BxFP8P+03DbOXkwMdPRm8CKCQ8F/LaOhVGUbANg+XynTu0DeqksQ==
X-Received: by 2002:aa7:904d:0:b0:4bc:a970:be1 with SMTP id n13-20020aa7904d000000b004bca9700be1mr24852038pfo.65.1642489777472;  Mon, 17 Jan 2022 23:09:37 -0800 (PST)
Received: from Patagonia.local (c-73-202-182-183.hsd1.ca.comcast.net. [73.202.182.183]) by smtp.gmail.com with ESMTPSA id s7sm17456918pfu.133.2022.01.17.23.09.36 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 17 Jan 2022 23:09:37 -0800 (PST)
Date: Mon, 17 Jan 2022 23:09:36 -0800
From: Kiran Makhijani <kiran.ietf@gmail.com>
To: "=?utf-8?Q?mops=40ietf.org?=" <mops@ietf.org>
Cc: "=?utf-8?Q?mops-chairs=40ietf.org?=" <mops-chairs@ietf.org>, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Message-ID: <C68D4F1D-5365-4728-A59D-C918BB678077@getmailspring.com>
In-Reply-To: <CAKKJt-e78BMmKQ2nWr18z8WiCtnOFba2xLsPvwyFT9Wwrx1CmQ@mail.gmail.com>
References: <CAKKJt-e78BMmKQ2nWr18z8WiCtnOFba2xLsPvwyFT9Wwrx1CmQ@mail.gmail.com>
X-Mailer: Mailspring
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="61e667b0_327b23c6_3c6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mops/NHmFXYt873dnWuJIQGcXtZc7Ecg>
Subject: Re: [Mops] [Internet] My notes on draft-ietf-mops-ar-use-case-03
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, 18 Jan 2022 07:09:44 -0000

--61e667b0_327b23c6_3c6
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline


Hello Authors,
I went through the document out of interest in the topic and I am no expe=
rt in AR. Spencer's comments are very valid. I also felt there there are =
two or three different things going on in the document - edge compute rel=
evance, processing-overheads and ABR.
Of these ABR discussion may be worth exploring more. =46or example, the t=
olerance to packet loss is not covered as a requirement. Is there a requi=
rement or should it be to change data rates in order prevent packet loss.=
 I was also curious to know will there be a requirement on chunk sizes of=
 a stream=3F Since headsets do not have a lot of buffering capability and=
 the field of view will change quickly, would you recommend chunk (or seg=
ment) durations to be shorter=3F I guess another requirement to explore w=
ill be will there be more than one stream sent to the headset if some mov=
ement prediction is used=3F In that case do bit-rates for those streams n=
eed to match. Last one - bit-rate negotiation may be initiated by the hea=
dset because they may have different capabilities (processing, buffering =
). Basically, getting into the streaming specific section will be more in=
teresting to me.

Some other nits:
in section 3.1, when you say mobile device do you really mean headset=3F

You have used terms like situated visualization, temporal coherence, natu=
ral features, lack of visual features in the grid environment - none of t=
hese were immediately obvious to me. perhaps define them for casual reade=
rs/newbies.

chapter 4, first bullet - what type of AI/ML processing will be needed.

Hope this helps.
Cheers
Kiran
On Jan 15 2022, at 8:14 am, Spencer Dawkins at IET=46 <spencerdawkins.iet=
f=40gmail.com> wrote:
> Dear MOPS,
>
> Just following up here - I know that the draft authors thanked Rohit an=
d I for our reviews during the MOPS session at IET=46 112, but is anyone =
else sending review comments to the working group=3F
>
> Best,
>
> Spencer
> On Tue, Nov 9, 2021 at 8:45 AM Rohit Abhishek <rabhishek=40rabhishek.co=
m (mailto:rabhishek=40rabhishek.com)> wrote:
> > Some comments below for the authors on section 3.
> >
> >
> > Best Regards,
> > Rohit
> >
> > =46rom: Mops <mops-bounces=40ietf.org (mailto:mops-bounces=40ietf.org=
)> on behalf of Spencer Dawkins at IET=46 <spencerdawkins.ietf=40gmail.co=
m (mailto:spencerdawkins.ietf=40gmail.com)>
> > Date: Saturday, November 6, 2021 at 3:24 PM
> > To: =22mops=40ietf.org (mailto:mops=40ietf.org)=22 <mops=40ietf.org (=
mailto:mops=40ietf.org)>
> > Cc: =22mops-chairs=40ietf.org (mailto:mops-chairs=40ietf.org)=22 <mop=
s-chairs=40ietf.org (mailto:mops-chairs=40ietf.org)>
> > Subject: =5BInternet=5D=5BMops=5D My notes on draft-ietf-mops-ar-use-=
case-03
> >
> >
> >
> >
> > Dear MOPS,
> >
> >
> >
> > Leslie reminded me that I had volunteered to send comments on this dr=
aft at IET=46 111. My apologies for getting distracted since July=21
> >
> >
> >
> > This draft was updated to -03 a couple of weeks ago, so I'm reviewing=
 the current version. I can't stress enough that I'm not an AR expert, al=
though I have co-workers who are, so I'm commenting on the draft as a gen=
eralist. Please read these comments as if I had ended each of them with =22=
does that make sense=3F=22
> >
> >
> >
> > Here are my thoughts.
> >
> > =C2=B7 I think it's definitely worth thinking about AR in MOPS. The m=
aterial on the use case in Section 3 seems useful for operators seeking t=
o better understand AR..
> >
> > =C2=B7 It's worth thinking about what the scope of this document is -=
 the title says =22Augmented Reality=22, but there are scattered referenc=
es to AR/VR and 360 degree streaming in Section 4. I suspect that most of=
 what section 3 and section 4 are saying about AR would be increasingly t=
rue about VR and 360-degree streaming, and a variety of other application=
s. Perhaps this document should be something like =22reasons to deploy ed=
ge computing=22, with the reasons not being about specific applications, =
but about the characteristics that make edge computing useful, or even cr=
itical, for successful application usage.
> > =C2=B7 It's worth thinking about who the intended audience for this d=
ocument is. =46rom the MOPS charter: =22The focus of MOPS is on identifyi=
ng areas where existing protocols and/or networks are challenged by updat=
ed requirements=22. Again, if the scope of this document is to explain wh=
y deploying edge computing to support high-bandwidth ultra-low latency ap=
plications that need to use network computing resources, that seems squar=
ely within the MOPS charter, and Section 3 seems headed the right directi=
on, but Sections 3.1, 3.2, and 4 contain a lot of details that are only r=
elevant to network operators to the extent that that those details affect=
 the application's demands on the network. I don't think it matters WHY A=
R headsets place additional demands on networking and computing resources=
 within the operator domain, it only matters that they do place those dem=
ands.
> > Rohit : =46rom what I understand, the AR headset identifies objects i=
n real-time and then overlays a historical 3D scene on top of the identif=
ied object. As the user moves, the view of the 3D scene changes. So, when=
 you say =E2=80=9Chistorical scenes in 3D=E2=80=9D what exactly does it m=
ean =3F. Does it mean a 3D video is overlaid, and it is pre-created and s=
tored somewhere in a server=3F. As the AR headset points to specific obje=
ct in a scene, the respective 3D video is streamed onto the user=E2=80=99=
s headset from the database. If this is not the case, then how are the 3D=
 videos generated and what would be its content=3F
> > =C2=B7 Section 5, on =22AR Network Traffic and Interaction with TCP=22=
 isn't WRONG, but I don't think it fits in a MOPS document. The choice of=
 transport protocols is still (sadly) up to application developers, and S=
ection 5 would make sense if AR application developers were the target au=
dience for this document. By the time an AR application arrives in a netw=
ork, the choice to use TCP, or not to use TCP, has already been made, and=
 is largely/completely outside the operator's control.
> > =C2=B7
> > =C2=B7 This draft definitely needs more working group input, so I hop=
e I'm not the only one who sends comments=21. Our experience with putting=
 https://www.ietf.org/archive/id/draft-ietf-mops-streaming-opcons-07.html=
 in Github definitely made it easier for people to contribute comments an=
d text for that draft. I hope it does so for the AR draft as well.
> > =C2=B7 The statement that =5BI-D.ietf-mops-streaming-opcons=5D doesn'=
t cover AR applications was certainly true when that text was written (th=
e first paragraph of the Introduction hasn't changed since draft-krishna-=
mops-ar-use-case-01 was submitted in October 2020, when draft-ietf-mops-s=
treaming-opcons was still at -02. It's definitely worth revisiting how th=
is document fits with https://datatracker.ietf.org/doc/draft-ietf-mops-st=
reaming-opcons/, now at -07 and in WGLC.
> > I hope this is helpful to the working group. If there are questions a=
bout my comments, please ask on this list - I'm at IET=46 112 all week =F0=
=9F=99=82.
> >
> >
> > Best,
> >
> >
> >
> > Spencer
> >
> >
> >
> >
> > --
> > Mops mailing list
> > Mops=40ietf.org (mailto:Mops=40ietf.org)
> > https://www.ietf.org/mailman/listinfo/mops
>
>
>
> --
> Mops mailing list
> Mops=40ietf.org
> https://www.ietf.org/mailman/listinfo/mops


--61e667b0_327b23c6_3c6
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<br><div>Hello Authors,</div><div>I went through the document out of inte=
rest in the topic and I am no expert in AR. Spencer's comments are very v=
alid. I also felt there there are two or three different things going on =
in the document - edge compute relevance, processing-overheads and ABR.</=
div><div>Of these ABR discussion may be worth exploring more. =46or examp=
le, the tolerance to packet loss is not covered as a requirement. Is ther=
e a requirement or should it be to change data rates in order prevent pac=
ket loss. I was also curious to know will there be a requirement on chunk=
 sizes of a stream=3F Since&nbsp; headsets do not have a lot of buffering=
 capability and the field of view will change&nbsp; quickly, would you re=
commend chunk (or segment) durations to be shorter=3F I guess another req=
uirement to explore will be will there be more than one&nbsp; stream sent=
 to the headset if&nbsp; some movement prediction is used=3F In that case=
 do bit-rates for those streams need to match. Last one - bit-rate negoti=
ation may be initiated&nbsp; by the headset because they may have differe=
nt capabilities (processing, buffering ). Basically, getting into the str=
eaming specific section will be more interesting to me.</div><br><div>Som=
e other nits:&nbsp;</div><ul><li><div>in section 3.1, when you say mobile=
 device do you really mean headset=3F</div></li><li><div>You have used te=
rms like situated visualization, temporal coherence, natural features, la=
ck of visual features in the grid environment - none of these were immedi=
ately obvious to me. perhaps define them for casual readers/newbies.</div=
></li><li><div>chapter 4, first bullet - what type of AI/ML&nbsp; process=
ing will be needed.</div></li></ul><div>Hope this helps.</div><div>Cheers=
</div><div>Kiran</div><div class=3D=22gmail=5Fquote=5Fattribution=22>On J=
an 15 2022, at 8:14 am, Spencer Dawkins at IET=46 &lt;spencerdawkins.ietf=
=40gmail.com&gt; wrote:</div><blockquote><div><div>Dear MOPS,&nbsp;</div>=
<div><br></div><div>Just following up here - I know that the draft author=
s thanked Rohit and I for our reviews during the MOPS session at IET=46 1=
12, but is anyone else sending review comments to the working group=3F</d=
iv><div><br></div><div>Best,</div><div><br></div><div>Spencer</div><br><d=
iv class=3D=22gmail=5Fquote=22><div class=3D=22gmail=5Fattr=22><div>On Tu=
e, Nov 9, 2021 at 8:45 AM Rohit Abhishek &lt;<a href=3D=22mailto:rabhishe=
k=40rabhishek.com=22 title=3D=22mailto:rabhishek=40rabhishek.com=22>rabhi=
shek=40rabhishek.com</a>&gt; wrote:</div></div><blockquote><div><div clas=
s=3D=22gmail-m=5F-1833884109856934390WordSection1=22><div class=3D=22MsoN=
ormal=22>Some comments below for the authors on section 3.</div><br><div =
class=3D=22MsoNormal=22>&nbsp;</div><br><div class=3D=22MsoNormal=22>Best=
 Regards,</div><br><div class=3D=22MsoNormal=22>Rohit</div><br><div class=
=3D=22MsoNormal=22>&nbsp;</div><br><div><div class=3D=22MsoNormal=22><div=
><strong><font style=3D=22font-size:12pt=22>=46rom: </font></strong><font=
 style=3D=22font-size:12pt=22>Mops &lt;</font><font style=3D=22font-size:=
12pt=22><a href=3D=22mailto:mops-bounces=40ietf.org=22 title=3D=22mailto:=
mops-bounces=40ietf.org=22>mops-bounces=40ietf.org</a></font><font style=3D=
=22font-size:12pt=22>&gt; on behalf of Spencer Dawkins at IET=46 &lt;</fo=
nt><font style=3D=22font-size:12pt=22><a href=3D=22mailto:spencerdawkins.=
ietf=40gmail.com=22 title=3D=22mailto:spencerdawkins.ietf=40gmail.com=22>=
spencerdawkins.ietf=40gmail.com</a></font><font style=3D=22font-size:12pt=
=22>&gt;</font></div><div><font style=3D=22font-size:12pt=22><strong>Date=
: </strong></font><font style=3D=22font-size:12pt=22>Saturday, November 6=
, 2021 at 3:24 PM</font></div><div><font style=3D=22font-size:12pt=22><st=
rong>To: </strong></font><font style=3D=22font-size:12pt=22>=22</font><fo=
nt style=3D=22font-size:12pt=22><a href=3D=22mailto:mops=40ietf.org=22 ti=
tle=3D=22mailto:mops=40ietf.org=22>mops=40ietf.org</a></font><font style=3D=
=22font-size:12pt=22>=22 &lt;</font><font style=3D=22font-size:12pt=22><a=
 href=3D=22mailto:mops=40ietf.org=22 title=3D=22mailto:mops=40ietf.org=22=
>mops=40ietf.org</a></font><font style=3D=22font-size:12pt=22>&gt;</font>=
</div><div><font style=3D=22font-size:12pt=22><strong>Cc: </strong></font=
><font style=3D=22font-size:12pt=22>=22</font><font style=3D=22font-size:=
12pt=22><a href=3D=22mailto:mops-chairs=40ietf.org=22 title=3D=22mailto:m=
ops-chairs=40ietf.org=22>mops-chairs=40ietf.org</a></font><font style=3D=22=
font-size:12pt=22>=22 &lt;</font><font style=3D=22font-size:12pt=22><a hr=
ef=3D=22mailto:mops-chairs=40ietf.org=22 title=3D=22mailto:mops-chairs=40=
ietf.org=22>mops-chairs=40ietf.org</a></font><font style=3D=22font-size:1=
2pt=22>&gt;</font></div><div><font style=3D=22font-size:12pt=22><strong>S=
ubject: </strong></font><font style=3D=22font-size:12pt=22>=5BInternet=5D=
=5BMops=5D My notes on draft-ietf-mops-ar-use-case-03</font></div></div><=
/div><div><div class=3D=22MsoNormal=22>&nbsp;</div></div><div><div><div c=
lass=3D=22MsoNormal=22>Dear MOPS,</div></div><div><div class=3D=22MsoNorm=
al=22>&nbsp;</div></div><div><div class=3D=22MsoNormal=22>Leslie reminded=
 me that I had volunteered to send comments on this draft at IET=46 111. =
My apologies&nbsp;for getting distracted since July=21&nbsp;</div></div><=
div><div class=3D=22MsoNormal=22>&nbsp;</div></div><div><div class=3D=22M=
soNormal=22>This draft was updated to -03 a couple of&nbsp;weeks ago, so =
I'm reviewing&nbsp;the current version. I can't&nbsp;stress enough that I=
'm not an AR expert, although I have co-workers who are, so I'm commentin=
g on the draft as a generalist. Please read these comments as if I had en=
ded each of them with =22does that make&nbsp;sense=3F=22</div></div><div>=
<div class=3D=22MsoNormal=22>&nbsp;</div></div><div><div class=3D=22MsoNo=
rmal=22>Here are my thoughts.&nbsp;</div></div><div><div class=3D=22MsoNo=
rmal=22><font style=3D=22font-size:10pt=22><font style=3D=22font-family:S=
ymbol=22>=C2=B7</font></font><font style=3D=22font-size:10pt=22><font sty=
le=3D=22font-family:Symbol=22><font style=3D=22font-size:7pt=22><font sty=
le=3D=22font-family:&quot;Times New Roman&quot;=22>&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; </font></font></font></font>I think it's defin=
itely worth thinking about AR in MOPS. The material on the use case in Se=
ction 3 seems useful for operators seeking to better understand AR..&nbsp=
;</div><br><div class=3D=22MsoNormal=22><font style=3D=22font-size:10pt=22=
><font style=3D=22font-family:Symbol=22>=C2=B7</font></font><font style=3D=
=22font-size:10pt=22><font style=3D=22font-family:Symbol=22><font style=3D=
=22font-size:7pt=22><font style=3D=22font-family:&quot;Times New Roman&qu=
ot;=22>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </font></font></f=
ont></font>It's worth thinking about what the scope of this&nbsp;document=
 is - the title says =22Augmented Reality=22, but there are scattered ref=
erences to AR/VR and 360 degree streaming&nbsp; in Section 4. I suspect t=
hat most of what section 3 and section 4 are saying about AR would be inc=
reasingly true about VR and 360-degree streaming, and a variety of other =
applications. Perhaps this document should be something like =22reasons t=
o deploy edge computing=22, with the reasons not being about specific app=
lications, but about the characteristics that make edge computing useful,=
 or even critical, for successful application usage.&nbsp;</div><br><div =
class=3D=22MsoNormal=22><font style=3D=22font-size:10pt=22><font style=3D=
=22font-family:Symbol=22>=C2=B7</font></font><font style=3D=22font-size:1=
0pt=22><font style=3D=22font-family:Symbol=22><font style=3D=22font-size:=
7pt=22><font style=3D=22font-family:&quot;Times New Roman&quot;=22>&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </font></font></font></font>It=
's worth thinking about who the intended audience for this document is. =46=
rom the MOPS charter: =22The focus of MOPS is on&nbsp;identifying areas w=
here existing protocols and/or networks are challenged by&nbsp;updated re=
quirements=22. Again, if the scope of this document is to explain why dep=
loying edge computing to support high-bandwidth ultra-low latency applica=
tions that need to use network computing resources, that seems squarely w=
ithin the MOPS charter, and Section 3 seems headed the right direction, b=
ut Sections 3.1, 3.2, and 4 contain a lot of details that are only releva=
nt to network operators to the extent that that those details affect the =
application's demands on the network. I don't think it matters WHY AR hea=
dsets place additional demands on networking and computing resources with=
in the operator domain, it only matters that they do place those demands.=
&nbsp;</div><br><div class=3D=22MsoNormal=22><span style=3D=22color:rgb(4=
7, 85, 151)=22>Rohit : =46rom what I understand, the AR headset identifie=
s objects in real-time and then overlays a historical 3D scene on top of =
the identified object. As the user moves, the view of the 3D scene change=
s. So, when you say =E2=80=9Chistorical scenes in 3D=E2=80=9D what exactl=
y does it mean =3F. Does it mean a 3D video is overlaid, and it is pre-cr=
eated and stored somewhere in a server=3F. As the AR headset points to sp=
ecific object in a scene, the respective 3D video is streamed onto the us=
er=E2=80=99s headset from the database. If this is not the case, then how=
 are the 3D videos generated and what would be its content=3F</span></div=
><br><div class=3D=22MsoNormal=22><font style=3D=22font-size:10pt=22><fon=
t style=3D=22font-family:Symbol=22>=C2=B7</font></font><font style=3D=22f=
ont-size:10pt=22><font style=3D=22font-family:Symbol=22><font style=3D=22=
font-size:7pt=22><font style=3D=22font-family:&quot;Times New Roman&quot;=
=22>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </font></font></font=
></font>Section 5, on =22AR Network Traffic and Interaction with TCP=22 i=
sn't WRONG, but I&nbsp;don't think it&nbsp;fits in a&nbsp;MOPS document. =
The choice of transport protocols is still (sadly) up to application deve=
lopers,&nbsp;and Section 5 would make sense if AR application developers =
were the target audience for this document. By the time an&nbsp;AR applic=
ation arrives in&nbsp;a network, the choice to use TCP,&nbsp;or not to us=
e TCP, has already been made, and is largely/completely outside the opera=
tor's control.&nbsp;</div><br><div class=3D=22MsoNormal=22><font style=3D=
=22font-size:10pt=22><font style=3D=22font-family:Symbol=22>=C2=B7</font>=
</font><font style=3D=22font-size:10pt=22><font style=3D=22font-family:Sy=
mbol=22><font style=3D=22font-size:7pt=22><font style=3D=22font-family:&q=
uot;Times New Roman&quot;=22>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; </font></font></font></font>&nbsp;</div><br><div class=3D=22MsoNorma=
l=22><font style=3D=22font-size:10pt=22><font style=3D=22font-family:Symb=
ol=22>=C2=B7</font></font><font style=3D=22font-size:10pt=22><font style=3D=
=22font-family:Symbol=22><font style=3D=22font-size:7pt=22><font style=3D=
=22font-family:&quot;Times New Roman&quot;=22>&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; </font></font></font></font>This draft definitely n=
eeds more working group&nbsp;input, so I hope I'm not the only one who se=
nds comments=21. Our experience with putting&nbsp;<a href=3D=22https://ww=
w.ietf.org/archive/id/draft-ietf-mops-streaming-opcons-07.html=22 title=3D=
=22https://www.ietf.org/archive/id/draft-ietf-mops-streaming-opcons-07.ht=
ml=22>https://www.ietf.org/archive/id/draft-ietf-mops-streaming-opcons-07=
.html</a>&nbsp;in Github definitely made it easier for people to contribu=
te comments and text for that draft. I hope it does so for the AR draft a=
s well.&nbsp;</div><br><div class=3D=22MsoNormal=22><font style=3D=22font=
-size:10pt=22><font style=3D=22font-family:Symbol=22>=C2=B7</font></font>=
<font style=3D=22font-size:10pt=22><font style=3D=22font-family:Symbol=22=
><font style=3D=22font-size:7pt=22><font style=3D=22font-family:&quot;Tim=
es New Roman&quot;=22>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </=
font></font></font></font>The statement that&nbsp;=5BI-D.ietf-mops-stream=
ing-opcons=5D doesn't cover AR applications was certainly true when that =
text was written (the first paragraph of the Introduction hasn't changed =
since draft-krishna-mops-ar-use-case-01 was submitted in October 2020, wh=
en draft-ietf-mops-streaming-opcons was still at -02. It's definitely wor=
th revisiting how this document fits with&nbsp;<a href=3D=22https://datat=
racker.ietf.org/doc/draft-ietf-mops-streaming-opcons/=22 title=3D=22https=
://datatracker.ietf.org/doc/draft-ietf-mops-streaming-opcons/=22>https://=
datatracker.ietf.org/doc/draft-ietf-mops-streaming-opcons/</a>, now at -0=
7 and in WGLC.&nbsp;</div><br><div class=3D=22MsoNormal=22>I hope this is=
 helpful to the working group. If there are questions about my comments, =
please&nbsp;ask on this&nbsp;list - I'm at IET=46 112 all week&nbsp;<font=
 style=3D=22font-family:&quot;Apple Color Emoji&quot;=22>=F0=9F=99=82</fo=
nt>.</div></div><div><div class=3D=22MsoNormal=22>&nbsp;</div></div><div>=
<div class=3D=22MsoNormal=22>Best,&nbsp;</div></div><div><div class=3D=22=
MsoNormal=22>&nbsp;</div></div><div><div class=3D=22MsoNormal=22>Spencer<=
/div></div></div></div></div><div>--</div><div>Mops mailing list</div><di=
v><a href=3D=22mailto:Mops=40ietf.org=22 title=3D=22mailto:Mops=40ietf.or=
g=22>Mops=40ietf.org</a></div><div><a href=3D=22https://www.ietf.org/mail=
man/listinfo/mops=22 title=3D=22https://www.ietf.org/mailman/listinfo/mop=
s=22>https://www.ietf.org/mailman/listinfo/mops</a></div></blockquote></d=
iv></div><div>--</div><div>Mops mailing list</div><div>Mops=40ietf.org</d=
iv><div>https://www.ietf.org/mailman/listinfo/mops</div></blockquote>
--61e667b0_327b23c6_3c6--


From nobody Tue Jan 18 10:15:04 2022
Return-Path: <ali.begen@networked.media>
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 861463A0B46 for <mops@ietfa.amsl.com>; Tue, 18 Jan 2022 10:15:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=networked.media
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 9PYYNWlmz13E for <mops@ietfa.amsl.com>; Tue, 18 Jan 2022 10:14:58 -0800 (PST)
Received: from mail-lf1-x12c.google.com (mail-lf1-x12c.google.com [IPv6:2a00:1450:4864:20::12c]) (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 03DEB3A0B47 for <mops@ietf.org>; Tue, 18 Jan 2022 10:14:57 -0800 (PST)
Received: by mail-lf1-x12c.google.com with SMTP id bu18so51127948lfb.5 for <mops@ietf.org>; Tue, 18 Jan 2022 10:14:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networked.media; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=eKZUjBYIvZ+ODuA0N6uU+ZQp2OFH++xxuJDsOdmaHT4=; b=cXxD5seRzaaca2JDAoBDcze58VpOhelVRttWWdq+mO/uaKUAOcSXWvqpiGxCBesVI4 nda1hCWvuybz043fpbcvq+PjZMeyTb8PZKVawXkz4EsfZ+ZQ8YIOi1AQgo5dbhHqp5D8 vmka5fH6pBI4mHiCRUMkvTzIoH6De4O/SFUWMvhLgoy+meyVum3R6er8ZudNflhQpG2y Ena0Epw5p1cKjU4H2JsBFZVwXlObMZPHwTndUp9vsdYFCllBxW2+3Dx03iQ9Bbd2DV+J i6VBdX8QhDr3MPa7u66xqU/QytsR8NN2fQ/Sq2kJmGIWce35NEcBYmrwNogO7WgYuKCD DW7g==
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=eKZUjBYIvZ+ODuA0N6uU+ZQp2OFH++xxuJDsOdmaHT4=; b=pPNDkIsFBbTIctgNnfmCUiaAMRx7MjXg/Secb2/KKFI4M3PFAPDTbySHj4Q7fJxa6A FnyfkO0tQZQTeNlnQ6uCd4sjYoZBgiHrwZSe3EUmexrSQFliVqCRwtNnL3Acrz5OJDWI n+LQCEqEXJz5g4Uxm8Cpn/DeFZTZVY71WrT19KvPdk3vRNBdAFJgbGk8uMxEmsUQoGnt V/t9CyY6gzMG40GY3VrdUg8Fqh56OvR/QhaqPpns6mJdlEcgvKHeZVmVtrl/F3vA1osW EiXrfHHBC/0dwVErG2n3pc2+1gQjnqPgklgS4QOvmm5nkrGOzzeWvd/9JD3yrYQpSz3c pPXg==
X-Gm-Message-State: AOAM531I/efOukl4lpdqKWtX9qkrRTVHJub+nl8aMSsekK9szMrHQoyJ geMyIcEZidJaLiK8Z7lKCG2LDd/pQOepwNtNKxis2g==
X-Google-Smtp-Source: ABdhPJwUQyIDB+WylMhvFXt2LzEQ6OTGGlsOWFrFBCYH+Nuei8y5OFCMlQvfz5vh5wajANo1yMVVblPH8kTkVDvSaVE=
X-Received: by 2002:a19:c50c:: with SMTP id w12mr22348591lfe.532.1642529694397;  Tue, 18 Jan 2022 10:14:54 -0800 (PST)
MIME-Version: 1.0
References: <CAKKJt-e78BMmKQ2nWr18z8WiCtnOFba2xLsPvwyFT9Wwrx1CmQ@mail.gmail.com> <C68D4F1D-5365-4728-A59D-C918BB678077@getmailspring.com>
In-Reply-To: <C68D4F1D-5365-4728-A59D-C918BB678077@getmailspring.com>
From: "Ali C. Begen" <ali.begen@networked.media>
Date: Tue, 18 Jan 2022 21:14:43 +0300
Message-ID: <CAA4Mczvd5wfBWOciJCofn01onSuPVLw=AfUyHmpjqrkL+bRYTw@mail.gmail.com>
To: Kiran Makhijani <kiran.ietf@gmail.com>
Cc: "mops@ietf.org" <mops@ietf.org>, "mops-chairs@ietf.org" <mops-chairs@ietf.org>,  Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000f7cce405d5df3efe"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mops/-5wuqbWQflU5RMhGKwra1fWwMSM>
Subject: Re: [Mops] [Internet] My notes on draft-ietf-mops-ar-use-case-03
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, 18 Jan 2022 18:15:03 -0000

--000000000000f7cce405d5df3efe
Content-Type: text/plain; charset="UTF-8"

I am not an author of this draft, but wanted to provide some input:

Of these ABR discussion may be worth exploring more. For example, the
> tolerance to packet loss is not covered as a requirement. Is there a
> requirement or should it be to change data rates in order prevent packet
> loss.
>

Well considering the HTTP-based adaptive streaming (ABR as you call it),
there is no tolerance to packet loss per se since media is almost always
carried over TCP (does not have to be but it is what it is). So, there is
no such thing as tolerance to packet loss in the ABR domain. Rather as the
throughput achieved by the transport varies (plus some other factors), the
streaming clients adapt by picking a different version of the watched
content.


> I was also curious to know will there be a requirement on chunk sizes of a
> stream?
>

Chunk/segment sizes depend on two things: encoding bitrate (target) and
chunk/segment duration. There are pros and cons for large/small sizes (and
long/short) durations. The ABR survey paper cited in the opcons draft
touches on this issue. But at the end, it does not (and cannot) draw
requirements.


> Since  headsets do not have a lot of buffering capability and the field of
> view will change  quickly, would you recommend chunk (or segment) durations
> to be shorter?
>

Since the viewport may change at any time, unless you are fetching and
storing the whole 360 video (very unlikely), you will never want to keep
several seconds worth of media on the device anyway. So, this means your
segments will have to be shorter compared to the case of traditional/non-VR
content.


> I guess another requirement to explore will be will there be more than
> one  stream sent to the headset if  some movement prediction is used?
>

If you are referring to the viewport-dependent delivery or tiled streaming,
the 360 video will be transmitted over multiple streams like the viewport
being streamed in high quality and other parts being streamed in low
quality. If viewport prediction is used, you may certainly fetch some of
the parts (tiles) in high quality, too, in the anticipation that those
parts will be viewed by the user. They may be streamed over an existing
stream or a new one. This depends on the tiling scheme, your HTTP version
and such.


> In that case do bit-rates for those streams need to match.
>

No, it is entirely up to your preference (ABR algorithm). As a matter of
fact, we have an ongoing study looking into all these things and it is in
the review process. When it gets published, I will be happy to share the
results.


> Last one - bit-rate negotiation may be initiated  by the headset because
> they may have different capabilities (processing, buffering ). Basically,
> getting into the streaming specific section will be more interesting to me.
>

Client-driven ABR gives you this capability already. The client on your
headset should determine/know what it can do or cannot do. The server is
only offering what is available, it is the client's responsibility to get
the right thing.

While at it, I would like to ask the authors to reconsider touching on the
generic ABR related matters, which are already detailed in the opcons draft
and frankly, only the AR/VR specific details should be kept in this draft.
That will ease the reading and reduce any potential confusion.

-acbegen

--000000000000f7cce405d5df3efe
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>I am not an author of this draft, but wanted to provi=
de some input:</div><div><br></div><div class=3D"gmail_quote"><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px soli=
d rgb(204,204,204);padding-left:1ex"><div>Of these ABR discussion may be wo=
rth exploring more. For example, the tolerance to packet loss is not covere=
d as a requirement. Is there a requirement or should it be to change data r=
ates in order prevent packet loss. </div></blockquote><div><br></div><div>W=
ell considering the HTTP-based adaptive streaming (ABR as you call it), the=
re is no tolerance to packet loss per se since media is almost always carri=
ed over TCP (does not have to be but it is what it is). So, there is no suc=
h thing as tolerance to packet loss in the ABR domain. Rather as the throug=
hput achieved by the transport varies (plus some other factors), the stream=
ing clients adapt by picking a different version of the watched content.=C2=
=A0=C2=A0</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-lef=
t:1ex"><div>I was also curious to know will there be a requirement on chunk=
 sizes of a stream? </div></blockquote><div><br></div><div>Chunk/segment si=
zes depend on two things: encoding bitrate (target) and chunk/segment durat=
ion. There are pros and cons for large/small sizes (and long/short) duratio=
ns. The ABR survey paper cited in the opcons draft touches on this issue. B=
ut at the end, it does not (and cannot) draw requirements.</div><div>=C2=A0=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex"><div>Since=C2=A0 he=
adsets do not have a lot of buffering capability and the field of view will=
 change=C2=A0 quickly, would you recommend chunk (or segment) durations to =
be shorter? </div></blockquote><div><br></div><div>Since the viewport may c=
hange at any time, unless you are fetching and storing the whole 360 video =
(very unlikely), you will never want to keep several seconds worth of media=
 on the device anyway. So, this means your segments will have to be shorter=
 compared to the case of traditional/non-VR content.=C2=A0</div><div>=C2=A0=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex"><div>I guess anothe=
r requirement to explore will be will there be more than one=C2=A0 stream s=
ent to the headset if=C2=A0 some movement prediction is used? </div></block=
quote><div><br></div><div>If you are referring to the viewport-dependent de=
livery or tiled streaming, the 360 video will be transmitted over multiple =
streams like the viewport being streamed in high quality and other parts be=
ing streamed in low quality. If viewport prediction is used, you may certai=
nly fetch some of the parts (tiles) in high quality, too, in the anticipati=
on that those parts will be viewed by the user. They may be streamed over a=
n existing stream or a new one. This depends on the tiling scheme, your HTT=
P version and such.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote"=
 style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);p=
adding-left:1ex"><div>In that case do bit-rates for those streams need to m=
atch. </div></blockquote><div><br></div><div>No, it is entirely up to your =
preference (ABR algorithm). As a matter of fact, we have an ongoing study l=
ooking into all these things and it is in the review process. When it gets =
published, I will be happy to share the results.</div><div>=C2=A0</div><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left=
:1px solid rgb(204,204,204);padding-left:1ex"><div>Last one - bit-rate nego=
tiation may be initiated=C2=A0 by the headset because they may have differe=
nt capabilities (processing, buffering ). Basically, getting into the strea=
ming specific section will be more interesting to me.</div></blockquote><di=
v><br></div><div>Client-driven ABR gives you this capability already. The c=
lient on your headset should determine/know what it can do or cannot do. Th=
e server is only offering what is available, it is the client&#39;s respons=
ibility to get the right thing.</div><div><br></div><div>While at it, I wou=
ld like to ask the authors to reconsider touching on the generic ABR relate=
d matters, which are already detailed in the opcons draft and frankly, only=
 the AR/VR specific details should be kept in this draft. That will ease th=
e reading and reduce any potential confusion.</div><div><br></div><div>-acb=
egen</div></div></div>

--000000000000f7cce405d5df3efe--


From nobody Thu Jan 20 16:01:48 2022
Return-Path: <ldaigle@thinkingcat.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 EBCDB3A0120; Thu, 20 Jan 2022 16:01:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.096
X-Spam-Level: 
X-Spam-Status: No, score=-7.096 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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 (1024-bit key) header.d=thinkingcat.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 hM6Xb6vnUKmb; Thu, 20 Jan 2022 16:01:41 -0800 (PST)
Received: from bee.birch.relay.mailchannels.net (bee.birch.relay.mailchannels.net [23.83.209.14]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C65D23A0113; Thu, 20 Jan 2022 16:01:40 -0800 (PST)
X-Sender-Id: dreamhost|x-authsender|ldaigle@thinkingcat.com
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id DF44C8618F7; Fri, 21 Jan 2022 00:01:38 +0000 (UTC)
Received: from pdx1-sub0-mail-a243.dreamhost.com (unknown [127.0.0.6]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 34B92861551; Fri, 21 Jan 2022 00:01:38 +0000 (UTC)
X-Sender-Id: dreamhost|x-authsender|ldaigle@thinkingcat.com
Received: from pdx1-sub0-mail-a243.dreamhost.com (pop.dreamhost.com [64.90.62.162]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384) by 100.121.92.82 (trex/6.4.3); Fri, 21 Jan 2022 00:01:38 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: dreamhost|x-authsender|ldaigle@thinkingcat.com
X-MailChannels-Auth-Id: dreamhost
X-Little-Power: 6e2f18070f1816a2_1642723298708_3652329325
X-MC-Loop-Signature: 1642723298708:286369840
X-MC-Ingress-Time: 1642723298707
Received: from [192.168.1.44] (vtelinet-216-66-102-83.vermontel.net [216.66.102.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: ldaigle@thinkingcat.com) by pdx1-sub0-mail-a243.dreamhost.com (Postfix) with ESMTPSA id 4Jg00d1wT1z1NY;  Thu, 20 Jan 2022 16:01:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=thinkingcat.com; s=thinkingcat.com; t=1642723297; bh=mbOv2ypnl/PScUbX0BFDfkyqNBU=; h=From:To:Cc:Subject:Date:Content-Type:Content-Transfer-Encoding; b=EQKD4AJQQr/Bf/nXZmGQYa5dZnBFdwNNZkZxiz52Fa6vd/cwKCYmZ+C9TkpH9XINz ajl4yP73cZZ1cU30M8OhVY15lJVXP5etex7FxYvro4P/eSt5XAxEP1O6011AvnNzoL CDHPrnbp1YKwa+OMNcAAbgEecsMLXQglcIR5+aVk=
From: "Leslie Daigle" <ldaigle@thinkingcat.com>
To: "Spencer Dawkins at IETF" <spencerdawkins.ietf@gmail.com>
Cc: mops@ietf.org, mops-chairs@ietf.org
Date: Thu, 20 Jan 2022 19:01:35 -0500
X-Mailer: MailMate (1.13.2r5673)
Message-ID: <50E478B8-7A16-4A56-939F-321B1A64527C@thinkingcat.com>
In-Reply-To: <CAKKJt-e8tuKn4jkER+VyTayivsUXjXQxVPwQMFwM8WTFL7rwnA@mail.gmail.com>
References: <164193510460.24681.7567031849577194163@ietfa.amsl.com> <CAKKJt-e8tuKn4jkER+VyTayivsUXjXQxVPwQMFwM8WTFL7rwnA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_2CE10D29-1E1A-4102-9D12-211045F7F7C7_="
Content-Transfer-Encoding: 8bit
Embedded-HTML: [{"HTML":[700, 2648], "plain":[269, 1619], "uuid":"AD684B8F-E432-4296-B9F2-A74FCBB393A4"}]
Archived-At: <https://mailarchive.ietf.org/arch/msg/mops/3r-JlAeCbFT8run039wFzzzjONg>
Subject: Re: [Mops] I-D Action: draft-ietf-mops-streaming-opcons-08.txt
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: Fri, 21 Jan 2022 00:01:46 -0000

--=_MailMate_2CE10D29-1E1A-4102-9D12-211045F7F7C7_=
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: 8bit


Thanks, Spencer, co-authors, and reviewers!

Kyle and I have reviewed the update, conferred, and agree it’s ready 
to go for publication requested.

Hurrah!

We’ll get that ball rolling.

Thanks,
Leslie.

On 11 Jan 2022, at 16:09, Spencer Dawkins at IETF wrote:

> Dear MOPS,
>
> I've submitted -08 of this draft. I believe it addresses the review
> comments we received since IETF 112, and subsequent discussion about 
> those
> comments.
>
> I believe this version is ready for Publication Requested.
>
> Best,
>
> Spencer
>
> On Tue, Jan 11, 2022 at 3:05 PM <internet-drafts@ietf.org> wrote:
>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>> This draft is a work item of the Media OPerationS WG of the IETF.
>>
>>         Title           : Operational Considerations for Streaming 
>> Media
>>         Authors         : Jake Holland
>>                           Ali Begen
>>                           Spencer Dawkins
>>         Filename        : draft-ietf-mops-streaming-opcons-08.txt
>>         Pages           : 48
>>         Date            : 2022-01-11
>>
>> Abstract:
>>    This document provides an overview of operational networking 
>> issues
>>    that pertain to quality of experience when streaming video and 
>> other
>>    high-bitrate media over the Internet.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-mops-streaming-opcons/
>>
>> There is also an HTML version available at:
>> https://www.ietf.org/archive/id/draft-ietf-mops-streaming-opcons-08.html
>>
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-mops-streaming-opcons-08
>>
>>
>> Internet-Drafts are also available by rsync at rsync.ietf.org:
>> :internet-drafts
>>
>>
>> --
>> Mops mailing list
>> Mops@ietf.org
>> https://www.ietf.org/mailman/listinfo/mops
>>


> -- 
> Mops mailing list
> Mops@ietf.org
> https://www.ietf.org/mailman/listinfo/mops

-- 

-------------------------------------------------------------------
Leslie Daigle
Principal, ThinkingCat Enterprises
ldaigle@thinkingcat.com
-------------------------------------------------------------------

--=_MailMate_2CE10D29-1E1A-4102-9D12-211045F7F7C7_=
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html>
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
>
</head>
<body>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal">
<p dir=3D"auto">Thanks, Spencer, co-authors, and reviewers!</p>

<p dir=3D"auto">Kyle and I have reviewed the update, conferred, and agree=
 it=E2=80=99s ready to go for publication requested.</p>

<p dir=3D"auto">Hurrah!</p>

<p dir=3D"auto">We=E2=80=99ll get that ball rolling.</p>

<p dir=3D"auto">Thanks,<br>
Leslie.</p>

<p dir=3D"auto">On 11 Jan 2022, at 16:09, Spencer Dawkins at IETF wrote:<=
/p>

</div>
<div style=3D"white-space:normal"></div>
<blockquote style=3D"border-left:2px solid #777; color:#777; margin:0 0 5=
px; padding-left:5px"><div id=3D"AD684B8F-E432-4296-B9F2-A74FCBB393A4"><d=
iv dir=3D"ltr">Dear MOPS,=C2=A0<div><br></div><div>I&#39;ve submitted -08=
 of this draft. I believe it addresses the review comments we received si=
nce IETF 112, and subsequent discussion about those comments.=C2=A0</div>=
<div><br></div><div>I believe this version is ready for Publication Reque=
sted.=C2=A0</div><div><br></div><div>Best,</div><div><br></div><div>Spenc=
er</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gm=
ail_attr">On Tue, Jan 11, 2022 at 3:05 PM &lt;<a href=3D"mailto:internet-=
drafts@ietf.org">internet-drafts@ietf.org</a>&gt; wrote:<br></div><blockq=
uote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:=
1px solid rgb(204,204,204);padding-left:1ex"><br>
A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.<br>
This draft is a work item of the Media OPerationS WG of the IETF.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
: Operational Considerations for Streaming Media<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Authors=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: Ja=
ke Holland<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Ali Begen<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Spencer Dawkins<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-i=
etf-mops-streaming-opcons-08.txt<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
: 48<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 : 2022-01-11<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0This document provides an overview of operational networking=
 issues<br>
=C2=A0 =C2=A0that pertain to quality of experience when streaming video a=
nd other<br>
=C2=A0 =C2=A0high-bitrate media over the Internet.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-mops-streaming-opc=
ons/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/d=
oc/draft-ietf-mops-streaming-opcons/</a><br>
<br>
There is also an HTML version available at:<br>
<a href=3D"https://www.ietf.org/archive/id/draft-ietf-mops-streaming-opco=
ns-08.html" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/arc=
hive/id/draft-ietf-mops-streaming-opcons-08.html</a><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mops-streaming-=
opcons-08" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/rfcd=
iff?url2=3Ddraft-ietf-mops-streaming-opcons-08</a><br>
<br>
<br>
Internet-Drafts are also available by rsync at rsync.ietf.org::internet-d=
rafts<br>
<br>
<br>
-- <br>
Mops mailing list<br>
<a href=3D"mailto:Mops@ietf.org" target=3D"_blank">Mops@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mops" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/mops</a><br>
</blockquote></div></div></blockquote>
<div style=3D"white-space:normal">
<blockquote style=3D"border-left:2px solid #777; color:#777; margin:0 0 5=
px; padding-left:5px">
</blockquote><blockquote style=3D"border-left:2px solid #777; color:#777;=
 margin:0 0 5px; padding-left:5px"><p dir=3D"auto">-- <br>
Mops mailing list<br>
Mops@ietf.org<br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mops" style=3D"color:#77=
7">https://www.ietf.org/mailman/listinfo/mops</a></p>
</blockquote></div>
<div style=3D"white-space:normal">

<p dir=3D"auto">-- </p>

<hr style=3D"background:#333; background-image:linear-gradient(to right, =
#ccc, #333, #ccc); border:0; height:1px" height=3D"1">

<p dir=3D"auto">Leslie Daigle<br>
Principal, ThinkingCat Enterprises</p>

<h2 style=3D"font-size:1.2em"><a href=3D"mailto:ldaigle@thinkingcat.com" =
style=3D"color:#3983C4">ldaigle@thinkingcat.com</a></h2>
</div>
</div>
</body>
</html>

--=_MailMate_2CE10D29-1E1A-4102-9D12-211045F7F7C7_=--


From nobody Thu Jan 20 16:13:16 2022
Return-Path: <session-request@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 11FBE3A0838; Thu, 20 Jan 2022 16:13:14 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Meeting Session Request Tool <session-request@ietf.org>
To: <session-request@ietf.org>
Cc: evyncke@cisco.com, ldaigle@thinkingcat.com, mops-chairs@ietf.org, mops@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.43.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <164272399399.25485.16476785215688685070@ietfa.amsl.com>
Date: Thu, 20 Jan 2022 16:13:14 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/mops/5D6mWm3OSqH02NY4jRX6-jpcpns>
Subject: [Mops] mops - New Meeting Session Request for IETF 113
X-BeenThere: mops@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 21 Jan 2022 00:13:14 -0000

A new meeting session request has just been submitted by Leslie Daigle, a Chair of the mops working group.


---------------------------------------------------------
Working Group Name: Media OPerationS
Area Name: Operations and Management Area
Session Requester: Leslie Daigle


Number of Sessions: 1
Length of Session(s): 2 Hours
Number of Attendees: 50
Conflicts to Avoid: 
 Technology overlap: tsvwg rtcweb quic
 Key participant conflict: mboned add

       


People who must be present:
  Eric Vyncke
  Spencer Dawkins
  Leslie Daigle
  Glenn Deen
  Kyle Rose
  Jake Holland
  Renan Krishna

Resources Requested:

Special Requests:
  
---------------------------------------------------------



From nobody Fri Jan 21 08:45:09 2022
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 27B023A0ABB; Fri, 21 Jan 2022 08:45:07 -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 yUOpW9eLKARi; Fri, 21 Jan 2022 08:45:02 -0800 (PST)
Received: from mail-vk1-xa33.google.com (mail-vk1-xa33.google.com [IPv6:2607:f8b0:4864:20::a33]) (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 6C0D03A0AB4; Fri, 21 Jan 2022 08:45:02 -0800 (PST)
Received: by mail-vk1-xa33.google.com with SMTP id d189so5923553vkg.3; Fri, 21 Jan 2022 08:45:02 -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=kWaqVf6voTG7vMeCGGg+xAvfiZZ8JeUXaZmJMQ75+a0=; b=CfHaw/TOC02jVr2cz+yW1Ag/d5qK9AZ6BbLc7OncOdPYg+ezmv2OFQgChtbavBy+Eo Kcd/fVCS9GTgx6V64x6SKgSXmfM5/bQCK6QEkWJfdITC6kqf6MAmD+XOM0us1qDi93Ud 1Rk4xDjPWjJqswhu/4+3IQpNBfd5gPShvfGHNRr6T1rVrnRpAeY4aNNG8S+wBEXVM3RE RZPQQJ+un0NwV53Epvti3KFLhzf8rz9daSYwkzGnINOmeuCnSZdbapVj4Rz9E2+qd4bb Gm5jNhBVa3CLaGauvbH9tkfVxionqBtTTY/VgneFT+aLhXnS+x62qmoO/UbvEjh7oUyK vC+Q==
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=kWaqVf6voTG7vMeCGGg+xAvfiZZ8JeUXaZmJMQ75+a0=; b=5ITzFirFK5si38orEb81tuLMqoYtqcMDtx7XVudASSh5bGtIxQUtoZxHT4s1qoGoj0 jRH7abd6Q3f3L+A8KdBT2fbg7CsJVbuKJV/sqDRKMoZQBJELxfgQML+jArVo9/vK1g8/ +G6htYLQ693wr+P1yecssFGOjEbLjpYaO57c8eeb/Ktf/bVw8KkFelTsoCek48yAhG9q RxLcL6rsarhUQDn+ghYTTSpdFt6d3fwez/5UD3Ugi3e6tS+TfB2rs64OgnnU32RB1Keb FqplgmmEJmRg4rvgcNRHYRH6wi5EWjGppGnU0fXt8r254g4i4XaT7DcNH926kx0gEg7e B0HQ==
X-Gm-Message-State: AOAM532U1BFuSK0xrphTuGT4cYi9xR1b6LYd27CgC16lOiIiiAHLGaiN ABikgPGPsLEqI63ip/D1lzkvkebVQ87svzcTlfK6aIxg
X-Google-Smtp-Source: ABdhPJyAbia3H75MIj2tXfHZywTlnyWZBUdRa9w29K+TZVPCpB8tcAjtrEmw082q+hSPkTisbXsFb+AyBlqpZ3yb4vI=
X-Received: by 2002:a05:6122:d9d:: with SMTP id bc29mr2045555vkb.35.1642783499995;  Fri, 21 Jan 2022 08:44:59 -0800 (PST)
MIME-Version: 1.0
References: <164193510460.24681.7567031849577194163@ietfa.amsl.com> <CAKKJt-e8tuKn4jkER+VyTayivsUXjXQxVPwQMFwM8WTFL7rwnA@mail.gmail.com> <50E478B8-7A16-4A56-939F-321B1A64527C@thinkingcat.com>
In-Reply-To: <50E478B8-7A16-4A56-939F-321B1A64527C@thinkingcat.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Fri, 21 Jan 2022 10:44:34 -0600
Message-ID: <CAKKJt-daytsqvy964qaRZOBHSRRK25ojsJ2a8AUcesa-1LHABA@mail.gmail.com>
To: Leslie Daigle <ldaigle@thinkingcat.com>
Cc: mops@ietf.org, mops-chairs@ietf.org
Content-Type: multipart/alternative; boundary="000000000000f5cf0405d61a5620"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mops/fM3XUac0_anuYmkPrSWCD2UIo08>
Subject: Re: [Mops] I-D Action: draft-ietf-mops-streaming-opcons-08.txt
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: Fri, 21 Jan 2022 16:45:07 -0000

--000000000000f5cf0405d61a5620
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Leslie and Kyle,

On Thu, Jan 20, 2022 at 6:01 PM Leslie Daigle <ldaigle@thinkingcat.com>
wrote:

> Thanks, Spencer, co-authors, and reviewers!
>
> Kyle and I have reviewed the update, conferred, and agree it=E2=80=99s re=
ady to go
> for publication requested.
>
> Hurrah!
>
Thank you for your quick response, and I echo your hurrah!

Best,

Spencer

> We=E2=80=99ll get that ball rolling.
>
> Thanks,
> Leslie.
>
> On 11 Jan 2022, at 16:09, Spencer Dawkins at IETF wrote:
>
> Dear MOPS,
>
> I've submitted -08 of this draft. I believe it addresses the review
> comments we received since IETF 112, and subsequent discussion about thos=
e
> comments.
>
> I believe this version is ready for Publication Requested.
>
> Best,
>
> Spencer
>
> On Tue, Jan 11, 2022 at 3:05 PM <internet-drafts@ietf.org> wrote:
>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>> This draft is a work item of the Media OPerationS WG of the IETF.
>>
>>         Title           : Operational Considerations for Streaming Media
>>         Authors         : Jake Holland
>>                           Ali Begen
>>                           Spencer Dawkins
>>         Filename        : draft-ietf-mops-streaming-opcons-08.txt
>>         Pages           : 48
>>         Date            : 2022-01-11
>>
>> Abstract:
>>    This document provides an overview of operational networking issues
>>    that pertain to quality of experience when streaming video and other
>>    high-bitrate media over the Internet.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-mops-streaming-opcons/
>>
>> There is also an HTML version available at:
>> https://www.ietf.org/archive/id/draft-ietf-mops-streaming-opcons-08.html
>>
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mops-streaming-opcons-08
>>
>>
>> Internet-Drafts are also available by rsync at rsync.ietf.org:
>> :internet-drafts
>>
>>
>> --
>> Mops mailing list
>> Mops@ietf.org
>> https://www.ietf.org/mailman/listinfo/mops
>>
> --
> Mops mailing list
> Mops@ietf.org
> https://www.ietf.org/mailman/listinfo/mops
>
> --
> ------------------------------
>
> Leslie Daigle
> Principal, ThinkingCat Enterprises
> ldaigle@thinkingcat.com
>

--000000000000f5cf0405d61a5620
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">Leslie and Kyle,=C2=A0</div><br><div clas=
s=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Jan 20, 202=
2 at 6:01 PM Leslie Daigle &lt;<a href=3D"mailto:ldaigle@thinkingcat.com">l=
daigle@thinkingcat.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,2=
04);padding-left:1ex"><u></u>




<div>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal">
<p dir=3D"auto">Thanks, Spencer, co-authors, and reviewers!</p>

<p dir=3D"auto">Kyle and I have reviewed the update, conferred, and agree i=
t=E2=80=99s ready to go for publication requested.</p>

<p dir=3D"auto">Hurrah!</p></div></div></div></blockquote><div>Thank you fo=
r your quick response, and I echo your hurrah!</div><div><br></div><div>Bes=
t,</div><div><br></div><div>Spencer=C2=A0</div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,2=
04);padding-left:1ex"><div><div style=3D"font-family:sans-serif"><div style=
=3D"white-space:normal">

<p dir=3D"auto">We=E2=80=99ll get that ball rolling.</p>

<p dir=3D"auto">Thanks,<br>
Leslie.</p>

<p dir=3D"auto">On 11 Jan 2022, at 16:09, Spencer Dawkins at IETF wrote:</p=
>

</div>
<div style=3D"white-space:normal"></div>
<blockquote style=3D"border-left:2px solid rgb(119,119,119);color:rgb(119,1=
19,119);margin:0px 0px 5px;padding-left:5px"><div id=3D"gmail-m_-2882443668=
517677145AD684B8F-E432-4296-B9F2-A74FCBB393A4"><div dir=3D"ltr">Dear MOPS,=
=C2=A0<div><br></div><div>I&#39;ve submitted -08 of this draft. I believe i=
t addresses the review comments we received since IETF 112, and subsequent =
discussion about those comments.=C2=A0</div><div><br></div><div>I believe t=
his version is ready for Publication Requested.=C2=A0</div><div><br></div><=
div>Best,</div><div><br></div><div>Spencer</div></div><br><div class=3D"gma=
il_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Jan 11, 2022 at 3:0=
5 PM &lt;<a href=3D"mailto:internet-drafts@ietf.org" target=3D"_blank">inte=
rnet-drafts@ietf.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204=
);padding-left:1ex"><br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
This draft is a work item of the Media OPerationS WG of the IETF.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 Operational Considerations for Streaming Media<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Authors=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: Jake=
 Holland<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Ali Begen<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Spencer Dawkins<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-iet=
f-mops-streaming-opcons-08.txt<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 48<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 :=
 2022-01-11<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0This document provides an overview of operational networking i=
ssues<br>
=C2=A0 =C2=A0that pertain to quality of experience when streaming video and=
 other<br>
=C2=A0 =C2=A0high-bitrate media over the Internet.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-mops-streaming-opcon=
s/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/doc/d=
raft-ietf-mops-streaming-opcons/</a><br>
<br>
There is also an HTML version available at:<br>
<a href=3D"https://www.ietf.org/archive/id/draft-ietf-mops-streaming-opcons=
-08.html" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/archive=
/id/draft-ietf-mops-streaming-opcons-08.html</a><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mops-streaming-op=
cons-08" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/rfcdiff?=
url2=3Ddraft-ietf-mops-streaming-opcons-08</a><br>
<br>
<br>
Internet-Drafts are also available by rsync at rsync.ietf.org::internet-dra=
fts<br>
<br>
<br>
-- <br>
Mops mailing list<br>
<a href=3D"mailto:Mops@ietf.org" target=3D"_blank">Mops@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mops" rel=3D"noreferrer" t=
arget=3D"_blank">https://www.ietf.org/mailman/listinfo/mops</a><br>
</blockquote></div></div></blockquote>
<div style=3D"white-space:normal">
<blockquote style=3D"border-left:2px solid rgb(119,119,119);color:rgb(119,1=
19,119);margin:0px 0px 5px;padding-left:5px">
</blockquote><blockquote style=3D"border-left:2px solid rgb(119,119,119);co=
lor:rgb(119,119,119);margin:0px 0px 5px;padding-left:5px"><p dir=3D"auto">-=
- <br>
Mops mailing list<br>
<a href=3D"mailto:Mops@ietf.org" target=3D"_blank">Mops@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mops" style=3D"color:rgb(1=
19,119,119)" target=3D"_blank">https://www.ietf.org/mailman/listinfo/mops</=
a></p>
</blockquote></div>
<div style=3D"white-space:normal">

<p dir=3D"auto">-- </p>

<hr style=3D"background:linear-gradient(to right,rgb(204,204,204),rgb(51,51=
,51),rgb(204,204,204)) rgb(51,51,51);border:0px;height:1px" height=3D"1">

<p dir=3D"auto">Leslie Daigle<br>
Principal, ThinkingCat Enterprises</p>

<h2 style=3D"font-size:1.2em"><a href=3D"mailto:ldaigle@thinkingcat.com" st=
yle=3D"color:rgb(57,131,196)" target=3D"_blank">ldaigle@thinkingcat.com</a>=
</h2>
</div>
</div>
</div>

</blockquote></div></div>

--000000000000f5cf0405d61a5620--

