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

Richard Barnes <rlb@ipv.sx> Tue, 07 January 2014 03:01 UTC

Return-Path: <rlb@ipv.sx>
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 0C0461ADF5A for <perpass@ietfa.amsl.com>; Mon, 6 Jan 2014 19:01:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 7ikoj-XuVO-J for <perpass@ietfa.amsl.com>; Mon, 6 Jan 2014 19:01:12 -0800 (PST)
Received: from mail-oa0-f42.google.com (mail-oa0-f42.google.com [209.85.219.42]) by ietfa.amsl.com (Postfix) with ESMTP id 36E161ADF35 for <perpass@ietf.org>; Mon, 6 Jan 2014 19:01:12 -0800 (PST)
Received: by mail-oa0-f42.google.com with SMTP id i4so20109246oah.29 for <perpass@ietf.org>; Mon, 06 Jan 2014 19:01:03 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=SiPfp+ZAAoCBcFfDLThWIYiC6pBxH/A9gBhH9Q4gf90=; b=hWtNeJtQUIOSIIYsIkLupCWL4J5HuWwGSwDMlKfOI32oj3NHITdjFrnE1sqCVtH2K4 QiPX0nMwKNaywC/UQd8gi0B3drHkeVsNplG+sY9zngQPLyNf9yL2pEjpo/mvs9eO+wP0 X3qFNnS9Ajgb8yqb2X4g58IiFSKuSmQlWzgZii94b58wGK9Ca9F4IiGuPhn99DUhwsK5 RmazSVUlQ6Z5naOKcYjrr86xh9dsGd8Y0mLYc8szCBPanShdo7vQV1Nc6sAP5TxJmGIx UB3rM5tZUMK6E11Oe/VtTRfWyr3QzejBBkhA1L//Q4SYGiwO82q71XsmXK/W3uIuqM1b LPvA==
X-Gm-Message-State: ALoCoQmuAy2l6O4W3+z/5G9gBjRXa3/EKzuQrNSesJ4rChsEGA4FkJzhemGgSc/U356I3rUhfk0S
MIME-Version: 1.0
X-Received: by 10.60.63.102 with SMTP id f6mr37758oes.76.1389063663281; Mon, 06 Jan 2014 19:01:03 -0800 (PST)
Received: by 10.60.54.65 with HTTP; Mon, 6 Jan 2014 19:01:03 -0800 (PST)
In-Reply-To: <7BAC95F5A7E67643AAFB2C31BEE662D018B7D6E1E4@SC-VEXCH2.marvell.com>
References: <20140107021702.7140.81609.idtracker@ietfa.amsl.com> <CAL02cgRsBQNYd2n05548ZbK-ciPkSNJ=U2V0iv+080p9-1gQbA@mail.gmail.com> <7BAC95F5A7E67643AAFB2C31BEE662D018B7D6E1E4@SC-VEXCH2.marvell.com>
Date: Mon, 06 Jan 2014 22:01:03 -0500
Message-ID: <CAL02cgT5u1w-MJfxWHZOdiDQRU_Ov_wGYf7=0O-BH_td-Nis8Q@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Paul Lambert <paul@marvell.com>
Content-Type: multipart/alternative; boundary="001a11c2553239317504ef5896cb"
Cc: 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 03:01:14 -0000

On Mon, Jan 6, 2014 at 9:49 PM, Paul Lambert <paul@marvell.com> wrote:

> > Comments welcome!
>
>
>
> Nice work!
>
>
Thanks!


Minor comment – don’t see any text on L2 wireless tracking.  All of our
> wireless devices effectively beacon our location and identity (e.g 802.11
> MAC addresses and probing). While not strictly a IETF domain of work (L2),
> the solutions to this class of problems do require changes in IETF
> protocols.
>

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.

What sorts of changes to IETF protocols are you imagining?

--Richard




>
>
> Paul
>
>
>
>
>
> *From:* perpass [mailto:perpass-bounces@ietf.org] *On Behalf Of *Richard
> Barnes
> *Sent:* Monday, January 06, 2014 6:24 PM
> *To:* perpass
> *Subject:* [perpass] Fwd: New Version Notification for
> draft-barnes-pervasive-problem-00.txt
>
>
>
> Dear PERPASS,
>
>
>
> Stephen asked me to take a stab at a problem statement for PERPASS.  With
> some help from Bruce, Cullen, and Ted, the results have just been published
> as draft-barnes-pervasive-problem-00.
>
>
>
> In general, this draft tries to outline at a technical level what we mean
> by pervasive attack, and what the high level mitigations are.
>
>
>
> Comments welcome!
>
>
>
> Thanks,
>
> --Richard
>
>
>
>
>
> ---------- Forwarded message ----------
> From: <internet-drafts@ietf.org>
> Date: Mon, Jan 6, 2014 at 9:17 PM
> Subject: New Version Notification for draft-barnes-pervasive-problem-00.txt
> To: Cullen Jennings <fluffy@cisco.com>, Ted Hardie <ted.ietf@gmail.com>,
> Bruce Schneier <schneier@schneier.com>, Richard Barnes <rlb@ipv.sx>
>
>
>
> A new version of I-D, draft-barnes-pervasive-problem-00.txt
> has been successfully submitted by Richard Barnes and posted to the
> IETF repository.
>
> Name:           draft-barnes-pervasive-problem
> Revision:       00
> Title:          Pervasive Attack: A Threat Model and Problem Statement
> Document date:  2014-01-06
> Group:          Individual Submission
> Pages:          23
> URL:
> http://www.ietf.org/internet-drafts/draft-barnes-pervasive-problem-00.txt
> Status:
> https://datatracker.ietf.org/doc/draft-barnes-pervasive-problem/
> Htmlized:
> http://tools.ietf.org/html/draft-barnes-pervasive-problem-00
>
>
> Abstract:
>    Documents published in 2013 have revealed several classes of
>    "pervasive" attack on Internet communications.  In this document, we
>    review the main attacks that have been published, and develop a
>    threat model that describes these pervasive attacks.  Based on this
>    threat model, we discuss the techniques that can be employed in
>    Internet protocol design to increase the protocols robustness to
>    pervasive attacks.
>
>
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>
>
>