Re: [perpass] IETF-89 perpass discussions
Scott Brim <scott.brim@gmail.com> Tue, 14 January 2014 20:45 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 D7CA51AE210 for <perpass@ietfa.amsl.com>; Tue, 14 Jan 2014 12:45:40 -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 mx-uJjm93evl for <perpass@ietfa.amsl.com>; Tue, 14 Jan 2014 12:45:39 -0800 (PST)
Received: from mail-ob0-x233.google.com (mail-ob0-x233.google.com [IPv6:2607:f8b0:4003:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id 344C61AE246 for <perpass@ietf.org>; Tue, 14 Jan 2014 12:45:39 -0800 (PST)
Received: by mail-ob0-f179.google.com with SMTP id wp4so177499obc.10 for <perpass@ietf.org>; Tue, 14 Jan 2014 12:45:27 -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=qTPac7K4A5XeosISmW8wCmQLw0VppBQ6Xs3SFqHTk94=; b=XiJgFBBGXoZMzeFZCbJe+uGkRZzS+yMPFzUSXvwSMJTzuVk5suXP8NiovilQiT3/zM +autyytSPE7mAHvMO7kf3ZWv6Zuy4SaMF1Cv9Gievm1BarG4Kc9G5xvTaYEEWu9C6ykm gKXAT2e6inDdmOyqilP5GmvParxSuPPUEAq5O+/PEb9u/eJn3IcGYB1SSSz9RVtJsyr6 kLF9A2KUCzdrqkv+boOWSs6OpneCKyX+E0YOwBcNk/CBOLVTVGUA8B4rdnPs1q3aWjOr sHmR8s557IELCPW9VF2VcINY0meKzchBhUjQ2jBJL+DBH2gLeXL1nNq35SAPM3DeHEES s9tA==
X-Received: by 10.182.129.201 with SMTP id ny9mr2976677obb.0.1389732327681; Tue, 14 Jan 2014 12:45:27 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Tue, 14 Jan 2014 12:45:07 -0800 (PST)
In-Reply-To: <52D59FFF.4000308@dcrocker.net>
References: <52D54E29.2090606@cs.tcd.ie> <52D59FFF.4000308@dcrocker.net>
From: Scott Brim <scott.brim@gmail.com>
Date: Tue, 14 Jan 2014 15:45:07 -0500
Message-ID: <CAPv4CP_02Mt1SXJSi5XUYd6ieke3nKBHAsBkUJtoG_qgSNubTA@mail.gmail.com>
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: perpass <perpass@ietf.org>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [perpass] IETF-89 perpass discussions
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, 14 Jan 2014 20:45:41 -0000
On Tue, Jan 14, 2014 at 3:37 PM, Dave Crocker <dhc@dcrocker.net> wrote: > I suggest having a session to discuss one or two basic issues. Better > community clarity about some of the basic might improve our ability to > discuss technical issues. > > For example, what is in scope for perpass and what is not? Sounds like either SAAG or a segment in a Plenary following up from last meeting.
- [perpass] IETF-89 perpass discussions Stephen Farrell
- Re: [perpass] IETF-89 perpass discussions Dave Crocker
- Re: [perpass] IETF-89 perpass discussions Scott Brim
- Re: [perpass] IETF-89 perpass discussions Dave Crocker