Re: [hiprg] Putting HIP on a Diet

"Henderson, Thomas R" <thomas.r.henderson@boeing.com> Tue, 18 May 2010 17:36 UTC

Return-Path: <thomas.r.henderson@boeing.com>
X-Original-To: hiprg@core3.amsl.com
Delivered-To: hiprg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 05E0F28C1C1; Tue, 18 May 2010 10:36:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.238
X-Spam-Level:
X-Spam-Status: No, score=-4.238 tagged_above=-999 required=5 tests=[AWL=-0.239, BAYES_50=0.001, 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 hXGwM8IrV5VM; Tue, 18 May 2010 10:36:16 -0700 (PDT)
Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com [130.76.96.56]) by core3.amsl.com (Postfix) with ESMTP id B316B28C1EF; Tue, 18 May 2010 10:31:36 -0700 (PDT)
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231]) by stl-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id o4IHVRE7013283 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 18 May 2010 12:31:28 -0500 (CDT)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id o4IHVR5V005419; Tue, 18 May 2010 10:31:27 -0700 (PDT)
Received: from XCH-NWHT-02.nw.nos.boeing.com (xch-nwht-02.nw.nos.boeing.com [130.247.70.248]) by blv-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id o4IHVR6U005407 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Tue, 18 May 2010 10:31:27 -0700 (PDT)
Received: from XCH-NW-10V.nw.nos.boeing.com ([130.247.25.83]) by XCH-NWHT-02.nw.nos.boeing.com ([130.247.70.248]) with mapi; Tue, 18 May 2010 10:31:27 -0700
From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
To: "'Noel Chiappa'" <jnc@mercury.lcs.mit.edu>, "hiprg@irtf.org" <hiprg@irtf.org>, "hipsec@ietf.org" <hipsec@ietf.org>
Date: Tue, 18 May 2010 10:31:26 -0700
Thread-Topic: [hiprg] Putting HIP on a Diet
Thread-Index: Acr16GiXDQ8FsTjNSDemomAua/o4iQAxf0rA
Message-ID: <7CC566635CFE364D87DC5803D4712A6C4CE9716194@XCH-NW-10V.nw.nos.boeing.com>
References: <20100517173256.798446BE575@mercury.lcs.mit.edu>
In-Reply-To: <20100517173256.798446BE575@mercury.lcs.mit.edu>
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: [hiprg] Putting HIP on a Diet
X-BeenThere: hiprg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Host Identity Protocol \(HIP\) Research Group" <hiprg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/hiprg>
List-Post: <mailto:hiprg@irtf.org>
List-Help: <mailto:hiprg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 May 2010 17:36:17 -0000

> -----Original Message-----
> From: hiprg-bounces@irtf.org [mailto:hiprg-bounces@irtf.org]
> On Behalf Of Noel Chiappa
> Sent: Monday, May 17, 2010 10:33 AM
> To: hiprg@irtf.org; hipsec@ietf.org
> Cc: jnc@mercury.lcs.mit.edu
> Subject: Re: [hiprg] Putting HIP on a Diet
>
>     > From: Robert Moskowitz <rgm@htt-consult.com>
>
>     > What is HIP? Is HIP the exchange we have now have and
> only that? Or is
>     > HIP a class of protocols built on a Host Identity, each bring a
>     > slightly different set of security claims and risks and
> a slightly
>     > different domain of use?
>
> Well, those are some key (and excellent) questions - and I
> would think you
> need to answer them all fairly fully, and fairly early in the
> design process.
>

I agree, and while it would be fine to work the protocol specifics in the research group (since the proposed WG charter doesn't include this for now), I think that the basic question above should be covered in RFC4423bis.  I would support the latter interpretation (that HIP is (potentially) a protocol family built around the concept of a namespace for IP stacks).

- Tom