RE: [Hipsec] draft-ietf-hip-esp-03

"Henderson, Thomas R" <thomas.r.henderson@boeing.com> Fri, 25 August 2006 14:30 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GGci2-00013m-Ih; Fri, 25 Aug 2006 10:30:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GGchz-0000tN-Vl for hipsec@ietf.org; Fri, 25 Aug 2006 10:30:55 -0400
Received: from blv-smtpout-01.boeing.com ([130.76.32.69] helo=blv-smtpout-01.ns.cs.boeing.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GGchw-0005WN-Me for hipsec@ietf.org; Fri, 25 Aug 2006 10:30:55 -0400
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [192.42.227.216]) by blv-smtpout-01.ns.cs.boeing.com (8.13.6/8.13.6/SMTPOUT) with ESMTP id k7PEUi7Q000809 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <hipsec@ietf.org>; Fri, 25 Aug 2006 07:30:50 -0700 (PDT)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.13.6/8.13.6/DOWNSTREAM_SMTPIN) with ESMTP id k7PEUhoF002220 for <hipsec@ietf.org>; Fri, 25 Aug 2006 07:30:44 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by blv-av-01.boeing.com (8.13.6/8.13.6/UPSTREAM_RELAY) with ESMTP id k7PEUaQb001740; Fri, 25 Aug 2006 07:30:41 -0700 (PDT)
Received: from XCH-NW-5V1.nw.nos.boeing.com ([130.247.55.44]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 25 Aug 2006 07:30:40 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Hipsec] draft-ietf-hip-esp-03
Date: Fri, 25 Aug 2006 07:30:40 -0700
Message-ID: <77F357662F8BFA4CA7074B0410171B6D01A2F5DA@XCH-NW-5V1.nw.nos.boeing.com>
In-Reply-To: <CE0B4481-4542-48FA-9606-384D8A6068A0@indranet.co.nz>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Hipsec] draft-ietf-hip-esp-03
Thread-Index: AcbHUkzxGIAdeKabQNuJEKyWglOYdAA/8Gzg
From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
To: Andrew McGregor <andrew@indranet.co.nz>
X-OriginalArrivalTime: 25 Aug 2006 14:30:40.0726 (UTC) FILETIME=[0A4C6F60:01C6C853]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: hipsec@ietf.org
X-BeenThere: hipsec@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/hipsec>
List-Post: <mailto:hipsec@lists.ietf.org>
List-Help: <mailto:hipsec-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@lists.ietf.org?subject=subscribe>
Errors-To: hipsec-bounces@lists.ietf.org

 

> -----Original Message-----
> From: Andrew McGregor [mailto:andrew@indranet.co.nz] 
> Sent: Thursday, August 24, 2006 12:54 AM
> To: Henderson, Thomas R
> Cc: Mark Townsley; hipsec@ietf.org
> Subject: Re: [Hipsec] draft-ietf-hip-esp-03
> 
> But isn't it the case that a node can perfectly well run HIP and  
> IPsec at the same time on different SPIs in any combination of  
> modes?  In other words, mere support of HIP should have no effect on  
> IPsec support.
> 

Yes, I misread the second part of the question as asking whether HIP
qualified as IPsec.  I agree with you.

mea culpa,
Tom 

_______________________________________________
Hipsec mailing list
Hipsec@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/hipsec