IETF Logo Mail Archive

Re: Call for Community Input: Web Analytics on www.ietf.org

"Salz, Rich" <rsalz@akamai.com> Tue, 21 May 2019 16:01 UTC

Return-Path: <rsalz@akamai.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3311120144 for <ietf@ietfa.amsl.com>; Tue, 21 May 2019 09:01:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.711
X-Spam-Level:
X-Spam-Status: No, score=-2.711 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 F8WUFHGneTXv for <ietf@ietfa.amsl.com>; Tue, 21 May 2019 09:01:49 -0700 (PDT)
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 1D6DD120041 for <ietf@ietf.org>; Tue, 21 May 2019 09:01:49 -0700 (PDT)
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 x4LFvHkt027462; Tue, 21 May 2019 17:01:47 +0100
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 : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=zfS48mTP2hu1RwK1wwVFNFsTaqMt8hF2XvNL5BVLbg8=; b=fWzH6jR3AeNWdjCG6JEynRycewU1jQOdxs5jSRIr4xML43vbmV430X+0NSQnpQm3AtZn 6bajJE6eE0mL+9FdfP0IrlDkJhfPNet5ewWhNgY/R7hp9XV8cstfItUnqoWU9dGefX0C RLh2Ym47o6Bctg5z5n0KQoP+KjgQU33q5aS998mG3UNWFgvq/R12ZDzDQlKe/0Ig1UTU XUF9Z8ZGmqXYFBs9IoRyxuHa8tB/Hz1tqdvLlKvO4XOAmlmp9nZOIBaYxK5fXkYlFGbn aDXe0iTXb+jIvdQxLh+VQrIwHsbccJdVrulD83NoHB0G5gXstbK88dDZiuag1biygkEk rg==
Received: from prod-mail-ppoint1 (prod-mail-ppoint1.akamai.com [184.51.33.18] (may be forged)) by mx0a-00190b01.pphosted.com with ESMTP id 2smd97j7ke-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 21 May 2019 17:01:47 +0100
Received: from pps.filterd (prod-mail-ppoint1.akamai.com [127.0.0.1]) by prod-mail-ppoint1.akamai.com (8.16.0.27/8.16.0.27) with SMTP id x4LFkmUa016833; Tue, 21 May 2019 12:01:45 -0400
Received: from email.msg.corp.akamai.com ([172.27.25.30]) by prod-mail-ppoint1.akamai.com with ESMTP id 2sjdcvmcm2-3 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 21 May 2019 12:01:42 -0400
Received: from USTX2EX-DAG1MB1.msg.corp.akamai.com (172.27.27.101) by ustx2ex-dag1mb3.msg.corp.akamai.com (172.27.27.103) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 21 May 2019 11:00:24 -0500
Received: from USTX2EX-DAG1MB1.msg.corp.akamai.com ([172.27.6.131]) by ustx2ex-dag1mb1.msg.corp.akamai.com ([172.27.6.131]) with mapi id 15.00.1473.003; Tue, 21 May 2019 11:00:24 -0500
From: "Salz, Rich" <rsalz@akamai.com>
To: Mark Nottingham <mnot@mnot.net>, Roman Danyliw <rdd@cert.org>
CC: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Call for Community Input: Web Analytics on www.ietf.org
Thread-Topic: Call for Community Input: Web Analytics on www.ietf.org
Thread-Index: AdUP5slpo2lErwMLRf2heyYkUQLDIwALN7OAAADVF4D//79igA==
Date: Tue, 21 May 2019 16:00:23 +0000
Message-ID: <74213819-4F21-4518-ADCA-8247ED9AD5BD@akamai.com>
References: <359EC4B99E040048A7131E0F4E113AFC01B336F9EC@marathon> <alpine.LRH.2.21.1905211123450.6478@bofh.nohats.ca> <C1F7C275-5EB6-4A18-8824-A18E5051C1D3@mnot.net>
In-Reply-To: <C1F7C275-5EB6-4A18-8824-A18E5051C1D3@mnot.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.19.0.190512
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.37.44]
Content-Type: text/plain; charset="utf-8"
Content-ID: <E14337135302F24388A0132B163C796D@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-05-21_03:, , 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=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1905210098
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-05-21_03:, , 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=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1905210099
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/anZ9K9dBXK7OzhD7xvi8oM_fE4I>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 May 2019 16:01:51 -0000

>    I agree that tools and datatracker should be included; while the "main" site is important, they are the critical resources that most people interact with.
  
I believe the community that uses datatracker is, mostly, different from the community that uses the main website. What is the point of doing analytics -- which community are we mainly trying to assess and improve?  I believe datatracker has a broad enough input channel for improvement and should be left out of this effort.

I will be sad on the day that the IETF puts up a "we use cookies" GDPR notification.  I share Stephen's mild concerns about tracking and privacy.

v2.23.0 | Report a Bug | By Email