CICM is at a critical point. July 24 - 29, 2011 is IETF 81 in Quebec City, 
Canada, where I want to propose CICM as a Working Group (WG) so that we can 
publish CICM as an IETF Proposed Standard.

To do this, we must discuss our WG Charter (draft below) and get maximum 
participation at IETF 81 (in-person and/or on the Jabber rooms) to prove that 
there is a community of high assurance crypto module developers, vendors, and 
users who are interested in having a standard API.

Here's what needs to happen:
1. Read the charter below. The most recent version will be hosted at:
   http://code.google.com/p/ietf-cicm/wiki/WGCharter
   
2. By COB Friday, 2011-05-20, reply to this email with one of the following:
    (a) I would vote for this charter as-is.
    (b) I would vote for a similar charter with following changes: <specify>
    (c) I would not vote for this charter at all.

3. Once a BOF is scheduled for IETF 81, we will get our own Jabber chat room. 
As many people as possible should join that chat room on the scheduled date 
(to be announced) and vote to adopt the Charter we agree to on this list.

With a Working Group we will be able to move forward in the IETF and propose 
it as a Standard. Please help make this a reality.

Thank you,
Lev


Draft CICM Working Group Charter

= Description of Working Group =
The Common Interface to Cryptographic Modules (CICM) API provides high 
assurance crypto applications with a security framework that accommodates the 
needs of a high assurance environment including security domain separation, 
and enhanced module, key, and channel management capabilities.

The purpose of the CICM Working Group is to shepherd the CICM specification 
documents to publication and provide guidance for any new submissions related 
to high assurance cryptos.

Specifically, the Working Group will:

  * Complete existing requests:
    * replace algorithm strings with OIDs
    * use ABNF notation for unique identifiers syntax
    * add module events for symmetric and asymmetric key filled

  * Shepard the following documents to publication:
    * draft-lanz-cicm
    * draft-lanz-cicm-lm
    * draft-lanz-cicm-mm
    * draft-lanz-cicm-km
    * draft-lanz-cicm-cm

= Goals and Milestones =
TBD   WGLC on draft-lanz-cicm-lm
TBD   WGLC on draft-lanz-cicm
TBD   WGLC on draft-lanz-cicm-mm
TBD   WGLC on draft-lanz-cicm-km
TBD   Submit draft-lanz-cicm to the IESG as Proposed Standard
_______________________________________________
cicm mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/cicm

Reply via email to