IETF Logo Mail Archive

Re: [Hipsec] comments on draft-ietf-hip-rfc4423-bis-01

"Ahrenholz, Jeffrey M" <jeffrey.m.ahrenholz@boeing.com> Mon, 21 February 2011 15:48 UTC

Return-Path: <jeffrey.m.ahrenholz@boeing.com>
X-Original-To: hipsec@core3.amsl.com
Delivered-To: hipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B3C2F3A7131 for <hipsec@core3.amsl.com>; Mon, 21 Feb 2011 07:48:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 N4qsK8JvJEGa for <hipsec@core3.amsl.com>; Mon, 21 Feb 2011 07:48:31 -0800 (PST)
Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com [130.76.96.56]) by core3.amsl.com (Postfix) with ESMTP id 180213A6EEC for <hipsec@ietf.org>; Mon, 21 Feb 2011 07:48:31 -0800 (PST)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by stl-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id p1LFmtKV013514 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 21 Feb 2011 09:49:00 -0600 (CST)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id p1LFmtcg018713; Mon, 21 Feb 2011 09:48:55 -0600 (CST)
Received: from XCH-NWHT-03.nw.nos.boeing.com (xch-nwht-03.nw.nos.boeing.com [130.247.71.23]) by stl-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id p1LFmsjN018692 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Mon, 21 Feb 2011 09:48:55 -0600 (CST)
Received: from XCH-NW-12V.nw.nos.boeing.com ([130.247.25.246]) by XCH-NWHT-03.nw.nos.boeing.com ([130.247.71.23]) with mapi; Mon, 21 Feb 2011 07:48:54 -0800
From: "Ahrenholz, Jeffrey M" <jeffrey.m.ahrenholz@boeing.com>
To: Miika Komu <mkomu@cs.hut.fi>, hip WG <hipsec@ietf.org>
Date: Mon, 21 Feb 2011 07:48:57 -0800
Thread-Topic: [Hipsec] comments on draft-ietf-hip-rfc4423-bis-01
Thread-Index: AcvR2/wBkUNVlKorQzu7ol66NZxUnwAAqGtA
Message-ID: <FD98F9C3CBABA74E89B5D4B5DE0263B9379AA0773F@XCH-NW-12V.nw.nos.boeing.com>
References: <FD98F9C3CBABA74E89B5D4B5DE0263B9379A8486D1@XCH-NW-12V.nw.nos.boeing.com><4D626A88.6060806@htt-consult.com> <4D62845E.1020603@cs.hut.fi>
In-Reply-To: <4D62845E.1020603@cs.hut.fi>
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
Subject: Re: [Hipsec] comments on draft-ietf-hip-rfc4423-bis-01
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hipsec>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Feb 2011 15:48:32 -0000

> > You would need a secure channel (hint, hint) to move the Security
> > Association, including all private key needed that are not
> technically
> > part of the SA.  But, yes, there are people looking into this for
> cloud
> > computing.
> 
> actually I would agree with Jeff here. I think the experiment report
> would be a better fit for such research work. I would include also
> reference to the earlier work:
> 
> http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.79.5588&rep=re
> p1&type=pdf

I just wanted to make sure that statement on HI mobility didn't appear out of thin air :)

-Jeff

v2.23.0 | Report a Bug | By Email