IETF Logo Mail Archive

[perpass] "Guide to intranet protection"?

Dave Crocker <dhc@dcrocker.net> Wed, 27 November 2013 14:07 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 1F2001ADF5C for <perpass@ietfa.amsl.com>; Wed, 27 Nov 2013 06:07:04 -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 zxGt5OklieQd for <perpass@ietfa.amsl.com>; Wed, 27 Nov 2013 06:06:58 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 9BACF1ADEA3 for <perpass@ietf.org>; Wed, 27 Nov 2013 06:06:58 -0800 (PST)
Received: from [192.168.200.184] (rrcs-74-62-19-234.west.biz.rr.com [74.62.19.234]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id rARE6tng031348 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <perpass@ietf.org>; Wed, 27 Nov 2013 06:06:58 -0800
Message-ID: <5295FC4F.7060309@dcrocker.net>
Date: Wed, 27 Nov 2013 06:06:07 -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: perpass <perpass@ietf.org>
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 06:06:58 -0800 (PST)
Subject: [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: Wed, 27 Nov 2013 14:07:04 -0000

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...

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

v2.23.0 | Report a Bug | By Email