Re: [SECMECH] Draft EMU working group charter

"T. Charles Clancy" <clancy@cs.umd.edu> Wed, 14 December 2005 14:52 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EmXzM-0003WA-GI; Wed, 14 Dec 2005 09:52:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EmXzK-0003Ty-Lh for secmech@megatron.ietf.org; Wed, 14 Dec 2005 09:52:14 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05548 for <secmech@ietf.org>; Wed, 14 Dec 2005 09:51:12 -0500 (EST)
Received: from flyer.cs.umd.edu ([128.8.128.178]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EmY0S-0001eZ-Dl for secmech@ietf.org; Wed, 14 Dec 2005 09:53:25 -0500
Received: from ismene (ismene.cs.umd.edu [128.8.126.62]) by flyer.cs.umd.edu (8.12.11/8.12.5) with ESMTP id jBEEpura028910; Wed, 14 Dec 2005 09:51:56 -0500
Date: Wed, 14 Dec 2005 09:50:29 -0500 (EST)
From: "T. Charles Clancy" <clancy@cs.umd.edu>
X-X-Sender: clancy@ismene
To: "Salowey, Joe" <jsalowey@cisco.com>
Subject: Re: [SECMECH] Draft EMU working group charter
In-Reply-To: <7210B31550AC934A8637D6619739CE69065487A5@e2k-sea-xch2.sea-alpha.cisco.com>
Message-ID: <Pine.GSO.4.60.0512140949210.12716@ismene>
References: <7210B31550AC934A8637D6619739CE69065487A5@e2k-sea-xch2.sea-alpha.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Cc: secmech@ietf.org
X-BeenThere: secmech@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Security mechanisms BOF <secmech.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/secmech>, <mailto:secmech-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/secmech>
List-Post: <mailto:secmech@lists.ietf.org>
List-Help: <mailto:secmech-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/secmech>, <mailto:secmech-request@lists.ietf.org?subject=subscribe>
Sender: secmech-bounces@lists.ietf.org
Errors-To: secmech-bounces@lists.ietf.org

> February 2006 - form design team to work on strong shared secret
> mechanism
> ...
> August 2006 - Submit strong shared secret mechanisms to the IESG

Does this imply creating a new mechanism, using an existing one, or 
starting with an existing one and modifying it?

[ t. charles clancy ]--[ tcc@umd.edu ]--[ www.cs.umd.edu/~clancy ]
[ computer science ]-----[ university of maryland | college park ]

_______________________________________________
SECMECH mailing list
SECMECH@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/secmech