IETF Logo Mail Archive

Re: [OPSEC] Prospective issue with IPsec ESP-NULL & IGP packets

"Darrel Lewis (darlewis)" <darlewis@cisco.com> Thu, 18 December 2008 19:52 UTC

Return-Path: <opsec-bounces@ietf.org>
X-Original-To: opsec-archive@optimus.ietf.org
Delivered-To: ietfarch-opsec-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6E1243A6A1F; Thu, 18 Dec 2008 11:52:43 -0800 (PST)
X-Original-To: opsec@core3.amsl.com
Delivered-To: opsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B57EC3A6A1F for <opsec@core3.amsl.com>; Thu, 18 Dec 2008 11:52:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.832
X-Spam-Level:
X-Spam-Status: No, score=-5.832 tagged_above=-999 required=5 tests=[AWL=0.767, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2aHMkUEcq+Lf for <opsec@core3.amsl.com>; Thu, 18 Dec 2008 11:52:41 -0800 (PST)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id EB0643A680C for <opsec@ietf.org>; Thu, 18 Dec 2008 11:52:40 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.36,244,1228089600"; d="scan'208";a="116893335"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-2.cisco.com with ESMTP; 18 Dec 2008 19:52:33 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id mBIJqXCq013770; Thu, 18 Dec 2008 11:52:33 -0800
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id mBIJqXqN011250; Thu, 18 Dec 2008 19:52:33 GMT
Received: from xmb-sjc-218.amer.cisco.com ([171.70.151.151]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 18 Dec 2008 11:52:33 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 18 Dec 2008 11:51:55 -0800
Message-ID: <60C4A248E730F249990993E3B9BD44D806E3788F@xmb-sjc-218.amer.cisco.com>
In-Reply-To: <77ead0ec0812171919t5c160a2fl423805c8ad0941c3@mail.gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [OPSEC] Prospective issue with IPsec ESP-NULL & IGP packets
thread-index: Aclgv333o9Yj1K8ATIeQ8eLRQLfwAwAik38A
References: <14198D76-AA32-4E02-9425-0700ED57B07B@gmail.com><77ead0ec0812161759g4900bd98h6ad6c07bb0d81fe3@mail.gmail.com><89F12E27-304C-41AD-BC27-556BD9FA7040@gmail.com><77ead0ec0812161851q204bd1e7nd9fc57538d161794@mail.gmail.com><596A619D-6D7B-421E-A43C-47AD1762093F@gmail.com><77ead0ec0812170814j3c34ea6aof7df345adfeee56f@mail.gmail.com><A1EB330A-67A7-4D9D-B7DF-630BE4EBD1C1@gmail.com> <77ead0ec0812171919t5c160a2fl423805c8ad0941c3@mail.gmail.com>
From: "Darrel Lewis (darlewis)" <darlewis@cisco.com>
To: Vishwas Manral <vishwas.ietf@gmail.com>, R Atkinson <ran.atkinson@gmail.com>
X-OriginalArrivalTime: 18 Dec 2008 19:52:33.0446 (UTC) FILETIME=[2B0C2460:01C9614A]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=669; t=1229629953; x=1230493953; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=darlewis@cisco.com; z=From:=20=22Darrel=20Lewis=20(darlewis)=22=20<darlewis@cisc o.com> |Subject:=20RE=3A=20[OPSEC]=20Prospective=20issue=20with=20 IPsec=20ESP-NULL=20&=20IGP=20packets |Sender:=20; bh=m1ynObDi5zG0fVO/6f891tmDWZKhX7ZDuUmShXDzCs0=; b=M6+mrLCDrCy3aEJh4tca2bL2BqAjzd25s7Zn+oagZg6GU8PwtdYemqGRzu QQY1pL4KF9Ebi+huQJgK4Pd96vvCHMifseOXd512ZbFR2fxI6vSBa13A56Wo +4hnEkklbYgGE/SpvFT3wJITj6TMDX470QtJtHbvI0FI4QOP+uCJI=;
Authentication-Results: sj-dkim-1; header.From=darlewis@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; );
Cc: opsec@ietf.org
Subject: Re: [OPSEC] Prospective issue with IPsec ESP-NULL & IGP packets
X-BeenThere: opsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: opsec wg mailing list <opsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsec>, <mailto:opsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/opsec>
List-Post: <mailto:opsec@ietf.org>
List-Help: <mailto:opsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsec>, <mailto:opsec-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: opsec-bounces@ietf.org
Errors-To: opsec-bounces@ietf.org

 
> Hi Ran,
> 
> As you have sent so many mails with so much text would it be 
> possible for you to point out which mail I should read.
> 
> I am unable to understand how you can say ESP packets can be 
> filtered at the edge based on the content. That is a problem 
> IPsecme is trying to solve.
> 

Vishwas,

I think you can in theory filter all packets at the edge based on their
destination.  Why would you allow anyone to send ESP packets to your
infrastructure addresses?

I believe this is the point Ran is trying to make.  Infrastructure
hiding/filtering is orthogonal to encryption between infrastructure
routers.

-Darrel
_______________________________________________
OPSEC mailing list
OPSEC@ietf.org
https://www.ietf.org/mailman/listinfo/opsec

v2.23.0 | Report a Bug | By Email