RE: [SECMECH] Draft EMU working group charter

"Salowey, Joe" <jsalowey@cisco.com> Wed, 14 December 2005 22: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 1EmfUQ-0001dt-1C; Wed, 14 Dec 2005 17:52:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EmfUO-0001cw-DX for secmech@megatron.ietf.org; Wed, 14 Dec 2005 17:52:48 -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 RAA09484 for <secmech@ietf.org>; Wed, 14 Dec 2005 17:51:41 -0500 (EST)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EmfVW-00050p-Si for secmech@ietf.org; Wed, 14 Dec 2005 17:54:00 -0500
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-3.cisco.com with ESMTP; 14 Dec 2005 14:52:24 -0800
X-IronPort-AV: i="3.99,253,1131350400"; d="scan'208"; a="378375369:sNHT809222322"
Received: from E2K-SEA-XCH2.sea-alpha.cisco.com (e2k-sea-xch2.cisco.com [10.93.132.68]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id jBEMqOQg024103; Wed, 14 Dec 2005 14:52:24 -0800 (PST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [SECMECH] Draft EMU working group charter
Date: Wed, 14 Dec 2005 14:58:25 -0800
Message-ID: <7210B31550AC934A8637D6619739CE69065DA23A@e2k-sea-xch2.sea-alpha.cisco.com>
Thread-Topic: [SECMECH] Draft EMU working group charter
Thread-Index: AcYAvtPid9hF1LRgQmS2uyb904ZfsAAQd1zg
From: "Salowey, Joe" <jsalowey@cisco.com>
To: "T. Charles Clancy" <clancy@cs.umd.edu>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: quoted-printable
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

 

> -----Original Message-----
> From: T. Charles Clancy [mailto:clancy@cs.umd.edu] 
> Sent: Wednesday, December 14, 2005 6:50 AM
> To: Salowey, Joe
> Cc: secmech@ietf.org
> Subject: Re: [SECMECH] Draft EMU working group charter
> 
> > 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?

[Joe] This would depend upon the output of the design team and what the
working group reaches consensus on.  The design team should work from
the existing literature (including drafts in this area) and not try to
invent something completely new.  The design team should work towards a
minimal implementation with a self contained set of functionality. It
could be possible to allow future extensions to meet additional
requirements if necessary.  My instincts and past experience tell me
that none of the current proposals would make it through the process
intact, but several of them would make acceptable starting points. 

> [ 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