[Hipsec] What is in a name -- HMAC HIP Parameter

Robert Moskowitz <rgm@htt-consult.com> Mon, 26 April 2010 14:32 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 24F0B28C1C7 for <hipsec@core3.amsl.com>; Mon, 26 Apr 2010 07:32:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.784
X-Spam-Level:
X-Spam-Status: No, score=-0.784 tagged_above=-999 required=5 tests=[AWL=-0.785, 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 RUEZAPQeDqie for <hipsec@core3.amsl.com>; Mon, 26 Apr 2010 07:32:31 -0700 (PDT)
Received: from klovia.htt-consult.com (klovia.htt-consult.com [208.83.67.149]) by core3.amsl.com (Postfix) with ESMTP id 97F2E28C1CD for <hipsec@ietf.org>; Mon, 26 Apr 2010 07:21:06 -0700 (PDT)
Received: from localhost (unknown [127.0.0.1]) by klovia.htt-consult.com (Postfix) with ESMTP id 76A7768B28 for <hipsec@ietf.org>; Mon, 26 Apr 2010 14:14:08 +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 piq5Nj5+BuJF for <hipsec@ietf.org>; Mon, 26 Apr 2010 10:13:59 -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 61BB168A87 for <hipsec@ietf.org>; Mon, 26 Apr 2010 10:13:59 -0400 (EDT)
Message-ID: <4BD5A108.1070407@htt-consult.com>
Date: Mon, 26 Apr 2010 10:19:52 -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: "hipsec@ietf.org" <hipsec@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: [Hipsec] What is in a name -- HMAC HIP Parameter
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, 26 Apr 2010 14:32:32 -0000

I do not like naming this parameter HMAC and HMAC2:

Eventhough according to draft-irtf-cfrg-kdf-uses-00.txt, we can only use 
HMAC (D-H derived key is NOT uniformly distributed), There may be a 
future hkdf that is NOT HMAC that is secure to use with a D-H derived 
key, or a different key derivation method is used.

This parameter is really the MAC operation of SIGMA compliance, which is 
currently achieved via HMAC.

So I offer two possible alternative parameter names:

HIP_MAC and HIP_MAC2

or

HIP_MIC and HIP_MIC2

The alternative 'MIC' TLA stands for Message Integrity Check.  This 
comes out of the IEEE 802 community that already had a MAC and needed a 
different TLA.

Hum 1)

Change HMAC to HIP-MxC

Hum 2)

x :== A  or  x:== I