[Hash] UMAC and HMAC

"Jim Schaad" <jimsch@nwlink.com> Tue, 21 June 2005 13:06 UTC

Received: from localhost.localdomain ([] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DkiSS-00033d-3v; Tue, 21 Jun 2005 09:06:28 -0400
Received: from odin.ietf.org ([] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dkcyx-0001HR-OI for hash@megatron.ietf.org; Tue, 21 Jun 2005 03:15:39 -0400
Received: from ietf-mx.ietf.org (ietf-mx []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA18678 for <hash@ietf.org>; Tue, 21 Jun 2005 03:15:37 -0400 (EDT)
Received: from smtp1.pacifier.net ([]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DkdMj-0003oO-0N for hash@ietf.org; Tue, 21 Jun 2005 03:40:19 -0400
Received: from romans (unknown []) by smtp1.pacifier.net (Postfix) with ESMTP id 4129874AF2 for <hash@ietf.org>; Tue, 21 Jun 2005 00:15:19 -0700 (PDT)
From: "Jim Schaad" <jimsch@nwlink.com>
To: <hash@ietf.org>
Date: Tue, 21 Jun 2005 00:17:12 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
Thread-Index: AcV2MT4RXrcRkWIRTNaRep6KLvNYDw==
Message-Id: <20050621071519.4129874AF2@smtp1.pacifier.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Tue, 21 Jun 2005 09:06:27 -0400
Subject: [Hash] UMAC and HMAC
X-BeenThere: hash@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: jimsch@exmsft.com
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

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?


Hash mailing list