Re: [perpass] "Its an attack" BCP draft
Dean Willis <dean.willis@softarmor.com> Sat, 23 November 2013 07:26 UTC
Return-Path: <dean.willis@softarmor.com>
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 E2BB81AE135 for <perpass@ietfa.amsl.com>; Fri, 22 Nov 2013 23:26:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 ahPwiFPy2VuN for <perpass@ietfa.amsl.com>; Fri, 22 Nov 2013 23:26:44 -0800 (PST)
Received: from mail-oa0-x22f.google.com (mail-oa0-x22f.google.com [IPv6:2607:f8b0:4003:c02::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 6A29F1AE14B for <perpass@ietf.org>; Fri, 22 Nov 2013 23:26:44 -0800 (PST)
Received: by mail-oa0-f47.google.com with SMTP id k1so2415095oag.34 for <perpass@ietf.org>; Fri, 22 Nov 2013 23:26:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=softarmor.com; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=KiTezyxZePHWbDC/JUHot916iWJZVdHXk72PggnEaV8=; b=Lg+zKmJ+IPevsXU/r7FpOYEIbbwNwkD2rAttGYJO0KFnX2NUXkmzhWT92daUCszOOe Pge+IZC7nyx9tKVf6jKJX28nJifaL4C7irgDNgkS0zwH7PsK8LgTs3jZ3W4CXpc3jV5D KWkZMJlh+GCloSEUM91Ila39kXkrLyS3FNJVM=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=KiTezyxZePHWbDC/JUHot916iWJZVdHXk72PggnEaV8=; b=ZbaS8Gsb7S40vsx80ONuapgE7DbYiyVWntK3jBjB3q1Zq6jN39FNI1xt4yHsHj/kkV 5S2GmjNWQZLTQfbvIN0hc29LdMkYMkIXD//UIWZwMy1HfPI3A6w00q+YMC22EunEOXmk J3U8mzI1vImTzrtvOrpQzDfqriBoy+78bXSZ78VScy9HuQqbbHk8VdSAdPWhI6NJqkz8 oEvOajMFVyROW8BgAdvAYDYCF3I7EF4SsCfA7PtagpitcfpfhH15jbDsvLA+diVcS5iP WRTIOUtYiDjb0yNiIAf6cOu9rSpKdLii9uAUXjnUWXqVUHIKkTWM9XhwWpJtRm1+kU6H vCew==
X-Gm-Message-State: ALoCoQmrXJMc4VwMvlE/2l/bIgBW3KrtJJfwmR58dIGBM1FJ5afPYEzmwNHihMA2VHWMeZyF4+yO
X-Received: by 10.182.22.18 with SMTP id z18mr740099obe.42.1385191596916; Fri, 22 Nov 2013 23:26:36 -0800 (PST)
Received: from [192.168.2.145] (cpe-72-181-157-19.tx.res.rr.com. [72.181.157.19]) by mx.google.com with ESMTPSA id m7sm53613954obo.7.2013.11.22.23.26.35 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 22 Nov 2013 23:26:36 -0800 (PST)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Dean Willis <dean.willis@softarmor.com>
In-Reply-To: <528D3A85.5090003@gmail.com>
Date: Sat, 23 Nov 2013 01:26:35 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <47115845-5892-4BAD-9FBA-0014AC026BE8@softarmor.com>
References: <528D34D7.1010303@cs.tcd.ie> <528D3A85.5090003@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1822)
Cc: perpass <perpass@ietf.org>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [perpass] "Its an attack" BCP draft
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: Sat, 23 Nov 2013 07:26:46 -0000
On Nov 20, 2013, at 4:41 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote: > > However, I am concerned by the 'bad actor' phrase. The problem is > that it's fine as explained in the draft, but it's highly likely to > be quoted out of context and thereby cause confusion. It would be > safer to use a neutral term ('observer'? 'surveyor'?). I like “perp”, which is cop-slang for “perpetrator”, which they now tend to say instead of “suspect”. But it fits nicely with “perpass”. If the surveillors are the perp in perpass, what does that make the surveilled? Donkeys? — Dean
- Re: [perpass] "Its an attack" BCP draft Ralf Skyper Kaiser
- [perpass] "Its an attack" BCP draft Stephen Farrell
- Re: [perpass] "Its an attack" BCP draft Brian E Carpenter
- Re: [perpass] "Its an attack" BCP draft Stephen Farrell
- Re: [perpass] "Its an attack" BCP draft joel jaeggli
- Re: [perpass] "Its an attack" BCP draft Rob Stradling
- Re: [perpass] "Its an attack" BCP draft Ted Lemon
- Re: [perpass] "Its an attack" BCP draft joel jaeggli
- Re: [perpass] "Its an attack" BCP draft Stephen Farrell
- Re: [perpass] "Its an attack" BCP draft Ted Lemon
- Re: [perpass] "Its an attack" BCP draft Paul Ferguson
- Re: [perpass] "Its an attack" BCP draft Fred Baker (fred)
- Re: [perpass] "Its an attack" BCP draft Fred Baker (fred)
- Re: [perpass] "Its an attack" BCP draft Stephen Farrell
- Re: [perpass] "Its an attack" BCP draft Yoav Nir
- Re: [perpass] "Its an attack" BCP draft Phillip Hallam-Baker
- Re: [perpass] "Its an attack" BCP draft Jon Callas
- Re: [perpass] "Its an attack" BCP draft Robin Wilton
- Re: [perpass] "Its an attack" BCP draft SM
- Re: [perpass] "Its an attack" BCP draft Stephen Kent
- Re: [perpass] "Its an attack" BCP draft Robin Wilton
- Re: [perpass] "Its an attack" BCP draft Warren Kumari
- Re: [perpass] "Its an attack" BCP draft Dean Willis
- Re: [perpass] "Its an attack" BCP draft Jari Arkko