Re: [cicm] Key Fill (was: Proposed WG Charter)

"Krishnamurthy, Hema - ES" <Hema.Krishnamurthy@itt.com> Fri, 15 July 2011 17:44 UTC

Return-Path: <prvs=1701294f7=Hema.Krishnamurthy@itt.com>
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 0C67F21F8BC8 for <cicm@ietfa.amsl.com>; Fri, 15 Jul 2011 10:44:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 vENICyKhG2oQ for <cicm@ietfa.amsl.com>; Fri, 15 Jul 2011 10:44:23 -0700 (PDT)
Received: from cip-fwa-c1.itt.com (cip-fwa-c1.itt.com [151.190.252.21]) by ietfa.amsl.com (Postfix) with ESMTP id 63C0921F8B94 for <cicm@ietf.org>; Fri, 15 Jul 2011 10:44:23 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AuQAAIl7IE4KHOwD/2dsb2JhbABUmCmQN8sshVtfBIclkEuLZQ
X-IronPort-AV: E=Sophos;i="4.67,209,1309737600"; d="scan'208";a="114198967"
Received: from usfwa1excas3.itt.net ([10.28.236.3]) by cip-fwa-c1.itt.com with ESMTP/TLS/AES128-SHA; 15 Jul 2011 17:44:23 +0000
Received: from USFWA1EXCAS5.itt.net (10.28.236.33) by USFWA1EXCAS3.itt.net (10.28.236.3) with Microsoft SMTP Server (TLS) id 8.2.255.0; Fri, 15 Jul 2011 13:44:22 -0400
Received: from CSFWCAS1.cs.de.ittind.com (10.32.129.151) by USFWA1EXCAS5.itt.net (10.28.236.33) with Microsoft SMTP Server (TLS) id 8.2.176.0; Fri, 15 Jul 2011 13:44:22 -0400
Received: from CSFWMAIL1.cs.de.ittind.com ([10.32.129.153]) by CSFWCAS1.cs.de.ittind.com ([10.32.129.151]) with mapi; Fri, 15 Jul 2011 13:44:22 -0400
From: "Krishnamurthy, Hema - ES" <Hema.Krishnamurthy@itt.com>
To: CICM Discussion List <cicm@ietf.org>
Date: Fri, 15 Jul 2011 13:44:20 -0400
Thread-Topic: [cicm] Key Fill (was: Proposed WG Charter)
Thread-Index: AcxDFnlslg89u/BhTjG5oDbDS24wvAAAEdxA
Message-ID: <86150541B533894DAD5CB2DB3F4788520E2AC58080@CSFWMAIL1.cs.de.ittind.com>
References: <F9AB58FA72BAE7449E7723791F6993ED062D0E5320@IMCMBX3.MITRE.ORG> <CAOPE6Pgbsr7Q3o_RL95XxQdVPSy4f8nj_j0j2g9auBROS7ZNbg@mail.gmail.com>
In-Reply-To: <CAOPE6Pgbsr7Q3o_RL95XxQdVPSy4f8nj_j0j2g9auBROS7ZNbg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [cicm] Key Fill (was: Proposed WG Charter)
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: Fri, 15 Jul 2011 17:44:24 -0000

Maybe just say " add module events for symmetric and asymmetric key fill"

'Key Fill' is a common terminology.


-----Original Message-----
From: cicm-bounces@ietf.org [mailto:cicm-bounces@ietf.org] On Behalf Of Kevin W. Wall
Sent: Friday, July 15, 2011 10:42 AM
To: CICM Discussion List
Subject: Re: [cicm] Key Fill (was: Proposed WG Charter)

Lev,

You mean like an HSM, as an example of a key filled device?

Seems like it should say something like "Key filled device" or
"key filled interface" or "key filled action" or "key filled protocol" or
_something_ then. The way it's worded is a bit odd as far as the
English grammar goes.

To me, that bullet reads as though some word is missing at the
end. Even with your explanation (which now makes it makes it sense)
it still reads very awkward to me.

-kevin

On Fri, Jul 15, 2011 at 9:51 AM, Novikov, Lev <lnovikov@mitre.org> wrote:
> On 2011-07-15 08:14, Kevin Wall wrote:
>>...[snip]...
>>>
>>>  * add module events for symmetric and asymmetric key filled
>>
>>               ^^^^^
>>
>>Is that supposed to be 'key field' ??? Because I don't get
>>"key filled".
>
> From: http://tools.ietf.org/html/draft-lanz-cicm-lm-00
>
>   $ key fill device
>
>      Devices that read-in, transfer, and store key material.
>
>   $ key fill interface
>
>      Set of protocols, electrical connections, and physical
>      characteristics that comprise the connecting link between a key
>      fill device and a cryptographic module.  CICM enables a key fill
>      interface to be configured and actions to be initiated on a key
>      fill device via the key fill interface.
>
> See Also:
> http://tools.ietf.org/html/draft-lanz-cicm-km-00 (search for "key fill")
>
> Lev
> _______________________________________________
> cicm mailing list
> cicm@ietf.org
> https://www.ietf.org/mailman/listinfo/cicm
>



--
Blog: http://off-the-wall-security.blogspot.com/
"The most likely way for the world to be destroyed, most experts agree,
is by accident. That's where we come in; we're computer professionals.
We *cause* accidents."        -- Nathaniel Borenstein
_______________________________________________
cicm mailing list
cicm@ietf.org
https://www.ietf.org/mailman/listinfo/cicm

This e-mail and any files transmitted with it may be proprietary and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in error please notify the sender.
Please note that any views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of ITT Corporation. The recipient should check this e-mail and any attachments for the presence of viruses. ITT accepts no liability for any damage caused by any virus transmitted by this e-mail.