Re: [GGIE] MOPS - Media Ops BoF request

Kyle Rose <krose@krose.org> Tue, 04 June 2019 20:40 UTC

Return-Path: <krose@krose.org>
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 9248E120628 for <ggie@ietfa.amsl.com>; Tue, 4 Jun 2019 13:40:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=krose.org
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 h90ulLTHtc6l for <ggie@ietfa.amsl.com>; Tue, 4 Jun 2019 13:40:44 -0700 (PDT)
Received: from mail-yb1-xb2c.google.com (mail-yb1-xb2c.google.com [IPv6:2607:f8b0:4864:20::b2c]) (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 378F112061C for <ggie@ietf.org>; Tue, 4 Jun 2019 13:40:44 -0700 (PDT)
Received: by mail-yb1-xb2c.google.com with SMTP id x7so5929909ybg.5 for <ggie@ietf.org>; Tue, 04 Jun 2019 13:40:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=krose.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=1z0EfBC98mhe9+sgI+GFKY4bHMyHJ3tYH5XJAtrDCAw=; b=U7fl1AefBkMjV9qFF6KANQdw8AjUQiaA+ZWdEz5ZPwL9AXj+221s0BpnzLfs1V/E84 QdOoPRrDbMv1FIcpoLx7Dp4ctSEYaKJIjsfviM9HJfsxXWu9K1YQ51y1VfvgSph8ZWz2 faI+PcAgznxARh55Jbhn+LjArT6lE/jPDPVD0=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=1z0EfBC98mhe9+sgI+GFKY4bHMyHJ3tYH5XJAtrDCAw=; b=MJ0xWNnI51HQj94lLAoQ4KsnZ/7IpcYMoPZZccDQ3rbIKLWjqJPZ1zUiKx0NfyoN0Z 52rK8oJFDXPP79dTfrZMPN7DZuXGY82gQsWq3B+PR4gOgOF+Mu/SlFWkXE1qOVblpw3l BfvivCUYK0jZuPDIvUxyW7fgMoZqvzHPNOrKEZNhMgl9iPToyGuJInG77VlBNbeZEVRe jD8lU9ZgyNczIL69lDIMwNC+abb8eKLH5PpOaSYN74Skl/2dVIo7YWAD5o4fhp26uQVC DsYnRDwrCTHOd7OoXIFGZsT4+zHplIR3kIJnZONbU/IS5jZcHYPEQlMD/3ihIA/gtMl2 Z6mg==
X-Gm-Message-State: APjAAAVIgnWmt7r8fvrYpudmNJJToXAqG7YO1MBC+G3CVGB8B6GFsGet Rbqq9L7GOc6QZ7AWBd0HoYltMDv+s84bzAeee5JJOT9B
X-Google-Smtp-Source: APXvYqzuMeFq/bjnp1TfePIH4frtQsbyL7skwodLJ7n+DHgSDQ8Zx4FKyr/Wf1inJi17b6i+fHQNupVdXS6ZIAgDim8=
X-Received: by 2002:a25:bf82:: with SMTP id l2mr12358093ybk.247.1559680842924; Tue, 04 Jun 2019 13:40:42 -0700 (PDT)
MIME-Version: 1.0
References: <B2A89BEE-C4BC-4752-9CDE-B4D346E0D2EF@nbcuni.com>
In-Reply-To: <B2A89BEE-C4BC-4752-9CDE-B4D346E0D2EF@nbcuni.com>
From: Kyle Rose <krose@krose.org>
Date: Tue, 04 Jun 2019 16:40:32 -0400
Message-ID: <CAJU8_nWGpyCH9mN1xzgHwe36q2S8-TPykCbMyssNb+N2UvPZJQ@mail.gmail.com>
To: "Deen, Glenn (NBCUniversal)" <Glenn.Deen@nbcuni.com>
Cc: "ggie@ietf.org" <ggie@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009b1aeb058a857e79"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ggie/_kdLXqOH56zPzylaM6US4m6yekQ>
Subject: Re: [GGIE] MOPS - Media Ops BoF request
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: Tue, 04 Jun 2019 20:40:58 -0000

I think the proposed WG charter looks good, and I am in favor of a BoF.

Video delivery poses a critical set of problems for scalable,
latency-sensitive delivery that aren't covered by other high-bandwidth use
cases, such as software downloads (which can tolerate arbitrarily-high
latency). The IETF has standardized many protocols that would be helpful in
scaling up video content delivery to levels seen with OTA and satellite
broadcast (q.v. Jake's slide deck on multicast), but without all the glue
necessary for deployability of those technologies. As a result, these
technologies have not reached the critical mass required to make for a
viable, self-sustaining ecosystem supporting the needs of content
providers, CDNs, networks, and users. The IETF seems like the right venue
for operators to identify blockers and to respond by developing and
publishing new protocols and best practices.

Thanks,
Kyle

On Mon, Jun 3, 2019 at 12:50 PM Deen, Glenn (NBCUniversal) <
Glenn.Deen@nbcuni.com> wrote:

> Hi everyone,
>
>
>
> IETF105 BoF requests are due this Friday, so now would be good time to
> send your comments on the MOPS BoF draft
>
>
>
>
> https://docs.google.com/document/d/1S4soR8QVjbCa1k1CXS8bCXox_h8-zK6kEsS8_IU4yXI/
>
>
>
> The current draft is an amalgam of the discussions we had at IETF104 and
> feedback from a few ADs, but the more the better so please don’t be shy.
>
>
>
> This is a chance to bring forward, officially the topic of creating an
> group with video expertise at the IETF that can help video problems across
> the great diversity of technical areas that are the IETF.  So I encourage
> you to please take a couple of minutes when you get this email, look at the
> draft and comment back the list your thoughts.
>
>
>
> Even – “it looks good to me”  – is helpful to hear.
>
>
>
> regards
>
> Glenn
>
>
>
>
> _______________________________________________
> GGIE mailing list
> GGIE@ietf.org
> https://www.ietf.org/mailman/listinfo/ggie
>