RE: HTTP/2 and Pervasive Monitoring
<K.Morgan@iaea.org> Fri, 15 August 2014 07:39 UTC
Return-Path: <ietf-http-wg-request@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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B1361A0931 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 15 Aug 2014 00:39:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.57
X-Spam-Level:
X-Spam-Status: No, score=-7.57 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.668, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 znWu9AyLC1X6 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 15 Aug 2014 00:39:47 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 85EA61A08E5 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Fri, 15 Aug 2014 00:39:47 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1XIC3u-0005wj-Pc for ietf-http-wg-dist@listhub.w3.org; Fri, 15 Aug 2014 07:36:34 +0000
Resent-Date: Fri, 15 Aug 2014 07:36:34 +0000
Resent-Message-Id: <E1XIC3u-0005wj-Pc@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <K.Morgan@iaea.org>) id 1XIC3T-0005vM-1L for ietf-http-wg@listhub.w3.org; Fri, 15 Aug 2014 07:36:07 +0000
Received: from vs-m201.iaea.org ([161.5.6.178]) by lisa.w3.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <K.Morgan@iaea.org>) id 1XIC3R-0001hW-7e for ietf-http-wg@w3.org; Fri, 15 Aug 2014 07:36:06 +0000
Received: from vs-m1.iaea.org (vs-mail1.iaea.org [172.24.1.26]) by vs-m201.iaea.org (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id s7F7ZWPU016774; Fri, 15 Aug 2014 09:35:34 +0200
Received: from E2.iaea.org (e2.iaea.org [172.24.0.42]) by vs-m1.iaea.org (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id s7F7ZUNT004720; Fri, 15 Aug 2014 09:35:31 +0200
X-Envelope-Sender: K.Morgan@iaea.org
Received: from SEM002PD.sg.iaea.org (161.5.105.93) by E2.iaea.org (172.24.0.42) with Microsoft SMTP Server (TLS) id 14.1.438.0; Fri, 15 Aug 2014 09:35:30 +0200
Received: from SEM001PD.sg.iaea.org ([169.254.1.3]) by SEM002PD.sg.iaea.org ([169.254.2.108]) with mapi id 14.01.0438.000; Fri, 15 Aug 2014 09:35:30 +0200
From: K.Morgan@iaea.org
To: gregw@intalio.com, mnot@mnot.net
CC: ietf-http-wg@w3.org
Thread-Topic: HTTP/2 and Pervasive Monitoring
Thread-Index: AQHPuDVYVIGxUMbNxUaTP7fBIHOzjpvRCpMAgAA7a1A=
Date: Fri, 15 Aug 2014 07:35:29 +0000
Message-ID: <0356EBBE092D394F9291DA01E8D28EC2012BC582C7@SEM001PD.sg.iaea.org>
References: <38BD57DB-98A9-4282-82DD-BB89F11F7C84@mnot.net> <CAH_y2NFr16YJEsN-=zUWjEdywuLpuOVijFmybjbXZtAE4LTMdg@mail.gmail.com>
In-Reply-To: <CAH_y2NFr16YJEsN-=zUWjEdywuLpuOVijFmybjbXZtAE4LTMdg@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [161.5.105.94]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-Product-Ver: SMEX-10.0.0.1412-7.000.1014-20880.005
X-TM-AS-Result: No--2.218400-0.000000-31
X-TM-AS-User-Approved-Sender: Yes
X-TM-AS-User-Blocked-Sender: No
X-KLMS-Rule-ID: 1
X-KLMS-Message-Action: clean
X-KLMS-AntiSpam-Status: not scanned, disabled by settings
X-KLMS-AntiPhishing: Clean, 2014/08/14 12:00:59
X-KLMS-AntiVirus: Kaspersky Security 8.0 for Linux Mail Server, version 8.0.1.705, bases: 2014/08/15 00:04:00 #9413612; khse: 2014-03-12 13:55:01
X-KLMS-AntiVirus-Status: Clean, skipped
X-Scanned-By: MIMEDefang 2.73
Received-SPF: pass client-ip=161.5.6.178; envelope-from=K.Morgan@iaea.org; helo=vs-m201.iaea.org
X-W3C-Hub-Spam-Status: No, score=-4.9
X-W3C-Hub-Spam-Report: AWL=-1.923, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.668, SPF_PASS=-0.001
X-W3C-Scan-Sig: lisa.w3.org 1XIC3R-0001hW-7e c61149880e650617044ea5ab99a0a375
X-Original-To: ietf-http-wg@w3.org
Subject: RE: HTTP/2 and Pervasive Monitoring
Archived-At: <http://www.w3.org/mid/0356EBBE092D394F9291DA01E8D28EC2012BC582C7@SEM001PD.sg.iaea.org>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/26607
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: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>
On Friday,15 August 2014 08:01 gregw@intalio.com wrote: > Note that I'm not necessarily arguing against https only.... I'm really just saying > that to pretend that this gives any significant defence against PM is to over sell > what it achieves or what can be achieved by any application protocol stand > alone. Indeed it is misguiding the public into a false sense of security to sell it as such. This email message is intended only for the use of the named recipient. Information contained in this email message and its attachments may be privileged, confidential and protected from disclosure. If you are not the intended recipient, please do not read, copy, use or disclose this communication to others. Also please notify the sender by replying to this message and then delete it from your system.
- HTTP/2 and Pervasive Monitoring Mark Nottingham
- Re: HTTP/2 and Pervasive Monitoring Amos Jeffries
- Re: HTTP/2 and Pervasive Monitoring Greg Wilkins
- RE: HTTP/2 and Pervasive Monitoring K.Morgan
- Re: HTTP/2 and Pervasive Monitoring Poul-Henning Kamp
- Re: HTTP/2 and Pervasive Monitoring Mark Nottingham
- Re: HTTP/2 and Pervasive Monitoring Mark Nottingham
- Re: HTTP/2 and Pervasive Monitoring Eliot Lear
- Re: HTTP/2 and Pervasive Monitoring Poul-Henning Kamp
- Re: HTTP/2 and Pervasive Monitoring Martin Nilsson
- Re: HTTP/2 and Pervasive Monitoring Poul-Henning Kamp
- RE: HTTP/2 and Pervasive Monitoring Albert Lunde
- Re: HTTP/2 and Pervasive Monitoring Cory Benfield
- Re: HTTP/2 and Pervasive Monitoring Erik Nygren
- Re: HTTP/2 and Pervasive Monitoring Poul-Henning Kamp
- Re: HTTP/2 and Pervasive Monitoring Roland Zink
- Re: HTTP/2 and Pervasive Monitoring Martin Thomson
- Re: HTTP/2 and Pervasive Monitoring Brian Smith
- Re: HTTP/2 and Pervasive Monitoring Poul-Henning Kamp
- Re: HTTP/2 and Pervasive Monitoring Eliot Lear
- Re: HTTP/2 and Pervasive Monitoring Greg Wilkins
- Re: HTTP/2 and Pervasive Monitoring Greg Wilkins
- Re: HTTP/2 and Pervasive Monitoring Poul-Henning Kamp
- Re: HTTP/2 and Pervasive Monitoring Stephen Farrell
- Re: HTTP/2 and Pervasive Monitoring Poul-Henning Kamp
- Re: HTTP/2 and Pervasive Monitoring Roland Zink
- Re: HTTP/2 and Pervasive Monitoring Stephen Farrell
- Re: HTTP/2 and Pervasive Monitoring Amos Jeffries
- Re: HTTP/2 and Pervasive Monitoring Eliot Lear
- Re: HTTP/2 and Pervasive Monitoring Poul-Henning Kamp
- Re: HTTP/2 and Pervasive Monitoring Poul-Henning Kamp
- Re: HTTP/2 and Pervasive Monitoring Ilari Liusvaara
- Re: HTTP/2 and Pervasive Monitoring Mark Nottingham
- Re: HTTP/2 and Pervasive Monitoring Greg Wilkins
- Re: HTTP/2 and Pervasive Monitoring Poul-Henning Kamp
- Re: HTTP/2 and Pervasive Monitoring Martin Thomson
- Re: HTTP/2 and Pervasive Monitoring Poul-Henning Kamp
- Re: HTTP/2 and Pervasive Monitoring Martin Thomson
- Re: HTTP/2 and Pervasive Monitoring Poul-Henning Kamp