IETF Logo Mail Archive

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

Mark Nottingham <mnot@mnot.net> Tue, 21 May 2019 15:51 UTC

Return-Path: <mnot@mnot.net>
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 81F8812016B for <ietf@ietfa.amsl.com>; Tue, 21 May 2019 08:51:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=XLR/KbNt; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=RlVywOYo
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 3Mh5KoGIDhCc for <ietf@ietfa.amsl.com>; Tue, 21 May 2019 08:51:47 -0700 (PDT)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 625A9120144 for <ietf@ietf.org>; Tue, 21 May 2019 08:51:45 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 7D55F51F; Tue, 21 May 2019 11:51:44 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Tue, 21 May 2019 11:51:44 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm2; bh=T NI8Pn1XYzLpa1vSucB4KUM8MDrvYPm/tsf6/mH6aH0=; b=XLR/KbNtgLyDxS8lU eK/W27ctfSmnWHTd2GUNDKmCzQpeetGmNc6Tu7Q6X8/97kMS+YebXL70SxgyEw92 xMx4KHB72e5zQpKQCP1hUfUO0OQgqVTATewpQgV+Wd5jBobJtEFpEUqkYusDflOb /XuWxfe7vSq3fv4SVp9vlw0wJ7KEmiv/XQzz0W3YS0CEndwpRr9AEh4Bnh/a6Uj6 j7YGPVLsbYmqh3QZHJS5tbsRhAF1GWPFp2cS7zZfao2un2TwZWx0eoy0EgyUIYy6 R5sAE1mgRANdd1Ekd0e3acJNist0Svj2UNTKHf41IFt6IzvlQRcO/QRpJMOXw+nT qPouA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=TNI8Pn1XYzLpa1vSucB4KUM8MDrvYPm/tsf6/mH6a H0=; b=RlVywOYoN/iI1o/KkGPL/NOZxipuj7BlmOqI2+XHrXfm6dNMSThKXQZXt P2Qq1908qEXPMzHTfEx6TBoPF2q+FfUjK77D4jqVoiwhwLdFyXRcZhY8zC/Di0hy 9lumT+Dm5ekhRwi69E3IAM6U5oxuqmTKDCIRw7gS65txTgvSrUfquCmtxpIb2W6o eCczPhdsTIxCblHhQNie5xHaRBmtJz9OANJ6n19vA+FCnskmEyQPp0Yaok6429FZ Bj4MLCRBn65I+FcNdnnyEvXn6R6nspB8XSTgRMn8XloRG5VkbhMcWjF7TLoA3Fa4 SzY5vkzG7a1sMmbt1w6UUYUL6HcjQ==
X-ME-Sender: <xms:jh7kXOUWu_AtYVNmYdznzkbEEKbmQ7RQsL57SOkhtH9H0feZ31z8bA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddruddutddgleehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpegtggfuhfgjfffgkfhfvffosehtqh hmtdhhtddvnecuhfhrohhmpeforghrkhcupfhothhtihhnghhhrghmuceomhhnohhtsehm nhhothdrnhgvtheqnecuffhomhgrihhnpehivghtfhdrohhrghdpmhhnohhtrdhnvghtne cukfhppedvudejrddufeekrdeivddrvdegfeenucfrrghrrghmpehmrghilhhfrhhomhep mhhnohhtsehmnhhothdrnhgvthenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:jh7kXLVMzK3sM3Pff9m-e5AQtGo82TIgyEYqSAdz8BhwpvQXoFUDAw> <xmx:jh7kXOhl88jWbvrkvUYNePLKJkzwbmCpXUD1Pz22M6BdBS9ogCcf5w> <xmx:jh7kXGZKGW0p4_KFGshDH8QGk5UQVbkNzuGsqvwn-8P_qLoD3KTZ6w> <xmx:kB7kXKLqSivc8pHLN2wpcVC2aQVM5CG3e6m8N7CCiOn4VNikxNl6kA>
Received: from [192.168.203.87] (unknown [217.138.62.243]) by mail.messagingengine.com (Postfix) with ESMTPA id 2BF4D8005C; Tue, 21 May 2019 11:51:42 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
Subject: Re: Call for Community Input: Web Analytics on www.ietf.org
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <alpine.LRH.2.21.1905211123450.6478@bofh.nohats.ca>
Date: Tue, 21 May 2019 16:51:39 +0100
Cc: "ietf@ietf.org" <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <C1F7C275-5EB6-4A18-8824-A18E5051C1D3@mnot.net>
References: <359EC4B99E040048A7131E0F4E113AFC01B336F9EC@marathon> <alpine.LRH.2.21.1905211123450.6478@bofh.nohats.ca>
To: Roman Danyliw <rdd@cert.org>
X-Mailer: Apple Mail (2.3445.104.8)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/aHiSrwLStMxgo9au6kdxjfZFAms>
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:51: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.

For performance monitoring, are we going to be measuring the server-side view of page generation time, or from the client (i.e. using RUM)?

Collecting errors -- e.g., JavaScript exceptions, those reported by CSP and similar facilities -- is extremely useful for finding problems on the site. Will we be doing that?

Cheers,

 

> On 21 May 2019, at 4:27 pm, Paul Wouters <paul@nohats.ca> wrote:
> 
> 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
> 

--
Mark Nottingham   https://www.mnot.net/

v2.23.0 | Report a Bug | By Email