Re: [perpass] "Guide to intranet protection"?

Dave Crocker <dhc@dcrocker.net> Thu, 28 November 2013 04:39 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 4618C1AE10A for <perpass@ietfa.amsl.com>; Wed, 27 Nov 2013 20:39:30 -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 pl84AA59M_Vf for <perpass@ietfa.amsl.com>; Wed, 27 Nov 2013 20:39:28 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id BA5EB1ADF87 for <perpass@ietf.org>; Wed, 27 Nov 2013 20:39:28 -0800 (PST)
Received: from [10.211.51.212] (rbiguest.jcresorts.com [206.170.126.120] (may be forged)) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id rAS4dOfn025753 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 27 Nov 2013 20:39:28 -0800
Message-ID: <5296C8CC.2060508@dcrocker.net>
Date: Wed, 27 Nov 2013 20:38:36 -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.1.1
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
References: <5295FC4F.7060309@dcrocker.net> <5295FDE8.5000402@cs.tcd.ie> <m2mwkpgpi0.wl%randy@psg.com>
In-Reply-To: <m2mwkpgpi0.wl%randy@psg.com>
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]); Wed, 27 Nov 2013 20:39:28 -0800 (PST)
Cc: perpass <perpass@ietf.org>
Subject: Re: [perpass] "Guide to intranet protection"?
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: Thu, 28 Nov 2013 04:39:30 -0000

On 11/27/2013 7:43 PM, Randy Bush wrote:
>>> I'm assuming that providing meaningful protection takes a statement
>>> beyond "encrypt all your links".  Perhaps it doesn't, but I thought
>>> I'd ask...
>> I'd say that'd be a fine thing if we could get someone who'd done that
>> job to help write it.
>
> may not work out as well as we might wish, as folk who have done it may
> not want to disclose details.  but i am sure there are folk who have not
> done it who will be happy to tell others how they should run their
> networks :)


with such a warm and inviting tone being offered at this stage of the 
topic, i'm sure everyone will feel quite comfortable testing their 
suggestions and comments, to produce a frank and open exchange that will 
vet the contents of the draft document.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net