Re: [Hipsec] [hiprg] Putting HIP on a Diet

Robert Moskowitz <rgm@htt-consult.com> Tue, 18 May 2010 17:56 UTC

Return-Path: <rgm@htt-consult.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 ACF3E3A6846 for <hipsec@core3.amsl.com>; Tue, 18 May 2010 10:56:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.518
X-Spam-Level:
X-Spam-Status: No, score=-0.518 tagged_above=-999 required=5 tests=[AWL=-0.519, BAYES_50=0.001]
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 zwfAqyfnJkiT for <hipsec@core3.amsl.com>; Tue, 18 May 2010 10:56:17 -0700 (PDT)
Received: from klovia.htt-consult.com (klovia.htt-consult.com [208.83.67.149]) by core3.amsl.com (Postfix) with ESMTP id 7F7E03A67A3 for <hipsec@ietf.org>; Tue, 18 May 2010 10:56:17 -0700 (PDT)
Received: from localhost (unknown [127.0.0.1]) by klovia.htt-consult.com (Postfix) with ESMTP id 4EC2268B7C; Tue, 18 May 2010 17:49:13 +0000 (UTC)
Received: from klovia.htt-consult.com ([127.0.0.1]) by localhost (klovia.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ePFXi1GuPvPJ; Tue, 18 May 2010 13:49:04 -0400 (EDT)
Received: from nc2400.htt-consult.com (h155.home.htt [208.83.67.155]) (Authenticated sender: rgm@htt-consult.com) by klovia.htt-consult.com (Postfix) with ESMTPSA id 3F46A68B81; Tue, 18 May 2010 13:49:04 -0400 (EDT)
Message-ID: <4BF2D498.9050907@htt-consult.com>
Date: Tue, 18 May 2010 13:55:36 -0400
From: Robert Moskowitz <rgm@htt-consult.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9) Gecko/20100330 Fedora/3.0.4-1.fc12 Thunderbird/3.0.4
MIME-Version: 1.0
To: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
References: <20100517173256.798446BE575@mercury.lcs.mit.edu> <7CC566635CFE364D87DC5803D4712A6C4CE9716194@XCH-NW-10V.nw.nos.boeing.com>
In-Reply-To: <7CC566635CFE364D87DC5803D4712A6C4CE9716194@XCH-NW-10V.nw.nos.boeing.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "hipsec@ietf.org" <hipsec@ietf.org>, 'Noel Chiappa' <jnc@mercury.lcs.mit.edu>
Subject: Re: [Hipsec] [hiprg] Putting HIP on a Diet
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: Tue, 18 May 2010 17:56:18 -0000

On 05/18/2010 01:31 PM, Henderson, Thomas R wrote:
>    
>> -----Original Message-----
>>
>>      >  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).

I am working on this wording being added to 4423-bis. I really think it 
captures my thoughts over the past 2 years on work being done with HIP 
RFID and HIP IOT. And now HIP DEX.