Common Interface to Cryptographic Modules (CICM) Channel Management
draft-lanz-cicm-cm-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Daniel Lanz , Lev Novikov | ||
| Last updated | 2011-07-25 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
[RFC Editor: Please update the RFC references prior to publication.] This memo defines a programming interface for the management of cryptographic channels as outlined in draft-lanz-cicm-lm-00 and required by draft-lanz-cicm-02 including creating and negotiating channels for encryption, decryption, bypass, data integrity, or to generate random data. Comments are solicited and should be addressed to the mailing list at cicm@ietf.org.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)