Re: [Mops] WG Review: Media OPerationS (mops)
"Eric Vyncke (evyncke)" <evyncke@cisco.com> Wed, 23 October 2019 06:40 UTC
Return-Path: <evyncke@cisco.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 4FAA312001E; Tue, 22 Oct 2019 23:40:58 -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=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=JcYLoX6Z; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=Jwm9EmPS
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 apwAQbmj-sER; Tue, 22 Oct 2019 23:40:54 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 660B6120046; Tue, 22 Oct 2019 23:40:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=32613; q=dns/txt; s=iport; t=1571812854; x=1573022454; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=WqyqRt0o3ou96vPnBomIFF4mFeINPOWRTs1KCAkKOzE=; b=JcYLoX6ZoANaZp/tbvNlEio1sWlcLSS1u14VofS/8VjN+znz+BjtBb0q oyBMae1FNu+W4sUbeDY2YXhkBMb6UmJqY8qSc5RDBXjzX2cyeIcIMWFXV C6S6xGvCTf2GMYTxHFT/bt7fcWjswbQ5U0NSGiRwS07zXB5kNIbkAWd+D 0=;
IronPort-PHdr: 9a23:XwlqzBHG9tto/hYxJmnyCZ1GYnJ96bzpIg4Y7IYmgLtSc6Oluo7vJ1Hb+e4z1A3SRYuO7fVChqKWqK3mVWEaqbe5+HEZON0pNVcejNkO2QkpAcqLE0r+efP0fioxH8lqX15+9Hb9Ok9QS47z
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DUAACq9K9d/4QNJK1bChoBAQEBAQEBAQEDAQEBAREBAQECAgEBAQGBe4EcL1AFbFcgBAsqhCaDRwOKWIJciW6OFIFCgRADVAkBAQEMAQEYAQoKAgEBhEACF4MaJDgTAgMJAQEEAQEBAgEFBG2FNwyFSwEBAQEDAQEQER0BASkDBAIFAQ8CAQYCEQMBAg0bAwICAh8GCxQJCAIEAQ0FGweDAAGBeU0DLgECDJVikGICgTiIYXWBMoJ+AQEFgUhBQIJCDQuCFwMGgTaMDxiBQD+BEScfgTcXfj6CG0cBAQMBgSUNEzgNCYJaMoIsjRKCZoU6iRGOMS1BCoIkhw6KDYQLG4I7h1OGQYh/jjaIJ4IQjxACBAIEBQIOAQEFgWkigVhwFTsqAYINATNQEBSDBgwXg1CFFIU/dIEpjnoBAQ
X-IronPort-AV: E=Sophos;i="5.68,219,1569283200"; d="scan'208,217";a="356393373"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 23 Oct 2019 06:40:53 +0000
Received: from XCH-ALN-019.cisco.com (xch-aln-019.cisco.com [173.36.7.29]) by alln-core-10.cisco.com (8.15.2/8.15.2) with ESMTPS id x9N6eq27012258 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 23 Oct 2019 06:40:53 GMT
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by XCH-ALN-019.cisco.com (173.36.7.29) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 23 Oct 2019 01:40:52 -0500
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 23 Oct 2019 02:40:51 -0400
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Wed, 23 Oct 2019 02:40:51 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=L++08TgF9qa498Io/V+bEAWJY9CoRVH4qtJKnSqiYL8FrJqZa2UhjiiQk00SMpeMsS4zAoJrl+dgFs1LIkKmscgDpldeh6ysjGNqK1KAFp6e/C7w8JOCSvX2k1klpRI021RWFRD0XqVoVu+4Wyldm/oTnBOKNhRh4xDkrG4aZ/ilGE11c8mpS2RND4RrlOOMdpPZA0/0ER563ZHZIcrxPJjEXOClafl9LWp3VtDLv79VNxkPfKGYdcVp+JmTE8BA1AC4BvIcE9EljEiN35vbvFEE3x8p/jZsktYuUKEgzsONs8+//V6XY9lcMejSdjhlHu5shLJ424S2WRk0GW6YPg==
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=WqyqRt0o3ou96vPnBomIFF4mFeINPOWRTs1KCAkKOzE=; b=GlJkBaijEt2L3hyii3ylAoJV9Q25AoAGtUngIijzg7h+2uPI/hgwp1IguzA5wMfrfRhn2cQxOvtaWzkDPX54QGkQBF9leVe4N2rCGsEiedpMXfcXk6crgtkgiBuGyT8thV2O8ElyZuCGnVvOAOz9pnSI4rQ9xcxiteywWoY5nYtZ9iZiSZk5ElKSjcecc4+CpSqQOeXDpadlu0q93B6oodwgCAjuulmjm22iX42YkHVQUUis7fH3Ni2dT1KWKhEZ19lE9ZbCXyHXbrDQ956EweHIIbWivYzCXSvTUjwiTl2GhLvG6gShbDxpgepUQ7B9ZVnYgm/2Zg7ZTeQkoYx2Dw==
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=WqyqRt0o3ou96vPnBomIFF4mFeINPOWRTs1KCAkKOzE=; b=Jwm9EmPSxYmEtmKkQhBk4NGZXgeq0zf/jxfb1R+sccwylNAMas6vPPz4GTH1eYSaXsMkiEfeafIIdZ7mPmXkMjFBlYMa8oiy2oPQRhNBuEYsDlgYR+3wqHqZfRCoYxeJEViU4uIFNH9kLtCKY8p2lISiFdTJHgQp7c5zIVX/Lhg=
Received: from MN2PR11MB4144.namprd11.prod.outlook.com (20.179.150.210) by MN2PR11MB4029.namprd11.prod.outlook.com (10.255.181.143) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2347.18; Wed, 23 Oct 2019 06:40:50 +0000
Received: from MN2PR11MB4144.namprd11.prod.outlook.com ([fe80::e4f8:d335:c018:c62a]) by MN2PR11MB4144.namprd11.prod.outlook.com ([fe80::e4f8:d335:c018:c62a%7]) with mapi id 15.20.2347.029; Wed, 23 Oct 2019 06:40:50 +0000
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, The IESG <iesg-secretary@ietf.org>
CC: "mops@ietf.org" <mops@ietf.org>
Thread-Topic: [Mops] WG Review: Media OPerationS (mops)
Thread-Index: AQHViTo+cStcxsWhYEidzr8OWCSCh6dn30gA
Date: Wed, 23 Oct 2019 06:40:50 +0000
Message-ID: <C12FCBF4-AE01-4FBE-9F21-957B5D2698B2@cisco.com>
References: <157141595198.3845.16528921337633672515.idtracker@ietfa.amsl.com> <CAKKJt-euxWw_j=OcV42YvW5Q1rWCsCKHxzyoFDJuvo8pXDDg+A@mail.gmail.com>
In-Reply-To: <CAKKJt-euxWw_j=OcV42YvW5Q1rWCsCKHxzyoFDJuvo8pXDDg+A@mail.gmail.com>
Accept-Language: fr-BE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1e.0.191013
authentication-results: spf=none (sender IP is ) smtp.mailfrom=evyncke@cisco.com;
x-originating-ip: [2001:420:c0c0:1004::49]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 6a07590b-496f-4c8c-5382-08d75783f1c3
x-ms-traffictypediagnostic: MN2PR11MB4029:
x-ms-exchange-purlcount: 4
x-microsoft-antispam-prvs: <MN2PR11MB4029E72F97D1AC4B33149178A96B0@MN2PR11MB4029.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 019919A9E4
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(376002)(396003)(366004)(346002)(39860400002)(51444003)(45074003)(189003)(199004)(6436002)(256004)(76176011)(58126008)(316002)(7736002)(66574012)(186003)(54896002)(14444005)(110136005)(99286004)(6512007)(606006)(236005)(36756003)(71190400001)(71200400001)(6306002)(81166006)(66446008)(33656002)(64756008)(66556008)(2616005)(6246003)(11346002)(6116002)(8676002)(76116006)(966005)(102836004)(91956017)(446003)(5660300002)(66946007)(25786009)(4326008)(81156014)(478600001)(8936002)(229853002)(46003)(6506007)(2906002)(6486002)(4001150100001)(14454004)(486006)(86362001)(476003)(53546011)(66476007); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB4029; H:MN2PR11MB4144.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: l0Cd+VIOE+nMljkCub8Zjz436jnskuSaoJavTmUEwwDNhkkHWD38sE6cUH+5MbdSy1SZ2daQZOlqO9CEWvqIyjV5kKl5k0ubzIoQIg2q/aWhlXLQ36/LOPYoPWfdFKBj4oxkep3GwuEUUZOuf/LFf9XClkM8auZj2ek72Tkf8JnUl/UHqpp8OuQaR7OcAThoi7hfWs9ANZzxB9Y4JW4pdpiN8S3Eob7cQ5ly22dnsYfEcPdPZImUy7J52cel7X/536WiaYUmBhYbu+Eb592qyr73kH1tOrTMG9nxtBs5xJleWFwwfH45zdS6aVMdehAe0e9cWaGg4PRXiepgg6cFPaSdvR7wT/sPOoxMkbrnn6Efsja6HyJ4S0H2OojcAupQZDUfhyP2NICBxy7eKVKZnQKLMsxtY3lpJmJG8pYs6tKJfQkRkTHMGqj4CBk7i/0bNNRyqlFcX66+7TuQQ7xjO8MLe5IO1z7gKhA3j+6Vd5A=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_C12FCBF4AE014FBE9F21957B5D2698B2ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 6a07590b-496f-4c8c-5382-08d75783f1c3
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Oct 2019 06:40:50.3197 (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: QJSyw+fVUg3N1XsMsC938crSN0Q+BAcJPF002gN8w4Y8e2+IxW8h+vDYgTO/yckDzOtsMqb69+5DKeJ8uO3vUw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB4029
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.29, xch-aln-019.cisco.com
X-Outbound-Node: alln-core-10.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/mops/kaXO36_mObJs3RaYcvjQOxVaHhc>
Subject: Re: [Mops] WG Review: Media OPerationS (mops)
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, 23 Oct 2019 06:40:58 -0000
Spencer, Thank you for your detailed reply. I can only support everything you wrote 😉 Regards -éric From: Mops <mops-bounces@ietf.org> on behalf of Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Date: Wednesday, 23 October 2019 at 02:38 To: The IESG <iesg-secretary@ietf.org> Cc: "mops@ietf.org" <mops@ietf.org> Subject: Re: [Mops] WG Review: Media OPerationS (mops) Dear IESG, Chartering MOPS as an IETF working group seems to be the Right Thing To Do. I agree with previous discussions that some topics may not be at the engineering level, but discussions on those topics will have a launching pad, no matter where they end up, which will be a good thing. I'm sure everyone involved is aware of the struggles we've had to obtain inputs and participation from operators (for longer than I've been active at IETF). This is pushing that effort down a level (from IAB and IESG interactions with NANOG, RIPE, and GSMA, among other places, over the past three or four years), and I think that's a good thing as well. I saw discussion about what gets published and what doesn't get published outside MOPS, and I would encourage the responsible AD to be flexible as MOPS figures that out - we have had discussions with NOGs about Best Current Operational Practices/BCOP documents, so the possible set of choices MOPS could consider might be broader than the usual IETF working group. The text in the proposed charter on liaison relationships is fine, as far as it goes, but I hope all the MOPSters remember that the IETF cooperates best when it and another organization have overlapping participants - that's even more informal than "informal liaisons". The more that can be encouraged, the better for MOPS. (Leslie will understand this very well, from her time as IAB chair) I hope I'm able to contribute to this working group, if it's approved by the IESG. Thanks for moving forward on this topic. Best wishes, Spencer On Fri, Oct 18, 2019 at 11:25 AM The IESG <iesg-secretary@ietf.org<mailto:iesg-secretary@ietf.org>> wrote: A new IETF WG has been proposed in the Operations and Management Area. 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<mailto:iesg@ietf.org>) by 2019-10-28. Media OPerationS (mops) ----------------------------------------------------------------------- Current status: Proposed WG Chairs: Leslie Daigle <ldaigle@thinkingcat.com<mailto:ldaigle@thinkingcat.com>> Assigned Area Director: Éric Vyncke <evyncke@cisco.com<mailto:evyncke@cisco.com>> Operations and Management Area Directors: Warren Kumari <warren@kumari.net<mailto:warren@kumari.net>> Ignas Bagdonas <ibagdona@gmail.com<mailto:ibagdona@gmail.com>> Technical advisors: Warren Kumari <warren@kumari.net<mailto:warren@kumari.net>> Mailing list: Address: mops@ietf.org<mailto: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- 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. The focus of MOPS 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; and 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 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 dispatch 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. The IESG is establishing this working group on an experimental basis and intends to review it, for rechartering to continue or else closure, in 2 years. Milestones: Feb 2020 - Draft of edge network operational considerations for streaming 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 Nov 2021 - IESG to decide whether continue, re-charter or close MOPS WG -- Mops mailing list Mops@ietf.org<mailto:Mops@ietf.org> https://www.ietf.org/mailman/listinfo/mops
- [Mops] WG Review: Media OPerationS (mops) The IESG
- Re: [Mops] WG Review: Media OPerationS (mops) Spencer Dawkins at IETF
- Re: [Mops] WG Review: Media OPerationS (mops) Eric Vyncke (evyncke)
- Re: [Mops] WG Review: Media OPerationS (mops) Deen, Glenn (NBCUniversal)
- Re: [Mops] WG Review: Media OPerationS (mops) Stephan Wenger
- Re: [Mops] WG Review: Media OPerationS (mops) Joerg Ott