Re: [Hipsec] What is in a name -- HMAC HIP Parameter
Miika Komu <mkomu@cs.hut.fi> Mon, 26 April 2010 14:53 UTC
Return-Path: <mkomu@cs.hut.fi>
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 032C83A6CCD for <hipsec@core3.amsl.com>; Mon, 26 Apr 2010 07:53:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.67
X-Spam-Level:
X-Spam-Status: No, score=-5.67 tagged_above=-999 required=5 tests=[AWL=-0.929, BAYES_20=-0.74, 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 bEZu-mGuWTcC for <hipsec@core3.amsl.com>; Mon, 26 Apr 2010 07:52:59 -0700 (PDT)
Received: from hutcs.cs.hut.fi (hutcs.cs.hut.fi [130.233.192.7]) by core3.amsl.com (Postfix) with ESMTP id C132628C2D5 for <hipsec@ietf.org>; Mon, 26 Apr 2010 07:38:37 -0700 (PDT)
Received: from hutcs.cs.hut.fi ([130.233.192.7] helo=[127.0.0.1]) by hutcs.cs.hut.fi with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.54) id 1O6PS4-0007OO-B5 for hipsec@ietf.org; Mon, 26 Apr 2010 17:38:24 +0300
Message-ID: <4BD5A5B2.2060602@cs.hut.fi>
Date: Mon, 26 Apr 2010 17:39:46 +0300
From: Miika Komu <mkomu@cs.hut.fi>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.10pre) Gecko/20100416 Shredder/3.0.5pre
MIME-Version: 1.0
To: hipsec@ietf.org
References: <4BD5A108.1070407@htt-consult.com>
In-Reply-To: <4BD5A108.1070407@htt-consult.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [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:53:00 -0000
On 26/04/10 17:19, Robert Moskowitz wrote: Hi, I would hum for option 2 (with slight preference for "MAC"). > 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 > > > _______________________________________________ > Hipsec mailing list > Hipsec@ietf.org > https://www.ietf.org/mailman/listinfo/hipsec
- [Hipsec] What is in a name -- HMAC HIP Parameter Robert Moskowitz
- Re: [Hipsec] What is in a name -- HMAC HIP Parame… Miika Komu
- Re: [Hipsec] What is in a name -- HMAC HIP Parame… Tobias Heer