IETF Logo Mail Archive

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

Roman Danyliw <rdd@cert.org> Wed, 22 May 2019 15:24 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 E6B7B12014B for <ietf@ietfa.amsl.com>; Wed, 22 May 2019 08:24:39 -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, RCVD_IN_DNSWL_NONE=-0.0001, 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 2t5PmA1AS66x for <ietf@ietfa.amsl.com>; Wed, 22 May 2019 08:24:37 -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 D8BDC120172 for <ietf@ietf.org>; Wed, 22 May 2019 08:24:24 -0700 (PDT)
Received: from delp.sei.cmu.edu (delp.sei.cmu.edu [10.64.21.31]) by veto.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id x4MFOM64023653; Wed, 22 May 2019 11:24:22 -0400
DKIM-Filter: OpenDKIM Filter v2.11.0 veto.sei.cmu.edu x4MFOM64023653
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cert.org; s=yc2bmwvrj62m; t=1558538662; bh=mmKauSMarcCZmWSS2iYuGiSZXPZlReQu/AfYHsToAno=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=BBpAblsKA2xm9MpCcGGZVFyFZoCyB35E2mHeDEXMm2mI4OvTs16NOaerZSuSLZZcX YPqIg3SAyqN424DMXrjm1LJljcO6Ca4Bj22gMmDRqehHXscWIDZ9RPefVMc4mBh22b Vz48e4YLGQYuTZwu+vD/Vnk3OcStLCfE8m9MJBas=
Received: from CASSINA.ad.sei.cmu.edu (cassina.ad.sei.cmu.edu [10.64.28.249]) by delp.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id x4MFOHR3032457; Wed, 22 May 2019 11:24:17 -0400
Received: from MARATHON.ad.sei.cmu.edu ([10.64.28.250]) by CASSINA.ad.sei.cmu.edu ([10.64.28.249]) with mapi id 14.03.0439.000; Wed, 22 May 2019 11:24:16 -0400
From: Roman Danyliw <rdd@cert.org>
To: Paul Wouters <paul@nohats.ca>
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: AdUP5slpo2lErwMLRf2heyYkUQLDIwAJH0KAAClXwgA=
Date: Wed, 22 May 2019 15:24:16 +0000
Message-ID: <359EC4B99E040048A7131E0F4E113AFC01B3370F2A@marathon>
References: <359EC4B99E040048A7131E0F4E113AFC01B336F9EC@marathon> <alpine.LRH.2.21.1905211123450.6478@bofh.nohats.ca>
In-Reply-To: <alpine.LRH.2.21.1905211123450.6478@bofh.nohats.ca>
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/LqhCyUcGMGryNz9h102uUBaVpPQ>
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: Wed, 22 May 2019 15:24:40 -0000

Hi Paul!

> -----Original Message-----
> From: Paul Wouters [mailto:paul@nohats.ca]
> Sent: Tuesday, May 21, 2019 11:28 AM
> To: Roman Danyliw <rdd@cert.org>
> Cc: ietf@ietf.org
> Subject: Re: Call for Community Input: Web Analytics on www.ietf.org
> 
> On Tue, 21 May 2019, Roman Danyliw wrote:
> 
> > https://www.ietf.org/iesg/docs/www.ietf.org-AnalyticsProposal-forRevie
> > w.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".

If the analytics meet their intent, the desired would be expand them across all of the web properties (e.g., tools.ietf, datatracker.ietf).  However, in the spirit of starting with a smaller scope and getting operational experience, www.ietf was chosen as an initial target.

> > 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 ?

Agreed.  This hesitance is a matter of not overcommitting, and getting initial operational experience with this new approach to gather usage data.  Incomplete stats are currently shared at [1].

Thanks for the feedback.

Roman

[1] https://www.ietf.org/usagedata/

> Otherwise, the plan looks fine to me.
> 
> Paul

v2.23.0 | Report a Bug | By Email