IETF Logo Mail Archive

Re: [perpass] Fwd: New Version Notification for draft-barnes-pervasive-problem-00.txt

Linus Nordberg <linus@nordberg.se> Tue, 07 January 2014 07:15 UTC

Return-Path: <linus@nordberg.se>
X-Original-To: perpass@ietfa.amsl.com
Delivered-To: perpass@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7685B1ADFBD for <perpass@ietfa.amsl.com>; Mon, 6 Jan 2014 23:15:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.09
X-Spam-Level:
X-Spam-Status: No, score=-2.09 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, RP_MATCHES_RCVD=-0.538, 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 EIqdHoDOPFSV for <perpass@ietfa.amsl.com>; Mon, 6 Jan 2014 23:15:39 -0800 (PST)
Received: from smtp.nordberg.se (smtp.nordberg.se [193.10.5.87]) by ietfa.amsl.com (Postfix) with ESMTP id 394D81AE45D for <perpass@ietf.org>; Mon, 6 Jan 2014 23:15:39 -0800 (PST)
Received: from tool.nordberg.se (h158n2-asp-a13.ias.bredband.telia.com [217.210.64.158]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.nordberg.se (Postfix) with ESMTPSA id 5F479116B4; Tue, 7 Jan 2014 08:15:29 +0100 (CET)
From: Linus Nordberg <linus@nordberg.se>
To: Richard Barnes <rlb@ipv.sx>
References: <20140107021702.7140.81609.idtracker@ietfa.amsl.com> <CAL02cgRsBQNYd2n05548ZbK-ciPkSNJ=U2V0iv+080p9-1gQbA@mail.gmail.com> <7BAC95F5A7E67643AAFB2C31BEE662D018B7D6E1E4@SC-VEXCH2.marvell.com> <CAL02cgT5u1w-MJfxWHZOdiDQRU_Ov_wGYf7=0O-BH_td-Nis8Q@mail.gmail.com>
Date: Tue, 07 Jan 2014 08:15:28 +0100
In-Reply-To: <CAL02cgT5u1w-MJfxWHZOdiDQRU_Ov_wGYf7=0O-BH_td-Nis8Q@mail.gmail.com> (Richard Barnes's message of "Mon, 6 Jan 2014 22:01:03 -0500")
Message-ID: <87lhys1cvj.fsf@nordberg.se>
User-Agent: Gnus/5.13 (Gnus v5.13)
MIME-Version: 1.0
Content-Type: text/plain
Cc: Paul Lambert <paul@marvell.com>, perpass <perpass@ietf.org>
Subject: Re: [perpass] Fwd: New Version Notification for draft-barnes-pervasive-problem-00.txt
X-BeenThere: perpass@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "The perpass list is for IETF discussion of pervasive monitoring. " <perpass.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/perpass>, <mailto:perpass-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/perpass/>
List-Post: <mailto:perpass@ietf.org>
List-Help: <mailto:perpass-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/perpass>, <mailto:perpass-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 07:15:41 -0000

Richard Barnes <rlb@ipv.sx> wrote
Mon, 6 Jan 2014 22:01:03 -0500:

| I also wonder to what degree this is a "pervasive attack" issue.  If the
| attack involves being physically close to the victim, it's hard to see how
| the attacker would achieve a pervasive scale.

An attacker could control a large number of "home routers".

Do we need stronger indications that's actually being done at a large
scale before we consider strengthening L2 protocols and best practices?
If so, what is "large scale" and "pervasive"?

v2.30.2 | Report a Bug | By Email | System Status