Re: [GGIE] MOPS - Media Ops BoF request

sanjay.mishra@verizon.com Wed, 05 June 2019 20:53 UTC

Return-Path: <sanjay.mishra@verizon.com>
X-Original-To: ggie@ietfa.amsl.com
Delivered-To: ggie@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 295F812013B for <ggie@ietfa.amsl.com>; Wed, 5 Jun 2019 13:53:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.309
X-Spam-Level:
X-Spam-Status: No, score=-2.309 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_MED=-2.3, 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=verizon.com header.b=kO5iG73o; dkim=pass (1024-bit key) header.d=verizon.com header.b=bRMIVJAC; dkim=pass (1024-bit key) header.d=verizon.com header.b=KliRNiv5
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 IT5brHloQhIZ for <ggie@ietfa.amsl.com>; Wed, 5 Jun 2019 13:53:26 -0700 (PDT)
Received: from omzsmtpe03.verizonbusiness.com (omzsmtpe03.verizonbusiness.com [199.249.25.208]) (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 91D0D1200B5 for <ggie@ietf.org>; Wed, 5 Jun 2019 13:53:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=verizon.com; i=@verizon.com; q=dns/txt; s=corp; t=1559768006; x=1591304006; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=vhKCfITun4ahFOCj/E6rFseyuSupmN0+MpxvlxMV4uY=; b=kO5iG73ouvkoIAbBwjdB7zwG91SDggbvbMphiXb87uypCEPQj+H7xfHm /dPUvn0k9Bz8PW4oiF7HBBsj/aDWMMhquJE66i1fHS+eVSYPfPgLZoBGh y2pGJZjv0SzTAIhkGMiuGZSRn2WPbBjnfJnMkedh8iZjgOcS5vepcMy9U E=;
Received: from unknown (HELO fldsmtpi01.verizon.com) ([166.68.71.143]) by omzsmtpe03.verizonbusiness.com with ESMTP; 05 Jun 2019 20:53:25 +0000
Received: from rogue-10-255-192-101.rogue.vzwcorp.com (HELO atlantis.verizonwireless.com) ([10.255.192.101]) by fldsmtpi01.verizon.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 05 Jun 2019 20:52:57 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=verizon.com; i=@verizon.com; q=dns/txt; s=corp; t=1559767977; x=1591303977; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=vhKCfITun4ahFOCj/E6rFseyuSupmN0+MpxvlxMV4uY=; b=bRMIVJAC8nusNL0vFDAjoPwlyYSz4rW1n0yBWrVUrnORzK7QEwVmTS6+ cyfSk2Bn3b0OGAXjGzQ1BmosleL6OfGFQlR7R2UKjAe2giB0JB9Hoz1az Q0ev+BmXGRu93/Y6eQ+v8gam0fAexfBpf0SN50YOQkcR2+HJX483lBzmm k=;
Received: from surveyor.tdc.vzwcorp.com (HELO eris.verizonwireless.com) ([10.254.88.83]) by atlantis.verizonwireless.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 05 Jun 2019 16:52:57 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=verizon.com; i=@verizon.com; q=dns/txt; s=corp; t=1559767977; x=1591303977; h=to:subject:date:message-id:references:in-reply-to: mime-version:from; bh=vhKCfITun4ahFOCj/E6rFseyuSupmN0+MpxvlxMV4uY=; b=KliRNiv5PGrvZ4PK+T+QQy2zToIOMEaEzuQrBpZMt7s25oFeMGMcvmUR eyO1/0Hn0igGcTJ8CuKiFz/tXpEl3Y4OhJQ3szWyR33ftg6xdEFZOwV9D XwG9+QshE8l7l/iUHYrnsUQ96/VqR4AedsH04rmuUDEiZG87DDJ5AALTn k=;
From: sanjay.mishra@verizon.com
X-Host: surveyor.tdc.vzwcorp.com
Received: from ohtwi1exh001.uswin.ad.vzwcorp.com ([10.144.218.43]) by eris.verizonwireless.com with ESMTP/TLS/AES128-SHA256; 05 Jun 2019 20:52:57 +0000
Received: from tbwexch03apd.uswin.ad.vzwcorp.com (153.114.162.27) by OHTWI1EXH001.uswin.ad.vzwcorp.com (10.144.218.43) with Microsoft SMTP Server (TLS) id 14.3.248.2; Wed, 5 Jun 2019 16:52:57 -0400
Received: from tbwexch02apd.uswin.ad.vzwcorp.com (153.114.162.26) by tbwexch03apd.uswin.ad.vzwcorp.com (153.114.162.27) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 5 Jun 2019 16:52:56 -0400
Received: from tbwexch02apd.uswin.ad.vzwcorp.com ([153.114.162.26]) by tbwexch02apd.uswin.ad.vzwcorp.com ([153.114.162.26]) with mapi id 15.00.1473.003; Wed, 5 Jun 2019 16:52:56 -0400
To: "Deen, Glenn (NBCUniversal)" <Glenn.Deen@nbcuni.com>, "ggie@ietf.org" <ggie@ietf.org>
Thread-Topic: MOPS - Media Ops BoF request
Thread-Index: AQHVGixmx3EcM8lWGEWwKx/aqdoChaaNeejw
Date: Wed, 5 Jun 2019 20:52:56 +0000
Message-ID: <4c9a01f5134b4dfa98ea72d742646212@tbwexch02apd.uswin.ad.vzwcorp.com>
References: <B2A89BEE-C4BC-4752-9CDE-B4D346E0D2EF@nbcuni.com>
In-Reply-To: <B2A89BEE-C4BC-4752-9CDE-B4D346E0D2EF@nbcuni.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.144.60.250]
Content-Type: multipart/alternative; boundary="_000_4c9a01f5134b4dfa98ea72d742646212tbwexch02apduswinadvzwc_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ggie/-z4ouGn1v492atQflo-QkzOO-GU>
Subject: Re: [GGIE] MOPS - Media Ops BoF request
X-BeenThere: ggie@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discuss IETF-related items for Glass to Glass Internet Ecosystem of Video Content <ggie.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ggie>, <mailto:ggie-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ggie/>
List-Post: <mailto:ggie@ietf.org>
List-Help: <mailto:ggie-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ggie>, <mailto:ggie-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jun 2019 20:53:29 -0000

Hi Glenn – The proposed charter looks good (ignoring some tightening needed around the text}  but you capture the purpose for MOPS well. I do have a comment noted under <SM>

Continued development of Internet-using technologies should be properly coordinated in order to ensure that the existing technologies are well-utilized, and new ones are developed in sympathy with the Internet’s core protocols and design.

<SM> I get the intent, though, it will be hard to ensure “existing technologies are well-utilized”. It will be up to the technology user or the platform provider to bring it to MOPS when observing or suspecting sub optimal use of Internet.

Thank you
Sanjay

From: GGIE [mailto:ggie-bounces@ietf.org] On Behalf Of Deen, Glenn (NBCUniversal)
Sent: Monday, June 3, 2019 12:50 PM
To: ggie@ietf.org
Cc: Deen, Glenn (NBCUniversal) <Glenn.Deen@nbcuni.com>;
Subject: [E] [GGIE] MOPS - Media Ops BoF request

Hi everyone,

IETF105 BoF requests are due this Friday, so now would be good time to send your comments on the MOPS BoF draft

https://docs.google.com/document/d/1S4soR8QVjbCa1k1CXS8bCXox_h8-zK6kEsS8_IU4yXI/<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1S4soR8QVjbCa1k1CXS8bCXox-5Fh8-2DzK6kEsS8-5FIU4yXI_&d=DwMGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=XniVbishGiO2Ao9hKqSc-hTVIWCi3T-x6GdHR4ZTgoM&m=u94j_YgUN8LsksB42QuDYsWMJCbd164-pBiGSmoSERM&s=nSwHjPlGz55ctVZyBgoKN_pOYuW2MKndAwHxWcYkSJE&e=>

The current draft is an amalgam of the discussions we had at IETF104 and feedback from a few ADs, but the more the better so please don’t be shy.

This is a chance to bring forward, officially the topic of creating an group with video expertise at the IETF that can help video problems across the great diversity of technical areas that are the IETF.  So I encourage you to please take a couple of minutes when you get this email, look at the draft and comment back the list your thoughts.

Even – “it looks good to me”  – is helpful to hear.

regards
Glenn