Return-Path: X-Original-To: pim@ietfa.amsl.com Delivered-To: pim@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8900F12013E; Tue, 16 Jul 2019 16:00:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.996 X-Spam-Level: X-Spam-Status: No, score=-1.996 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 OVPRmuqs8wNn; Tue, 16 Jul 2019 16:00:05 -0700 (PDT) Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 782881200A4; Tue, 16 Jul 2019 16:00:05 -0700 (PDT) Received: by mail-ed1-x52a.google.com with SMTP id w13so22455067eds.4; Tue, 16 Jul 2019 16:00:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:mime-version:date:message-id:subject:to:cc; bh=OUe2YbajMtweKkYwkWlahwxW9QXRbfNaNdSyVCVmKyw=; b=ujWPJbsH0VWJSPomIi6Hy0Euu/Xf9rLkRkzKUtfEvdpCgVoyhmBLIjqtI4qpAHVAZ2 F9km9mIUgXqCMmhVuzOUeF9rAApAAoxt94yuGLNns7/tSW4st52May4aogeHIyTD0G+/ nVk0IFXtasmX0aoLxmJFkpKdQkaK2c8paa6Hd8ghC/iYOOuxqtCxs96snsw7Ru0JlOiQ TU7GXf4sCPTY2GckaKMwzBUMnTYlmr6xiOD26YmgjAGuvS5QMNJW+9HIUa/TXswvFFdA 6uXTHk2R4TnamVzX1peCFg9eKZ/MvdkDopHs9PtNAo4ERy9We4YDGd0S5X1AwHPGNByJ GbUg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:date:message-id:subject:to:cc; bh=OUe2YbajMtweKkYwkWlahwxW9QXRbfNaNdSyVCVmKyw=; b=s8s+ZFhvPoBZlU8Scj98cdipLBfLs4s2VyTyNoVSJZImmo9ovPPXIOBh7qT4kIKJqu 6P94Iad9aFhexq8K3QGtHp2nYJMuw6Axbnhey8sAZYHVMi6tIxb764KHm79HOq68l6Al N+7pJLwFCwNMcdkSl4aS9aIA3DpP/1QaR7cUHkrdXgPRAwr9+ssVTMqG9nfxnzGbZsaN Ngw0KKHtO4NEnLXNZqLYqXJYYauegBq7LXmIp243+CPQ4DztmGwsJkQxh733CQaHXZma E4sO5BejaHAWSlnqbnrDnfd9cGLB18QMJ+eBgQjnnxXWwVsHfBV7u+6D6cLKyd6Z9YBn P+sg== X-Gm-Message-State: APjAAAVGgRsQHBo7D0RNHiWglgrW72Z596WBrxWtDWKhgd4tUs4tuRF+ kQe1+jiIu+DZyM5kLsB+f7leUvWx+dxJXnvF6l9hlenh X-Google-Smtp-Source: APXvYqx7VgLwOfvlIlNeA2+eHfZVELXFRDic6pftepDiaDZ4HZkjKPDOAI3NmNIm/UWBji2hcpXRwOoTAsyrcbW8i4I= X-Received: by 2002:a17:906:1916:: with SMTP id a22mr27559703eje.271.1563318003928; Tue, 16 Jul 2019 16:00:03 -0700 (PDT) Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Tue, 16 Jul 2019 19:00:03 -0400 From: Alvaro Retana MIME-Version: 1.0 Date: Tue, 16 Jul 2019 19:00:03 -0400 Message-ID: To: pim@ietf.org Cc: mboned@ietf.org Content-Type: multipart/alternative; boundary="0000000000004b9397058dd4568e" Archived-At: Subject: [pim] FYI:Media Operations BOF in Montreal X-BeenThere: pim@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Protocol Independent Multicast List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jul 2019 23:00:08 -0000 --0000000000004b9397058dd4568e Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I think the MOPS BOF in Montreal may be interesting to some of you. This is the description from the =E2=80=9CBOFs @ IETF 105=E2=80=9D blog [1]= : "Media Operations (MOPS): Many of those involved in the delivery of streaming Internet video have been gathering regularly during unofficial side meetings and on the Glass-to-Glass Ecosystem (GGIE) mailing list to discuss operational and interoperability issues related to video. The MOPS BOF will solicit input on operational issues and practices as well as existing and proposed technologies related to the deployment, engineering, and operation of media streaming and manipulation protocols and procedures on the Internet. The BOF=E2=80=99s scope is media and media protocols=E2=80= =99 interactions with the network, but not the technologies of control protocols or media formats. This will be a working-group-forming BOF.=E2=80=9D The agenda [2] includes a link to a potential charter. Alvaro. [1] https://www.ietf.org/blog/ietf105-bofs/ [2] https://datatracker.ietf.org/meeting/105/materials/agenda-105-mops-00 --0000000000004b9397058dd4568e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable =
I think the MOPS BOF in Montreal may be interest= ing to some of you.

This is the description from the =E2=80=9CBOFs @ IETF 105=E2=80=9D blog [1= ]:

"Media Oper= ations (MOPS): Many of those involved in the delivery of streaming Internet= video have been gathering regularly during unofficial side meetings and on= the Glass-to-Glass Ecosystem (GGIE) mailing list to discuss operational an= d interoperability issues related to video. The MOPS BOF will solicit input= on operational issues and practices as well as existing and proposed techn= ologies related to the deployment, engineering, and operation of media stre= aming and manipulation protocols and procedures on the Internet. The BOF=E2= =80=99s scope is media and media protocols=E2=80=99 interactions with the n= etwork, but not the technologies of control protocols or media formats. Thi= s will be a working-group-forming BOF.=E2=80=9D

The agenda [2] includes a link to a potential = charter.
[2]=C2=A0https://datatracker.ietf.org/meeting/10= 5/materials/agenda-105-mops-00=C2=A0
=
--0000000000004b9397058dd4568e--