WG Review: Media OPerationS (mops)

The IESG <iesg-secretary@ietf.org> Thu, 03 September 2026 16:25 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@mail2.ietf.org
Received: from [10.244.8.80] (gaia.k8s.ietf.org [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id EFE62134EC00E; Thu, 3 Sep 2026 09:25:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1788452706; bh=pn+9TMWFAT2rW3ZhPjxWJEGjRhyj9h7Cz2AjNaJ1/6w=; h=From:To:Subject:Cc:Reply-To:Date; b=SOr8NZrAkZz+z0QQDVQ+v4uxlHv22Mk6q0UzDAowSlNt05Y0BmqHzEZYzetpR4mHj 5FybZbTrLdSJEcQ32XANXIX7VbkpfuQc0Ck5n4vYoOstSRl7eLjBsxtLVEO9y9vq6P xJyeVaa/yvq8PnE6lrtBuXstxU03pTmApEs7Lgls=
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: WG Review: Media OPerationS (mops)
X-Test-IDTracker: no
X-IETF-IDTracker: 12.73.0
Auto-Submitted: auto-generated
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Message-ID: <178845270571.700896.7674374899378852362@dt-datatracker-6669c7b496-s9mrn>
Date: Thu, 03 Sep 2026 09:25:05 -0700
Message-ID-Hash: JNT7GH35ORR2456HKTCNHCMHGCDANBU7
X-Message-ID-Hash: JNT7GH35ORR2456HKTCNHCMHGCDANBU7
X-MailFrom: iesg-secretary@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: mops@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: iesg@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/nMruAHdDByRkiDI0uQzp7a9RpWw>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>

The Media OPerationS (mops) WG in the Operations and Management Area of the
IETF is undergoing rechartering. The IESG has not made any determination yet.
The following draft charter was submitted, and is provided for informational
purposes only. Please send your comments to the IESG mailing list
(iesg@ietf.org) by 2026-09-13.

Media OPerationS (mops)
-----------------------------------------------------------------------
Current status: Active WG

Chairs:
  Leslie Daigle <ldaigle@thinkingcat.com>
  Jana Iyengar <jri.ietf@gmail.com>

Assigned Area Director:
  Éric Vyncke <evyncke@cisco.com>

Operations and Management Area Directors:
  Mahesh Jethanandani <mjethanandani@gmail.com>
  Mohamed Boucadair <mohamed.boucadair@orange.com>

Technical advisors:
  Glenn Deen <glenn.deen@nbcuni.com>
  Mohamed Boucadair <mohamed.boucadair@orange.com>

Mailing list:
  Address: mops@ietf.org
  To subscribe: https://www.ietf.org/mailman/listinfo/mops
  Archive: https://mailarchive.ietf.org/arch/browse/mops/

Group page: https://datatracker.ietf.org/group/mops/

Charter: https://datatracker.ietf.org/doc/charter-ietf-mops/

Internet-wide and within-domain IP-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. The
focus of MOPS is on identifying areas where existing protocols and/or
networks are challenged by updated requirements.

MOPS will solicit input on media-related 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 within-domain networking. In the
context of this working group, 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.

MOPS provides a venue for both video industry and Internet engineering
experts to engage in discussion of video technology’s requirements of
networking standards, as well as proposals for new uses of IP technology
in video. Where new protocols are needed, MOPS will help identify candidate
venues for their development.

The goals of MOPS include documenting existing protocol and operational issues
with media on the Internet, and identifying requirements for potential IETF
work. The general process of elaboration through documentation will be for
issues to be identified (on the mailing list) and presentations made at WG
meetings. When topics merit more coherent documentation, MOPS will adopt
working group documents to capture the information in Internet-Drafts. If the
working group consensus is that the material of the Internet-Draft is
generally useful for archival purposes, the WG will seek publication of the
work items as informational RFCs. At any point — from early discussion of
topics, through later documentation stages — MOPS may identify a more
appropriate WG for the matter and/or document, and redirect it.

With that in mind, 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 protocols and
technologies developed outside the IETF.

4/ Document operational requirements for media acquisition (for example, from
cameras and recording devices) 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.

In all cases of working with other organizations mentioned above, MOPS will
work with existing liaison managers where the IETF has them, and informal
connections with other organizations otherwise. If new formal liaison
relationships are required, MOPS will work with the IAB to help establish
them.

Media operational and deployment issues with specific protocols or
technologies (such as Applications, Transport Protocols, Routing Protocols,
DNS or Sub-IP Protocols) remain the 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.

There must be a continuing 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:

  Sep 2026 - Last-call document on Network Overlay Impacts to Streaming Video

  Nov 2026 - Network Overlay Impacts to Streaming Video to IESG for
  publication as Informational