[GGIE] Where from here?
"Leslie Daigle" <ldaigle@thinkingcat.com> Fri, 30 November 2018 17:25 UTC
Return-Path: <ldaigle@thinkingcat.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 EAE4C130E7A for <ggie@ietfa.amsl.com>; Fri, 30 Nov 2018 09:25:53 -0800 (PST)
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_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=thinkingcat.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 ySDw-YTIWPXG for <ggie@ietfa.amsl.com>; Fri, 30 Nov 2018 09:25:51 -0800 (PST)
Received: from bisque.maple.relay.mailchannels.net (bisque.maple.relay.mailchannels.net [23.83.214.18]) (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 19CE2130E6E for <ggie@ietf.org>; Fri, 30 Nov 2018 09:25:50 -0800 (PST)
X-Sender-Id: dreamhost|x-authsender|leslie@oceanpurl.net
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 56120502F7C; Fri, 30 Nov 2018 17:25:50 +0000 (UTC)
Received: from pdx1-sub0-mail-a71.g.dreamhost.com (unknown [100.96.26.166]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 1D443502FB6; Fri, 30 Nov 2018 17:25:50 +0000 (UTC)
X-Sender-Id: dreamhost|x-authsender|leslie@oceanpurl.net
Received: from pdx1-sub0-mail-a71.g.dreamhost.com (pop.dreamhost.com [64.90.62.162]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.16.2); Fri, 30 Nov 2018 17:25:50 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: dreamhost|x-authsender|leslie@oceanpurl.net
X-MailChannels-Auth-Id: dreamhost
X-Minister-Quick: 213e319025d16b03_1543598750248_1230243905
X-MC-Loop-Signature: 1543598750248:235300085
X-MC-Ingress-Time: 1543598750248
Received: from pdx1-sub0-mail-a71.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a71.g.dreamhost.com (Postfix) with ESMTP id CDBDB806F3; Fri, 30 Nov 2018 09:25:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=thinkingcat.com; h=from:to :subject:date:message-id:mime-version:content-type :content-transfer-encoding; s=thinkingcat.com; bh=JZ0clgiXziflsB SkzSqoRvUpyG4=; b=b5+j7PYXs0vVoyV2qfspEeDmM8dVBqoFsXj9EAqwGQRaOP eQWHJDEvM4+h0JRt59LX+uRdT2VpEwkfKWhv3poSDNKAamgtUfUDEG8o4a2qnatb 0/hQMGVKUsJGmGa9Qoe5T+hp8LoiH8sX9tGyztwgXoUjAEtM373siTtZna9ic=
Received: from [192.168.1.94] (vtelinet-216-66-102-83.vermontel.net [216.66.102.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: leslie@oceanpurl.net) by pdx1-sub0-mail-a71.g.dreamhost.com (Postfix) with ESMTPSA id 1930680682; Fri, 30 Nov 2018 09:25:48 -0800 (PST)
X-DH-BACKEND: pdx1-sub0-mail-a71
From: Leslie Daigle <ldaigle@thinkingcat.com>
To: ggie@ietf.org
Date: Fri, 30 Nov 2018 12:25:18 -0500
X-Mailer: MailMate (1.12.2r5568)
Message-ID: <16C0F13D-CBCA-48AE-8292-13D87762F402@thinkingcat.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_8CCD087E-857D-488A-8AF8-C273E298AEEC_="
X-VR-OUT-STATUS: OK
X-VR-OUT-SCORE: 0
X-VR-OUT-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedtkedruddvhedguddttdcutefuodetggdotefrodftvfcurfhrohhfihhlvgemucggtfgfnhhsuhgsshgtrhhisggvpdfftffgtefojffquffvnecuuegrihhlohhuthemuceftddtnecunecujfgurhephffvufffoffkgggtgfesrgekmherredtjeenucfhrhhomhepfdfnvghslhhivgcuffgrihhglhgvfdcuoehluggrihhglhgvsehthhhinhhkihhnghgtrghtrdgtohhmqeenucffohhmrghinhepthgvtghhrghrkhdrohhrghenucfkphepvdduiedrieeirddutddvrdekfeenucfrrghrrghmpehmohguvgepshhmthhppdhhvghloheplgduledvrdduieekrddurdelgegnpdhinhgvthepvdduiedrieeirddutddvrdekfedprhgvthhurhhnqdhprghthhepfdfnvghslhhivgcuffgrihhglhgvfdcuoehluggrihhglhgvsehthhhinhhkihhnghgtrghtrdgtohhmqedpmhgrihhlfhhrohhmpehluggrihhglhgvsehthhhinhhkihhnghgtrghtrdgtohhmpdhnrhgtphhtthhopehluggrihhglhgvsehthhhinhhkihhnghgtrghtrdgtohhmnecuvehluhhsthgvrhfuihiivgeptd
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ggie/HQqXeKi5wc1hKTo4hwmjRfAPfds>
Subject: [GGIE] Where from here?
X-BeenThere: ggie@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discuss IETF-related items surfaced in the W3C GGIE Task Force <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: Fri, 30 Nov 2018 17:25:54 -0000
I want to pick up the thread about whether or not we should see about establishing some more formal group at the IETF. Also, see the bottom of this message for a history of the meetings we’ve had at the IETF, and attendance levels. The table probably looks like crap in e-mail; better formatting and more detail (including links to notes!) at https://yana.techark.org/vig-at-ietf/ . Now, a couple of words about what we’ve been trying to achieve with these “video interest group” meetings. One of the things we discovered, while working on the GGIE proposal at the IETF, was that there are a lot of people who are doing video-related work, with and to Internet protocols at the IETF. Nonetheless, many people are not aware of each other’s efforts, if for no other reason than that the work winds up in different Areas — transport, security, art, and even routing. It has seemed to us that bringing these people together so that there is greater awareness — of each other, of the work that’s being done — would help both the work being done, and the IETF as a whole. It can be pretty daunting to try to get one particular thing done in the IETF, and knowing that there are others interested in the outcome can be helpful. Also, the more we can raise awareness of general video interests at the IETF, the more likely the IETF is to recognize the need to address them. We’ve kept on using the GGIE list for coordination simply because it spans those areas, and has 64 members who have, at some time, been interested in/working on video at the IETF. So, that’s where we’ve been. Where from here? If the IETF had a concept of “interest group”, the way other organizations do, we’d pursue that. As it doesn’t, we can look at Working Groups or Research Groups. Working Groups are generally chartered to achieve specific technical outcomes — whether it’s developing a standard or taking care of maintenance tasks on a deployed standard (like the v6ops and dnsop groups that someone mentioned). However, we haven’t been talking about an individual protocol/technology, and we don’t fit in a single area. There are also some “dispatch”-style WGs, typically one per Area — if we had a Video Area at the IETF, we could easily set that up :-). That would suppose there is enough video work at the IETF (beyond the applications and realtime work currently being done) to have multiple working groups. Are we there, yet? So then we come to the other obvious candidate — a research group. It would address the operational needs of finding actual time on the IETF schedule, and it would open us up to broader participation. On the one hand, it seems to fit because we are trying to bring together people to talk about a broad swath of advanced issues related to video. On the other — we’re explicitly not talking about research. We’ve been talking about stuff that is current protocol work, and active product and service development. To do a research group properly, we should actively solicit more input on the longer term work that’s being researched, related to video. While that certainly could be interesting, I’m not sure I see how it feeds back into increasing IETF awareness of video-requirements in protocol work. The alternative, that we’ve been pursuing, is to keep doing the informal thing, until we have some kind of critical mass of IETF participants doing video work to have a clearer idea of whether there is a WG, or an Area, or something else that would better support the ongoing discussion. Here’s our history at the IETF: Video Interest Group IETF 103 (Bangkok) 16 Video Interest Group IETF 102 (Montreal) 19 Video Interest Group IETF 101 (London) 19 Video Content Handling side meeting IETF 100 (Singapore) 16 Streaming Video bar bof IETF 99 (Prague) 20 Streaming Video bar bof IETF 98 (Chicago) 62 GGIE at DISPATCH WG IETF 96 (Berlin) N/A GGIE Bar BoF IETF 94 (Yokohama) 14 Again — more detail, better formatting, at https://yana.techark.org/vig-at-ietf/ . Thoughts? Leslie. -- ------------------------------------------------------------------- Leslie Daigle Principal, ThinkingCat Enterprises ldaigle@thinkingcat.com -------------------------------------------------------------------
- [GGIE] Where from here? Leslie Daigle
- Re: [GGIE] Where from here? Holland, Jake
- Re: [GGIE] Where from here? Leslie Daigle
- Re: [GGIE] Where from here? Holland, Jake
- Re: [GGIE] Where from here? Ali C. Begen
- Re: [GGIE] Where from here? Ali C. Begen
- Re: [GGIE] [EXTERNAL] Re: Where from here? Deen, Glenn (NBCUniversal)