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

Stephen Farrell <stephen.farrell@cs.tcd.ie> Wed, 27 November 2013 14:13 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
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 929821ADF85 for <perpass@ietfa.amsl.com>; Wed, 27 Nov 2013 06:13:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-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 udMYsWO1guCw for <perpass@ietfa.amsl.com>; Wed, 27 Nov 2013 06:13:04 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id CA2591ADFC7 for <perpass@ietf.org>; Wed, 27 Nov 2013 06:12:57 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 19EB6BE58; Wed, 27 Nov 2013 14:12:56 +0000 (GMT)
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nSD3faVUWFCb; Wed, 27 Nov 2013 14:12:56 +0000 (GMT)
Received: from [134.226.36.180] (stephen-think.dsg.cs.tcd.ie [134.226.36.180]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id F3283BE55; Wed, 27 Nov 2013 14:12:55 +0000 (GMT)
Message-ID: <5295FDE8.5000402@cs.tcd.ie>
Date: Wed, 27 Nov 2013 14:12:56 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: dcrocker@bbiw.net, perpass <perpass@ietf.org>
References: <5295FC4F.7060309@dcrocker.net>
In-Reply-To: <5295FC4F.7060309@dcrocker.net>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: Re: [perpass] "Guide to intranet protection"?
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, 27 Nov 2013 14:13:11 -0000

On 11/27/2013 02:06 PM, Dave Crocker wrote:
> Morning mid-coffee question:
> 
>      There have been some recent news articles about various major ISPs
> taking steps to encrypt their (internal) traffic.  These prompt me to
> wonder whether it would be practical and useful for the IETF to produce
> a basic draft that gives guidance to other ISP and enterprise operators
> about the steps they should take to protect their traffic.
> 
>      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.

S.

> d/