From nobody Sun Aug 6 01:15:07 2017 Return-Path: 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 71FB6132017 for ; Sun, 6 Aug 2017 01:15:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.22 X-Spam-Level: X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no 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 KDpOjSJqMa0k for ; Sun, 6 Aug 2017 01:15:04 -0700 (PDT) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D2C0A131C96 for ; Sun, 6 Aug 2017 01:15:03 -0700 (PDT) Received: from 172.18.7.190 (EHLO lhreml708-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DMA33155; Sun, 06 Aug 2017 08:15:01 +0000 (GMT) Received: from DGGEMM404-HUB.china.huawei.com (10.3.20.212) by lhreml708-cah.china.huawei.com (10.201.108.49) with Microsoft SMTP Server (TLS) id 14.3.301.0; Sun, 6 Aug 2017 09:14:59 +0100 Received: from DGGEMM506-MBX.china.huawei.com ([169.254.3.170]) by DGGEMM404-HUB.china.huawei.com ([10.3.20.212]) with mapi id 14.03.0301.000; Sun, 6 Aug 2017 16:14:55 +0800 From: Roni Even To: "Glenn.Deen@nbcuni.com" CC: "ggie@ietf.org" Thread-Topic: Prague side meeting Thread-Index: AdMOjBVWSBfR989zS7uhWfn0UsfJyA== Date: Sun, 6 Aug 2017 08:14:54 +0000 Message-ID: <6E58094ECC8D8344914996DAD28F1CCD7F180D@DGGEMM506-MBX.china.huawei.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.200.202.51] Content-Type: multipart/alternative; boundary="_000_6E58094ECC8D8344914996DAD28F1CCD7F180DDGGEMM506MBXchina_" MIME-Version: 1.0 X-CFilter-Loop: Reflected X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020205.5986D005.00E3, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.3.170, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32 X-Mirapoint-Loop-Id: 086f87a47050a344f16ebf2ab79199ac Archived-At: Subject: [GGIE] Prague side meeting X-BeenThere: ggie@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discuss IETF-related items surfaced in the W3C GGIE Task Force List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Aug 2017 08:15:06 -0000 --_000_6E58094ECC8D8344914996DAD28F1CCD7F180DDGGEMM506MBXchina_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Glen, We had a good meeting in Prague. I did not take notes but I think it will b= e good to start the discussion on the topics we would like to cover when we= talk about media transport. Do you have any plans to send the minutes from our meeting. It will also be good to use the list of participants to ask those who are n= ot on the ggie mailing list to join it, if they have an interest in working= together. Thanks Roni Even --_000_6E58094ECC8D8344914996DAD28F1CCD7F180DDGGEMM506MBXchina_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi Glen,

We had a good meeting in Prague. I did not take note= s but I think it will be good to start the discussion on the topics we woul= d like to cover when we talk about media transport.

Do you have any plans to send the minutes from our m= eeting.

It will also be good to use the list of participants= to ask those who are not on the ggie mailing list to join it, if they have= an interest in working together.

Thanks

Roni Even

--_000_6E58094ECC8D8344914996DAD28F1CCD7F180DDGGEMM506MBXchina_-- From nobody Mon Aug 14 14:39:34 2017 Return-Path: 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 1C04113243B for ; Mon, 14 Aug 2017 14:39:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.92 X-Spam-Level: X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no 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 OszUWyYzXv7f for ; Mon, 14 Aug 2017 14:39:28 -0700 (PDT) Received: from mx0a-00176a04.pphosted.com (mx0a-00176a04.pphosted.com [67.231.149.53]) (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 9E6D5132431 for ; Mon, 14 Aug 2017 14:39:28 -0700 (PDT) Received: from pps.filterd (m0048276.ppops.net [127.0.0.1]) by m0048276.ppops.net-00176a04. (8.16.0.21/8.16.0.21) with SMTP id v7ELbZvX015822 for ; Mon, 14 Aug 2017 17:39:27 -0400 Received: from usushmgip001.mail.tfayd.com ([216.178.109.235]) by m0048276.ppops.net-00176a04. with ESMTP id 2c9xatbta5-1 (version=TLSv1.2 cipher=RC4-SHA bits=128 verify=NOT) for ; Mon, 14 Aug 2017 17:39:26 -0400 Received: from unknown (HELO USUSHECWP003.mail.tfayd.com) ([10.40.33.204]) by usushmgip001.mail.tfayd.com with ESMTP; 14 Aug 2017 14:39:26 -0700 Received: from potemwp00027.mail.tfayd.com (100.124.56.51) by USUSHECWP003.mail.tfayd.com (3.156.41.21) with Microsoft SMTP Server (TLS) id 14.3.266.1; Mon, 14 Aug 2017 14:39:24 -0700 Received: from potemwp00029.mail.tfayd.com (100.124.56.53) by potemwp00027.mail.tfayd.com (100.124.56.51) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.669.32; Mon, 14 Aug 2017 15:39:22 -0600 Received: from potemwp00029.mail.tfayd.com ([100.124.56.53]) by potemwp00029.mail.tfayd.com ([100.124.56.53]) with mapi id 15.01.0669.032; Mon, 14 Aug 2017 15:39:22 -0600 From: "Deen, Glenn (NBCUniversal)" To: Roni Even CC: "ggie@ietf.org" Thread-Topic: Notes from Prague side meeting on a Video Interest Community @ IETF Thread-Index: AQHTFUXLyFNjnRcDe0uBx/6Zk3FXRw== Date: Mon, 14 Aug 2017 21:39:22 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.7.3.170325 x-ms-exchange-messagesentrepresentingtype: 1 x-originating-ip: [100.126.25.30] x-exclaimer-md-config: 47edc00f-f2d6-45ef-be83-8a353bd47e45 Content-Type: multipart/alternative; boundary="_000_D5AF7C8BE141Fglenndeennbcunicom_" MIME-Version: 1.0 X-CFilter-Loop: Forward X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-08-14_19:, , signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1706020000 definitions=main-1708140355 Archived-At: Subject: [GGIE] Notes from Prague side meeting on a Video Interest Community @ IETF X-BeenThere: ggie@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discuss IETF-related items surfaced in the W3C GGIE Task Force List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Aug 2017 21:39:32 -0000 --_000_D5AF7C8BE141Fglenndeennbcunicom_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Roni, Sorry for the delayed response due to travel and vacation. How's this? A= nyone, please feel free to contribute any corrections, or comments, or even= begin the discussion. - Here's an attempt at a summary of the session, and more importantly capturi= ng the next steps that we discussed at the end of the meeting: At IETF99 on July 20th ,a small group of ~20 attendees, had a side meetin= g to talk about the general topic of video related interests and activity a= t the IETF. (side note: having rooms available for signup is very helpful in arrangi= ng side meetings, and I hope the IETF chooses to continue doing it). The core discussion was around there being a growing participation at the I= ETF from people working on video, and that with the switch by broadcasters,= film makers, and professional production and distribution equipment away f= rom SDI to IP that this community is likely to see continued growth. Part= of the discussion was about how those of us already at IETF could better c= onnect with one another, and what could possibly be done to create a way fo= r new comers with an interest in video to easily connect with the iETF and = with IETFers already working on video. We also discussed, recent meetings and experiences we IETF participants wor= king on video have had,and that there is general agreement that video is im= pacted by, and impacts, many IETF areas of work. This makes it challenging = for people working with video technologies to find a single place within th= e IETF to discuss needed advances: any one problem touches on multiple Area= s of the IETF. Having a way to connect with an share video related interests, activity, an= d needs across different IETF areas was of interest to those in the room. The room consensus was that there is interest in forming some sort of group= , though it wasn't clear what sort of group at the IETF this would would fi= t into. More examination of the problem space is needed, and more discussi= on amongst those interested is also needed. As a next step the room agreed that it seems useful to create some forum fo= r regular engagement of video technology people at or around IETF meetings.= The purpose of this engagement would be to share and discuss current issue= s (with transport, production, distribution of video). Discussion of impact= ed and important IETF technologies is in scope, along with developing speci= fic proposals for work to update those standards (to be proposed within exi= sting IETF working groups, or new ones, as needed). It is not expected that= these discussions will focus on any one architecture for handling video, o= r seek to standardize a particular outcome. Actions from the meeting: 1. We agreed to continue to discuss what a group might look like, and fu= nction - the thinking was to use the Glass to Glass mailing list GGIE@IETF.= ORG until a better option comes around as it is a Glass to Glass Ecosystem = discussion. 2. Have a second meeting in Singapore during IETF100 (possibly with remo= te access), and also IETF101 in London as a number of people said they did= not expect to attend IETF100 in person. 3. Discuss what areas/aspect of the video ecosystem people are intereste= d in including. For example it was thought that perhaps WebRTC, while it d= oes include video, was perhaps an ecosystem unto itself and already had an = active place for those interested to engage one another, but that there wa= s other video activity that touched transport, production, naming, routing,= and operations that might be right to include. The decision was to attemp= t to have that discussion on the GGIE list between now and IETF100, and the= n continue it in person at IETF100. -Glenn From: Roni Even > Date: Sunday, August 6, 2017 at 1:14 AM To: Glenn Deen > Cc: "ggie@ietf.org" > Subject: Prague side meeting Hi Glen, We had a good meeting in Prague. I did not take notes but I think it will b= e good to start the discussion on the topics we would like to cover when we= talk about media transport. Do you have any plans to send the minutes from our meeting. It will also be good to use the list of participants to ask those who are n= ot on the ggie mailing list to join it, if they have an interest in working= together. Thanks Roni Even --_000_D5AF7C8BE141Fglenndeennbcunicom_ Content-Type: text/html; charset="iso-8859-1" Content-ID: <236B192504C33E40BA6AC65862AC2EDE@NBCUNI.COM> Content-Transfer-Encoding: quoted-printable

Hi Roni,

Sorry for the delayed response due to travel and vacation. How’s this= ? Anyone, please feel free to contribute any corrections, or c= omments, or even begin the discussion.

—

Here’s an attempt at a summary of the session, and more importantly c= apturing the next steps that we discussed at the end of the meeting:

At IETF99 on July 20th ,a small group of ~20 attendees, had a s= ide meeting to talk about the general topic of video related interests and = activity at the IETF.

(side note: having rooms available for signup is very hel= pful in arranging side meetings, and I hope the IETF chooses to continue do= ing it).

The core discussion was around there being a= growing participation at the IETF from people working on video, and that w= ith the switch by broadcasters, film makers, and professional producti= on and distribution equipment away from SDI to IP that this community is likely to see continued growth. Pa= rt of the discussion was about how those of us already at IETF could b= etter connect with one another, and what could possibly be done to create a= way for new comers with an interest in video to easily connect with the iETF and with IETFers already working on video.=

We also disc= ussed, recent meetings and experiences we IETF participants working on vide= o have had,and that there is general agreement that video is impacted by, a= nd impacts, many IETF areas of work. This makes it challenging for people working with video technologies to fi= nd a single place within the IETF to discuss needed advances: any one probl= em touches on multiple Areas of the IETF.

Having a way to connect with an share video = related interests, activity, and needs across different IETF areas was of i= nterest to those in the room.

The room consensus was that there is interes= t in forming some sort of group, though it wasn’t clear what sort of = group at the IETF this would would fit into. More examination of = ;the problem space is needed, and more discussion amongst those interested is also needed.

As a next st= ep the room agreed that it seems useful to create some forum for regular en= gagement of video technology people at or around IETF meetings. The purpose= of this engagement would be to share and discuss current issues (with transport, production, distribution of vi= deo). Discussion of impacted and important IETF technologies is in scope, a= long with developing specific proposals for work to update those standards = (to be proposed within existing IETF working groups, or new ones, as needed). It is not expected that thes= e discussions will focus on any one architecture for handling video, or see= k to standardize a particular outcome.

Actions from the meeting:

We agreed to continue to discuss what a group might look like, and func= tion – the thinking was to use the Glass to Glass mailing list GGIE@I= ETF.ORG until a better option comes around as it is a Glass to Glass Ecosys= tem discussion.
Have a second meeting in Singapore during IETF100 (= possibly with remote access), and also IETF101 in London as a number = of people said they did not expect to attend IETF100 in person.
Dis= cuss what areas/aspect of the video ecosystem people are interested in incl= uding. For example it was thought that perhaps WebRTC, while it does = include video, was perhaps an ecosystem unto itself and already had an acti= ve place for those interested to engage one another, but that there was other video activity that = touched transport, production, naming, routing, and operations that might b= e right to include. The decision was to attempt to have that discussi= on on the GGIE list between now and IETF100, and then continue it in person at IETF100.

-Glenn