Summary of Community Feedback on Web Analytics Project

Roman Danyliw <rdd@cert.org> Thu, 13 June 2019 16:16 UTC

Return-Path: <rdd@cert.org>
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 A36A912015F for <ietf@ietfa.amsl.com>; Thu, 13 Jun 2019 09:16:25 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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=cert.org
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 h1cfNhQeGUBg for <ietf@ietfa.amsl.com>; Thu, 13 Jun 2019 09:16:24 -0700 (PDT)
Received: from veto.sei.cmu.edu (veto.sei.cmu.edu [147.72.252.17]) (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 E12351201C3 for <ietf@ietf.org>; Thu, 13 Jun 2019 09:16:23 -0700 (PDT)
Received: from korb.sei.cmu.edu (korb.sei.cmu.edu [10.64.21.30]) by veto.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id x5DGGM7F047514 for <ietf@ietf.org>; Thu, 13 Jun 2019 12:16:22 -0400
DKIM-Filter: OpenDKIM Filter v2.11.0 veto.sei.cmu.edu x5DGGM7F047514
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cert.org; s=yc2bmwvrj62m; t=1560442582; bh=idFJDhSLSZ/CH+fomLIwLzfVYUuw9hTsq34TcbqGxZs=; h=From:To:Subject:Date:From; b=hIJJAyASOFEu6tWhV0pPWNlP7flXoDS4bZPwM08YBXOWLGXfIdguK6cDIE5u6Pc3/ 4mBch3P8OgWCE4dv3W0oTdCDLbovPfsFYGeOLS+A1cPnAmitNfMevdkkHqwXW/TL/Y 3sYWNgvBnJmv/1UNiu8PJAZ5hsCN3gw2l5w6XwIM=
Received: from CASCADE.ad.sei.cmu.edu (cascade.ad.sei.cmu.edu [10.64.28.248]) by korb.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id x5DGGKQ2013824 for <ietf@ietf.org>; Thu, 13 Jun 2019 12:16:20 -0400
Received: from MARATHON.ad.sei.cmu.edu ([10.64.28.250]) by CASCADE.ad.sei.cmu.edu ([10.64.28.248]) with mapi id 14.03.0439.000; Thu, 13 Jun 2019 12:16:20 -0400
From: Roman Danyliw <rdd@cert.org>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Summary of Community Feedback on Web Analytics Project
Thread-Topic: Summary of Community Feedback on Web Analytics Project
Thread-Index: AdUiAx3+IdQebyi8RheHZn8u/yekpg==
Date: Thu, 13 Jun 2019 16:16:19 +0000
Message-ID: <359EC4B99E040048A7131E0F4E113AFC01B3392762@marathon>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.64.22.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4F64H3feYZxNAi3VCiOyanUOID0>
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: Thu, 13 Jun 2019 16:16:26 -0000

Hello!

Thank you for the input in response to the call for community feedback on web analytics on www.ietf.org [1].

To summarize the themes and subsequent discussion expressed in this call, the following was heard:

** Questions about which exact IETF websites would be covered
** Requests to ensure there is public access to summary data
** The need to identify the detailed uses of the data prior to implementation
** General concerns about privacy in any scheme that collects data
** Questions about the anonymization scheme that will be used on the data
** Concerns about the re-identification of users who repeatedly visit the site
** Questions about who would have access to the data
** Suggestions to minimize the retention period of the data
** Questions on how the success of this project will be evaluated
** Suggestions to use the performance measurement capabilities of the proposed tool
** The need to review and potentially update the IETF Privacy Statement [2] and consider GDPR
** Caution on the interpretation of any statistics or metrics derived from the data
** Questions about the value of this class of data in driving improvements to the website
** Endorsement of the approach as a reasonable practice for a website

Additionally, there was feedback out scope for this call that raised concerns about the utility and performance of the current website to IETF participants; and discussed the audience of www.ietf.org.

The IESG plans to revisit the proposal based on these comments; further analyze the proposed tool; and share a revised plan before considering implementation.

Again, thanks for the feedback.

Regards,
Roman
(as the IESG Tools liaison)


[1] https://mailarchive.ietf.org/arch/msg/ietf/5NLuTQfU60dXOzr4iH5hs4feIIw
[2] https://www.ietf.org/privacy-statement/