[OPSEC] IRTF CFRG & analysis of cryptographic considerations
RJ Atkinson <rja@extremenetworks.com> Tue, 06 January 2009 13:48 UTC
Return-Path: <opsec-bounces@ietf.org>
X-Original-To: opsec-archive@optimus.ietf.org
Delivered-To: ietfarch-opsec-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 244103A6A32; Tue, 6 Jan 2009 05:48:05 -0800 (PST)
X-Original-To: opsec@core3.amsl.com
Delivered-To: opsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BDAD43A6975 for <opsec@core3.amsl.com>; Tue, 6 Jan 2009 05:48:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.157
X-Spam-Level:
X-Spam-Status: No, score=-2.157 tagged_above=-999 required=5 tests=[AWL=-0.357, BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 4ZIp7HzK3MN5 for <opsec@core3.amsl.com>; Tue, 6 Jan 2009 05:48:03 -0800 (PST)
Received: from vms173003pub.verizon.net (vms173003pub.verizon.net [206.46.173.3]) by core3.amsl.com (Postfix) with ESMTP id 1907B3A6768 for <opsec@ietf.org>; Tue, 6 Jan 2009 05:48:03 -0800 (PST)
Received: from [10.30.20.71] ([70.104.193.39]) by vms173003.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0KD1007W7YBE8VU7@vms173003.mailsrvcs.net> for opsec@ietf.org; Tue, 06 Jan 2009 07:47:43 -0600 (CST)
Date: Tue, 06 Jan 2009 08:47:38 -0500
From: RJ Atkinson <rja@extremenetworks.com>
To: opsec@ietf.org
Message-id: <970C8DD8-0979-4721-B3D2-78FD2FC2D543@extremenetworks.com>
MIME-version: 1.0 (Apple Message framework v930.3)
X-Mailer: Apple Mail (2.930.3)
Subject: [OPSEC] IRTF CFRG & analysis of cryptographic considerations
X-BeenThere: opsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: opsec wg mailing list <opsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsec>, <mailto:opsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/opsec>
List-Post: <mailto:opsec@ietf.org>
List-Help: <mailto:opsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsec>, <mailto:opsec-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: opsec-bounces@ietf.org
Errors-To: opsec-bounces@ietf.org
Hi, It turns out that a number of other IETF WGs have been facing the same issues about cryptographic recommendations that arose here. As of yesterday, it seems that a set of folks will be analysing the cryptographic considerations, including the most recent published literature, and putting together a document summarising the current state of things. David McGrew, co-chair of the IRTF CFRG, is organising this, and will be one of the reviewers for this document. So my suggestion is that the OPsec WG defer questions of cryptographic recommendations for now, waiting until the document sponsored by the IRTF CFRG can be put together and reviewed by the CFRG folks. Cheers, Ran rja@extremenetworks.com REFERENCES: Selected IETF Security Area list notes on this topic: <http://www.ietf.org/mail-archive/web/saag/current/msg02373.html> <http://www.ietf.org/mail-archive/web/saag/current/msg02382.html> <http://www.ietf.org/mail-archive/web/saag/current/msg02430.html> <http://www.ietf.org/mail-archive/web/saag/current/msg02431.html> <http://www.ietf.org/mail-archive/web/saag/current/msg02435.html> <http://www.ietf.org/mail-archive/web/saag/current/msg02436.html> IRTF CFRG: http://www.irtf.org/charter?gtype=rg&group=cfrg _______________________________________________ OPSEC mailing list OPSEC@ietf.org https://www.ietf.org/mailman/listinfo/opsec