Re: [GGIE] [Mops] [E] Updated proposed charter for a MOPS WG

"Eric Vyncke (evyncke)" <evyncke@cisco.com> Thu, 05 September 2019 11:34 UTC

Return-Path: <evyncke@cisco.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 60D28120059; Thu, 5 Sep 2019 04:34:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 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, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=f+48F7X1; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=i449CIBp
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 GOY_jZJ-thpf; Thu, 5 Sep 2019 04:34:31 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DAFBA1200A1; Thu, 5 Sep 2019 04:34:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=37593; q=dns/txt; s=iport; t=1567683270; x=1568892870; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=qgqjPGPCPfujaiTSt3oi9rplZUUV2yP9+FZTHW/ppes=; b=f+48F7X1nr/WLtP6ylluLKm/Gs3dHRGh4y1a9pagB+9OKjOnATQv16k8 lz8+6fMR6zvyfMF4CUOTi2DOf0txcjVP8AylA1yl7W78dxyXrOnvIJUxx xdr3dBIttZu1wDn/EnaIju1jlIzkV0Sr0M9Gssnw4TXyy4CMcFeFUPpiR s=;
IronPort-PHdr: =?us-ascii?q?9a23=3AKvYFfhTLjRybN1QILw83Oz/dP9psv++ubAcI9p?= =?us-ascii?q?oqja5Pea2//pPkeVbS/uhpkESXBdfA8/wRje3QvuigQmEG7Zub+FE6OJ1XH1?= =?us-ascii?q?5g640NmhA4RsuMCEn1NvnvOiEkDcJJV1JN9HCgOk8TE8H7NBXf?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CwAAC88XBd/5NdJa1bChoBAQEBAQI?= =?us-ascii?q?BAQEBBwIBAQEBgWeBFi8kLANtViAECyqEIYNHA4p1gjcll2yBQoEQA1QJAQE?= =?us-ascii?q?BDAEBLQIBAYQ/AheCHyM4EwIDCAEBBAEBAQIBBgRthS4MhUoBAQEBAxIRChM?= =?us-ascii?q?BASwLAQ8CAQYCEQMBAQEhBwMCAgIwFAkIAgQBDQUUBweDAAGBHU0DHQECjVy?= =?us-ascii?q?QYQKBOIhhc4Eygn0BAQWFExiCFgmBNIt4GIFAP4ERJwwTgh4uPoJhBIE0Ex0?= =?us-ascii?q?DDwkHD4JVMoImjzaFIYh1HY5LCoIfjAOIZRuCNIc8hi6EMIJOgVmMT4ErmF0?= =?us-ascii?q?CBAIEBQIOAQEFgWkhKoEucBU7KgGCQYJCDBeDT4pTcwEBgSePIQEB?=
X-IronPort-AV: E=Sophos;i="5.64,470,1559520000"; d="scan'208,217";a="331889133"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 05 Sep 2019 11:34:29 +0000
Received: from XCH-ALN-012.cisco.com (xch-aln-012.cisco.com [173.36.7.22]) by rcdn-core-11.cisco.com (8.15.2/8.15.2) with ESMTPS id x85BYTgs024331 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 5 Sep 2019 11:34:29 GMT
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by XCH-ALN-012.cisco.com (173.36.7.22) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 5 Sep 2019 06:34:28 -0500
Received: from xhs-aln-002.cisco.com (173.37.135.119) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 5 Sep 2019 07:34:27 -0400
Received: from NAM01-SN1-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Thu, 5 Sep 2019 06:34:27 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=YlzJzlENYazOdm2fi+ZNJeGrLnULtDdpWDbkdWLcSaNLKUKiRvxHIPSStOSG9c8Kwa4y4Di8aoxmdnhgdOZq1NS3e3gYRuO54jPygdNPahKHDjSRKckGA1rcKrq7j7lT/1aSKLtFk5JtJNxC6pmDhD1t5VkhMjqjAneIoQBq0EbK6iDGOeJ9v6zhlCTh0Q+2qpPSrTVo3X4KDcojo/+2f7/thbvCHuvdbYJQnZ7Ik273ZZYripB887jOwHJUqksymOTJ6yZjnkZfk+/5CnxfhgVr7v6uhKczJu3MVf0Vpr43m86s0wZ4TWcUFiXa+rTU4b3Dt3ihPpUBs+Moa+qCvQ==
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-SenderADCheck; bh=qgqjPGPCPfujaiTSt3oi9rplZUUV2yP9+FZTHW/ppes=; b=XVB3h2dtpcAuvCN9Phb8MChmFHGc4Aad6BbeyK5pmIRgzjJJZ02RNf2EwzdngM3Va8rZ6xiIS6bZaNcr57nZo6DRZXzeA6XUNqilvkqy+OfVs+njPbomBL8pOS1GpopqwiNrsLoI6aVnU57dQ/KTRYzGa2TjrjBlq6EJXgPWFtP9ItMT1hWAk55HiSup7e0bSv4m/hCpd3PwVC+g9mLGzavpMBO5zPoCs1EYp8trwDoTLMwZqyistbqpbKvLZCuWHgeDVkPMDGUEw4eHxKuM1zNo9+WzIMnY2r6okqAc3ZmSdgBNf6KA6KDV2kbkeTlCqOMXcRsi2R3Kvzm3F/jdug==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=qgqjPGPCPfujaiTSt3oi9rplZUUV2yP9+FZTHW/ppes=; b=i449CIBpbXOW6xWuW5IVqCpGyYSPTT0aolXdJEX6ApxVSk2+poH+yvELtrFRb8uFmzjMXLpSllmm7uDUrj/6NyP4tUccGZH5PFThz0lIhAM1RmXOMpFp4tGN7bA8TSATrfGRz3UrQlKnVVoqC6IpsMB0v7oFAz0MCiYxHC7cmEk=
Received: from MN2PR11MB4144.namprd11.prod.outlook.com (20.179.150.210) by MN2PR11MB3856.namprd11.prod.outlook.com (20.178.251.203) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2220.20; Thu, 5 Sep 2019 11:34:26 +0000
Received: from MN2PR11MB4144.namprd11.prod.outlook.com ([fe80::d5c4:be39:66cb:449b]) by MN2PR11MB4144.namprd11.prod.outlook.com ([fe80::d5c4:be39:66cb:449b%6]) with mapi id 15.20.2220.020; Thu, 5 Sep 2019 11:34:26 +0000
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: "sanjay.mishra=40verizon.com@dmarc.ietf.org" <sanjay.mishra=40verizon.com@dmarc.ietf.org>, Leslie Daigle <ldaigle@thinkingcat.com>, "mops@ietf.org" <mops@ietf.org>
CC: "ggie@ietf.org" <ggie@ietf.org>, Warren Kumari <warren@kumari.net>
Thread-Topic: [Mops] [E] Updated proposed charter for a MOPS WG
Thread-Index: AQHVXz1BGU6blWfS3kyslIGsZYrQe6cdHsmA
Date: Thu, 5 Sep 2019 11:34:26 +0000
Message-ID: <6D0E7991-96E1-4394-84D7-D4E3BDDDBFBE@cisco.com>
References: <76DEB7E9-5E0F-4306-9975-7285D8EB51BC@thinkingcat.com> <e99e45985ba740689a47e84757c7e784@tbwexch02apd.uswin.ad.vzwcorp.com>
In-Reply-To: <e99e45985ba740689a47e84757c7e784@tbwexch02apd.uswin.ad.vzwcorp.com>
Accept-Language: fr-BE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1c.0.190812
authentication-results: spf=none (sender IP is ) smtp.mailfrom=evyncke@cisco.com;
x-originating-ip: [2001:420:c0c1:36:6d9e:f11c:f541:48f0]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 285fd985-5ea3-48c8-33f6-08d731f501da
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600166)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:MN2PR11MB3856;
x-ms-traffictypediagnostic: MN2PR11MB3856:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <MN2PR11MB3856D6BBA2D9C177F5705005A9BB0@MN2PR11MB3856.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 015114592F
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(366004)(396003)(376002)(39860400002)(346002)(199004)(189003)(6506007)(486006)(99286004)(2501003)(229853002)(2616005)(46003)(6512007)(236005)(6306002)(54896002)(53546011)(14454004)(790700001)(102836004)(14444005)(256004)(476003)(478600001)(86362001)(66574012)(6486002)(7110500001)(11346002)(5660300002)(316002)(446003)(58126008)(4326008)(25786009)(66446008)(64756008)(2420400007)(66556008)(6436002)(33656002)(91956017)(76116006)(66476007)(6116002)(66946007)(186003)(2906002)(81156014)(81166006)(15650500001)(36756003)(110136005)(53936002)(71200400001)(7736002)(71190400001)(76176011)(54906003)(6246003)(8936002)(8676002); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB3856; H:MN2PR11MB4144.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: iaCjvwc+UUvrKRLehO/fZ80/s02hrAQzb0F/85kwZ/rwf1FSMIHLnzLcK4vtwH4gwFIEr1JLMYE28w+aUKKQ+qdZHQIjCKWgw/6acrmGbMbORNUPX1Nc4gvowZP1XB3aVw/SownGXabl083vkVEY1O86C4y996RCM20s0AqWN/KH8mB0aL+3tp333S7CxdSkaKJdo2/rWmMY1VeVLArSOF0hcmWr97trL6JAzmU+S4PA6bfrxr/Tbh8SArP8/rJJfcW757J9xqcB7ZjtSFuT+C86mVuFLZlFHdjHbEHA4/JK4AdSZyf5L384r0ogE+ayc44KMnQK01yfGk43mCFQP6DnjCbiDpevByL5dRwybAWfLYYDPukZVXWZ+nV3joIZO/T3kbK9663ouG8Uwu//9CM0PSJd1lpLdsXzvPJorAY=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_6D0E799196E1439484D7D4E3BDDDBFBEciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 285fd985-5ea3-48c8-33f6-08d731f501da
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Sep 2019 11:34:26.2181 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 0J8zlHXrlWLJQmrghCfT5stgkje0JHYpg/6GBY3uziZGoQDbbCOQmBrAZYsuJjyVsO18hso2mM6jKrGA6+wyvQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB3856
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.22, xch-aln-012.cisco.com
X-Outbound-Node: rcdn-core-11.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ggie/IhpfaAdwHTN9ZCM-Cd9He3PFBmQ>
Subject: Re: [GGIE] [Mops] [E] Updated proposed charter for a MOPS WG
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: Thu, 05 Sep 2019 11:34:34 -0000

[Adding the old GGIE mailing list as perhaps some GGIE members did not switch/join the MOPS mailing list]

As the potential Area Director supporting a potential MOPS Working Group, I must:

  1.  Thank Sanjay for his support (and comment)
  2.  Wonder whether other group members are still supporting this MOPS effort?

About 2) May be some members are not fully aware of IETF rules / processes, but, having only one reply for a charter review is not a good sign as it does not indicate a high level of support.

Can people interested in MOPS review the charter (see below) and approve it? or suggest changes ? Or disapprove completely ?

Please reply to all

Regards

-éric

From: Mops <mops-bounces@ietf.org>; on behalf of "sanjay.mishra=40verizon.com@dmarc.ietf.org"; <sanjay.mishra=40verizon.com@dmarc.ietf.org>;
Date: Friday, 30 August 2019 at 16:14
To: Leslie Daigle <ldaigle@thinkingcat.com>;, "mops@ietf.org"; <mops@ietf.org>;
Subject: Re: [Mops] [E] Updated proposed charter for a MOPS WG

Hi Leslie – The proposed charter looks good. I just have a comment RE need of clarity on the text “or networks are inadequate to meet these updated requirements”.

Otherwise, the charter seems consistent with the discussions during the BOF.

Thanks
Sanjay


From: Mops [mailto:mops-bounces@ietf.org] On Behalf Of Leslie Daigle
Sent: Friday, August 23, 2019 11:22 AM
To: mops@ietf.org
Subject: [E] [Mops] Updated proposed charter for a MOPS WG


Hi,

The two clear takeaways I had from the MOPS bof at IETF 105 were that there is interest in “this area of work” and that the proposed charter was not nearly crisp enough to agree on what the area of work was, or the specific things to be done.

As I said in the meeting, the challenge in trying to be crisp by narrowing the focus is that we actually need a rather broad “catchment” area, specifically pulling in things from several areas within the IETF and being open to input from other organizations. To achieve some level of sanity, I’ve attempted to make things clearer by being more specific about the work to be done. I’ve copied below an UPDATED proposed charter, that is aiming to be at least a little more concrete.

Action items:

1/ Please review the draft charter and provide feedback. (Yes, it looks like the sort of thing you would like to see chartered; suggestions for greater crispness, etc).

2/ Of particular importance, we need more work items in the Milestones. I told the ADs that I didn’t want to just write a bunch of things and then try to badger people into working on them (though I will if I have to :^) ). I’d rather have suggestions from interested parties about the things they are willing to work on in this area, or that they’d like to see done with a little help from others.

Okay — please comment.

Leslie.

—8<——8<——8<—

Media OPS WG

Internet- and Internet-protocol-delivered media is widespread, leading to significant technology development across industries not traditionally thought of as Internet technology developers or operators, as well as considerable quantities of traffic on local and transit networks. MOPS’ focus is on identifying areas where existing protocols and/or networks are inadequate to meet these updated requirements.

[I would like to add that the issue is more than to meet these “updated” requirements. In fact, I see MOPS to focus specifically on how protocols coming out of the IETF “factory” when used in “real-world” may have implications across the service delivery food chain. Some of the implications may be by design or not as expected. MOPS will help bring operational issue whether it relates to delivery of service using a protocol that is efficient (or inefficient), or, is the network on which protocol is running supporting the protocol “as-is” or is there a need for network operators adjust the network, or is there an issue for UA conforming to delivery using a particular protocol.].

Not necessarily suggesting above commentary as a substitute text as it is not meant to be, but, a little more specificity will be helpful. I know, you do go into that part of specificity in the next paragraph but some up front clarity is useful.

MOPS will solicit input on operational issues and practices, existing and proposed technologies related to the deployment, engineering, and operation of media streaming and manipulation protocols and procedures in the global Internet, inter-domain and single domain networking. In this case, media is considered to include the transport of video, audio, objects and any combination thereof, possibly non-sequentially. The scope is media and media protocols’ interactions with the network, but not the technologies of control protocols or media formats.

The premise of MOPS is that 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. MOPS acts as a clearinghouse to identify appropriate venues for further protocol development, where necessary.

MOPS goals include documenting existing protocol and operational issues with media on the Internet, and identifying requirements for potential IETF work.

To those ends, MOPS will:

1/ Solicit regular updates from other media technology developing consortia/standards bodies working with IETF-developed protocols.

2/ Solicit input from network operators and users to identify operational issues with media delivery in and across networks, and determine solutions or workarounds to those issues.

3/ Solicit discussion and documentation of the issues and opportunities in media acquisition and delivery, and of the resulting innovations developed outside the IETF

4/ Document operational requirements for media acquisition and delivery.

5/ Develop operational information to aid in operation of media technologies in the global Internet.

These activities should document media operational experience, including global Internet, inter-domain and within-domain operations.

Media operational and deployment issues with specific protocols or technologies (such as Applications, Transport Protocols, Routing Protocols, DNS or Sub-IP Protocols) are the primary responsibility of the groups or areas responsible for those protocols or technologies. However, the MOPS Working Group may provide input to those areas/groups, as needed, and cooperate with those areas/groups in reviewing solutions to MOPS operational and deployment problems.

Future work items within this scope will be adopted by the Working Group only if there is a substantial expression of interest from the community and if the work clearly does not fit elsewhere in the IETF.

There must be a continuous expression of interest for the Working Group to work on a particular work item. If there is no longer sufficient interest in the Working Group in a work item, the item may be removed from the list of Working Group items.

Milestones

July 2020 Taxonomy of Issues in Internet Media

<more concrete, committed work items needed>

--

________________________________

Leslie Daigle
Principal, ThinkingCat Enterprises

ldaigle@thinkingcat.com<mailto:ldaigle@thinkingcat.com>