Subject: [GGIE] Minutes from the Chicago Bar Bof on Video Streaming

From: "Deen, Glenn (NBCUniversal)" <[email-masked]>
Date: Mon, 10 Jul 2017 22:48:27 +0000

Hi everyone,

Here are some rough minutes of the Video Streaming bar-bof in Chicago at IETF98.

-glenn

----------------

Video Streaming Bar-BoF Meeting Minutes

Held on 3/27/2017 During IETF 98, Chicago, IL

Introduction

These are the rough minutes from the informal Video Streaming Bar-BoF held during IETF98.  As a barBoF it wasn't an official IETF event, instead it was an informal meet up of people interested in the topic of Internet video.

Call for Participation

Topic: Video Streaming eXtensions (V-SX)

Description:

Due to its size and sensitivity to network conditions, the transport of video over the Internet has highlighted a significant scalability problem for the Internet.  On the belief that addressing this scalability problem requires better integration between application transport and networking technologies and leveraging IPv6, this Bar BOF will solicit experiences of the scaling problem as perceived from different parts of the industry (network, producer, vendors).

Video is without rival the top use of Internet bandwidth, and its ever growing demand for more bandwidth easily out paces the new capacity being added both globally and regionally with no let up in sight.   Users are frustrated by quality, buffering, and stuttering problems. Video providers and access networks are investing heavily to keep up with demand.  Significant work has be done at the application layer producing more efficient codecs and innovative adaptive bitrate transports like MPEG-DASH.  These access investments and application layer work have helped but they alone have not been enough.

A target of any eventual work and product is to enable video and network routing / management to work more cooperatively and efficiently to transport video.  Successful approaches will need to do so in a backward compatible ways to permit exiting devices and players to take advantage of the improved network efficiencies.

One proposed approach to dealing with issues was outlined in the Glass to Glass Internet Ecosystem BoF proposal - related drafts and mailing list information is provided below.  A demonstration of GGIE will be provided during the BoF, for illustration purposes.  Discussion is expected and encouraged to range further than the specific GGIE proposal.

This will be an interactive discussion and we encourage anyone with an interest in this topic to come and share their ideas.

Agenda

Introduction

Context setting [5min]

Roundtable discussion of the issue(s) [30min]

Demo of GGIE prototype [10min]

Where from here? [15min]

Potential for IETF work - is there interest to pursue?

Work for other groups?

         Mailing List: https://www.ietf.org/mailman/listinfo/ggie

        Relevant drafts:

            draft-deen-daigle-ggie-02 :

            Glass to Glass Internet Ecosystem Introduction

            draft-rose-deen-ggie-use-cases-00 :

            GGIE Internet Video Use Cases

            draft-daigle-deen-ggie-uri-snaptr-00 :

            Glass to Glass Internet Ecosystem URI and S-NAPTR Use

            draft-deen-naik-ggie-men-mpeg-dash-00 :

            Using Media Encoding Networks to address MPEG-DASH video

The Bar BoF Session

Attendance:

Attendance was very good with 70 people counted in the room and a number of others that didn't get counted as they extended out into the hallway.

Unfortunately the session wasn't able to be held in an actual Bar.  After it's initial announcement the response level was going to be too large for the small bar we had picked for the Bar BoF and so the session was relocated to accommodate to large room to handle the attenence.  As it was even the large room was insufficient with many interested people spilling into the hall.

Notes about the BoF

One thing to note when reading the minutes is that while the organizers attempted to make the session discussion a more general discussion and sharing about problems in video streaming as well as exploiting IPv6 features, many attendees where interested in directly discussing the ideas in the GGIE Internet Drafts.  Hence the points raised in the session notes jump between being higher level and being specifically about the IDs.

Session Overview:

* Glenn Deen gave the background - why GGIE?

* Leslie Daigle provided additional info - scaling video; integrating applications at IETF - keeping levels separate but flowing between.

* Mark Townsley - Cisco: Provided some background on Cisco efforts.

* Q: How to extend the network to the higher layers? What can the network layer do to stop the "spinning disc" problem; help the higher layers to do their job.

Audience: [Lars Eggert] - Not clear on the problem statement? Streaming media is not new.

A: [Glenn Deen] - #1 use of the network today is video; growing exponentially... bandwidth/devices. Despite growth of infrastructure, can't keep up. Need to go beyond pipes, codecs, etc.

* Audience: [Jake Holland/Akamai] - See holes in the proposal. ICN looking at this too. What about Multicast?; Looks like large routing tables, etc.

A: [Glenn Deen] There isn't a simple one size fits all problem. We need multiple solutions because there are multiple problems and situations. ICN, Multicast, + others. Could do this in isolation alone but better to do in a public forum with multiple perspectives instead of waiting 5-10 years and then doing a harmonization exercise.

Leslie: Move to round table discussion on the topic.

* [Roni Even]: Differences between VOD and video running around the network. Service provider has a problem with carriage/delivery. Network solutions are being discussed in DVB, elsewhere. They have to buy the equipment, etc. File format is another issue. Major problem is the scope of the work is broad - includes video transport. Not much work in IETF on transport. 5G is addressing similar issues.

* Q: What about multicast? Simultaneous, on demand? AMT for offnet...

A: Addressing sports/live, TV shows, all content in general. YouTube 400 hours/minute upload. [Mark Townsley]- multicast keeps coming up. Not just distribution - G2G [?]. Cisco has an effort called "IP better than broadcast". Multicast is good for concurrency when it can be identified, filling buffers. ICN/CCN is pull-based. Push-based needs to be addressed too. Export some of the multicast from one network to another. Might look different when it looks like v6.

* [Glenn Deen]: Great that others are working on this. But there is one group that is not as active - IETF. IETF helped build the Internet and others look to IETF for expertise for knowledge and expertise.

* [Leslie Daigle] - raise your hands

o How many people came looking for the answer - [none raised].

o How many have the answer - [1 or 2].

o How many have part of the answer. [More hands raised]

* [?] - "ICN guys heads are exploding!". Need a problem statement. Have people start with their problem statements.

* [Greg Shepard] - Cisco: List problems and prioritize.

* Q: [Dave Oran] - how many people believe the problem is at the network layer? Others parts? Own transport, application, naming, other. If the problem scope is what to do in the network layer you need to look more broadly. Have not looked carefully at improving video streaming using QUIC [Google?]. Couple resource management of provider, with edge delivery, other. Microsoft - SDN provider, edge, transport but no network layer.

*  [Leslie Daigle] - How do we stop video from being a monolithic chunk of data,

* [?] - Need to improve the codec because it is linearized.

* [Allison Mankin] - Not much reference to the application - selecting among codecs, abilities of codec. [BITAG - Broadband Tech Advisory Group] looks at managing between video providers. Encourage looking at these.

*

Gaurav/Demo

* Explained and ran the demo

* Q: [Jake Holland] - can this be done by redirect?

A: [Gaurav Naik]: it can't be done unless all sources are aware of alternate sources to do the redirect to them.  That requires a high level of coherency and exterior knowledge and that adds to brittleness and complexity.

o Then why give v6 address. Network already knows how to find prefixes.

A: [Glenn Deen] - Part of the motivation is that today manifest tables are a kind of routing table of their own. But they can make poor choices because they are made by the application/cdn layer and not in cooperation with the network.

* [Jake Holland] - if the problem is mapping to the wrong place, then it could occur at network layer as well.

* [From person in "ICN corner"] - you will no longer have persistent connections? Where is the gain?

*  [Dave Oran]- Server load is a better measure of performance than distance to cache. Need QoS routing with server load metrics.

* [??] - Privacy issues. Passing boundaries causes security issues.

A: [Glenn Deen]- we have an answer to that.

Should provide some potential answers here.

* [Eric Vyncke] - 6CN solution video. Use some bits as a profile in the prefix. Other experiments being done. Matrix of metrics.

* [Alexander Pretrescu - CEA]: For the 3 videos on the demo can they be put on real encoding machines? IPV6 is insignificant compared to v4 today. Are the producers of video v6 ready?

o A: [Glenn Deen]- The encoders used are standard MPEG encoders. We pump out segments. Works with any encoder that produces segments. And the player used is off-the-shelf.

o A: [John Brzozowski] - we live with that every day but will get solved with time.

* Are there any equipment manufacturers that consider v6?

A: John - they will

* Jonathan Lennox - is this just for content from Comcast?

o A: [Glenn Deen] - No

* Jonathan Lennox - This gives Comcast full visibility to competitors' content.

A: [Glenn Deen] - You can assign session level address space as one solution. Looking for other solutions.

o [Mark Townsley] - One Use Case for bits in prefix with meaning is to protect lowest level traffic. Protect existing streams.

Leslie Daigle - wrap up.

* Are people interested in continuing the discussion to see what parts of this can be addressed by IETF? Please hmmm

* General response was hmmms for, none against.

* Provide links, contact info, more information on website, etc., here. Should be a continuously updated (curated?) space for Q&A.

Glenn Deen:

* Please come to bits and bytes on Thursday night [Mar 30, 2017].

* Go to [email-masked] for discussion.

Attendees List

In attendance: ~62 on signup sheet. Total attendance: >70.

(Missing some standing in hallway, a few others that didn't sign up).

Name

Company

Email

Glenn Deen

NBCUniversal

[email-masked]

Bill Rose

WJRConsulting

[email-masked]

Leslie Daigle

Thinking Cat Enterprises

[email-masked]

Lenny Giulianio

Juniper

[email-masked]

Jeffrey Zhang

Juniper

[email-masked]

Alex Afanasyev

UCLA

Matt Green

BT

[email-masked]

Craig Taylor

BBC

[email-masked]

Lucas Pardue

BBC R&D

[email-masked]

Gaurav Naik

Drexel Univ.

[email-masked]

Pierre Pfister

Cisco

[email-masked]

Kyle Larose

Sandvine

[email-masked]

Eric Vyncke

Cisco

[email-masked]

Dan Druta

AT&T

[email-masked]

Natasha Rooney

GSMA

[email-masked]

Jon Hudson

Earth [Desnet Industries]

[email-masked]

Al Morton

AT&T Labs

[email-masked]

Robert Kebler

Juniper

[email-masked]

Linda Dunbar

Huawei

[email-masked]

Lixia Zhang

UCLA

[email-masked]

Alex Petrescu

CEA

[email-masked]

Luis M. Contreras

Telefonica

[email-masked]

Marvin Zheng

Huawei

[email-masked]

Rachel Huang

Huawei

[email-masked]

Boris Grozev

Atlassian, Jitsi

[email-masked]

Alex Deacon

MPAA

[email-masked]

Mike Wilkinson

NBCUniversal

[email-masked]

Scott Mansfield

Ericsson

[email-masked]

Ted Mooney

Internet Society

[email-masked]

Greg Shepherd

Cisco

[email-masked]

David Lawrence

Akamai

[email-masked]

Allison Mankin

Salesforce

Thomas Schmidt

Hamburg Univ.

[email-masked]

Phil Sorber

Comcast

Bryan Call

Yahoo

Alex Roscoe

Comcast

[email-masked]

Helen Chen

Jabil

Rong Gu

China Mobile

Dirk Kutscher

Huawei

JÜrg Ott

TUM

Sanjay Mishra

Verizon

[email-masked]

Wes George

Neustar

Phil Hallam-Baker

Comodo

Jonathan Lennox

Vidyo

Roni Even

Huawei

 [email-masked] (from internet search)

Lars Eggert

NetApp

 [email-masked] (from Internet search)

Thomas Fossati

Nokia

Salvatore Lopez

Ericsson

Dan York

Internet Society

Magnus Westerlund

Ericsson

Christer Holmberg

Ericsson

Jake Holland

Akamia

[email-masked]

Jeffry Handal

Cisco

Stephan Emile

Orange

HervÄ Ruellan

Canon CRF

Justin Cerdones

Arris

Tony Tauber

Comcast

Goran Djukic

Cisco

Daniel Migault

Ericsson