Re: [perpass] draft-farrell-perpass-attack architecture issue

Scott Brim <scott.brim@gmail.com> Wed, 15 January 2014 14:28 UTC

Return-Path: <scott.brim@gmail.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 BD2211AE0F4 for <perpass@ietfa.amsl.com>; Wed, 15 Jan 2014 06:28:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, 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 RiJY_9ih44oe for <perpass@ietfa.amsl.com>; Wed, 15 Jan 2014 06:28:14 -0800 (PST)
Received: from mail-ob0-x232.google.com (mail-ob0-x232.google.com [IPv6:2607:f8b0:4003:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id C1AE91AE0D2 for <perpass@ietf.org>; Wed, 15 Jan 2014 06:28:14 -0800 (PST)
Received: by mail-ob0-f178.google.com with SMTP id uz6so1207760obc.23 for <perpass@ietf.org>; Wed, 15 Jan 2014 06:28:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=DQhM/JqLSNZaF8O23vwpxO/xCUWiBkzV5rhtSqS9UCU=; b=jzyHRkffsHMfu6EuHUQGUdVpPwFq7+Zc86TdV2l3b2AbDFbGKHiiFFNkpb50X17R/e a+N/2hQ5hPWLWC1KVRQr7/tgmF+Ymt6QTaxrjXJ4Pkl2IJNhiyckPE+PySqRSsFff102 4SwODF/wMztrzGH06vteg6X45ze5H3YrvoGSvvPxHKCOyZbl1puZ/prS+8umOKPQft3c Ekw7Kfd1NhBnR4deqa4EtNDKURsppnmchSPA09Y0E9Rrd1uM0zwk12cigd0hrh2sfOUx 35lRUCYavTf+S0pU8hvgzRuHHJEs9uD6xMB7CUMhBMGLMPJ/zoPBc3kT2bemYVPMg9oH Bvkg==
X-Received: by 10.60.174.167 with SMTP id bt7mr2005401oec.54.1389796082964; Wed, 15 Jan 2014 06:28:02 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Wed, 15 Jan 2014 06:27:42 -0800 (PST)
In-Reply-To: <52D688B3.3040907@cs.tcd.ie>
References: <52D43E69.6090001@cs.tcd.ie> <C19E19BF-B9A2-4EEB-8E77-DF0CAD548277@cisco.com> <52D5B36D.1020405@gmail.com> <52D688B3.3040907@cs.tcd.ie>
From: Scott Brim <scott.brim@gmail.com>
Date: Wed, 15 Jan 2014 09:27:42 -0500
Message-ID: <CAPv4CP9-=2Mt4XJ5KR7ThULa8L0NZH5p8TeqN7SnVdJy=NH3vw@mail.gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: perpass <perpass@ietf.org>, Melinda Shore <melinda.shore@gmail.com>
Subject: Re: [perpass] draft-farrell-perpass-attack architecture issue
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: Wed, 15 Jan 2014 14:28:16 -0000

On Wed, Jan 15, 2014 at 8:10 AM, Stephen Farrell
<stephen.farrell@cs.tcd.ie> wrote:
> I'd be interested if someone wanted to start work on some
> WG-chair/shepherd guidance for how to consider pervasive
> monitoring. That'd likely take a while to get baked, and
> would maybe end up not (just) as an RFC, but as training
> material and/or an IESG statement or something, but could
> easily start as an I-D. Any takers?

I think we already have a lot of it. (1) Add RFC6973 to BCP72. (2)
Keep moving the perpass-related drafts forward, and add them as they
become mature. (3) In the shepherds writeup template, have a question
such as "(18) Describe the Document Shepherd's review of the security
considerations section (see BCP 72 for guidelines), especially with
regard to its consistency with the body of the document."

Scott