Re: [GGIE] [E] Proposing an actual BoF for IETF 105 in Montreal, looking for volunteers and suggestions

sanjay.mishra@verizon.com Tue, 04 June 2019 22:49 UTC

Return-Path: <sanjay.mishra@verizon.com>
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 07567120397 for <ggie@ietfa.amsl.com>; Tue, 4 Jun 2019 15:49:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.299
X-Spam-Level:
X-Spam-Status: No, score=-4.299 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_MED=-2.3, 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=verizon.com header.b=dm7sZnGU; dkim=pass (1024-bit key) header.d=verizon.com header.b=N+rh77J9; dkim=pass (1024-bit key) header.d=verizon.com header.b=keEyU1R9
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 6gngBgnqda9y for <ggie@ietfa.amsl.com>; Tue, 4 Jun 2019 15:49:01 -0700 (PDT)
Received: from omzsmtpe02.verizonbusiness.com (omzsmtpe02.verizonbusiness.com [199.249.25.209]) (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 A6C1412033C for <ggie@ietf.org>; Tue, 4 Jun 2019 15:49:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=verizon.com; i=@verizon.com; q=dns/txt; s=corp; t=1559688540; x=1591224540; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=UZV8fY0TXxyIOs1RQV9pw+CdfQLpbedN17atZUNawtw=; b=dm7sZnGUPKiCyPNWH+aMyhFKfdMD4ZtlVGaYblNWtVWhXyUsFcyKCudB erZaXFjouJV0OiD+BjO/V69fNF1Dnj6+JGJABD4WnlaEvghgrL91mTrzo eDBhusGvW0mdSbqOjn2fP4gpfVBo/OSd8DCHMr83bzpCPcNWAb5DS1MW8 M=;
Received: from unknown (HELO fldsmtpi01.verizon.com) ([166.68.71.143]) by omzsmtpe02.verizonbusiness.com with ESMTP; 04 Jun 2019 22:48:59 +0000
Received: from rogue-10-255-192-101.rogue.vzwcorp.com (HELO apollo.verizonwireless.com) ([10.255.192.101]) by fldsmtpi01.verizon.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 04 Jun 2019 22:48:43 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=verizon.com; i=@verizon.com; q=dns/txt; s=corp; t=1559688523; x=1591224523; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=UZV8fY0TXxyIOs1RQV9pw+CdfQLpbedN17atZUNawtw=; b=N+rh77J9o3Pk2oWl951YqjdKA4JDa+a8jlLJwfykSNwhVNZqqtErR4su 0WQmPU+6h5BQwc8bZL9sYC2NOhVaxnH8NnxbgpzA3AtXsfPncDl2+7G2W /GAA8COTi2D5y8gp2TInTjiTV1KHT4QfQA8PAZbLQepRQxrbKBE3R0/Wf E=;
Received: from endeavour.tdc.vzwcorp.com (HELO eris.verizonwireless.com) ([10.254.88.163]) by apollo.verizonwireless.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 04 Jun 2019 18:48:43 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=verizon.com; i=@verizon.com; q=dns/txt; s=corp; t=1559688523; x=1591224523; h=to:subject:date:message-id:references:in-reply-to: mime-version:from; bh=UZV8fY0TXxyIOs1RQV9pw+CdfQLpbedN17atZUNawtw=; b=keEyU1R9h4UvoG+iwcfWYfiydSDMTens9sy9iHQZK9yzYCJhCSAFrAES uAVmLfe+9A6S1Q9On0WfXjAR8D4i/Hfn/XjCHtacwihfAUO0ATW4tHA1E NhVTRkrszecdM/4pBiH1phSkA2kQ3VPYKgSc7BWoV7kwAJJPpY0b7bqSZ M=;
From: sanjay.mishra@verizon.com
X-Host: endeavour.tdc.vzwcorp.com
Received: from ohtwi1exh001.uswin.ad.vzwcorp.com ([10.144.218.43]) by eris.verizonwireless.com with ESMTP/TLS/AES128-SHA256; 04 Jun 2019 22:48:43 +0000
Received: from tbwexch03apd.uswin.ad.vzwcorp.com (153.114.162.27) by OHTWI1EXH001.uswin.ad.vzwcorp.com (10.144.218.43) with Microsoft SMTP Server (TLS) id 14.3.248.2; Tue, 4 Jun 2019 18:48:43 -0400
Received: from tbwexch02apd.uswin.ad.vzwcorp.com (153.114.162.26) by tbwexch03apd.uswin.ad.vzwcorp.com (153.114.162.27) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 4 Jun 2019 18:48:42 -0400
Received: from tbwexch02apd.uswin.ad.vzwcorp.com ([153.114.162.26]) by tbwexch02apd.uswin.ad.vzwcorp.com ([153.114.162.26]) with mapi id 15.00.1473.003; Tue, 4 Jun 2019 18:48:42 -0400
To: Leslie Daigle <ldaigle@thinkingcat.com>, "ggie@ietf.org" <ggie@ietf.org>
Thread-Topic: [E] [GGIE] Proposing an actual BoF for IETF 105 in Montreal, looking for volunteers and suggestions
Thread-Index: AQHVFkiVq2FbmQ7ArkyClXvXBzoeJqaMGy8w
Date: Tue, 04 Jun 2019 22:48:42 +0000
Message-ID: <0432da5a81a340e4bb2fcdad5c6b00f4@tbwexch02apd.uswin.ad.vzwcorp.com>
References: <694B8D88-4811-4EC3-BC16-83B37E2EB2D2@thinkingcat.com>
In-Reply-To: <694B8D88-4811-4EC3-BC16-83B37E2EB2D2@thinkingcat.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.144.60.250]
Content-Type: multipart/alternative; boundary="_000_0432da5a81a340e4bb2fcdad5c6b00f4tbwexch02apduswinadvzwc_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ggie/Tyr5j543i0I7krBtO5luD7hRp70>
Subject: Re: [GGIE] [E] Proposing an actual BoF for IETF 105 in Montreal, looking for volunteers and suggestions
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 22:49:04 -0000

Hi Leslie – Thank you for putting the agenda for BOF at Montreal. I fully support this effort and hope this leads to a home for much of “operational” issues relating with delivery of video that otherwise, don’t seem to have a home.

The open caching working group within the Streaming Video Alliance relied on CDNI RFCs and extended those RFCs to account for use case extension however, there are areas such as interoperability, for example, HLS client browser sessions maintaining a sticky session with the final redirected source. This issue has been brought up previously with the HTTP WG without resolution.  When it comes to CDN delegation, the IETF publications do not provide detailed guidance or clarify issues associated with HTTP redirections and how they should be handled by HAS video players.

These “operational” issues would have a better chance of being examined in MOPS and specifications can be developed.

I will send comments to the agenda separately but I wanted to call out my support for the BOF.

Thanks
Sanjay

From: GGIE [mailto:ggie-bounces@ietf.org] On Behalf Of Leslie Daigle
Sent: Wednesday, May 29, 2019 2:01 PM
To: ggie@ietf.org
Subject: [E] [GGIE] Proposing an actual BoF for IETF 105 in Montreal, looking for volunteers and suggestions


Hi,

We’ve been working with Éric to see about having a “Media OPS” bof in Montreal, and I’ve copied a draft agenda/proposal framework, below. Comments welcome.

As the BoF request deadline is approaching, I’d like to get some firm commits on concrete contributions (I-Ds are ideal; presentations are possible). If you have a contribution you’d like to share in the agenda, please let me know; if you’ve already heard from me with a request, I’ll be following up :^) .

Media OPerationS (MOPS) BoF
Area: OPS
Chairs: Leslie Daigle (ldaigle@thinkingcat.com<mailto:ldaigle@thinkingcat.com>), Glenn Deen (glenn.deen@nbcuni.com<mailto:glenn.deen@nbcuni.com>)

Agenda

0/ Agenda bash

1/ Scope of video on the Internet
<contributions solicited>

2/ Video using IETF technologies
<contributions solicited; I was thinking that LURK and OpenCache might fit well here, again>

3/ Open questions for IETF and video

AOB

Full description of BoF:

Internet- and Internet-protocol-delivered video/media is popular, 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. 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.

The purpose of this BoF is to highlight the many existing video activities that are leveraging IETF protocol work, identify gaps in IETF work and/or areas of incompatibility with video technology development efforts being carried out elsewhere, and identify a core group of IETF participants working on video activities across the IETF’s technology areas.

Conflicts to avoid: ???

Expected attendance: 40

Length of session: 90min

Leslie.

--

________________________________

Leslie Daigle
Principal, ThinkingCat Enterprises

ldaigle@thinkingcat.com<mailto:ldaigle@thinkingcat.com>