Re: [cicm] Proposed WG Charter

["Novikov, Lev" <[e-mail]>]

A few weeks ago, there were some tweaks to the charter language from "shepherd" to "propose" that were not finished.

Below is an updated text (changes are in the second paragraph).

Thanks,
Lev

From: http://code.google.com/p/ietf-cicm/wiki/WGCharter

The Common Interface to Cryptographic Modules (CICM) defines an abstract
API for the security services provided by cryptographic modules 
developed by multiple vendors. The API is intended to support high 
assurance cryptography, security domain separation, and enhanced module,
key, and channel management capabilities that are vendor neutral.

The purpose of the CICM Working Group is to publish an API for high 
assurance cryptographic devices and to 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
  * add unprotected-side APIs for:
    * moving data into / out of the module
    * performing administrative functions (e.g., supply IV, 
      header-bypass data)

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  introduce draft-lanz-cicm-lm to WG
TBD  introduce draft-lanz-cicm to WG
TBD  introduce draft-lanz-cicm-mm to WG
TBD  introduce draft-lanz-cicm-km to WG
TBD  Submit draft-lanz-cicm to the IESG as Proposed Standard