[Mops] Updated charter, with milestones
"Leslie Daigle" <ldaigle@thinkingcat.com> Wed, 18 September 2019 16:25 UTC
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 85D271200DE for <mops@ietfa.amsl.com>; Wed, 18 Sep 2019 09:25:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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_NONE=-0.0001, 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 tx86vPw_A9VY for <mops@ietfa.amsl.com>; Wed, 18 Sep 2019 09:25:48 -0700 (PDT)
Received: from buffalo.birch.relay.mailchannels.net (buffalo.birch.relay.mailchannels.net [23.83.209.24]) (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 8EF8B12006A for <mops@ietf.org>; Wed, 18 Sep 2019 09:25:48 -0700 (PDT)
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 8837422D84; Wed, 18 Sep 2019 16:25:47 +0000 (UTC)
Received: from pdx1-sub0-mail-a67.g.dreamhost.com (100-96-29-66.trex.outbound.svc.cluster.local [100.96.29.66]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id CF73422629; Wed, 18 Sep 2019 16:25:46 +0000 (UTC)
X-Sender-Id: dreamhost|x-authsender|ldaigle@thinkingcat.com
Received: from pdx1-sub0-mail-a67.g.dreamhost.com ([TEMPUNAVAIL]. [64.90.62.162]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.17.5); Wed, 18 Sep 2019 16:25:47 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: dreamhost|x-authsender|ldaigle@thinkingcat.com
X-MailChannels-Auth-Id: dreamhost
X-Decisive-Befitting: 7fae482b1468f7b8_1568823947258_4266813366
X-MC-Loop-Signature: 1568823947257:3004573781
X-MC-Ingress-Time: 1568823947257
Received: from pdx1-sub0-mail-a67.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a67.g.dreamhost.com (Postfix) with ESMTP id 8349785840; Wed, 18 Sep 2019 09:25:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=thinkingcat.com; h=from:to :subject:date:message-id:mime-version:content-type :content-transfer-encoding; s=thinkingcat.com; bh=/4o4RB4jAwXYtO AysqkJc5xStzY=; b=Ud99fCoWtvXfcLAJFIFCSaZH4U7syh4NbJNam9jM8+Zpua UW7Hv49AyvJyKcyYPC/6DVgxxPU0p4b29ojA/j3GK3t37ixvX8lix16aZZmJ/R9z 4x50Nj+XwZGkctvFvIAOU8AiEXBnM8VbykNF56bhXkeK7eYRHy1FhduSNHOVw=
Received: from [192.168.1.57] (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-a67.g.dreamhost.com (Postfix) with ESMTPSA id 984ED8583A; Wed, 18 Sep 2019 09:25:40 -0700 (PDT)
X-DH-BACKEND: pdx1-sub0-mail-a67
From: Leslie Daigle <ldaigle@thinkingcat.com>
To: mops@ietf.org
Date: Wed, 18 Sep 2019 12:25:35 -0400
X-Mailer: MailMate (1.12.5r5635)
Message-ID: <A838C342-4D37-4B8F-8519-E92A9ADF77F1@thinkingcat.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_361B3DE1-54C5-4F90-A2E5-19ADA12C6B36_="
X-VR-OUT-STATUS: OK
X-VR-OUT-SCORE: 0
X-VR-OUT-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedufedrudekgddutdduucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuggftfghnshhusghstghrihgsvgdpffftgfetoffjqffuvfenuceurghilhhouhhtmecufedttdenucenucfjughrpefhvffufffokfggtgfgsegrkehmreertdejnecuhfhrohhmpedfnfgvshhlihgvucffrghighhlvgdfuceolhgurghighhlvgesthhhihhnkhhinhhgtggrthdrtghomheqnecukfhppedvudeirdeiiedruddtvddrkeefnecurfgrrhgrmhepmhhouggvpehsmhhtphdphhgvlhhopegludelvddrudeikedruddrheejngdpihhnvghtpedvudeirdeiiedruddtvddrkeefpdhrvghtuhhrnhdqphgrthhhpedfnfgvshhlihgvucffrghighhlvgdfuceolhgurghighhlvgesthhhihhnkhhinhhgtggrthdrtghomheqpdhmrghilhhfrhhomheplhgurghighhlvgesthhhihhnkhhinhhgtggrthdrtghomhdpnhhrtghpthhtoheplhgurghighhlvgesthhhihhnkhhinhhgtggrthdrtghomhenucevlhhushhtvghrufhiiigvpedt
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mops/gAkPkB3WMXG9p6KCC2zfI6jat8Y>
Subject: [Mops] Updated charter, with milestones
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: Wed, 18 Sep 2019 16:25:52 -0000
Hi, Here’s an updated proposal for the charter. Key updates include milestones, and a bit of language adjustment in the first paragraph to make it not seem like we are asking network operators to declare they are crumbling in the face of video. Input appreciated. 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 challenged by these updated requirements. 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 Feb 2020 Draft of edge network operational considerations for streaming media (was Taxonomy of Issues in Internet Media) Feb 2020 Initial draft operational considerations for low latency streaming video applications Mar 2020 Draft documenting Streaming Video Alliance (SVA) reliance on IETF protocols Mar 2020 Draft documenting Society of Motion Picture and Television Engineers (SMPTE) protocol reliance on IETF protocols Jul 2020 Last-call document on Streaming Video Alliance (SVA) reliance on IETF protocols (including explicit outreach to SVA) Jul 2020 Last-call document on Society of Motion Picture and Television Engineers (SMPTE) protocol reliance on IETF protocols (including explicit outreach to SMPTE) Jul 2020 Revised draft of edge network operational considerations for streaming media Jul 2020 Revised draft operational considerations for low latency streaming video applications Nov 2020 Last-call document on edge network considerations for streaming media Nov 2020 Last-call document on operational considerations for low latency streaming video applications Nov 2020 Develop work items specific to media acquisition and delivery -- ------------------------------------------------------------------- Leslie Daigle Principal, ThinkingCat Enterprises ldaigle@thinkingcat.com -------------------------------------------------------------------
- [Mops] Updated charter, with milestones Leslie Daigle