[Cfrg] New CFRG I-D: Fast MAC Requirements
Brian Weis <bew@cisco.com> Mon, 29 October 2007 20:11 UTC
Return-path: <cfrg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1ImaxZ-0003WY-Je; Mon, 29 Oct 2007 16:11:41 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1ImaxY-0003WT-RW for cfrg@ietf.org; Mon, 29 Oct 2007 16:11:40 -0400
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ImaxY-0003UQ-FO for cfrg@ietf.org; Mon, 29 Oct 2007 16:11:40 -0400
X-IronPort-AV: E=Sophos;i="4.21,344,1188802800"; d="scan'208";a="411367346"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-2.cisco.com with ESMTP; 29 Oct 2007 13:11:40 -0700
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l9TKBdHa027736 for <cfrg@ietf.org>; Mon, 29 Oct 2007 13:11:39 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l9TKBRUt012604 for <cfrg@ietf.org>; Mon, 29 Oct 2007 20:11:37 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 29 Oct 2007 13:11:23 -0700
Received: from [128.107.163.176] ([128.107.163.176]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 29 Oct 2007 13:11:23 -0700
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <7E92AA78-BE51-4D77-8399-14319B39AB45@cisco.com>
Content-Transfer-Encoding: 7bit
From: Brian Weis <bew@cisco.com>
Date: Mon, 29 Oct 2007 13:11:37 -0700
To: cfrg@ietf.org
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 29 Oct 2007 20:11:23.0150 (UTC) FILETIME=[E08F4AE0:01C81A67]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1107; t=1193688699; x=1194552699; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=bew@cisco.com; z=From:=20Brian=20Weis=20<bew@cisco.com> |Subject:=20New=20CFRG=20I-D=3A=20Fast=20MAC=20Requirements |Sender:=20; bh=j6WUhZu4mqfW8gWfaaItua9joN1bdW5Fh8VDTPImyy0=; b=MxGz28aqSul9aEiui4AcZqtkGFlWZVz3pW/VVc29MHuJdFqXDmIpZpgAAmpKpofE519tqarX PEAqSC7wdJOSZVHfmGw6/PcFH0yok4NaRg7G/0b1eOZWpfmjIj7o1JhB/yhtcMg8kwRxfike1i gyEC0quCA2dY45hR8jkFElknk=;
Authentication-Results: sj-dkim-1; header.From=bew@cisco.com; dkim=pass (sig from cisco.com/sjdkim1004 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: mcgrew@cisco.com
Subject: [Cfrg] New CFRG I-D: Fast MAC Requirements
X-BeenThere: cfrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:cfrg@ietf.org>
List-Help: <mailto:cfrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@ietf.org?subject=subscribe>
Errors-To: cfrg-bounces@ietf.org
Greetings, The new I-D http://www.ietf.org/internet-drafts/draft-irtf-cfrg-fast- mac-requirements-00.txt is available. It describes the need for a fast MAC (in software) and proposes a set of requirements for such a MAC. Although there are possibly many applications for a fast MAC, the particular one we have in mind is the replacement for the TCP MD5 Signature Option (being discussed in the transport area). Abstract: This memo outlines requirements guiding the development of a fast Message Authentication Code (MAC) algorithm suitable for use with many IETF protocols, but in particular routing protocols that use a MAC for packet authentication. It is widely conjectured that secure MACs that are fast in software are possible, and many interesting MACs have appeared in the literature. Nevertheless, none of these MACs have seen broad adoption, and none are a good match for the routing protocol case. We hope that this memo brings together MAC designers and MAC users for a fruitful discussion. Comments to the authors or CFRG list are invited. Brian & David _______________________________________________ Cfrg mailing list Cfrg@ietf.org https://www1.ietf.org/mailman/listinfo/cfrg