Re: [perpass] IETF-89 perpass discussions
Dave Crocker <dhc@dcrocker.net> Tue, 14 January 2014 20:37 UTC
Return-Path: <dhc@dcrocker.net>
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 BF5CE1AE19D for <perpass@ietfa.amsl.com>; Tue, 14 Jan 2014 12:37:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 x5wU0WKtHIy0 for <perpass@ietfa.amsl.com>; Tue, 14 Jan 2014 12:37:49 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 6C4161AE133 for <perpass@ietf.org>; Tue, 14 Jan 2014 12:37:49 -0800 (PST)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s0EKbQpf000955 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 14 Jan 2014 12:37:29 -0800
Message-ID: <52D59FFF.4000308@dcrocker.net>
Date: Tue, 14 Jan 2014 12:37:19 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, perpass <perpass@ietf.org>
References: <52D54E29.2090606@cs.tcd.ie>
In-Reply-To: <52D54E29.2090606@cs.tcd.ie>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Tue, 14 Jan 2014 12:37:29 -0800 (PST)
Subject: Re: [perpass] IETF-89 perpass discussions
X-BeenThere: perpass@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
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:37:51 -0000
On 1/14/2014 6:48 AM, Stephen Farrell wrote: > But if lots of you yell at us before Friday that that's > a bad plan we can request a perpass slot. (You can yell > off list or on, whatever:-) On the average, the f2f meeting isn't very efficient or productive for dealing with broad group discussion questions. Perpass might be an exception. 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? d/ -- Dave Crocker Brandenburg InternetWorking bbiw.net
- [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