[cicm] Support for a Common Interface for Cryptographic Modules

"Ridge, Mike" <mridge@mitre.org> Mon, 25 July 2011 11:54 UTC

Return-Path: <mridge@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 E52D421F8BE7 for <cicm@ietfa.amsl.com>; Mon, 25 Jul 2011 04:54:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QVIewzfYnkBm for <cicm@ietfa.amsl.com>; Mon, 25 Jul 2011 04:54:54 -0700 (PDT)
Received: from smtpksrv1.mitre.org (smtpksrv1.mitre.org [198.49.146.77]) by ietfa.amsl.com (Postfix) with ESMTP id AFE7821F8C69 for <cicm@ietf.org>; Mon, 25 Jul 2011 04:09:25 -0700 (PDT)
Received: from smtpksrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id F0B5C21B135F; Mon, 25 Jul 2011 07:09:24 -0400 (EDT)
Received: from imchub2.MITRE.ORG (imchub2.mitre.org [129.83.29.74]) by smtpksrv1.mitre.org (Postfix) with ESMTP id E435421B135E; Mon, 25 Jul 2011 07:09:24 -0400 (EDT)
Received: from IMCMBX2.MITRE.ORG ([129.83.29.205]) by imchub2.MITRE.ORG ([129.83.29.74]) with mapi; Mon, 25 Jul 2011 07:09:24 -0400
From: "Ridge, Mike" <mridge@mitre.org>
To: "'cicm@ietf.org'" <cicm@ietf.org>
Date: Mon, 25 Jul 2011 07:09:23 -0400
Thread-Topic: Support for a Common Interface for Cryptographic Modules
Thread-Index: AcxKu04oU6wdK/O1QHmkiCh7hzg/XQ==
Message-ID: <292B774B15DB61439D9CB2131BBFE227085B9AA92A@IMCMBX2.MITRE.ORG>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg="SHA1"; boundary="----=_NextPart_000_000C_01CC4A99.C84F8C90"
MIME-Version: 1.0
Cc: "fdavis@nsa.gov" <fdavis@nsa.gov>
Subject: [cicm] Support for a Common Interface for Cryptographic Modules
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, 25 Jul 2011 11:54:56 -0000

To the CICM Forum,

 

  I wanted to express my support for approval of the CICM standard. A common
standard for Crypto interfaces is a foundation for improvements in
interoperability and reductions in cost of cryptographic solutions. What is
helpful to me is a solution approvable for cryptographic interfaces to
include High Assurance cryptographic solutions. The fact that the interface
is acceptable for High Assurance solutions and implementable in products
with lower robustness is credit to the Engineers involved and the group at
large.

 

  In the mid 1990's the automotive world standardized on "On Board
Diagnostics II" (OBD II) interfaces for reading fault indicators from
automobiles. This then allowed standardized diagnostics between
manufacturers, significantly reducing costs at repair shops and improving
equipment available. Today every automobile sold in the world has an OBD-II
interface - from the $4000 Tata Nano to the $400,000 Rolls Royce Phantom
(not that I take my Rolls just anywhere..). My point being that CICM could
likely be applied across the spectrum of crypto solutions just like OBD II
has become the standard for automobiles.

 

Mike Ridge