IETF Logo Mail Archive

Re: [IPsec] WESP - Roadmap Ahead

"Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com> Fri, 13 November 2009 04:55 UTC

Return-Path: <manav.bhatia@alcatel-lucent.com>
X-Original-To: ipsec@core3.amsl.com
Delivered-To: ipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 38D543A6801 for <ipsec@core3.amsl.com>; Thu, 12 Nov 2009 20:55:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.457
X-Spam-Level:
X-Spam-Status: No, score=-2.457 tagged_above=-999 required=5 tests=[AWL=0.142, 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 fNrYSaOYxl+d for <ipsec@core3.amsl.com>; Thu, 12 Nov 2009 20:55:21 -0800 (PST)
Received: from hoemail2.alcatel.com (hoemail2.alcatel.com [192.160.6.149]) by core3.amsl.com (Postfix) with ESMTP id 5E33D3A67DB for <ipsec@ietf.org>; Thu, 12 Nov 2009 20:55:21 -0800 (PST)
Received: from horh1.usa.alcatel.com (h172-22-218-55.lucent.com [172.22.218.55]) by hoemail2.alcatel.com (8.13.8/IER-o) with ESMTP id nAD4toQd007573; Thu, 12 Nov 2009 22:55:50 -0600 (CST)
Received: from mail.apac.alcatel-lucent.com (h202-65-2-130.alcatel.com [202.65.2.130]) by horh1.usa.alcatel.com (8.13.8/emsr) with ESMTP id nAD4tma6021181; Thu, 12 Nov 2009 22:55:49 -0600 (CST)
Received: from INBANSXCHHUB02.in.alcatel-lucent.com (inbansxchhub02.in.alcatel-lucent.com [135.250.12.35]) by mail.apac.alcatel-lucent.com (8.13.7/8.13.7/Alcanet1.0) with ESMTP id nAD4pGI1016640; Fri, 13 Nov 2009 12:54:18 +0800
Received: from INBANSXCHMBSA1.in.alcatel-lucent.com ([135.250.12.56]) by INBANSXCHHUB02.in.alcatel-lucent.com ([135.250.12.35]) with mapi; Fri, 13 Nov 2009 10:24:29 +0530
From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
To: Richard Graveman <rfgraveman@gmail.com>
Date: Fri, 13 Nov 2009 10:24:27 +0530
Thread-Topic: [IPsec] WESP - Roadmap Ahead
Thread-Index: AcpkAd3D8mOSnPSbSvmyQgCKy2ELlgAGlD9A
Message-ID: <7C362EEF9C7896468B36C9B79200D8350AB2C85E6D@INBANSXCHMBSA1.in.alcatel-lucent.com>
References: <dc8fd0140911110805q67759507t6cf75a1e9d81c5aa@mail.gmail.com> <p06240800c720d4538dd2@133.93.112.234> <p0624080ac7212e67c860@133.93.16.246> <8CCEE8E4-9AC4-46FB-93E4-FE61E0135EB7@doubleshotsecurity.com> <p0624080ec7213743dc05@133.93.16.246> <dc8fd0140911112030y46aa24f9hf3715d57446e96c0@mail.gmail.com> <51eafbcb0911112144u6e25b826w4ec8110d1f73e652@mail.gmail.com> <7C362EEF9C7896468B36C9B79200D8350AB2C85E06@INBANSXCHMBSA1.in.alcatel-lucent.com> <45c8c21a0911121737v1659cc01vd716ab401023af1e@mail.gmail.com>
In-Reply-To: <45c8c21a0911121737v1659cc01vd716ab401023af1e@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 172.22.12.28
X-Scanned-By: MIMEDefang 2.64 on 202.65.2.130
Cc: "ipsec@ietf.org" <ipsec@ietf.org>
Subject: Re: [IPsec] WESP - Roadmap Ahead
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipsec>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Nov 2009 04:55:22 -0000

Yup, that's correct I had not considered multicast.

SSM groups would use a 3-tuple SA identifier composed of an SPI, a dest mcast address, and the source IP. An Any-Source Multicast group SA would only require an SPI and a dest mcast identifier. If either of the IPs change, wouldn't the SAD lookup fail?

Cheers, Manav

> -----Original Message-----
> From: Richard Graveman [mailto:rfgraveman@gmail.com] 
> Sent: Friday, November 13, 2009 7.07 AM
> To: Bhatia, Manav (Manav)
> Cc: Daniel Migault; ipsec@ietf.org; Stephen Kent; Kaeo; 
> Merike@core3.amsl.com
> Subject: Re: [IPsec] WESP - Roadmap Ahead
> 
> I think this argument implicitly assumes unicast.
> 
> Rich Graveman
> 
> On Thu, Nov 12, 2009 at 8:18 PM, Bhatia, Manav (Manav)
> <manav.bhatia@alcatel-lucent.com> wrote:
> > Daniel,
> >
> >> AH is a security feature we need to keep for header authentication
> >
> > Am really not sure about the value that AH adds even in 
> case of header authentication.
> >
> > So what fields does AH protect:
> >
> > Version, Payload length, Next Header, Source IP and dest IP
> >

v2.23.0 | Report a Bug | By Email