
From lnovikov@mitre.org  Mon Feb 20 05:43:23 2012
Return-Path: <lnovikov@mitre.org>
X-Original-To: cicm@ietfa.amsl.com
Delivered-To: cicm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AD3421F873B; Mon, 20 Feb 2012 05:43:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.74
X-Spam-Level: 
X-Spam-Status: No, score=-4.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XY5zIRvFmJQh; Mon, 20 Feb 2012 05:43:19 -0800 (PST)
Received: from smtpksrv1.mitre.org (smtpksrv1.mitre.org [198.49.146.77]) by ietfa.amsl.com (Postfix) with ESMTP id 9037221F84FA; Mon, 20 Feb 2012 05:43:19 -0800 (PST)
Received: from smtpksrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id D398C21B0198; Mon, 20 Feb 2012 08:43:18 -0500 (EST)
Received: from IMCCAS02.MITRE.ORG (imccas02.mitre.org [129.83.29.79]) by smtpksrv1.mitre.org (Postfix) with ESMTP id AAA4521B075B; Mon, 20 Feb 2012 08:43:18 -0500 (EST)
Received: from IMCMBX04.MITRE.ORG ([169.254.4.153]) by IMCCAS02.MITRE.ORG ([129.83.29.79]) with mapi id 14.01.0339.001; Mon, 20 Feb 2012 08:43:18 -0500
From: "Novikov, Lev" <lnovikov@mitre.org>
To: "cicm@ietf.org" <cicm@ietf.org>, "saag@ietf.org" <saag@ietf.org>
Thread-Topic: Taking over High Assurance Crypto Mailing List
Thread-Index: Aczv1Zd5TMnoDlqjRS+Pooqob3LoEg==
Date: Mon, 20 Feb 2012 13:43:17 +0000
Message-ID: <09861FAE910C7E439C2A0B00901895A3181D5187@IMCMBX04.MITRE.ORG>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [129.83.31.51]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [cicm] Taking over High Assurance Crypto Mailing List
X-BeenThere: cicm@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: CICM Discussion List <cicm@ietf.org>
List-Id: CICM Discussion List <cicm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cicm>, <mailto:cicm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/cicm>
List-Post: <mailto:cicm@ietf.org>
List-Help: <mailto:cicm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cicm>, <mailto:cicm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Feb 2012 13:43:23 -0000

For the past few years, I've been managing the Common Interface to Cryptogr=
aphic
Modules (CICM) mailing list (cicm@ietf.org) and the associated drafts=20
(draft-lanz-cicm-*; see: <https://datatracker.ietf.org/doc/draft-lanz-cicm/=
>)

Unfortunately, late last fiscal year funding for CICM was cut (although rum=
ors
of its return persist) making it difficult for me to contribute in any way.

However, instead of declaring this effort dead (or indefinitely offline), I=
 want
to know if anyone is interested in taking over the management of the list a=
nd
moving the spec forward.

The use cases would need to be finalized and the spec would have to be rebu=
ilt
according to those use cases, although a substantial part could be moved ov=
er
from the five existing drafts. The result would be an API that is flexible =
enough
to handle existing commercial applications, but robust enough to handle exi=
sting
scenarios with security domain separation for which PKCS#11-like APIs are=20
inadequate due to differences in logical model.

Contact me privately to discuss a transition of leadership.

Thanks,
Lev
