Re: [Hipsec] The Host Identity Hash

Robert Moskowitz <rgm@htt-consult.com> Tue, 29 December 2009 23:08 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 062163A6940 for <hipsec@core3.amsl.com>; Tue, 29 Dec 2009 15:08:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.497
X-Spam-Level:
X-Spam-Status: No, score=-2.497 tagged_above=-999 required=5 tests=[AWL=0.102, 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 tw4oUhymY+ip for <hipsec@core3.amsl.com>; Tue, 29 Dec 2009 15:08:58 -0800 (PST)
Received: from klovia.htt-consult.com (klovia.htt-consult.com [208.83.67.149]) by core3.amsl.com (Postfix) with ESMTP id 284C73A67C0 for <hipsec@ietf.org>; Tue, 29 Dec 2009 15:08:57 -0800 (PST)
Received: from localhost (unknown [127.0.0.1]) by klovia.htt-consult.com (Postfix) with ESMTP id E016A68A8B; Wed, 30 Dec 2009 00:06:36 +0000 (UTC)
X-Virus-Scanned: amavisd-new at localhost
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 1lvNXdaSY6TG; Tue, 29 Dec 2009 19:06:28 -0500 (EST)
Received: from nc2400.htt-consult.com (unknown [IPv6:2607:f4b8:3:1:21b:77ff:fe43:978]) (Authenticated sender: rgm@htt-consult.com) by klovia.htt-consult.com (Postfix) with ESMTPSA id 00D316818E; Tue, 29 Dec 2009 19:06:27 -0500 (EST)
Message-ID: <4B3A8C8E.2020300@htt-consult.com>
Date: Tue, 29 Dec 2009 18:11:10 -0500
From: Robert Moskowitz <rgm@htt-consult.com>
User-Agent: Thunderbird 2.0.0.22 (X11/20090625)
MIME-Version: 1.0
To: "Laganier, Julien" <julienl@qualcomm.com>
References: <4B30DF8A.5060201@htt-consult.com> <4B38D75F.7050802@hiit.fi> <BF345F63074F8040B58C00A186FCA57F1C675844F0@NALASEXMB04.na.qualcomm.com>
In-Reply-To: <BF345F63074F8040B58C00A186FCA57F1C675844F0@NALASEXMB04.na.qualcomm.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: HIP <hipsec@ietf.org>
Subject: Re: [Hipsec] The Host Identity Hash
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, 29 Dec 2009 23:08:59 -0000

Laganier, Julien wrote:
> Miika Komu wrote:
>   
>> Robert Moskowitz wrote:
>>
>> Hi,
>>
>>     
>>> A **NEW** acronym for HIP:
>>>
>>> HIH ::=  Host Identity Hash
>>>
>>> This is the Hash used to produce the HIT from the HI, via the ORCHID
>>> algorithm.
>>>
>>> This definition will be added to 4423-bis and anyone with a better
>>> acronym is welcome to speak up.
>>>       
>> what about some more intuitive term such as HIP fingerprint? It doesn't
>> have to be an acronym.
>>     
>
> The HIP fingerprint would be the output of the hash, i.e. the HIT, not the hash used to produce it.

Thanks, Julien.

I was trying to figure out why "HIP fingerprint" did not roll around 
right in my mind.