Re: IAB statement on draft-farrell-perpass-attack-00
Mary Barnes <mary.h.barnes@gmail.com> Wed, 27 November 2013 20:18 UTC
Return-Path: <mary.h.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 948041AE133 for <ietf@ietfa.amsl.com>; Wed, 27 Nov 2013 12:18:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=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 MB5_guBUJIc1 for <ietf@ietfa.amsl.com>; Wed, 27 Nov 2013 12:18:12 -0800 (PST)
Received: from mail-vb0-x22c.google.com (mail-vb0-x22c.google.com [IPv6:2607:f8b0:400c:c02::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 892421AE268 for <ietf@ietf.org>; Wed, 27 Nov 2013 12:12:58 -0800 (PST)
Received: by mail-vb0-f44.google.com with SMTP id w20so5357177vbb.31 for <ietf@ietf.org>; Wed, 27 Nov 2013 12:12:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=GOar2jRlliUF/o1nYtbjYAgpBGf+/MOHqpNOziikMBg=; b=v1z9K3vT2qycrBhEDNS3W3mjLQuxtKUGPTpEj/GoFvA3qPTBMTUfHFbV/6V/FzUIUE H9pQaBf4XLBV5ULjb1Ohti9CGhZyDPP+RCvunnngfMA1IG+p0gUmDd4uGhmeJKcHDpBp IeP0D7Ymi2Fd1j653afj6E+QuCy8H+1oBchw74ulrKW4XgoFHtfukHUeU3dzlzztL1sG J50PyzwysfLReYcP7/D9EZJShGgWu35DwwWHukNB6mTgJgEMcSBAUG3uBZrgBc5EJJR2 uznIz7/aXfSqTgTV9Xzn8nMBOYQRlp8ldPJb+VQBcbZmNFzQryETcxSBVXsEJ0NmqxzQ V+JA==
MIME-Version: 1.0
X-Received: by 10.220.132.194 with SMTP id c2mr16356vct.55.1385583177822; Wed, 27 Nov 2013 12:12:57 -0800 (PST)
Received: by 10.58.44.226 with HTTP; Wed, 27 Nov 2013 12:12:57 -0800 (PST)
In-Reply-To: <6.2.5.6.2.20131127084710.0dd761c0@resistor.net>
References: <E2DA1477-C86E-441E-A33D-D47A0D67AFF3@iab.org> <6.2.5.6.2.20131127084710.0dd761c0@resistor.net>
Date: Wed, 27 Nov 2013 14:12:57 -0600
Message-ID: <CABmDk8=pe+hMbQTTVa+sXDxEGbAZTLiy_LLDHbLEji4in0_3Ag@mail.gmail.com>
Subject: Re: IAB statement on draft-farrell-perpass-attack-00
From: Mary Barnes <mary.h.barnes@gmail.com>
To: SM <sm@resistor.net>
Content-Type: multipart/alternative; boundary="001a1134a3ca1ef79d04ec2e39ba"
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 27 Nov 2013 20:18:15 -0000
On Wed, Nov 27, 2013 at 12:56 PM, SM <sm@resistor.net> wrote: > At 08:13 27-11-2013, IAB Chair wrote: > >> At the Vancouver IETF meeting, the IAB held a technical plenary that >> discussed pervasive monitoring. The IAB believes that pervasive monitoring >> represents an attack on the >> > > The minutes for that plenary is not available at the moment. I would > appreciate if the minutes could be published. > [MB] A last round of edits (editorial clarifications) are underway right now. The minutes will be published no later than Tuesday, December 3rd, 2013. [/MB] > > Internet in as much as large amounts of information that is intended to >> be confidential between sets of individuals is in fact gathered and >> aggregated by third parties. Such a broad scale attack can undermine >> confidence in the infrastructure, no matter the intent of those collecting >> the information. >> >> draft-farrell-perpass-attack-00 is intended to establish an IETF >> community consensus on this matter. We encourage the community to read and >> engage in discussion about this draft, and also to take practical measures >> to limit pervasive monitoring within their environments. >> > > In Section 1: > > "that should be mitigated where possible via the design of protocols > that make pervasive monitoring significantly more expensive or > infeasible" > > That sounds like an arms race [1]. > > "A fuller problem statement with more examples and description can be > found in [ProblemStatement]" > That document is not available. > > "In particular, the term, when used technically, implies nothing about > the motivation of the bad-actor mounting the attack, who is still > called a bad-actor no matter what one really thinks about their > motivation." > > The usual term in the IETF is "adversary" and not "bad-actor". "bad > actor" is sometimes defined as "contentious individual". > > The Security Considerations section that the intended BCP is all about > privacy. The Introduction section mentions "illegal purposes by > criminals". I would describe the problem as having different angles; bad > people could capture the information being exchanged and use it for > nefarious purposes, nation states [2] can capture the information and use > it to find out what the people are discussing. > > The draft is well-written. Given the catchy title I am left to wonder > which parts of the document is polite fiction (a social scenario in which > all participants are aware of a truth, but pretend to believe in some > alternative version of events to avoid conflict or embarrassment). In very > simplistic terms the draft says: > > "consensus to design protocols so as to mitigate the attack, where > possible." > > Quoting Martin Thomson: we trusted you; we were naive; never again. > > Regards, > -sm > > 1. the continuing competitive attempt by two or more nations each to have > available to it more and more powerful weapons than the other(s). > > 2. http://ir.elbitsystems.com/phoenix.zhtml?c=61849&p=irol- > newsArticle&ID=1810121&highlight= >
- IAB statement on draft-farrell-perpass-attack-00 IAB Chair
- Re: IAB statement on draft-farrell-perpass-attack… SM
- Re: IAB statement on draft-farrell-perpass-attack… Mary Barnes
- Re: IAB statement on draft-farrell-perpass-attack… Stephen Farrell
- Re: IAB statement on draft-farrell-perpass-attack… Jari Arkko
- Re: IAB statement on draft-farrell-perpass-attack… SM
- Re: IAB statement on draft-farrell-perpass-attack… Abdussalam Baryun
- Re: IAB statement on draft-farrell-perpass-attack… SM
- Re: [perpass] perens-perpass-appropriate-response… Martin Millnert
- RE: [perpass] perens-perpass-appropriate-response… JOSEFSSON Erik
- perens-perpass-appropriate-response-01 Bruce Perens
- RE: perens-perpass-appropriate-response-01 l.wood
- Re: perens-perpass-appropriate-response-01 Ted Lemon