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

"Vishwas Manral" <vishwas.ietf@gmail.com> Thu, 18 December 2008 03:19 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 258233A6B6A; Wed, 17 Dec 2008 19:19:38 -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 BC8C63A6B6A for <opsec@core3.amsl.com>; Wed, 17 Dec 2008 19:19:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 QOy+FfWMscuR for <opsec@core3.amsl.com>; Wed, 17 Dec 2008 19:19:36 -0800 (PST)
Received: from mail-bw0-f21.google.com (mail-bw0-f21.google.com [209.85.218.21]) by core3.amsl.com (Postfix) with ESMTP id 8995C3A68AB for <opsec@ietf.org>; Wed, 17 Dec 2008 19:19:35 -0800 (PST)
Received: by bwz14 with SMTP id 14so823408bwz.13 for <opsec@ietf.org>; Wed, 17 Dec 2008 19:19:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=sJYcrfNIqUVIEaquFFxKlIIHdiZrtiJIBITfGOFiaWE=; b=uyvL/0pc8DO/a/ni0e0T0OVAdPNQiCE5eKnNGGvrP55EYdIsRltFB5NVcC3VaY0cHV A9E5j8tuBkWMH8Xtjuuq8WZ+aJ+SK7Tc4IO8sdIF/SpCW3PRY8cxL9nvsPidBf7kWdK5 xZlyj+elyE0YHC3wWFFUQ1h/YmZMsqNHCu9to=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=wrlYU+uIrxoyyIlAyii+JIOX79CuPVsFux0gv/c1QuYlciG/bRg2u16J149HZgg9bA lYaDXyJJSO/6p4qEwFwRRck8uoD+vUVaKU41IYJmfbOEKJ/PhjgVaY+9dfd3fjd/0ZLm WO7ktcBNuoyXRw4wiOFKFQuWWATemqv3nCSpc=
Received: by 10.181.158.3 with SMTP id k3mr483990bko.182.1229570366550; Wed, 17 Dec 2008 19:19:26 -0800 (PST)
Received: by 10.181.31.13 with HTTP; Wed, 17 Dec 2008 19:19:26 -0800 (PST)
Message-ID: <77ead0ec0812171919t5c160a2fl423805c8ad0941c3@mail.gmail.com>
Date: Wed, 17 Dec 2008 19:19:26 -0800
From: Vishwas Manral <vishwas.ietf@gmail.com>
To: R Atkinson <ran.atkinson@gmail.com>
In-Reply-To: <A1EB330A-67A7-4D9D-B7DF-630BE4EBD1C1@gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
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>
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.

Thanks,
Vishwas

On Wed, Dec 17, 2008 at 8:21 AM, R Atkinson <ran.atkinson@gmail.com> wrote:
>
> On  17 Dec 2008, at 11:14, Vishwas Manral wrote:
>>
>> Ran, the point we were talking is about the packet actually not being
>> able to be filtered by the edge node/ device because the packet is
>> encapsulated in the ESP header. Is there something amiss here - when
>> you say such a packet can be filtered?
>
> Please go re-read my note to OPsec from yesterday
> for the full analysis.
>
> Cheers,
>
> Ran
>
> _______________________________________________
> OPSEC mailing list
> OPSEC@ietf.org
> https://www.ietf.org/mailman/listinfo/opsec
>
_______________________________________________
OPSEC mailing list
OPSEC@ietf.org
https://www.ietf.org/mailman/listinfo/opsec