Re: Migrating some high-entropy HTTP headers to Client Hints.

Mike West <mkwst@google.com> Fri, 30 November 2018 08:47 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76989130DC0 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 30 Nov 2018 00:47:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.957
X-Spam-Level:
X-Spam-Status: No, score=-11.957 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-1.459, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 kbV3zZ895WGr for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 30 Nov 2018 00:47:27 -0800 (PST)
Received: from frink.w3.org (frink.w3.org [IPv6:2603:400a:ffff:804:801e:34:0:38]) (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 B31AD12F1A2 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Fri, 30 Nov 2018 00:47:21 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.89) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1gSeQc-0006dw-JI for ietf-http-wg-dist@listhub.w3.org; Fri, 30 Nov 2018 08:45:38 +0000
Resent-Date: Fri, 30 Nov 2018 08:45:38 +0000
Resent-Message-Id: <E1gSeQc-0006dw-JI@frink.w3.org>
Received: from titan.w3.org ([2603:400a:ffff:804:801e:34:0:4c]) by frink.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <mkwst@google.com>) id 1gSeQY-0006NM-B3 for ietf-http-wg@listhub.w3.org; Fri, 30 Nov 2018 08:45:34 +0000
Received: from mail-ot1-x331.google.com ([2607:f8b0:4864:20::331]) by titan.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from <mkwst@google.com>) id 1gSeQW-0002xg-KG for ietf-http-wg@w3.org; Fri, 30 Nov 2018 08:45:33 +0000
Received: by mail-ot1-x331.google.com with SMTP id k98so4442951otk.3 for <ietf-http-wg@w3.org>; Fri, 30 Nov 2018 00:45:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=kOZdHAGkOdAFF6u65TxW49qTZPKPjXic+XR6Vp9oGKY=; b=mrxRdG8oQiqGsPoDkKWaTj6b5wvganDmdD4jx+hStXDFctw/YEVkhBMb0p7K4eX+lt 5g+WImvWZQ1scuDQnnhL+y4GFvySN+G0yeAK7vJ9Z6iv1qp1YQkz50/xPTNMpxRKI1wQ ih+3bZO39+t8ZTFqdDr/ZNpPr/H3/STuNuVwStdj0EKmBK+zp3CJYQoHL8Dm7slYzr1K 6U9r1RszCZ+xKkyjp1A8ObUsXFIC4J94CbJOlIAfvca1B45Vcf+8x0t7dYcmBcJP5Qd3 hC8d2DNjLiV90XBJ3ZAsnuFSKDSL0PWb6C8nPUlk2ezZ0N071ASlAtVW7F3o4foF3pA3 Fzxw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=kOZdHAGkOdAFF6u65TxW49qTZPKPjXic+XR6Vp9oGKY=; b=japtXmuF7Cx91vACTnPuUDAFGb2B3nlSNBcWjEcofuCfMjS8fTZPyBtL+Y8ceDnwwp mjffZMUWjfpwjihPElxY8om+mcc85e7eRNuuFTZPuMH2EHrGjCyAVd95J8W9sJbmBhFq eOCYTmSJYga/9I1v21AEu1Ab+HCXNEto4/EifsNgqftod9ZGbEen8zl0XZWiyzbb1Unz to9YZyeRuFlQwxvtt7qNRtViOUKgsPQfZWXmhP2BkmqXJWI3Bu50yAkUYkNcHawThECN SjK9Ey4yMh3aMXzNc1dSJGfZU+3u8Qa7dzPsJn+yNcgpWUUuS6eLVap85PLsAxnHMfHp Gn1w==
X-Gm-Message-State: AA+aEWZ5apTjxnIPtBBE/5q5dR7fXkAniNAW36eKjXNyh52utZEWKDhz IRFkY3lAptn29YPwM3giEGsxpWopK5HnqGNiBoTZiAzlKuuBOw==
X-Google-Smtp-Source: AFSGD/UnSLJ8EbCbaKIK7w5vdt80pl1LlfzeVyQROG0v7Ywgfutav+0mnxcsrk7Zbxoqx82sU1wOTe3Npc1mxa1gM0k=
X-Received: by 2002:a9d:7653:: with SMTP id o19mr2964248otl.12.1543567511444; Fri, 30 Nov 2018 00:45:11 -0800 (PST)
MIME-Version: 1.0
References: <CAKXHy=eHiMtXi8vkDYtADHdU0tnUfd3p+Wfy7vSkLgT7cA1W0w@mail.gmail.com> <538F7C6E-EB14-4B49-B9B5-BED066E5838F@mnot.net>
In-Reply-To: <538F7C6E-EB14-4B49-B9B5-BED066E5838F@mnot.net>
From: Mike West <mkwst@google.com>
Date: Fri, 30 Nov 2018 09:44:59 +0100
Message-ID: <CAKXHy=dhdrbB1i5d5=dXC-kz2kby3-GVwkwHESvP8uwqgrQAwg@mail.gmail.com>
To: Mark Nottingham <mnot@mnot.net>
Cc: HTTP Working Group <ietf-http-wg@w3.org>, Ilya Grigorik <igrigorik@google.com>
Content-Type: multipart/alternative; boundary="000000000000356361057bddd147"
X-W3C-Hub-Spam-Status: No, score=-21.7
X-W3C-Hub-Spam-Report: AWL=2.900, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_IRR=-3, W3C_WL=-1
X-W3C-Scan-Sig: titan.w3.org 1gSeQW-0002xg-KG c49cf80d94903b18503043a57a9a7633
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Migrating some high-entropy HTTP headers to Client Hints.
Archived-At: <https://www.w3.org/mid/CAKXHy=dhdrbB1i5d5=dXC-kz2kby3-GVwkwHESvP8uwqgrQAwg@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/36116
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <https://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

On Fri, Nov 30, 2018 at 1:30 AM Mark Nottingham <mnot@mnot.net> wrote:

> I, for one, welcome our new Client Hint overlords.
>
> Personally, I'd like to see these integrated into the current CH document,
> rather than as separate drafts. CH still needs some work, so it's not like
> we're going to get it out the door tomorrow.
>

These hints seem pretty clearly separable from the infrastructure upon
which they're built. I'd prefer to split them out into things-in-themselves
that we can point developers towards independently, giving ourselves the
opportunity to explain the rationale and background more coherently than I
think we'll be able to if we bury these in a subsection of the larger
document.

I'll defer to the group as to how y'all would like to handle these, but I'd
prefer several short and focused docs as a reader.

-mike

However, it seems like Ilya wants to go in a different direction, based
> upon the notes we received for Bangkok.
>
> Ilya, your thoughts?
>
>
>
> > On 29 Nov 2018, at 9:22 pm, Mike West <mkwst@google.com> wrote:
> >
> > Hey folks,
> >
> > Section 9.7 of RFC7231 rightly notes that some of the content
> negotiation headers user agents deliver in HTTP requests create substantial
> fingerprinting surface. I think it would be beneficial if we took steps to
> reduce their prevalence on the wire, and Client Hints looks like a
> reasonable infrastructure on top of which to build.
> >
> > `User-Agent` and `Accept-Language` seem like particularly tasty and
> low-hanging fruit, and I've sketched out two proposals as proofs of concept:
> >
> > *   `User-Agent` could be represented as ~four distinct hints: `UA`,
> `Model`, `Platform`, and `Arch`:
> https://github.com/mikewest/ua-client-hints is a high-level explainer,
> and https://tools.ietf.org/html/draft-west-ua-client-hints a sketchy ID
> for the new headers.
> >
> > *   `Accept-Language` could be represented as a `Lang` hint:
> https://github.com/mikewest/lang-client-hint is a high-level explainer,
> https://tools.ietf.org/html/draft-west-lang-client-hint an equally
> sketchy ID for the new header.
> >
> > I'd appreciate y'all's feedback. Thanks!
> >
> > -mike
>
> --
> Mark Nottingham   https://www.mnot.net/
>
>