Re: [GGIE] Where from here?

"Holland, Jake" <jholland@akamai.com> Fri, 30 November 2018 20:55 UTC

Return-Path: <jholland@akamai.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 E3FEE130F11 for <ggie@ietfa.amsl.com>; Fri, 30 Nov 2018 12:55:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.159
X-Spam-Level:
X-Spam-Status: No, score=-4.159 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.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 Lxj6IQr_FK4t for <ggie@ietfa.amsl.com>; Fri, 30 Nov 2018 12:55:55 -0800 (PST)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::1]) (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 0401E130E8F for <ggie@ietf.org>; Fri, 30 Nov 2018 12:55:54 -0800 (PST)
Received: from pps.filterd (m0122332.ppops.net [127.0.0.1]) by mx0a-00190b01.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id wAUKnIIk014110; Fri, 30 Nov 2018 20:55:54 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=jan2016.eng; bh=N7I2kC4WMp4T2G7nRIy0KV3ENSxi26MFyCST5TlwtsQ=; b=UdVIlmS5S7DvMjgPiP8RNAlKgRKLL7adfPRoC4YGs3xbIUcbp7TVS8pSNrt4WfEarX2R FPdqhUK01+DoVLiWYpQeh2v8hx/3dXG78PI55uzBNBm2KXWUp0UjQKK/agA1kksPY0sg bl3Kadg+OlZz/M0OafjKWHnbYFg+Wewgk2oC7laqZNtayqZWnhROFK4OsR+HFdVN345V MUb9uqzVBDXapNAxc99g4PWgBV2VNYoe9NxJMI/UJu92dTdu9TQ/FnO85DFgyj063D15 SfZU8snA3exCHZEOelcbKxiiRUO/L3X2UswzYziLBkYX/q0fvU6isrDIGUwhEZ3XwQZb Cw==
Received: from prod-mail-ppoint3 (a96-6-114-86.deploy.static.akamaitechnologies.com [96.6.114.86] (may be forged)) by mx0a-00190b01.pphosted.com with ESMTP id 2p271wy4p7-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 30 Nov 2018 20:55:54 +0000
Received: from pps.filterd (prod-mail-ppoint3.akamai.com [127.0.0.1]) by prod-mail-ppoint3.akamai.com (8.16.0.21/8.16.0.21) with SMTP id wAUKlPoB001009; Fri, 30 Nov 2018 15:55:53 -0500
Received: from email.msg.corp.akamai.com ([172.27.27.25]) by prod-mail-ppoint3.akamai.com with ESMTP id 2p3cb7r2ku-2 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Fri, 30 Nov 2018 15:55:52 -0500
Received: from USTX2EX-DAG1MB4.msg.corp.akamai.com (172.27.27.104) by ustx2ex-dag1mb4.msg.corp.akamai.com (172.27.27.104) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Fri, 30 Nov 2018 14:55:46 -0600
Received: from USTX2EX-DAG1MB4.msg.corp.akamai.com ([172.27.6.134]) by ustx2ex-dag1mb4.msg.corp.akamai.com ([172.27.6.134]) with mapi id 15.00.1365.000; Fri, 30 Nov 2018 14:55:46 -0600
From: "Holland, Jake" <jholland@akamai.com>
To: Leslie Daigle <ldaigle@thinkingcat.com>
CC: "ggie@ietf.org" <ggie@ietf.org>
Thread-Topic: [GGIE] Where from here?
Thread-Index: AQHUiNHSqxWyruxgYEytRe5amK+k5KVon/4AgACLzoD//38oAA==
Date: Fri, 30 Nov 2018 20:55:45 +0000
Message-ID: <13F6C6E4-1D4A-466F-9582-3DAF231FBAD4@akamai.com>
References: <16C0F13D-CBCA-48AE-8292-13D87762F402@thinkingcat.com> <3061D1B1-F6E2-4E16-A83A-B984E566078C@akamai.com> <0FB000CF-DFD2-4643-9F7B-2C9839E18BCE@thinkingcat.com>
In-Reply-To: <0FB000CF-DFD2-4643-9F7B-2C9839E18BCE@thinkingcat.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.13.0.181109
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.112.231]
Content-Type: multipart/alternative; boundary="_000_13F6C6E41D4A466F95823DAF231FBAD4akamaicom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-11-30_10:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=939 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1811300177
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-11-30_10:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=942 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1811300177
Archived-At: <https://mailarchive.ietf.org/arch/msg/ggie/qAMdXF0wyX7VLOnmtWrA2f_XKC4>
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: Fri, 30 Nov 2018 20:55:57 -0000

From: Leslie Daigle <ldaigle@thinkingcat.com>
But I don’t think you’ve addressed my implied point: it doesn’t much matter what we think, it matters what the IESG thinks if there is to be a WG. And, I’d appreciate others’ thoughts if there is the belief that an OPS working group for anything other than an IETF protocol is something that the IESG is likely to be supportive of.

<Jake>
mboned is an existing example of an ops group that’s not chartered to work on specific protocols, but on a broad suite of technology space. So there’s a precedent in favor of this, at least.
Of course I agree my opinion is not the important one in the final decision, I was only trying to provide my own answer to your question to the group. I would also prefer to see others’ opinions.
</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>

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>