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

Paul Wouters <paul@nohats.ca> Tue, 21 May 2019 15:27 UTC

Return-Path: <paul@nohats.ca>
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 E71C6120120 for <ietf@ietfa.amsl.com>; Tue, 21 May 2019 08:27:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 YeFY0SgJysjZ for <ietf@ietfa.amsl.com>; Tue, 21 May 2019 08:27:55 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::68]) (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 1439512006F for <ietf@ietf.org>; Tue, 21 May 2019 08:27:55 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 457fls4PjLz722; Tue, 21 May 2019 17:27:53 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1558452473; bh=0vUYBy42oVt61L0vh6kSTMZ9ARqS5O77wRjk4Q1zsj0=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=QQQ24e91BgpId0nBsivLIl1yxjiC6NdYC7ccml7HMEPyefeGjWsqASS56UcNCMMd4 Ngkar4Dd6leKcopFBeNfwIm4ny7yJopD9qSuDPbB551/HUOylZRrDS9eSkA5zdts06 t+ufs/7rTNRwAszJ1lVDviugG1ZHnzeThPAkS+FQ=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id 7_DFNPbLVU_y; Tue, 21 May 2019 17:27:51 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Tue, 21 May 2019 17:27:50 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 55DA1373B; Tue, 21 May 2019 11:27:49 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca 55DA1373B
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 49C7540D6FE3; Tue, 21 May 2019 11:27:49 -0400 (EDT)
Date: Tue, 21 May 2019 11:27:49 -0400
From: Paul Wouters <paul@nohats.ca>
To: Roman Danyliw <rdd@cert.org>
cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Call for Community Input: Web Analytics on www.ietf.org
In-Reply-To: <359EC4B99E040048A7131E0F4E113AFC01B336F9EC@marathon>
Message-ID: <alpine.LRH.2.21.1905211123450.6478@bofh.nohats.ca>
References: <359EC4B99E040048A7131E0F4E113AFC01B336F9EC@marathon>
User-Agent: Alpine 2.21 (LRH 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bbraWUpobfILeuGwR0XNJA6UAng>
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 15:27:57 -0000

On Tue, 21 May 2019, Roman Danyliw wrote:

> https://www.ietf.org/iesg/docs/www.ietf.org-AnalyticsProposal-forReview.pdf
>
> The IESG appreciates any input from the community on this proposal and will consider all input received by June 4, 2019.

I'm a bit confused that tools.ietf.org is not included. It's where I go
mostly to read RFCs. (in fact, I google "rfc XXX tools" to not get any
ancient www.ietf.org text versions but the proper html version on
tools.ietf.org".

> Providing a publicly-available summary of analytics data will be explored.

Since I'm part of the data collection, it makes sense to me to see the
end summary. I see no reason this should be restricted to the IESG and
IETF Secretariat - unless you don't trust your anonymization ?

Otherwise, the plan looks fine to me.

Paul