Re: [GGIE] Where from here?

"Ali C. Begen" <ali.begen@networked.media> Sat, 01 December 2018 00:06 UTC

Return-Path: <ali.begen@networked.media>
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 CB67E130EDA for <ggie@ietfa.amsl.com>; Fri, 30 Nov 2018 16:06:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.358
X-Spam-Level:
X-Spam-Status: No, score=-3.358 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-1.459, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=networked-media.20150623.gappssmtp.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 Gj0-QWXE9iTs for <ggie@ietfa.amsl.com>; Fri, 30 Nov 2018 16:06:04 -0800 (PST)
Received: from mail-it1-x12f.google.com (mail-it1-x12f.google.com [IPv6:2607:f8b0:4864:20::12f]) (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 03F1712D7F8 for <ggie@ietf.org>; Fri, 30 Nov 2018 16:06:04 -0800 (PST)
Received: by mail-it1-x12f.google.com with SMTP id i7so1192574iti.2 for <ggie@ietf.org>; Fri, 30 Nov 2018 16:06:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networked-media.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=XDeEqe3bYK4EmTlPfx3zKJsSFCj99wk9rr690aQ17vE=; b=pA3O8ySYX5N6+LmVjDwMbqz0NNXTRGuTtP7RM0sFM7/uv+LdMRmpCwb4nS1Pc51A46 p1MSSEA2F/9pKpzVLwwrb9I19S3/TN9KmPmKaMRGcJNG+0fLHErkOURWRtFGCMAHsIFh kfFKerIjekp6rtQYBI9+jAKyt4FHgvM8V0h3Pz/qjFkKPgZ1qhnaDsJz+eB7cwk+hNIS nXcBZBAxcDC8OMxVqFRSyDTGOAWtVaTwfCYRDnj3RErz9mZEKV/Up8cQyRMdnFXqld8o sMpGH/BVGr6Ivg5eKaf3hR7Co/TQre4K45OSt+oIPXvybujwj/pI9UfqBhoE/NC605lw gjPA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=XDeEqe3bYK4EmTlPfx3zKJsSFCj99wk9rr690aQ17vE=; b=dbFZYznCL7x1DgfTQ6u4WuMPjAKkUme/kWwYyNV8cid4AtfsghiH2ReH53ebtz8Mez CdNDBPZX9MMJu6BM8rhWoROPt4iTd4ioOzMVjH6HLb3cUKcAB8ChaEJEAFFT+ZCXOK/0 q27wThwWzTG/ceQfSjErlaeP4oFXTaV632S7RAgliV2lcSoFz4TP4hGY5vqn9clFa6Z3 NYlpW8YY7y9cBAu+Qu/mgz59iss3vWOdMEF+l23ZyEtrV5EpWzE36r6aCDUXDndhtB0Y 6qtkEoKvYtPny3NNsAhiiJ7FW7DN1ALILr9nvrJrXmm40FcZIwm2ontuOeZmZlotAFP2 uAwQ==
X-Gm-Message-State: AA+aEWbRgtX0maLYl4oRAif07wBiajrnhEgJwVRg6tWM/VQrTaCZf7mp JeMsBOm9QyulvRVqqLfLIYJHjCRTt9HqKUsR
X-Google-Smtp-Source: AFSGD/VVp0BG1hgokGYkUnJyYgA9vrs54uHxeGaWiUYLOicKxZOKvgSuGHDkoaFiKT5evluW3U2eZg==
X-Received: by 2002:a02:410e:: with SMTP id x14mr6689881jaa.36.1543622763134; Fri, 30 Nov 2018 16:06:03 -0800 (PST)
Received: from [10.152.0.107] (fw800-d-iowa-aurora-co-dnv.comcast.net. [198.178.8.81]) by smtp.gmail.com with ESMTPSA id z133sm278009itb.36.2018.11.30.16.06.01 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 30 Nov 2018 16:06:02 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 12.1 \(3445.101.1\))
From: "Ali C. Begen" <ali.begen@networked.media>
In-Reply-To: <13F6C6E4-1D4A-466F-9582-3DAF231FBAD4@akamai.com>
Date: Fri, 30 Nov 2018 17:05:58 -0700
Cc: Leslie Daigle <ldaigle@thinkingcat.com>, "ggie@ietf.org" <ggie@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <42C5C573-3826-4A71-BE2D-53BC3BD5C85D@networked.media>
References: <16C0F13D-CBCA-48AE-8292-13D87762F402@thinkingcat.com> <3061D1B1-F6E2-4E16-A83A-B984E566078C@akamai.com> <0FB000CF-DFD2-4643-9F7B-2C9839E18BCE@thinkingcat.com> <13F6C6E4-1D4A-466F-9582-3DAF231FBAD4@akamai.com>
To: "Holland, Jake" <jholland@akamai.com>
X-Mailer: Apple Mail (2.3445.101.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ggie/n405BwZF_vrgGpfpOybMET2vBCQ>
Subject: Re: [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: Sat, 01 Dec 2018 00:06:06 -0000

> </Jake>
>> However, Ali had some good counterpoints that I haven’t seen addressed,
>> namely:
>> 2. Certain folks in the ietf community are interested in media but then
>> many media related people are not even aware of the ietf or irtf. How
>> do we go about them?
> What’s your definition of success? For the purposes of what we’ve been trying to do within the IETF (get existing players to have more awareness of each other and generally raise awareness of the work that exists already), I don’t think that’s true.
> <Jake>
> Sorry I was unclear on this, but this was a quote from Ali, not me.
> I was saying I don’t fully understand Ali’s position, and on the bottom line, that I don’t agree with it right now. I’m not sure what his definition of success is in this context, but I assumed it meant something like “having a positive impact on how media operates on the internet”.
> </Jake>

Media touches on a lot of things. There is the production side, distribution side and consumption side. All those are trying to move to all-IP, hence the relevance to the IETF. There are several organizations (some regional like DVB vs. ATSC or SCTE or global like MPEG, CTA, 3GPP) working in each of these domains. If there were to be an ops group or IRTF group, what would the charter look like? We cannot boil the ocean, so we need to pick some certain problems. What would they be?

Doing an audio codec in the IETF worked, but the same is not true for video. There were attempts to bring adaptive streaming related work to the IETF (I recall three attempts), they were shot down right away. There were parity FEC related RFCs, yet external organizations (VSF and DVB) went ahead and defined their own version, creating incompatibility with the RFCs. That was PITA for many operators and vendors. Then, we did the correct one here in the IETF, but nobody cared about it anymore because their stuff was already deployed.

Don’t get me wrong, I wish there were more collaboration, and problems were well defined and handled in few rather than too many places. But, the differences in culture as well as IPR rules make it quite difficult to work together. If we can make something happen to improve the situation, I am all supportive.


> Again — not a complete follow up to your note, but I’m going to go back to listening for a bit.
> <Jake>
> Me too, I think I’ve said more than enough. I’ve expressed my opinion and I’m done except if I think I’ve been misunderstood.
> Cheers, and thanks.
> </Jake>
> _______________________________________________
> GGIE mailing list
> GGIE@ietf.org
> https://www.ietf.org/mailman/listinfo/ggie