Re: [Hash] UMAC and HMAC

Russ Housley <housley@vigilsec.com> Tue, 21 June 2005 13:17 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DkidE-0005Cj-7x; Tue, 21 Jun 2005 09:17:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DkidC-0005C6-Qb for hash@megatron.ietf.org; Tue, 21 Jun 2005 09:17:34 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16943 for <hash@ietf.org>; Tue, 21 Jun 2005 09:17:33 -0400 (EDT)
Received: from woodstock.binhost.com ([144.202.243.4]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1Dkj16-0004cD-Vn for hash@ietf.org; Tue, 21 Jun 2005 09:42:18 -0400
Received: (qmail 29898 invoked by uid 0); 21 Jun 2005 13:17:26 -0000
Received: from unknown (HELO Russ-Laptop.vigilsec.com) (138.88.91.211) by woodstock.binhost.com with SMTP; 21 Jun 2005 13:17:26 -0000
Message-Id: <6.2.1.2.2.20050621091559.04d12960@mail.binhost.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.1.2
Date: Tue, 21 Jun 2005 09:17:25 -0400
To: jimsch@exmsft.com
From: Russ Housley <housley@vigilsec.com>
Subject: Re: [Hash] UMAC and HMAC
In-Reply-To: <20050621071519.4129874AF2@smtp1.pacifier.net>
References: <20050621071519.4129874AF2@smtp1.pacifier.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: hash@ietf.org
X-BeenThere: hash@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: hash.lists.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hash>, <mailto:hash-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/hash>
List-Post: <mailto:hash@lists.ietf.org>
List-Help: <mailto:hash-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hash>, <mailto:hash-request@lists.ietf.org?subject=subscribe>
Sender: hash-bounces@lists.ietf.org
Errors-To: hash-bounces@lists.ietf.org

Jim:

These have very different requirements.  My preference is to focus on the 
one-way hash function for this charter.  If your intuition turns out to be 
correct, then the charter can be expanded.

Russ

At 03:17 AM 6/21/2005, Jim Schaad wrote:
>In the process of reviewing some other documents a question has occurred to
>me.  If we are looking at the different places where hash functions are used
>during phase 2 of the charter work, should we include a section in these
>documents deal with other methods of acheving these aims?  Thus should we,
>at least in a cursory fashion, deal with items such as HMAC and UMAC for
>message authentication problems?
>
>Jim


_______________________________________________
Hash mailing list
Hash@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/hash