
From lnovikov@mitre.org  Fri May 13 07:53:58 2011
Return-Path: <lnovikov@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 28040E0788 for <cicm@ietfa.amsl.com>; Fri, 13 May 2011 07:53:58 -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 VSbMdRYKcXnN for <cicm@ietfa.amsl.com>; Fri, 13 May 2011 07:53:57 -0700 (PDT)
Received: from smtpksrv1.mitre.org (smtpksrv1.mitre.org [198.49.146.77]) by ietfa.amsl.com (Postfix) with ESMTP id 96C99E0787 for <cicm@ietf.org>; Fri, 13 May 2011 07:53:57 -0700 (PDT)
Received: from smtpksrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id E9E4421B0754 for <cicm@ietf.org>; Fri, 13 May 2011 10:53:56 -0400 (EDT)
Received: from imchub1.MITRE.ORG (imchub1.mitre.org [129.83.29.73]) by smtpksrv1.mitre.org (Postfix) with ESMTP id E56B421B0013 for <cicm@ietf.org>; Fri, 13 May 2011 10:53:56 -0400 (EDT)
Received: from IMCMBX3.MITRE.ORG ([129.83.29.206]) by imchub1.MITRE.ORG ([129.83.29.73]) with mapi; Fri, 13 May 2011 10:53:57 -0400
From: "Novikov, Lev" <lnovikov@mitre.org>
To: "CICM Discussion List (cicm@ietf.org)" <cicm@ietf.org>
Date: Fri, 13 May 2011 10:52:28 -0400
Thread-Topic: Proposed WG Charter
Thread-Index: AcwRfV7zdlb/iMYcQcqUmsEHwaNhZg==
Message-ID: <F9AB58FA72BAE7449E7723791F6993ED05D2FB0AEA@IMCMBX3.MITRE.ORG>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [cicm] 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, 13 May 2011 14:53:58 -0000

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

To do this, we must discuss our WG Charter (draft below) and get maximum=20
participation at IETF 81 (in-person and/or on the Jabber rooms) to prove th=
at=20
there is a community of high assurance crypto module developers, vendors, a=
nd=20
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
  =20
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 roo=
m.=20
As many people as possible should join that chat room on the scheduled date=
=20
(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 propos=
e=20
it as a Standard. Please help make this a reality.

Thank you,
Lev


Draft CICM Working Group Charter

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

The purpose of the CICM Working Group is to shepherd the CICM specification=
=20
documents to publication and provide guidance for any new submissions relat=
ed=20
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

=3D Goals and Milestones =3D
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

From lnovikov@mitre.org  Fri May 13 10:02:15 2011
Return-Path: <lnovikov@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 B22D5E0824; Fri, 13 May 2011 10:02:15 -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 JC95GiulB2Gm; Fri, 13 May 2011 10:02:15 -0700 (PDT)
Received: from smtpksrv1.mitre.org (smtpksrv1.mitre.org [198.49.146.77]) by ietfa.amsl.com (Postfix) with ESMTP id 03BFCE068E; Fri, 13 May 2011 10:02:14 -0700 (PDT)
Received: from smtpksrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 543D121B1C6C; Fri, 13 May 2011 13:02:14 -0400 (EDT)
Received: from imchub1.MITRE.ORG (imchub1.mitre.org [129.83.29.73]) by smtpksrv1.mitre.org (Postfix) with ESMTP id 4B92121B0216; Fri, 13 May 2011 13:02:14 -0400 (EDT)
Received: from IMCMBX3.MITRE.ORG ([129.83.29.206]) by imchub1.MITRE.ORG ([129.83.29.73]) with mapi; Fri, 13 May 2011 13:02:14 -0400
From: "Novikov, Lev" <lnovikov@mitre.org>
To: "saag@ietf.org" <saag@ietf.org>
Date: Fri, 13 May 2011 13:01:05 -0400
Thread-Topic: BoF Request for CICM at IETF 81
Thread-Index: AcwRj1iyU3mEFP0FTbiX7uP3S3GSUQ==
Message-ID: <F9AB58FA72BAE7449E7723791F6993ED05D2FB0B91@IMCMBX3.MITRE.ORG>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "CICM Discussion List \(cicm@ietf.org\)" <cicm@ietf.org>
Subject: [cicm] BoF Request for CICM at IETF 81
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, 13 May 2011 17:02:15 -0000

I'm formally requesting a BoF at IETF 81 to form a CICM WG based on the dra=
ft charter below.
Updated version at: http://code.google.com/p/ietf-cicm/wiki/WGCharter
Discussion also at: cicm@ietf.org

Thanks,
Lev

Draft CICM Working Group Charter

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

The purpose of the CICM Working Group is to shepherd the CICM specification=
=20
documents to publication and provide guidance for any new submissions relat=
ed=20
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

=3D Goals and Milestones =3D
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

From JOHN.A.DAVIDSON@saic.com  Fri May 13 10:34:53 2011
Return-Path: <JOHN.A.DAVIDSON@saic.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 52A2FE071C for <cicm@ietfa.amsl.com>; Fri, 13 May 2011 10:34:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 o2j2QFJCUDKQ for <cicm@ietfa.amsl.com>; Fri, 13 May 2011 10:34:51 -0700 (PDT)
Received: from cpmx2.mail.saic.com (cpmx2.mail.saic.com [139.121.17.172]) by ietfa.amsl.com (Postfix) with ESMTP id 63C4EE070A for <cicm@ietf.org>; Fri, 13 May 2011 10:34:51 -0700 (PDT)
Received: from 0599-its-sbg02.saic.com ([139.121.20.253] [139.121.20.253]) by cpmx2.mail.saic.com with ESMTP id BT-MMP-10220838 for cicm@ietf.org; Fri, 13 May 2011 10:34:48 -0700
X-AuditID: 8b7911db-b7c5bae0000051d3-0e-4dcd6bb87b66
Received: from 0599-its-exbh01.us.saic.com (cpe-z7-si-srcnat.sw.saic.com [139.121.20.253]) by 0599-its-sbg02.saic.com (Symantec Brightmail Gateway) with SMTP id DE.06.20947.8BB6DCD4; Fri, 13 May 2011 10:34:48 -0700 (PDT)
Received: from 0461-its-exmb09.us.saic.com ([10.8.67.20]) by 0599-its-exbh01.us.saic.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 13 May 2011 10:34:48 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 13 May 2011 10:34:48 -0700
Message-Id: <7EDDD87A9A1D7F4DB6F78BC55AA495502B7748@0461-its-exmb09.us.saic.com>
In-Reply-To: <F9AB58FA72BAE7449E7723791F6993ED05D2FB0B91@IMCMBX3.MITRE.ORG>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [cicm] BoF Request for CICM at IETF 81
Thread-Index: AcwRj1iyU3mEFP0FTbiX7uP3S3GSUQAA2lGg
References: <F9AB58FA72BAE7449E7723791F6993ED05D2FB0B91@IMCMBX3.MITRE.ORG>
From: "Davidson, John A." <JOHN.A.DAVIDSON@saic.com>
To: "CICM Discussion List" <cicm@ietf.org>
X-OriginalArrivalTime: 13 May 2011 17:34:48.0737 (UTC) FILETIME=[0EC2A110:01CC1194]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [cicm] BoF Request for CICM at IETF 81
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, 13 May 2011 17:34:53 -0000

Lev,=20
I am wondering if we need to (or even can) clarify what we mean by High
Assurance.  Assurance levels were fairly well-defined under the Orange
Book but that has been grayed out by the move to international flavored
Common Criteria.  Today when we say we are addressing HA, it is no
longer clear to me whether we mean to restrict our view to approaches
that are logically "closed form," or if we mean just a better version of
"best effort," whatever that is. =20

In my mind, there are IA critical capabilities we can support with one
that may be ruled out by the other. =20

Thanks,=20
John


-----Original Message-----
From: cicm-bounces@ietf.org [mailto:cicm-bounces@ietf.org] On Behalf Of
Novikov, Lev
Sent: Friday, May 13, 2011 10:01 AM
To: saag@ietf.org
Cc: CICM Discussion List (cicm@ietf.org)
Subject: [cicm] BoF Request for CICM at IETF 81

I'm formally requesting a BoF at IETF 81 to form a CICM WG based on the
draft charter below.
Updated version at: http://code.google.com/p/ietf-cicm/wiki/WGCharter
Discussion also at: cicm@ietf.org

Thanks,
Lev

Draft CICM Working Group Charter

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

The purpose of the CICM Working Group is to shepherd the CICM
specification=20
documents to publication and provide guidance for any new submissions
related=20
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

=3D Goals and Milestones =3D
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
cicm@ietf.org
https://www.ietf.org/mailman/listinfo/cicm

From jfitton@harris.com  Fri May 13 14:56:09 2011
Return-Path: <jfitton@harris.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 80481E08BD for <cicm@ietfa.amsl.com>; Fri, 13 May 2011 14:56:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 JE0hXveTezlI for <cicm@ietfa.amsl.com>; Fri, 13 May 2011 14:56:08 -0700 (PDT)
Received: from mlbe2k2.cs.myharris.net (mlbe2k2.cs.myharris.net [137.237.90.89]) by ietfa.amsl.com (Postfix) with ESMTP id AD091E08BB for <cicm@ietf.org>; Fri, 13 May 2011 14:56:08 -0700 (PDT)
Received: from mail pickup service by mlbe2k2.cs.myharris.net with Microsoft SMTPSVC; Fri, 13 May 2011 17:56:06 -0400
Received: from mlbrst2.cs.myharris.net ([137.237.89.11]) by mlbe2k2.cs.myharris.net with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 13 May 2011 17:56:04 -0400
Received: from MLBMXHTUS1.cs.myharris.net ([137.237.89.77]) by mlbrst2.cs.myharris.net with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 13 May 2011 17:56:04 -0400
Received: from ROCMXCAHT22.cs.myharris.net (10.64.228.25) by MLBMXHTUS1.cs.myharris.net (137.237.89.77) with Microsoft SMTP Server (TLS) id 8.2.254.0; Fri, 13 May 2011 17:56:04 -0400
Received: from ROCMXUS21.cs.myharris.net ([fe80::1161:8dee:2d75:5ac]) by ROCMXCAHT22.cs.myharris.net ([::1]) with mapi id 14.01.0270.001; Fri, 13 May 2011 17:56:03 -0400
From: "Fitton, John" <jfitton@harris.com>
To: CICM Discussion List <cicm@ietf.org>
Thread-Topic: [cicm] BoF Request for CICM at IETF 81
Thread-Index: AQHMEaBeRtnlEkJu4EOsE4KXi9EFaZSLSjgd
Date: Fri, 13 May 2011 21:56:02 +0000
Message-ID: <06D46EAFF7D0C946BEC108DB7CCDC9A608B282C8@ROCMXUS21.cs.myharris.net>
References: <F9AB58FA72BAE7449E7723791F6993ED05D2FB0B91@IMCMBX3.MITRE.ORG>, <7EDDD87A9A1D7F4DB6F78BC55AA495502B7748@0461-its-exmb09.us.saic.com>
In-Reply-To: <7EDDD87A9A1D7F4DB6F78BC55AA495502B7748@0461-its-exmb09.us.saic.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.64.228.54]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 13 May 2011 21:56:04.0713 (UTC) FILETIME=[8E5EBD90:01CC11B8]
Subject: Re: [cicm] BoF Request for CICM at IETF 81
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, 13 May 2011 21:56:09 -0000

I would suggest defining High Assurance in terms of  FIPS-140-2 Level 4. Of=
 course FIPS 140-2 refers to the Common Criteria AL4 or higher, but does of=
fer specific criteria to be used in the evaluation. That being said, howeve=
r, while the stated goal is for a high assurance API, there is nothing in p=
rincipal which limits the API to high assurance applications.=20

I would also point out that the Orange Book (as was the entire original Rai=
nbow series) was targeted at information processing systems. These systems =
were essentially large data bases with many users gaining access via dedica=
ted terminals, and there are those who would argue that the old  assurance =
levels, were also not that well defined. As these system evolved and  inter=
net access was introdouced there was additional volumes created to address =
some of the security issues involved.=20

I would argue that nothing in the Rainbow series specifically addressed sec=
urity requirements or assurance levels for cryptographic modules.=20

One advantage of the Common Criteria, is that the meaning of any given Assu=
rance Level for a given application (e.g. a Cryptographic module) can be de=
fined through an evaluation profile. Another advantage is that it is an int=
ernationally recognized set of criteria with a group of international evalu=
ation/certification bodies.=20

________________________________________
From: Davidson, John A. [JOHN.A.DAVIDSON@saic.com]
Sent: Friday, May 13, 2011 1:34 PM
To: CICM Discussion List
Subject: Re: [cicm] BoF Request for CICM at IETF 81

Lev,
I am wondering if we need to (or even can) clarify what we mean by High
Assurance.  Assurance levels were fairly well-defined under the Orange
Book but that has been grayed out by the move to international flavored
Common Criteria.  Today when we say we are addressing HA, it is no
longer clear to me whether we mean to restrict our view to approaches
that are logically "closed form," or if we mean just a better version of
"best effort," whatever that is.

In my mind, there are IA critical capabilities we can support with one
that may be ruled out by the other.

Thanks,
John


-----Original Message-----
From: cicm-bounces@ietf.org [mailto:cicm-bounces@ietf.org] On Behalf Of
Novikov, Lev
Sent: Friday, May 13, 2011 10:01 AM
To: saag@ietf.org
Cc: CICM Discussion List (cicm@ietf.org)
Subject: [cicm] BoF Request for CICM at IETF 81

I'm formally requesting a BoF at IETF 81 to form a CICM WG based on the
draft charter below.
Updated version at: http://code.google.com/p/ietf-cicm/wiki/WGCharter
Discussion also at: cicm@ietf.org

Thanks,
Lev

Draft CICM Working Group Charter

=3D Description of Working Group =3D
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

=3D Goals and Milestones =3D
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
cicm@ietf.org
https://www.ietf.org/mailman/listinfo/cicm=

From dennis.bourget@viasat.com  Fri May 13 15:13:09 2011
Return-Path: <dennis.bourget@viasat.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 23712E0870 for <cicm@ietfa.amsl.com>; Fri, 13 May 2011 15:13:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 gZMHyum52pOP for <cicm@ietfa.amsl.com>; Fri, 13 May 2011 15:13:08 -0700 (PDT)
Received: from viasat.com (bateleur.viasat.com [199.106.52.160]) by ietfa.amsl.com (Postfix) with ESMTP id 10ED1E0785 for <cicm@ietf.org>; Fri, 13 May 2011 15:13:07 -0700 (PDT)
Received: from ([172.20.1.71]) by bateleur.viasat.com with ESMTP  id H6GMFJ1.44252456; Fri, 13 May 2011 15:13:05 -0700
Received: from vcaexch06.hq.corp.viasat.com ([172.18.46.74]) by VCAEXCH02.hq.corp.viasat.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 13 May 2011 15:13:05 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 13 May 2011 15:12:15 -0700
Message-ID: <9742CF2025F5FD41AAF6D9B8679F806201EF4EDE@vcaexch06.hq.corp.viasat.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
thread-topic: [cicm] BoF Request for CICM at IETF 81
thread-index: AQHMEaBeRtnlEkJu4EOsE4KXi9EFaZSLSjgdgAAErFA=
References: <F9AB58FA72BAE7449E7723791F6993ED05D2FB0B91@IMCMBX3.MITRE.ORG>, <7EDDD87A9A1D7F4DB6F78BC55AA495502B7748@0461-its-exmb09.us.saic.com> <06D46EAFF7D0C946BEC108DB7CCDC9A608B282C8@ROCMXUS21.cs.myharris.net>
From: "Bourget, Dennis" <dennis.bourget@viasat.com>
To: "CICM Discussion List" <cicm@ietf.org>
X-OriginalArrivalTime: 13 May 2011 22:13:05.0464 (UTC) FILETIME=[EEC8FB80:01CC11BA]
Subject: Re: [cicm] BoF Request for CICM at IETF 81
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, 13 May 2011 22:13:09 -0000

I just don't see how any API can provide "high assurance", it is the
implementation of the API, host platform and operating system that would
need to be evaluated to FIPS 140-2 or Common Criteria.  For example, the
API does not and cannot provide domain separation, I suggest that we
strike that text from the charter.

Perhaps the following:

The Common Interface to Cryptographic Modules (CICM) API defines a
"standardized" application interface
for the security services provided by cryptographic modules developed by
multiple vendors. The API supports=20
security domain separation, and enhanced module, key, and channel
management capabilities that is vendor agnostic.=20

-----Original Message-----
From: cicm-bounces@ietf.org [mailto:cicm-bounces@ietf.org] On Behalf Of
Fitton, John
Sent: Friday, May 13, 2011 2:56 PM
To: CICM Discussion List
Subject: Re: [cicm] BoF Request for CICM at IETF 81

I would suggest defining High Assurance in terms of  FIPS-140-2 Level 4.
Of course FIPS 140-2 refers to the Common Criteria AL4 or higher, but
does offer specific criteria to be used in the evaluation. That being
said, however, while the stated goal is for a high assurance API, there
is nothing in principal which limits the API to high assurance
applications.=20

I would also point out that the Orange Book (as was the entire original
Rainbow series) was targeted at information processing systems. These
systems were essentially large data bases with many users gaining access
via dedicated terminals, and there are those who would argue that the
old  assurance levels, were also not that well defined. As these system
evolved and  internet access was introdouced there was additional
volumes created to address some of the security issues involved.=20

I would argue that nothing in the Rainbow series specifically addressed
security requirements or assurance levels for cryptographic modules.=20

One advantage of the Common Criteria, is that the meaning of any given
Assurance Level for a given application (e.g. a Cryptographic module)
can be defined through an evaluation profile. Another advantage is that
it is an internationally recognized set of criteria with a group of
international evaluation/certification bodies.=20

________________________________________
From: Davidson, John A. [JOHN.A.DAVIDSON@saic.com]
Sent: Friday, May 13, 2011 1:34 PM
To: CICM Discussion List
Subject: Re: [cicm] BoF Request for CICM at IETF 81

Lev,
I am wondering if we need to (or even can) clarify what we mean by High
Assurance.  Assurance levels were fairly well-defined under the Orange
Book but that has been grayed out by the move to international flavored
Common Criteria.  Today when we say we are addressing HA, it is no
longer clear to me whether we mean to restrict our view to approaches
that are logically "closed form," or if we mean just a better version of
"best effort," whatever that is.

In my mind, there are IA critical capabilities we can support with one
that may be ruled out by the other.

Thanks,
John


-----Original Message-----
From: cicm-bounces@ietf.org [mailto:cicm-bounces@ietf.org] On Behalf Of
Novikov, Lev
Sent: Friday, May 13, 2011 10:01 AM
To: saag@ietf.org
Cc: CICM Discussion List (cicm@ietf.org)
Subject: [cicm] BoF Request for CICM at IETF 81

I'm formally requesting a BoF at IETF 81 to form a CICM WG based on the
draft charter below.
Updated version at: http://code.google.com/p/ietf-cicm/wiki/WGCharter
Discussion also at: cicm@ietf.org

Thanks,
Lev

Draft CICM Working Group Charter

=3D Description of Working Group =3D
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

=3D Goals and Milestones =3D
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
cicm@ietf.org
https://www.ietf.org/mailman/listinfo/cicm
_______________________________________________
cicm mailing list
cicm@ietf.org
https://www.ietf.org/mailman/listinfo/cicm

From prvs=11004d389=Hema.Krishnamurthy@itt.com  Mon May 16 07:05:40 2011
Return-Path: <prvs=11004d389=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 07B4EE06B1 for <cicm@ietfa.amsl.com>; Mon, 16 May 2011 07:05:40 -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 7AFUUclFSVmN for <cicm@ietfa.amsl.com>; Mon, 16 May 2011 07:05:39 -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 4E2BFE067E for <cicm@ietf.org>; Mon, 16 May 2011 07:05:38 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtYAAPsu0U0KHOwB/2dsb2JhbACXTY9AxweGGQSUSYpZ
X-IronPort-AV: E=Sophos;i="4.64,374,1301875200"; d="scan'208";a="95776396"
Received: from usfwa1excas1.itt.net ([10.28.236.1]) by cip-fwa-c1.itt.com with ESMTP/TLS/AES128-SHA; 16 May 2011 14:05:27 +0000
Received: from fwexhub5.itt.net (10.32.76.115) by USFWA1EXCAS1.itt.net (10.28.236.1) with Microsoft SMTP Server (TLS) id 8.2.255.0; Mon, 16 May 2011 10:05:27 -0400
Received: from CSFWCAS2.cs.de.ittind.com (10.32.129.152) by fwexhub5.itt.net (10.32.76.115) with Microsoft SMTP Server (TLS) id 8.2.255.0; Mon, 16 May 2011 10:05:25 -0400
Received: from CSFWMAIL1.cs.de.ittind.com ([10.32.129.153]) by CSFWCAS2.cs.de.ittind.com ([10.32.129.152]) with mapi; Mon, 16 May 2011 10:05:23 -0400
From: "Krishnamurthy, Hema - ES" <Hema.Krishnamurthy@itt.com>
To: CICM Discussion List <cicm@ietf.org>
Date: Mon, 16 May 2011 10:05:21 -0400
Thread-Topic: Proposed WG Charter
Thread-Index: AcwRfV7zdlb/iMYcQcqUmsEHwaNhZgCVKl5g
Message-ID: <86150541B533894DAD5CB2DB3F4788520C667F8CA5@CSFWMAIL1.cs.de.ittind.com>
References: <F9AB58FA72BAE7449E7723791F6993ED05D2FB0AEA@IMCMBX3.MITRE.ORG>
In-Reply-To: <F9AB58FA72BAE7449E7723791F6993ED05D2FB0AEA@IMCMBX3.MITRE.ORG>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [cicm] 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: Mon, 16 May 2011 14:05:40 -0000

I would vote for this charter as-is.

-----Original Message-----
From: cicm-bounces@ietf.org [mailto:cicm-bounces@ietf.org] On Behalf Of Nov=
ikov, Lev
Sent: Friday, May 13, 2011 7:52 AM
To: CICM Discussion List (cicm@ietf.org)
Subject: [cicm] Proposed WG Charter

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 th=
at
there is a community of high assurance crypto module developers, vendors, a=
nd
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 roo=
m.
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 propos=
e
it as a Standard. Please help make this a reality.

Thank you,
Lev


Draft CICM Working Group Charter

=3D Description of Working Group =3D
The Common Interface to Cryptographic Modules (CICM) API provides high
assurance crypto applications with a security framework that accommodates t=
he
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 relat=
ed
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

=3D Goals and Milestones =3D
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
cicm@ietf.org
https://www.ietf.org/mailman/listinfo/cicm

This e-mail and any files transmitted with it may be proprietary and are in=
tended solely for the use of the individual or entity to whom they are addr=
essed. 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 Corporati=
on. The recipient should check this e-mail and any attachments for the pres=
ence of viruses. ITT accepts no liability for any damage caused by any viru=
s transmitted by this e-mail.

From James.L.Howard@L-3Com.com  Mon May 16 09:06:11 2011
Return-Path: <James.L.Howard@L-3Com.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 A2058E0789 for <cicm@ietfa.amsl.com>; Mon, 16 May 2011 09:06:11 -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 oRVu9gY3D6HI for <cicm@ietfa.amsl.com>; Mon, 16 May 2011 09:06:10 -0700 (PDT)
Received: from smtp4out.l-3com.com (smtp4out.l-3com.com [128.170.207.112]) by ietfa.amsl.com (Postfix) with ESMTP id AE9D3E0784 for <cicm@ietf.org>; Mon, 16 May 2011 09:06:10 -0700 (PDT)
X-filenames: None
X-filesizes: None
X-filetypes: None
X-IronPort-AV: E=Sophos;i="4.64,375,1301875200"; d="scan'208";a="273399361"
From: James.L.Howard@L-3Com.com
Received: from host-166-20-16-165.l-3com.com (HELO csemail02.cse.l-3com.com) ([166.20.16.165]) by smtp4out.l-3com.com with ESMTP; 16 May 2011 16:06:09 +0000
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Mon, 16 May 2011 12:06:08 -0400
Message-ID: <F37CEC154221074F88CAEF7386DB55F4DD92B9@csemail02.cse.l-3com.com>
In-Reply-To: <F9AB58FA72BAE7449E7723791F6993ED05D2FB0AEA@IMCMBX3.MITRE.ORG>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [cicm] Proposed WG Charter
Thread-Index: AcwRfV7zdlb/iMYcQcqUmsEHwaNhZgCZcAfA
References: <F9AB58FA72BAE7449E7723791F6993ED05D2FB0AEA@IMCMBX3.MITRE.ORG>
To: "CICM Discussion List" <cicm@ietf.org>
Subject: Re: [cicm] 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: Mon, 16 May 2011 16:06:11 -0000

(a) I vote for this charter as-is.

Jim=A0Howard
Director and Chief Engineer - Information Assurance
L-3 Communications, Communication Systems - East
Phone: 856-338-3504
James.L.Howard@L-3Com.com
=A0

-----Original Message-----
From: cicm-bounces@ietf.org [mailto:cicm-bounces@ietf.org] On Behalf Of =
Novikov, Lev
Sent: Friday, May 13, 2011 10:52 AM
To: CICM Discussion List (cicm@ietf.org)
Subject: [cicm] Proposed WG Charter

CICM is at a critical point. July 24 - 29, 2011 is IETF 81 in Quebec =
City,=20
Canada, where I want to propose CICM as a Working Group (WG) so that we =
can=20
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=20
there is a community of high assurance crypto module developers, =
vendors, and=20
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
  =20
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.=20
As many people as possible should join that chat room on the scheduled =
date=20
(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=20
it as a Standard. Please help make this a reality.

Thank you,
Lev


Draft CICM Working Group Charter

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

The purpose of the CICM Working Group is to shepherd the CICM =
specification=20
documents to publication and provide guidance for any new submissions =
related=20
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

=3D Goals and Milestones =3D
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
cicm@ietf.org
https://www.ietf.org/mailman/listinfo/cicm

From jxc@mitre.org  Mon May 16 10:08:51 2011
Return-Path: <jxc@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 27C0FE074A for <cicm@ietfa.amsl.com>; Mon, 16 May 2011 10:08:51 -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 7IYlYiuQgkKO for <cicm@ietfa.amsl.com>; Mon, 16 May 2011 10:08:50 -0700 (PDT)
Received: from smtpksrv1.mitre.org (smtpksrv1.mitre.org [198.49.146.77]) by ietfa.amsl.com (Postfix) with ESMTP id 4C8F2E0784 for <cicm@ietf.org>; Mon, 16 May 2011 10:08:49 -0700 (PDT)
Received: from smtpksrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id F0D3A21B0DF4 for <cicm@ietf.org>; Mon, 16 May 2011 13:08:48 -0400 (EDT)
Received: from imchub2.MITRE.ORG (imchub2.mitre.org [129.83.29.74]) by smtpksrv1.mitre.org (Postfix) with ESMTP id DFBCC21B0DBF for <cicm@ietf.org>; Mon, 16 May 2011 13:08:48 -0400 (EDT)
Received: from IMCMBX1.MITRE.ORG ([129.83.29.204]) by imchub2.MITRE.ORG ([129.83.29.74]) with mapi; Mon, 16 May 2011 13:08:48 -0400
From: "Cottrell Jr., James R." <jxc@mitre.org>
To: CICM Discussion List <cicm@ietf.org>
Date: Mon, 16 May 2011 13:08:47 -0400
Thread-Topic: [cicm] BoF Request for CICM at IETF 81
Thread-Index: AQHMEaBeRtnlEkJu4EOsE4KXi9EFaZSLSjgdgAAErFCABGTbAA==
Message-ID: <E48B962F2B71EC4C97EF42A839D0F2DE05875E6FD7@IMCMBX1.MITRE.ORG>
References: <F9AB58FA72BAE7449E7723791F6993ED05D2FB0B91@IMCMBX3.MITRE.ORG>, <7EDDD87A9A1D7F4DB6F78BC55AA495502B7748@0461-its-exmb09.us.saic.com> <06D46EAFF7D0C946BEC108DB7CCDC9A608B282C8@ROCMXUS21.cs.myharris.net> <9742CF2025F5FD41AAF6D9B8679F806201EF4EDE@vcaexch06.hq.corp.viasat.com>
In-Reply-To: <9742CF2025F5FD41AAF6D9B8679F806201EF4EDE@vcaexch06.hq.corp.viasat.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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [cicm] BoF Request for CICM at IETF 81
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, 16 May 2011 17:08:51 -0000

Dennis,

I agree that the API by itself cannot provide "high assurance" but this API=
 has been designed to be targeted for use in high assurance applications.  =
Not sure how to work this thought into your suggested charter wording.

Jim C.

-----Original Message-----
From: cicm-bounces@ietf.org [mailto:cicm-bounces@ietf.org] On Behalf Of Bou=
rget, Dennis
Sent: Friday, May 13, 2011 6:12 PM
To: CICM Discussion List
Subject: Re: [cicm] BoF Request for CICM at IETF 81

I just don't see how any API can provide "high assurance", it is the
implementation of the API, host platform and operating system that would
need to be evaluated to FIPS 140-2 or Common Criteria.  For example, the
API does not and cannot provide domain separation, I suggest that we
strike that text from the charter.

Perhaps the following:

The Common Interface to Cryptographic Modules (CICM) API defines a
"standardized" application interface
for the security services provided by cryptographic modules developed by
multiple vendors. The API supports=20
security domain separation, and enhanced module, key, and channel
management capabilities that is vendor agnostic.=20

-----Original Message-----
From: cicm-bounces@ietf.org [mailto:cicm-bounces@ietf.org] On Behalf Of
Fitton, John
Sent: Friday, May 13, 2011 2:56 PM
To: CICM Discussion List
Subject: Re: [cicm] BoF Request for CICM at IETF 81

I would suggest defining High Assurance in terms of  FIPS-140-2 Level 4.
Of course FIPS 140-2 refers to the Common Criteria AL4 or higher, but
does offer specific criteria to be used in the evaluation. That being
said, however, while the stated goal is for a high assurance API, there
is nothing in principal which limits the API to high assurance
applications.=20

I would also point out that the Orange Book (as was the entire original
Rainbow series) was targeted at information processing systems. These
systems were essentially large data bases with many users gaining access
via dedicated terminals, and there are those who would argue that the
old  assurance levels, were also not that well defined. As these system
evolved and  internet access was introdouced there was additional
volumes created to address some of the security issues involved.=20

I would argue that nothing in the Rainbow series specifically addressed
security requirements or assurance levels for cryptographic modules.=20

One advantage of the Common Criteria, is that the meaning of any given
Assurance Level for a given application (e.g. a Cryptographic module)
can be defined through an evaluation profile. Another advantage is that
it is an internationally recognized set of criteria with a group of
international evaluation/certification bodies.=20

________________________________________
From: Davidson, John A. [JOHN.A.DAVIDSON@saic.com]
Sent: Friday, May 13, 2011 1:34 PM
To: CICM Discussion List
Subject: Re: [cicm] BoF Request for CICM at IETF 81

Lev,
I am wondering if we need to (or even can) clarify what we mean by High
Assurance.  Assurance levels were fairly well-defined under the Orange
Book but that has been grayed out by the move to international flavored
Common Criteria.  Today when we say we are addressing HA, it is no
longer clear to me whether we mean to restrict our view to approaches
that are logically "closed form," or if we mean just a better version of
"best effort," whatever that is.

In my mind, there are IA critical capabilities we can support with one
that may be ruled out by the other.

Thanks,
John


-----Original Message-----
From: cicm-bounces@ietf.org [mailto:cicm-bounces@ietf.org] On Behalf Of
Novikov, Lev
Sent: Friday, May 13, 2011 10:01 AM
To: saag@ietf.org
Cc: CICM Discussion List (cicm@ietf.org)
Subject: [cicm] BoF Request for CICM at IETF 81

I'm formally requesting a BoF at IETF 81 to form a CICM WG based on the
draft charter below.
Updated version at: http://code.google.com/p/ietf-cicm/wiki/WGCharter
Discussion also at: cicm@ietf.org

Thanks,
Lev

Draft CICM Working Group Charter

=3D Description of Working Group =3D
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

=3D Goals and Milestones =3D
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
cicm@ietf.org
https://www.ietf.org/mailman/listinfo/cicm
_______________________________________________
cicm mailing list
cicm@ietf.org
https://www.ietf.org/mailman/listinfo/cicm
_______________________________________________
cicm mailing list
cicm@ietf.org
https://www.ietf.org/mailman/listinfo/cicm

From lnovikov@mitre.org  Mon May 16 17:54:29 2011
Return-Path: <lnovikov@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 E3D67E0684 for <cicm@ietfa.amsl.com>; Mon, 16 May 2011 17:54:29 -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 8PU6Z3-HZ3kF for <cicm@ietfa.amsl.com>; Mon, 16 May 2011 17:54:28 -0700 (PDT)
Received: from smtpksrv1.mitre.org (smtpksrv1.mitre.org [198.49.146.77]) by ietfa.amsl.com (Postfix) with ESMTP id 67291E0701 for <cicm@ietf.org>; Mon, 16 May 2011 17:54:27 -0700 (PDT)
Received: from smtpksrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 21C7921B10E7 for <cicm@ietf.org>; Mon, 16 May 2011 20:54:27 -0400 (EDT)
Received: from imchub1.MITRE.ORG (imchub1.mitre.org [129.83.29.73]) by smtpksrv1.mitre.org (Postfix) with ESMTP id 1B61621B10E1 for <cicm@ietf.org>; Mon, 16 May 2011 20:54:27 -0400 (EDT)
Received: from IMCMBX3.MITRE.ORG ([129.83.29.206]) by imchub1.MITRE.ORG ([129.83.29.73]) with mapi; Mon, 16 May 2011 20:54:27 -0400
From: "Novikov, Lev" <lnovikov@mitre.org>
To: CICM Discussion List <cicm@ietf.org>
Date: Mon, 16 May 2011 20:54:24 -0400
Thread-Topic: [cicm] BoF Request for CICM at IETF 81
Thread-Index: AcwULPctLU/0vGXGSRy/ae2qzI1emw==
Message-ID: <F9AB58FA72BAE7449E7723791F6993ED05D308F8B0@IMCMBX3.MITRE.ORG>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [cicm] BoF Request for CICM at IETF 81
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: Tue, 17 May 2011 00:54:30 -0000

On 2011-05-13 at 13:34, John Davidson wrote:
> I am wondering if we need to (or even can) clarify what we mean by=20
> High Assurance.

On 2011-05-13 at 17:56, John Fitton wrote:
> I would suggest defining High Assurance in terms of  FIPS-140-2=20
> Level 4. Of course FIPS 140-2 refers to the Common Criteria AL4 or=20
> higher, but does offer specific criteria to be used in the evaluation.
> That being said, however, while the stated goal is for a high=20
> assurance API, there is nothing in principal which limits the API to=20
> high assurance applications.

On 2011-05-14 at 18:12, Dennis Bourget wrote:
> I just don't see how any API can provide "high assurance", it is the
> implementation of the API, host platform and operating system that=20
> would need to be evaluated to FIPS 140-2 or Common Criteria.  For=20
> example, the API does not and cannot provide domain separation, I=20
> suggest that we strike that text from the charter.

On 2011-05-16 at 13:08, Jim Cottrell wrote:
> I agree that the API by itself cannot provide "high assurance" but=20
> this API has been designed to be targeted for use in high assurance=20
> applications.

Interesting discussion.=20

What do people think of the following? It is based on Dennis's suggestion,=
=20
but emphasizes that the API targets high assurance environments.

  The Common Interface to Cryptographic Modules (CICM) defines an applicati=
on=20
  programming interface for the security services provided by cryptographic=
=20
  modules developed by multiple vendors. The API is intended to support hig=
h=20
  assurance cryptography, and thus offers security domain separation, and=20
  enhanced module, key, and channel management capabilities that are vendor=
=20
  agnostic.

Lev

From dennis.bourget@viasat.com  Mon May 16 18:10:44 2011
Return-Path: <dennis.bourget@viasat.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 C946CE06ED for <cicm@ietfa.amsl.com>; Mon, 16 May 2011 18:10:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 n9BQYqZB2xub for <cicm@ietfa.amsl.com>; Mon, 16 May 2011 18:10:44 -0700 (PDT)
Received: from viasat.com (bateleur.viasat.com [199.106.52.160]) by ietfa.amsl.com (Postfix) with ESMTP id DAC0CE06E5 for <cicm@ietf.org>; Mon, 16 May 2011 18:10:43 -0700 (PDT)
Received: from ([172.20.1.71]) by bateleur.viasat.com with ESMTP  id H6GMFJ1.44391230; Mon, 16 May 2011 18:10:39 -0700
Received: from vcaexch06.hq.corp.viasat.com ([172.18.46.74]) by VCAEXCH02.hq.corp.viasat.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 16 May 2011 18:10:39 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 16 May 2011 18:10:33 -0700
Message-ID: <9742CF2025F5FD41AAF6D9B8679F806201EF55D1@vcaexch06.hq.corp.viasat.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
thread-topic: [cicm] BoF Request for CICM at IETF 81
thread-index: AcwULPctLU/0vGXGSRy/ae2qzI1emwAAcUnA
References: <F9AB58FA72BAE7449E7723791F6993ED05D308F8B0@IMCMBX3.MITRE.ORG>
From: "Bourget, Dennis" <dennis.bourget@viasat.com>
To: "CICM Discussion List" <cicm@ietf.org>
X-OriginalArrivalTime: 17 May 2011 01:10:39.0551 (UTC) FILETIME=[3C5AE4F0:01CC142F]
Subject: Re: [cicm] BoF Request for CICM at IETF 81
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: Tue, 17 May 2011 01:10:44 -0000

Again, I may be picking nits, but I still don't believe that the API
offers any security domain separation. =20
I would just delete "and thus offers".

It would then read:=20
"The API is intended to support high assurance cryptography, security
domain separation, and=20
 enhanced module, key, and channel management capabilities that are
vendor agnostic."

-----Original Message-----
From: cicm-bounces@ietf.org [mailto:cicm-bounces@ietf.org] On Behalf Of
Novikov, Lev
Sent: Monday, May 16, 2011 5:54 PM
To: CICM Discussion List
Subject: Re: [cicm] BoF Request for CICM at IETF 81

On 2011-05-13 at 13:34, John Davidson wrote:
> I am wondering if we need to (or even can) clarify what we mean by=20
> High Assurance.

On 2011-05-13 at 17:56, John Fitton wrote:
> I would suggest defining High Assurance in terms of  FIPS-140-2=20
> Level 4. Of course FIPS 140-2 refers to the Common Criteria AL4 or=20
> higher, but does offer specific criteria to be used in the evaluation.
> That being said, however, while the stated goal is for a high=20
> assurance API, there is nothing in principal which limits the API to=20
> high assurance applications.

On 2011-05-14 at 18:12, Dennis Bourget wrote:
> I just don't see how any API can provide "high assurance", it is the
> implementation of the API, host platform and operating system that=20
> would need to be evaluated to FIPS 140-2 or Common Criteria.  For=20
> example, the API does not and cannot provide domain separation, I=20
> suggest that we strike that text from the charter.

On 2011-05-16 at 13:08, Jim Cottrell wrote:
> I agree that the API by itself cannot provide "high assurance" but=20
> this API has been designed to be targeted for use in high assurance=20
> applications.

Interesting discussion.=20

What do people think of the following? It is based on Dennis's
suggestion,=20
but emphasizes that the API targets high assurance environments.

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

Lev
_______________________________________________
cicm mailing list
cicm@ietf.org
https://www.ietf.org/mailman/listinfo/cicm

From JOHN.A.DAVIDSON@saic.com  Mon May 16 20:40:06 2011
Return-Path: <JOHN.A.DAVIDSON@saic.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 6BC68E0713 for <cicm@ietfa.amsl.com>; Mon, 16 May 2011 20:40:06 -0700 (PDT)
X-Quarantine-ID: <Nikp+NnirGRB>
X-Amavis-Modified: Mail body modified (defanged) by ietfa.amsl.com
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BANNED, message contains part: multipart/mixed | application/ms-tnef,.tnef,winmail.dat
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 Nikp+NnirGRB for <cicm@ietfa.amsl.com>; Mon, 16 May 2011 20:40:05 -0700 (PDT)
Content-Type: multipart/mixed; boundary="----------=_1305603606-1633-7"
Content-Transfer-Encoding: binary
MIME-Version: 1.0
Received: from cpmx.mail.saic.com (cpmx.mail.saic.com [139.121.17.160]) by ietfa.amsl.com (Postfix) with ESMTP id A2DB4E06B5 for <cicm@ietf.org>; Mon, 16 May 2011 20:40:05 -0700 (PDT)
Received: from 0599-its-sbg03.saic.com ([139.121.20.253] [139.121.20.253]) by cpmx.mail.saic.com with ESMTP id BT-MMP-10050338 for cicm@ietf.org; Mon, 16 May 2011 20:39:52 -0700
Received: from 0599-its-exbh01.us.saic.com (cpe-z7-si-srcnat.sw.saic.com [139.121.20.253]) by 0599-its-sbg03.saic.com (Symantec Brightmail Gateway) with SMTP id 0E.67.27244.80EE1DD4; Mon, 16 May 2011 20:39:52 -0700 (PDT)
Received: from 0461-its-exmb09.us.saic.com ([10.8.67.20]) by 0599-its-exbh01.us.saic.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 16 May 2011 20:39:52 -0700
Date: Mon, 16 May 2011 20:35:44 -0700
Message-Id: <7EDDD87A9A1D7F4DB6F78BC55AA495502F7337@0461-its-exmb09.us.saic.com>
References: <F9AB58FA72BAE7449E7723791F6993ED05D308F8B0@IMCMBX3.MITRE.ORG> <9742CF2025F5FD41AAF6D9B8679F806201EF55D1@vcaexch06.hq.corp.viasat.com>
From: "Davidson, John A." <JOHN.A.DAVIDSON@saic.com>
To: "CICM Discussion List" <cicm@ietf.org>
Subject: Re: [cicm] BoF Request for CICM at IETF 81
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: Tue, 17 May 2011 03:40:06 -0000

This is a multi-part message in MIME format...

------------=_1305603606-1633-7
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

WARNING: contains banned part

------------=_1305603606-1633-7
Content-Type: message/rfc822; x-spam-type=original; name="message"
Content-Disposition: attachment; filename="message"
Content-Transfer-Encoding: 7bit
Content-Description: Original message

Return-Path: <JOHN.A.DAVIDSON@saic.com>
Received: from cpmx.mail.saic.com (cpmx.mail.saic.com [139.121.17.160])
	by ietfa.amsl.com (Postfix) with ESMTP id A2DB4E06B5
	for <cicm@ietf.org>; Mon, 16 May 2011 20:40:05 -0700 (PDT)
Received: from 0599-its-sbg03.saic.com ([139.121.20.253] [139.121.20.253]) by cpmx.mail.saic.com with ESMTP id BT-MMP-10050338 for cicm@ietf.org; Mon, 16 May 2011 20:39:52 -0700
X-AuditID: 8b79132a-b7bc1ae000006a6c-85-4dd1ee083439
Received: from 0599-its-exbh01.us.saic.com (cpe-z7-si-srcnat.sw.saic.com [139.121.20.253])
	by 0599-its-sbg03.saic.com (Symantec Brightmail Gateway) with SMTP id 0E.67.27244.80EE1DD4; Mon, 16 May 2011 20:39:52 -0700 (PDT)
Received: from 0461-its-exmb09.us.saic.com ([10.8.67.20]) by 0599-its-exbh01.us.saic.com with Microsoft SMTPSVC(6.0.3790.4675);
	 Mon, 16 May 2011 20:39:52 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_001_01CC1444.14B16C7F"
Subject: RE: [cicm] BoF Request for CICM at IETF 81
Date: Mon, 16 May 2011 20:35:44 -0700
Message-Id: <7EDDD87A9A1D7F4DB6F78BC55AA495502F7337@0461-its-exmb09.us.saic.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: <7EDDD87A9A1D7F4DB6F78BC55AA495502F7337@0461-its-exmb09.us.saic.com>
Thread-Topic: [cicm] BoF Request for CICM at IETF 81
Thread-Index: AcwULPctLU/0vGXGSRy/ae2qzI1emwAAcUnAAAUxGJQ=
References: <F9AB58FA72BAE7449E7723791F6993ED05D308F8B0@IMCMBX3.MITRE.ORG> <9742CF2025F5FD41AAF6D9B8679F806201EF55D1@vcaexch06.hq.corp.viasat.com>
From: "Davidson, John A." <JOHN.A.DAVIDSON@saic.com>
To: "CICM Discussion List" <cicm@ietf.org>
X-OriginalArrivalTime: 17 May 2011 03:39:52.0716 (UTC) FILETIME=[14DB74C0:01CC1444]
X-Brightmail-Tracker: AAAAAQPmCRA=

This is a multi-part message in MIME format.

------_=_NextPart_001_01CC1444.14B16C7F
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Dennis wrote:  ...I still don't believe that the API offers any security =
domain separation.
I wish I had written that!  Policy enforcement is not an API's thing, =
IMHO. =20

-----Original Message-----
From: cicm-bounces@ietf.org on behalf of Bourget, Dennis
Sent: Mon 5/16/2011 6:10 PM
To: CICM Discussion List
Subject: Re: [cicm] BoF Request for CICM at IETF 81
=20
Again, I may be picking nits, but I still don't believe that the API
offers any security domain separation. =20
I would just delete "and thus offers".

It would then read:=20
"The API is intended to support high assurance cryptography, security
domain separation, and=20
 enhanced module, key, and channel management capabilities that are
vendor agnostic."

-----Original Message-----
From: cicm-bounces@ietf.org [mailto:cicm-bounces@ietf.org] On Behalf Of
Novikov, Lev
Sent: Monday, May 16, 2011 5:54 PM
To: CICM Discussion List
Subject: Re: [cicm] BoF Request for CICM at IETF 81

On 2011-05-13 at 13:34, John Davidson wrote:
> I am wondering if we need to (or even can) clarify what we mean by=20
> High Assurance.

On 2011-05-13 at 17:56, John Fitton wrote:
> I would suggest defining High Assurance in terms of  FIPS-140-2=20
> Level 4. Of course FIPS 140-2 refers to the Common Criteria AL4 or=20
> higher, but does offer specific criteria to be used in the evaluation.
> That being said, however, while the stated goal is for a high=20
> assurance API, there is nothing in principal which limits the API to=20
> high assurance applications.

On 2011-05-14 at 18:12, Dennis Bourget wrote:
> I just don't see how any API can provide "high assurance", it is the
> implementation of the API, host platform and operating system that=20
> would need to be evaluated to FIPS 140-2 or Common Criteria.  For=20
> example, the API does not and cannot provide domain separation, I=20
> suggest that we strike that text from the charter.

On 2011-05-16 at 13:08, Jim Cottrell wrote:
> I agree that the API by itself cannot provide "high assurance" but=20
> this API has been designed to be targeted for use in high assurance=20
> applications.

Interesting discussion.=20

What do people think of the following? It is based on Dennis's
suggestion,=20
but emphasizes that the API targets high assurance environments.

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

Lev
_______________________________________________
cicm mailing list
cicm@ietf.org
https://www.ietf.org/mailman/listinfo/cicm
_______________________________________________
cicm mailing list
cicm@ietf.org
https://www.ietf.org/mailman/listinfo/cicm


------_=_NextPart_001_01CC1444.14B16C7F
Content-Type: application/ms-tnef;
	name="winmail.dat"
Content-Transfer-Encoding: base64

eJ8+IjUDAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy
b3NvZnQgTWFpbC5Ob3RlADEIAQ2ABAACAAAAAgACAAEEgAEAKwAAAFJFOiBbY2ljbV0gQm9GIFJl
cXVlc3QgZm9yIENJQ00gYXQgSUVURiA4MQDODAEFgAMADgAAANsHBQAQABQAIwAsAAEAWwEBIIAD
AA4AAADbBwUAEAAUACcANAABAGcBAQmAAQAhAAAARTI3RkI3N0Y4RThCQTk0MEIzMEJDMjc1NEVD
QzYxRDEAYgcBA5AGAKwOAAA5AAAAAwAmAAAAAAADADYAAAAAAEAAOQDjvbOAQxTMAR4APQABAAAA
BQAAAFJFOiAAAAAAAgFHAAEAAAAzAAAAYz1VUzthPSA7cD1TQUlDO2w9MDQ2MS1JVFMtRVhNLTEx
MDUxNzAzMzk1MlotNTczMDYAAB4ASQABAAAAKwAAAFJlOiBbY2ljbV0gQm9GIFJlcXVlc3QgZm9y
IENJQ00gYXQgSUVURiA4MQAAQABOAIBKczgvFMwBHgBaAAEAAAAWAAAAY2ljbS1ib3VuY2VzQGll
dGYub3JnAAAAAgFbAAEAAABJAAAAAAAAAIErH6S+oxAZnW4A3QEPVAIAAAAAY2ljbS1ib3VuY2Vz
QGlldGYub3JnAFNNVFAAY2ljbS1ib3VuY2VzQGlldGYub3JnAAAAAAIBXAABAAAAGwAAAFNNVFA6
Q0lDTS1CT1VOQ0VTQElFVEYuT1JHAAAeAF0AAQAAABAAAABCb3VyZ2V0LCBEZW5uaXMAAgFeAAEA
AABHAAAAAAAAAIErH6S+oxAZnW4A3QEPVAIAAAAAQm91cmdldCwgRGVubmlzAFNNVFAAZGVubmlz
LmJvdXJnZXRAdmlhc2F0LmNvbQAAAgFfAAEAAAAfAAAAU01UUDpERU5OSVMuQk9VUkdFVEBWSUFT
QVQuQ09NAAAeAGYAAQAAAAUAAABTTVRQAAAAAB4AZwABAAAAFgAAAGNpY20tYm91bmNlc0BpZXRm
Lm9yZwAAAB4AaAABAAAABQAAAFNNVFAAAAAAHgBpAAEAAAAaAAAAZGVubmlzLmJvdXJnZXRAdmlh
c2F0LmNvbQAAAB4AcAABAAAAJwAAAFtjaWNtXSBCb0YgUmVxdWVzdCBmb3IgQ0lDTSBhdCBJRVRG
IDgxAAACAXEAAQAAACAAAAABzBQs9y0tT/S8ZcZJHL9p7arMjV6bAABxScAABTEYlB4AdAABAAAA
FQAAAENJQ00gRGlzY3Vzc2lvbiBMaXN0AAAAAB4AGgwBAAAAEgAAAERhdmlkc29uLCBKb2huIEEu
AAAAHgAdDgEAAAAnAAAAW2NpY21dIEJvRiBSZXF1ZXN0IGZvciBDSUNNIGF0IElFVEYgODEAAAIB
CRABAAAAFgcAABIHAADVDQAATFpGdbof4JIDAAoAcmNwZzEyNeIyA0N0ZXgFQQEDAff/CoACpAPk
BxMCgA/zAFAEVj8IVQeyESUOUQMBAgBjaOEKwHNldDIGAAbDESX2MwRGE7cwEiwRMwjvCfe2Oxgf
DjA1ESIMYGMAUDMLCQFkMzYWUAumIEQ3CfADAAQgdwNgDrA6IIQgLh3gSSBzdAMQFQMgZAIgJwVA
YmVs4QiQdmUgdBPgBUAfcOkfUEFQHhBvASAEkAQg3QBweR4gBZAIcXQg0B6QXwDAC4Ag4QqxH5Bp
AiAuzwqiCoAeEAPxaCAeEBPgvmQdUSFADrADoB9yIR3APlAG8A3gINAJ8AIQcmPWZQeAAjAgHTFu
HYAgoZ0f8icEIB9wC4BnLCNgcE1ITy4dwCKkIqQt9SiSTwUQZwuAB0AF0AeQsHNhZ2UokyKkRgNh
JR2wYw3gbS0G4HVuWSWAc0AIkAAwLgWwZ08gMAOgHvAT4GxmIDEg9kIIYSnAdCdAHPQipAZgCwIw
HbBNLFE1LzE2Ai8B0DExIDY6MUkWUFBNIqRUbx2wQ/hJQ00c4AQAIRAEECJhFCBMBAB0LhV1Ymqr
BZAuoVIdoVsq8l0tEdpGMuFxClAeMCAlUTC00R+RSUVUM8A4GvMKgNknxUFnC3EnQSAAwCDQ6R7w
IHAN4GsnESYQIUDycydAYnU1AR4vHz4ipL8gTyFfImIntiMBCGBsI7BuajFQBUABAGwUIB9QIt8A
cCOwH3AxUCA1IiKVIqX/BUA+BB/BA6AYICOgHbAipPwiVB/VHTELgCQRAQA/UeJvOJB1cHAXwSOA
KQB9I1BhBBAIcABwJYAq4HIKeQUwbwnAYXBoef8nQDu2IqQ8TydAPzI1lQnwXxPgK3EjsARhPiBl
J0Br/mVGQT8yE9EdEDlwNuEpMPspwCWjY0YQAaADEDwACJD3JtIfkQrAZSKkH0A/QAWxxymwJiA4
oWMuIiffKO9XKf8rDywSWyGhbEPwOldR7ywCM4BPA6BCLJRPgmYipE5vdmlrVmBtJ0BMHzAuHWQ3
ACdATQ83AS8wJ0AvYzU6NTT/L/8xDzIfMy80PzVJIqRVMYEvYi0wNS0xM15SEWBwOjM0J0BKb2jJ
A6BEYVZwZHMsUR1k5SKkPiNhYW098UOhBRC/N7EGkB1QH1BLEEPEKAWx5x8xA6BMAG4pUdALYAaB
vTuQdx+CZCEHgAORYjuQdWKGSESyQUUGQDtfzzHuN1kwWKFhQ0Yj8WH/PebtRCBnULA+g2YLgDei
Z7w3Q1EfYASQbT+iHcBGScRQU2BgNDAtFEBihvtW4UshNCegVdBR0AhhFBD/b8NYgHAzGCA7I0Px
H8IIUF5tBGASETvxBnFhEMBM/1lQBbFihkSiBJA4JDkAB5H7OwM4kHAFkAaQDeBFgXRV/0PxNzFa
wEPBbwIf0R8wB0D+dSJKYuBCsB+ROWA3olCQ82HAJ0Bob2QgH0B2AWYwPwMQH1IfUDigH5BDwWdv
/1AxHTFd0nSgRKNihkT4IAG/J0AfwRggJeUnAm7ycGOhX1PACrADIHwxE9AgOYBt/zfxH7dD8XU6
ROlGEAtQDeC9IkNzaJ9gBllQYKI4L8D+Mi2WLRZrnz5kORMUEB9Q/3uhO2MgAmVhgRFWYQEAPxD9
RKwiJ0A8ACXiH8Fihgdw/wtQJZMiQyziH8V7gl2hC1HvADAFsGMwPzJvdzAiMnsS/nk4oCWQH2Ri
hj4EZFY3Mb95ZUPEcjld4nPcJ6FGdQn/DsBjII5xf8Mf83ZzJiRKsf9K8SYxi6ZHXzayYoZtBh9z
/2QhOKAFEEpAH2UOwgNSH7MvE9JvMYV/YAY2YJUwOP9hIQdwEiECQBggONFiLwnC/x9sZwE38Tlw
caGZnIwuODP/YoYm8RCxIBET4AQgOWAkIf8BAACQTjCThwGQLVJDwV3S/3ihbvJErX53hM9AlkNx
GCC7OKE3sWRalyegTspXH4K7OQA3UGWRIHxjC4BrjzZvAhA40HuwJxE/I2Al02L/RPBDwSxRHPQm
wCKkbQVIM58ipDhCJZBGIETwaXpMpn+Cl6ojBCBErQnwVnADYG6/JaKFbB3AQrJzxa5TZgDQ/x9R
RAB0MEW3d4Eu0EniBCD+KFoyZZBtgweRAHAipKzJ/0i2paJF8XPggLS7pl3SfJP7O8YUEHJWcCuB
paYjsGcA/yKkRZl3gbpWScQEIAEAcSH/kSHD0jbgPiA4sLFCTbSFYP+6w0L/RAcipH4pHcBE/0YF
/z89O69Hyb7FSJhJL0o/S0+/TF9NasrXTjZOylbnX9f//9kP2drEFVPRNuHTwTexOYAfW1ZTwiu3
yiUCQHBzOqgvL3feYC4rxi9TUt0DgS/cEguAAhAvU8LXn//hj+Kf2s/b39zv3f/fD+AbBSKkfepA
AAAeADUQAQAAAEUAAAA8N0VEREQ4N0E5QTFEN0Y0REI2Rjc4QkM1NUFBNDk1NTAyRjczMzdAMDQ2
MS1pdHMtZXhtYjA5LnVzLnNhaWMuY29tPgAAAAAeADkQAQAAAIcAAAA8RjlBQjU4RkE3MkJBRTc0
NDlFNzcyMzc5MUY2OTkzRUQwNUQzMDhGOEIwQElNQ01CWDMuTUlUUkUuT1JHPiA8OTc0MkNGMjAy
NUY1RkQ0MUFBRjZEOUI4Njc5RjgwNjIwMUVGNTVEMUB2Y2FleGNoMDYuaHEuY29ycC52aWFzYXQu
Y29tPgAAHgBHEAEAAAAPAAAAbWVzc2FnZS9yZmM4MjIAAAsA8hABAAAAHwDzEAEAAABiAAAAUgBF
ACUAMwBBACAAWwBjAGkAYwBtAF0AIABCAG8ARgAgAFIAZQBxAHUAZQBzAHQAIABmAG8AcgAgAEMA
SQBDAE0AIABhAHQAIABJAEUAVABGACAAOAAxAC4ARQBNAEwAAAAAAAsA9hAAAAAAQAAHMIVbsYBD
FMwBQAAIMLO6vxREFMwBAwDeP69vAAADAPE/CQQAAB4A+D8BAAAAEgAAAERhdmlkc29uLCBKb2hu
IEEuAAAAAgH5PwEAAABOAAAAAAAAANynQMjAQhAatLkIACsv4YIBAAAAAAAAAC9PPVNBSUMvT1U9
VVMtU0QtUExUQy9DTj1SRUNJUElFTlRTL0NOPURBVklEU09OSkEAAAAeAPo/AQAAABUAAABTeXN0
ZW0gQWRtaW5pc3RyYXRvcgAAAAACAfs/AQAAAB4AAAAAAAAA3KdAyMBCEBq0uQgAKy/hggEAAAAA
AAAALgAAAAMA/T/kBAAAAwAZQAAAAAADABpAAAAAAAMAHUAAAAAAAwAeQAAAAAAeADBAAQAAAAsA
AABEQVZJRFNPTkpBAAAeADFAAQAAAAsAAABEQVZJRFNPTkpBAAAeADJAAQAAABYAAABjaWNtLWJv
dW5jZXNAaWV0Zi5vcmcAAAAeADNAAQAAABoAAABkZW5uaXMuYm91cmdldEB2aWFzYXQuY29tAAAA
HgA4QAEAAAALAAAAREFWSURTT05KQQAAHgA5QAEAAAACAAAALgAAAAMAdkD/////CwApAAAAAAAL
ACMAAAAAAAMABhAV7bldAwAHENAIAAADABAQAAAAAAMAERAAAAAAHgAIEAEAAABlAAAAREVOTklT
V1JPVEU6SVNUSUxMRE9OVEJFTElFVkVUSEFUVEhFQVBJT0ZGRVJTQU5ZU0VDVVJJVFlET01BSU5T
RVBBUkFUSU9OSVdJU0hJSEFEV1JJVFRFTlRIQVRQT0xJQ1lFTgAAAAACAX8AAQAAAEUAAAA8N0VE
REQ4N0E5QTFEN0Y0REI2Rjc4QkM1NUFBNDk1NTAyRjczMzdAMDQ2MS1pdHMtZXhtYjA5LnVzLnNh
aWMuY29tPgAAAAAGLA==

------_=_NextPart_001_01CC1444.14B16C7F--

------------=_1305603606-1633-7--

From kevin.w.wall@gmail.com  Mon May 16 21:55:56 2011
Return-Path: <kevin.w.wall@gmail.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 CAF4DE06EB for <cicm@ietfa.amsl.com>; Mon, 16 May 2011 21:55:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 yRBZ1e5H7Sxq for <cicm@ietfa.amsl.com>; Mon, 16 May 2011 21:55:56 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id BDF8BE0656 for <cicm@ietf.org>; Mon, 16 May 2011 21:55:55 -0700 (PDT)
Received: by wyb29 with SMTP id 29so100202wyb.31 for <cicm@ietf.org>; Mon, 16 May 2011 21:55:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=vAarDuANVdLvC8wmrCPw6u7muWPtsDcaMipl8o7anIU=; b=RcUFwRPO3KwqOpHsh9J/jdoybmsqD4tzcXLsl56Z8g//BqnyFXhdyHYA9OT+XNtbnP HucmZygZqGjEbkOI5jWf+cKn/tPtaN9I4KnQ4lP65/cpQeZO2cRCJfikiT9e58GThajM BQqWtiDOVQggg1nYlh9DGhBFOD8n7646GLsas=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=mdr+safDjToeBkFBHlIdedRJfVbGevVCB6ksf0UnZHLeEqXfXbSGio8zXscEMZZvJB 6MX+LtwCcaifiiJ0rswg95HiMbR5pfOd+uqQcZtWvPeuFrIrqCgRA5UQNLZiw+1j5uiv qaP2hfFGT2GVzF133mq1fbE0V2ZX4URf0x6Rk=
MIME-Version: 1.0
Received: by 10.227.6.219 with SMTP id a27mr169797wba.46.1305608154662; Mon, 16 May 2011 21:55:54 -0700 (PDT)
Received: by 10.227.136.83 with HTTP; Mon, 16 May 2011 21:55:54 -0700 (PDT)
In-Reply-To: <F9AB58FA72BAE7449E7723791F6993ED05D2FB0AEA@IMCMBX3.MITRE.ORG>
References: <F9AB58FA72BAE7449E7723791F6993ED05D2FB0AEA@IMCMBX3.MITRE.ORG>
Date: Tue, 17 May 2011 00:55:54 -0400
Message-ID: <BANLkTik+LKXc5q4kOcXkyKeu7wY6tAeNNg@mail.gmail.com>
From: "Kevin W. Wall" <kevin.w.wall@gmail.com>
To: CICM Discussion List <cicm@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [cicm] 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: Tue, 17 May 2011 04:55:56 -0000

Lev,

Looks fine to me, as is, assuming that everyone has a common understanding
of "high assurance", which I'm not so certain of.

-kevin

On Fri, May 13, 2011 at 10:52 AM, Novikov, Lev <lnovikov@mitre.org> wrote:
> 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 c=
an
> 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:
> =A0 http://code.google.com/p/ietf-cicm/wiki/WGCharter
>
> 2. By COB Friday, 2011-05-20, reply to this email with one of the followi=
ng:
> =A0 =A0(a) I would vote for this charter as-is.
> =A0 =A0(b) I would vote for a similar charter with following changes: <sp=
ecify>
> =A0 =A0(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 r=
oom.
> As many people as possible should join that chat room on the scheduled da=
te
> (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 prop=
ose
> it as a Standard. Please help make this a reality.
>
> Thank you,
> Lev
>
>
> Draft CICM Working Group Charter
>
> =3D Description of Working Group =3D
> 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 separatio=
n,
> and enhanced module, key, and channel management capabilities.
>
> The purpose of the CICM Working Group is to shepherd the CICM specificati=
on
> documents to publication and provide guidance for any new submissions rel=
ated
> to high assurance cryptos.
>
> Specifically, the Working Group will:
>
> =A0* Complete existing requests:
> =A0 =A0* replace algorithm strings with OIDs
> =A0 =A0* use ABNF notation for unique identifiers syntax
> =A0 =A0* add module events for symmetric and asymmetric key filled
>
> =A0* Shepard the following documents to publication:
> =A0 =A0* draft-lanz-cicm
> =A0 =A0* draft-lanz-cicm-lm
> =A0 =A0* draft-lanz-cicm-mm
> =A0 =A0* draft-lanz-cicm-km
> =A0 =A0* draft-lanz-cicm-cm
>
> =3D Goals and Milestones =3D
> TBD =A0 WGLC on draft-lanz-cicm-lm
> TBD =A0 WGLC on draft-lanz-cicm
> TBD =A0 WGLC on draft-lanz-cicm-mm
> TBD =A0 WGLC on draft-lanz-cicm-km
> TBD =A0 Submit draft-lanz-cicm to the IESG as Proposed Standard
> _______________________________________________
> cicm mailing list
> cicm@ietf.org
> https://www.ietf.org/mailman/listinfo/cicm
>



--=20
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." =A0 =A0 =A0 =A0-- Nathaniel Borenstein

From jfitton@harris.com  Tue May 17 05:15:24 2011
Return-Path: <jfitton@harris.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 9A29AE0715 for <cicm@ietfa.amsl.com>; Tue, 17 May 2011 05:15:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 jgL6cvdrZ9rS for <cicm@ietfa.amsl.com>; Tue, 17 May 2011 05:15:23 -0700 (PDT)
Received: from mlbe2k2.cs.myharris.net (mlbe2k2.cs.myharris.net [137.237.90.89]) by ietfa.amsl.com (Postfix) with ESMTP id 36075E0743 for <cicm@ietf.org>; Tue, 17 May 2011 05:15:22 -0700 (PDT)
Received: from mail pickup service by mlbe2k2.cs.myharris.net with Microsoft SMTPSVC; Tue, 17 May 2011 08:15:20 -0400
Received: from mlbrst2.cs.myharris.net ([137.237.89.11]) by mlbe2k2.cs.myharris.net with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 17 May 2011 08:15:18 -0400
Received: from MLBMXHT1.cs.myharris.net ([137.237.89.19]) by mlbrst2.cs.myharris.net with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 17 May 2011 08:15:18 -0400
Received: from ROCMXCAHT22.cs.myharris.net (10.64.228.25) by MLBMXHT1.cs.myharris.net (137.237.89.19) with Microsoft SMTP Server (TLS) id 8.2.254.0; Tue, 17 May 2011 08:15:18 -0400
Received: from ROCMXUS21.cs.myharris.net ([fe80::1161:8dee:2d75:5ac]) by ROCMXCAHT22.cs.myharris.net ([::1]) with mapi id 14.01.0270.001; Tue, 17 May 2011 08:15:17 -0400
From: "Fitton, John" <jfitton@harris.com>
To: CICM Discussion List <cicm@ietf.org>
Thread-Topic: [cicm] BoF Request for CICM at IETF 81
Thread-Index: AQHME/x27Om8i3qNBEKAIbc8ql6/r5SQ7PB9
Date: Tue, 17 May 2011 12:15:17 +0000
Message-ID: <06D46EAFF7D0C946BEC108DB7CCDC9A608B2A3A6@ROCMXUS21.cs.myharris.net>
References: <F9AB58FA72BAE7449E7723791F6993ED05D2FB0B91@IMCMBX3.MITRE.ORG>, <7EDDD87A9A1D7F4DB6F78BC55AA495502B7748@0461-its-exmb09.us.saic.com> <06D46EAFF7D0C946BEC108DB7CCDC9A608B282C8@ROCMXUS21.cs.myharris.net> <9742CF2025F5FD41AAF6D9B8679F806201EF4EDE@vcaexch06.hq.corp.viasat.com>, <E48B962F2B71EC4C97EF42A839D0F2DE05875E6FD7@IMCMBX1.MITRE.ORG>
In-Reply-To: <E48B962F2B71EC4C97EF42A839D0F2DE05875E6FD7@IMCMBX1.MITRE.ORG>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.64.228.53]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 17 May 2011 12:15:18.0811 (UTC) FILETIME=[163F0EB0:01CC148C]
Subject: Re: [cicm] BoF Request for CICM at IETF 81
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: Tue, 17 May 2011 12:15:24 -0000

I agree that the API does not provide "high assurance" nor does it "offers =
security domain separation" as stated in the draft Charter.  How about stat=
ing it like this:

"The API is intended to support high assurance cryptography by allowing for=
 security domain separation and includes provisions for enhanced module, ke=
y and channel management capabilities that are vendor agnostic."  The fact =
that there is an API is what allows for security domain separation.=20

While an API in and of itself cannot be "high assurance", it is possible to=
 define security policy concerning its application and use that would enabl=
e a high assurance implementation. A question then arises, is should the AP=
I include a section which includes API related security policies which supp=
ort high assurance applications. =20
________________________________________
From: Cottrell Jr., James R. [jxc@mitre.org]
Sent: Monday, May 16, 2011 1:08 PM
To: CICM Discussion List
Subject: Re: [cicm] BoF Request for CICM at IETF 81

Dennis,

I agree that the API by itself cannot provide "high assurance" but this API=
 has been designed to be targeted for use in high assurance applications.  =
Not sure how to work this thought into your suggested charter wording.

Jim C.

-----Original Message-----
From: cicm-bounces@ietf.org [mailto:cicm-bounces@ietf.org] On Behalf Of Bou=
rget, Dennis
Sent: Friday, May 13, 2011 6:12 PM
To: CICM Discussion List
Subject: Re: [cicm] BoF Request for CICM at IETF 81

I just don't see how any API can provide "high assurance", it is the
implementation of the API, host platform and operating system that would
need to be evaluated to FIPS 140-2 or Common Criteria.  For example, the
API does not and cannot provide domain separation, I suggest that we
strike that text from the charter.

Perhaps the following:

The Common Interface to Cryptographic Modules (CICM) API defines a
"standardized" application interface
for the security services provided by cryptographic modules developed by
multiple vendors. The API supports
security domain separation, and enhanced module, key, and channel
management capabilities that is vendor agnostic.

-----Original Message-----
From: cicm-bounces@ietf.org [mailto:cicm-bounces@ietf.org] On Behalf Of
Fitton, John
Sent: Friday, May 13, 2011 2:56 PM
To: CICM Discussion List
Subject: Re: [cicm] BoF Request for CICM at IETF 81

I would suggest defining High Assurance in terms of  FIPS-140-2 Level 4.
Of course FIPS 140-2 refers to the Common Criteria AL4 or higher, but
does offer specific criteria to be used in the evaluation. That being
said, however, while the stated goal is for a high assurance API, there
is nothing in principal which limits the API to high assurance
applications.

I would also point out that the Orange Book (as was the entire original
Rainbow series) was targeted at information processing systems. These
systems were essentially large data bases with many users gaining access
via dedicated terminals, and there are those who would argue that the
old  assurance levels, were also not that well defined. As these system
evolved and  internet access was introdouced there was additional
volumes created to address some of the security issues involved.

I would argue that nothing in the Rainbow series specifically addressed
security requirements or assurance levels for cryptographic modules.

One advantage of the Common Criteria, is that the meaning of any given
Assurance Level for a given application (e.g. a Cryptographic module)
can be defined through an evaluation profile. Another advantage is that
it is an internationally recognized set of criteria with a group of
international evaluation/certification bodies.

________________________________________
From: Davidson, John A. [JOHN.A.DAVIDSON@saic.com]
Sent: Friday, May 13, 2011 1:34 PM
To: CICM Discussion List
Subject: Re: [cicm] BoF Request for CICM at IETF 81

Lev,
I am wondering if we need to (or even can) clarify what we mean by High
Assurance.  Assurance levels were fairly well-defined under the Orange
Book but that has been grayed out by the move to international flavored
Common Criteria.  Today when we say we are addressing HA, it is no
longer clear to me whether we mean to restrict our view to approaches
that are logically "closed form," or if we mean just a better version of
"best effort," whatever that is.

In my mind, there are IA critical capabilities we can support with one
that may be ruled out by the other.

Thanks,
John


-----Original Message-----
From: cicm-bounces@ietf.org [mailto:cicm-bounces@ietf.org] On Behalf Of
Novikov, Lev
Sent: Friday, May 13, 2011 10:01 AM
To: saag@ietf.org
Cc: CICM Discussion List (cicm@ietf.org)
Subject: [cicm] BoF Request for CICM at IETF 81

I'm formally requesting a BoF at IETF 81 to form a CICM WG based on the
draft charter below.
Updated version at: http://code.google.com/p/ietf-cicm/wiki/WGCharter
Discussion also at: cicm@ietf.org

Thanks,
Lev

Draft CICM Working Group Charter

=3D Description of Working Group =3D
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

=3D Goals and Milestones =3D
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
cicm@ietf.org
https://www.ietf.org/mailman/listinfo/cicm
_______________________________________________
cicm mailing list
cicm@ietf.org
https://www.ietf.org/mailman/listinfo/cicm
_______________________________________________
cicm mailing list
cicm@ietf.org
https://www.ietf.org/mailman/listinfo/cicm=

From JOHN.A.DAVIDSON@saic.com  Tue May 17 07:28:37 2011
Return-Path: <JOHN.A.DAVIDSON@saic.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 2FA03E0665 for <cicm@ietfa.amsl.com>; Tue, 17 May 2011 07:28:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 TshYzcnCureD for <cicm@ietfa.amsl.com>; Tue, 17 May 2011 07:28:35 -0700 (PDT)
Received: from cpmx.mail.saic.com (cpmx.mail.saic.com [139.121.17.160]) by ietfa.amsl.com (Postfix) with ESMTP id 0F9FBE0658 for <cicm@ietf.org>; Tue, 17 May 2011 07:28:34 -0700 (PDT)
Received: from 0599-its-sbg02.saic.com ([139.121.20.253] [139.121.20.253]) by cpmx.mail.saic.com with ESMTP id BT-MMP-10113201 for cicm@ietf.org; Tue, 17 May 2011 07:28:21 -0700
X-AuditID: 8b7911db-b7c5bae0000051d3-e7-4dd28605b33d
Received: from 0599-its-exbh01.us.saic.com (cpe-z7-si-srcnat.sw.saic.com [139.121.20.253]) by 0599-its-sbg02.saic.com (Symantec Brightmail Gateway) with SMTP id BC.E4.20947.50682DD4; Tue, 17 May 2011 07:28:21 -0700 (PDT)
Received: from 0461-its-exmb09.us.saic.com ([10.8.67.20]) by 0599-its-exbh01.us.saic.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 17 May 2011 07:28:21 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 17 May 2011 07:28:20 -0700
Message-Id: <7EDDD87A9A1D7F4DB6F78BC55AA495502B7752@0461-its-exmb09.us.saic.com>
In-Reply-To: <06D46EAFF7D0C946BEC108DB7CCDC9A608B2A3A6@ROCMXUS21.cs.myharris.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [cicm] BoF Request for CICM at IETF 81
Thread-Index: AQHME/x27Om8i3qNBEKAIbc8ql6/r5SQ7PB9gAAj54A=
References: <F9AB58FA72BAE7449E7723791F6993ED05D2FB0B91@IMCMBX3.MITRE.ORG>, <7EDDD87A9A1D7F4DB6F78BC55AA495502B7748@0461-its-exmb09.us.saic.com><06D46EAFF7D0C946BEC108DB7CCDC9A608B282C8@ROCMXUS21.cs.myharris.net><9742CF2025F5FD41AAF6D9B8679F806201EF4EDE@vcaexch06.hq.corp.viasat.com>, <E48B962F2B71EC4C97EF42A839D0F2DE05875E6FD7@IMCMBX1.MITRE.ORG> <06D46EAFF7D0C946BEC108DB7CCDC9A608B2A3A6@ROCMXUS21.cs.myharris.net>
From: "Davidson, John A." <JOHN.A.DAVIDSON@saic.com>
To: "CICM Discussion List" <cicm@ietf.org>
X-OriginalArrivalTime: 17 May 2011 14:28:21.0355 (UTC) FILETIME=[AC369BB0:01CC149E]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [cicm] BoF Request for CICM at IETF 81
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: Tue, 17 May 2011 14:28:37 -0000

This may be a case for just leaving out the "high assurance" (HA) part.
Our APIs support that so-called "necessary evil" bypass which (from my
distorted COMPUSEC background POV) technically contradicts HA.  (From my
background, HA originally implied cross domain flow but only in the down
direction.)  Despite what *any* APIs may aspire to do, an MLS HA OE can
impose rigorous HA on any kind of APIs.  However, if it does, that can
break some applications that expect use APIs that enable prohibited flow
(down.) =20

As originally applied to COMPUSEC, HA loosely referred to mechanisms
intended to *absolutely* enforce a particular policy and separate
hierarchical security levels (as mathematical "lattices") underneath
software systems.  As the line between software and cryptos blurs, HA
has migrated into crypto lingo, but it doesn't seem to fit well when
cryptos (and SDRs) are approached as HW wires and components rather than
software. =20

In my opinion, there are two approaches to IA in a complex system of
systems, like a SDR.  One is the classical HA COMPUSEC approach that
precludes flow up and allows flow down.  I realize this is contentious,
but I can only say this has a long history of working fine in MLS
processing environments without needing bypass.  The other approach is
the way we did hardware (HW) cryptos, which allows bypass provided it is
"not harmful" (epitomized by header bypass).   There are technical IA
issues with doing the latter with HA because it allows flow down and we
lack a rigorous HA criteria for "not harmful."  That is why bypass is
termed "evil" in the phrase "necessary evil."  I think that while a SDR
contains a crypto, it is more of a generic software MLS application than
a crypto with wires and components. =20

To me, supporting HA means supporting the approach above that does not
require crypto bypass, like we used in Blacker, an MLS software FEP.  It
still moved unclassified header to the unclassified processes, but by a
COMPUSEC scheme of isolating flow at the source instead of trying to
inspect bypass object content downstream.  Our APIs allow either.  Since
our APIs do support bypass, it is up to the users not to try to use it
if they expect to run in a conventional HA OE.  I know everyone wants to
call everything HA, (myself included) but to me, allowing HA is not
exactly "supporting" everybody's view of HA, it just blurs the line
between "best effort" and HA.  Isn't our API more about being generic
and allowing the user to make design choices between best effort and
rigorous HA? =20

-----Original Message-----
From: cicm-bounces@ietf.org [mailto:cicm-bounces@ietf.org] On Behalf Of
Fitton, John
Sent: Tuesday, May 17, 2011 5:15 AM
To: CICM Discussion List
Subject: Re: [cicm] BoF Request for CICM at IETF 81

I agree that the API does not provide "high assurance" nor does it
"offers security domain separation" as stated in the draft Charter.  How
about stating it like this:

"The API is intended to support high assurance cryptography by allowing
for security domain separation and includes provisions for enhanced
module, key and channel management capabilities that are vendor
agnostic."  The fact that there is an API is what allows for security
domain separation.=20

While an API in and of itself cannot be "high assurance", it is possible
to define security policy concerning its application and use that would
enable a high assurance implementation. A question then arises, is
should the API include a section which includes API related security
policies which support high assurance applications. =20
________________________________________
From: Cottrell Jr., James R. [jxc@mitre.org]
Sent: Monday, May 16, 2011 1:08 PM
To: CICM Discussion List
Subject: Re: [cicm] BoF Request for CICM at IETF 81

Dennis,

I agree that the API by itself cannot provide "high assurance" but this
API has been designed to be targeted for use in high assurance
applications.  Not sure how to work this thought into your suggested
charter wording.

Jim C.

-----Original Message-----
From: cicm-bounces@ietf.org [mailto:cicm-bounces@ietf.org] On Behalf Of
Bourget, Dennis
Sent: Friday, May 13, 2011 6:12 PM
To: CICM Discussion List
Subject: Re: [cicm] BoF Request for CICM at IETF 81

I just don't see how any API can provide "high assurance", it is the
implementation of the API, host platform and operating system that would
need to be evaluated to FIPS 140-2 or Common Criteria.  For example, the
API does not and cannot provide domain separation, I suggest that we
strike that text from the charter.

Perhaps the following:

The Common Interface to Cryptographic Modules (CICM) API defines a
"standardized" application interface
for the security services provided by cryptographic modules developed by
multiple vendors. The API supports
security domain separation, and enhanced module, key, and channel
management capabilities that is vendor agnostic.

-----Original Message-----
From: cicm-bounces@ietf.org [mailto:cicm-bounces@ietf.org] On Behalf Of
Fitton, John
Sent: Friday, May 13, 2011 2:56 PM
To: CICM Discussion List
Subject: Re: [cicm] BoF Request for CICM at IETF 81

I would suggest defining High Assurance in terms of  FIPS-140-2 Level 4.
Of course FIPS 140-2 refers to the Common Criteria AL4 or higher, but
does offer specific criteria to be used in the evaluation. That being
said, however, while the stated goal is for a high assurance API, there
is nothing in principal which limits the API to high assurance
applications.

I would also point out that the Orange Book (as was the entire original
Rainbow series) was targeted at information processing systems. These
systems were essentially large data bases with many users gaining access
via dedicated terminals, and there are those who would argue that the
old  assurance levels, were also not that well defined. As these system
evolved and  internet access was introdouced there was additional
volumes created to address some of the security issues involved.

I would argue that nothing in the Rainbow series specifically addressed
security requirements or assurance levels for cryptographic modules.

One advantage of the Common Criteria, is that the meaning of any given
Assurance Level for a given application (e.g. a Cryptographic module)
can be defined through an evaluation profile. Another advantage is that
it is an internationally recognized set of criteria with a group of
international evaluation/certification bodies.

________________________________________
From: Davidson, John A. [JOHN.A.DAVIDSON@saic.com]
Sent: Friday, May 13, 2011 1:34 PM
To: CICM Discussion List
Subject: Re: [cicm] BoF Request for CICM at IETF 81

Lev,
I am wondering if we need to (or even can) clarify what we mean by High
Assurance.  Assurance levels were fairly well-defined under the Orange
Book but that has been grayed out by the move to international flavored
Common Criteria.  Today when we say we are addressing HA, it is no
longer clear to me whether we mean to restrict our view to approaches
that are logically "closed form," or if we mean just a better version of
"best effort," whatever that is.

In my mind, there are IA critical capabilities we can support with one
that may be ruled out by the other.

Thanks,
John


-----Original Message-----
From: cicm-bounces@ietf.org [mailto:cicm-bounces@ietf.org] On Behalf Of
Novikov, Lev
Sent: Friday, May 13, 2011 10:01 AM
To: saag@ietf.org
Cc: CICM Discussion List (cicm@ietf.org)
Subject: [cicm] BoF Request for CICM at IETF 81

I'm formally requesting a BoF at IETF 81 to form a CICM WG based on the
draft charter below.
Updated version at: http://code.google.com/p/ietf-cicm/wiki/WGCharter
Discussion also at: cicm@ietf.org

Thanks,
Lev

Draft CICM Working Group Charter

=3D Description of Working Group =3D
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

=3D Goals and Milestones =3D
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
cicm@ietf.org
https://www.ietf.org/mailman/listinfo/cicm
_______________________________________________
cicm mailing list
cicm@ietf.org
https://www.ietf.org/mailman/listinfo/cicm
_______________________________________________
cicm mailing list
cicm@ietf.org
https://www.ietf.org/mailman/listinfo/cicm
_______________________________________________
cicm mailing list
cicm@ietf.org
https://www.ietf.org/mailman/listinfo/cicm

From jxc@mitre.org  Tue May 17 08:06:12 2011
Return-Path: <jxc@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 AE5DDE0840 for <cicm@ietfa.amsl.com>; Tue, 17 May 2011 08:06:12 -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 KfFV6tLSLzo3 for <cicm@ietfa.amsl.com>; Tue, 17 May 2011 08:06:11 -0700 (PDT)
Received: from smtpksrv1.mitre.org (smtpksrv1.mitre.org [198.49.146.77]) by ietfa.amsl.com (Postfix) with ESMTP id 8BDDAE083E for <cicm@ietf.org>; Tue, 17 May 2011 08:06:11 -0700 (PDT)
Received: from smtpksrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 6083B21B1564 for <cicm@ietf.org>; Tue, 17 May 2011 11:06:10 -0400 (EDT)
Received: from imchub1.MITRE.ORG (imchub1.mitre.org [129.83.29.73]) by smtpksrv1.mitre.org (Postfix) with ESMTP id 5970E21B146A for <cicm@ietf.org>; Tue, 17 May 2011 11:06:10 -0400 (EDT)
Received: from IMCMBX1.MITRE.ORG ([129.83.29.204]) by imchub1.MITRE.ORG ([129.83.29.73]) with mapi; Tue, 17 May 2011 11:06:10 -0400
From: "Cottrell Jr., James R." <jxc@mitre.org>
To: CICM Discussion List <cicm@ietf.org>
Date: Tue, 17 May 2011 11:06:08 -0400
Thread-Topic: [cicm] BoF Request for CICM at IETF 81
Thread-Index: AcwULPctLU/0vGXGSRy/ae2qzI1emwAAcUnAAB1LxlA=
Message-ID: <E48B962F2B71EC4C97EF42A839D0F2DE05875E7384@IMCMBX1.MITRE.ORG>
References: <F9AB58FA72BAE7449E7723791F6993ED05D308F8B0@IMCMBX3.MITRE.ORG> <9742CF2025F5FD41AAF6D9B8679F806201EF55D1@vcaexch06.hq.corp.viasat.com>
In-Reply-To: <9742CF2025F5FD41AAF6D9B8679F806201EF55D1@vcaexch06.hq.corp.viasat.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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [cicm] BoF Request for CICM at IETF 81
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: Tue, 17 May 2011 15:06:12 -0000

Sound good.

-----Original Message-----
From: cicm-bounces@ietf.org [mailto:cicm-bounces@ietf.org] On Behalf Of Bou=
rget, Dennis
Sent: Monday, May 16, 2011 9:11 PM
To: CICM Discussion List
Subject: Re: [cicm] BoF Request for CICM at IETF 81

Again, I may be picking nits, but I still don't believe that the API
offers any security domain separation. =20
I would just delete "and thus offers".

It would then read:=20
"The API is intended to support high assurance cryptography, security
domain separation, and=20
 enhanced module, key, and channel management capabilities that are
vendor agnostic."

-----Original Message-----
From: cicm-bounces@ietf.org [mailto:cicm-bounces@ietf.org] On Behalf Of
Novikov, Lev
Sent: Monday, May 16, 2011 5:54 PM
To: CICM Discussion List
Subject: Re: [cicm] BoF Request for CICM at IETF 81

On 2011-05-13 at 13:34, John Davidson wrote:
> I am wondering if we need to (or even can) clarify what we mean by=20
> High Assurance.

On 2011-05-13 at 17:56, John Fitton wrote:
> I would suggest defining High Assurance in terms of  FIPS-140-2=20
> Level 4. Of course FIPS 140-2 refers to the Common Criteria AL4 or=20
> higher, but does offer specific criteria to be used in the evaluation.
> That being said, however, while the stated goal is for a high=20
> assurance API, there is nothing in principal which limits the API to=20
> high assurance applications.

On 2011-05-14 at 18:12, Dennis Bourget wrote:
> I just don't see how any API can provide "high assurance", it is the
> implementation of the API, host platform and operating system that=20
> would need to be evaluated to FIPS 140-2 or Common Criteria.  For=20
> example, the API does not and cannot provide domain separation, I=20
> suggest that we strike that text from the charter.

On 2011-05-16 at 13:08, Jim Cottrell wrote:
> I agree that the API by itself cannot provide "high assurance" but=20
> this API has been designed to be targeted for use in high assurance=20
> applications.

Interesting discussion.=20

What do people think of the following? It is based on Dennis's
suggestion,=20
but emphasizes that the API targets high assurance environments.

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

Lev
_______________________________________________
cicm mailing list
cicm@ietf.org
https://www.ietf.org/mailman/listinfo/cicm
_______________________________________________
cicm mailing list
cicm@ietf.org
https://www.ietf.org/mailman/listinfo/cicm

From prvs=11145f0f8=Hema.Krishnamurthy@itt.com  Tue May 17 08:31:59 2011
Return-Path: <prvs=11145f0f8=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 70F1DE06C6 for <cicm@ietfa.amsl.com>; Tue, 17 May 2011 08:31:59 -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 Dd6YGqig-WBV for <cicm@ietfa.amsl.com>; Tue, 17 May 2011 08:31:59 -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 DCB16E069C for <cicm@ietf.org>; Tue, 17 May 2011 08:31:58 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApsEAFCU0k0KHOwC/2dsb2JhbACnEchHhhkElEmKWQ
X-IronPort-AV: E=Sophos;i="4.65,225,1304294400"; d="scan'208";a="96155846"
Received: from usfwa1excas2.itt.net ([10.28.236.2]) by cip-fwa-c1.itt.com with ESMTP/TLS/AES128-SHA; 17 May 2011 15:31:57 +0000
Received: from fwexhub5.itt.net (10.32.76.115) by USFWA1EXCAS2.itt.net (10.28.236.2) with Microsoft SMTP Server (TLS) id 8.2.255.0; Tue, 17 May 2011 11:31:57 -0400
Received: from CSFWCAS1.cs.de.ittind.com (10.32.129.151) by fwexhub5.itt.net (10.32.76.115) with Microsoft SMTP Server (TLS) id 8.2.255.0; Tue, 17 May 2011 11:31:56 -0400
Received: from CSFWMAIL1.cs.de.ittind.com ([10.32.129.153]) by CSFWCAS1.cs.de.ittind.com ([10.32.129.151]) with mapi; Tue, 17 May 2011 11:31:56 -0400
From: "Krishnamurthy, Hema - ES" <Hema.Krishnamurthy@itt.com>
To: CICM Discussion List <cicm@ietf.org>
Date: Tue, 17 May 2011 11:31:54 -0400
Thread-Topic: Ports
Thread-Index: AcvecAHnin9Ov/v6QEyqL6Hw4PsUbwAA4gFQAAAHL3AAAELE4AAANbOwDYxz6uA=
Message-ID: <86150541B533894DAD5CB2DB3F4788520C6691D071@CSFWMAIL1.cs.de.ittind.com>
References: <86150541B533894DAD5CB2DB3F4788520B726163E9@CSFWMAIL1.cs.de.ittind.com> <F9AB58FA72BAE7449E7723791F6993ED05C244C32C@IMCMBX3.MITRE.ORG> <7EDDD87A9A1D7F4DB6F78BC55AA495502B7664@0461-its-exmb09.us.saic.com> <F9AB58FA72BAE7449E7723791F6993ED05C244C381@IMCMBX3.MITRE.ORG>
In-Reply-To: <F9AB58FA72BAE7449E7723791F6993ED05C244C381@IMCMBX3.MITRE.ORG>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [cicm] Ports
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: Tue, 17 May 2011 15:31:59 -0000

Lev,

Could you provide me some info on the usage of ports(remote/local) in the c=
hannel manager?

Hema


This e-mail and any files transmitted with it may be proprietary and are in=
tended solely for the use of the individual or entity to whom they are addr=
essed. 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 Corporati=
on. The recipient should check this e-mail and any attachments for the pres=
ence of viruses. ITT accepts no liability for any damage caused by any viru=
s transmitted by this e-mail.

From kevin.w.wall@gmail.com  Tue May 17 10:31:11 2011
Return-Path: <kevin.w.wall@gmail.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 03259E06DE for <cicm@ietfa.amsl.com>; Tue, 17 May 2011 10:31:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 S1-m4LFna0+O for <cicm@ietfa.amsl.com>; Tue, 17 May 2011 10:31:10 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id BDBABE06B0 for <cicm@ietf.org>; Tue, 17 May 2011 10:31:09 -0700 (PDT)
Received: by wwa36 with SMTP id 36so573213wwa.13 for <cicm@ietf.org>; Tue, 17 May 2011 10:31:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=tR34kF+uutP1MqD49si9Xl/975YcfHFcKovYhDPzWmI=; b=j5EbUO0+TX4X+mFE4HouVU88BEvoJBn6utv9vWkGaTLUdMzvxsVZGIjUdZYiMv93CE vjLuc2DM2aVCq0/mPgZYQfDFLxHBORpafYCUWbjSUV5NmeMCuGRySFnw22MRdgqxLHDQ 5VOln/8YZNyDPvB1FXGBbIdktVnqqYEwUV9w0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=tlffDPxijVYD0w8gQW4UrxoTUNkRQCg7/GPiEZX4iCoiqnOeS6os2JjgNOG5pfuyy6 PpBtj93GrrrMspvUCjgjI1aFUyKwSyOUe9Ks1REu87HCtHdLzdf3ai6HNS1yP/Z9388v AHvKt5Z9R9c/WHit7fpcj6b0+ZdD3V1reoLU4=
MIME-Version: 1.0
Received: by 10.227.6.219 with SMTP id a27mr899115wba.46.1305653468340; Tue, 17 May 2011 10:31:08 -0700 (PDT)
Received: by 10.227.136.83 with HTTP; Tue, 17 May 2011 10:31:08 -0700 (PDT)
Received: by 10.227.136.83 with HTTP; Tue, 17 May 2011 10:31:08 -0700 (PDT)
In-Reply-To: <E48B962F2B71EC4C97EF42A839D0F2DE05875E7384@IMCMBX1.MITRE.ORG>
References: <F9AB58FA72BAE7449E7723791F6993ED05D308F8B0@IMCMBX3.MITRE.ORG> <9742CF2025F5FD41AAF6D9B8679F806201EF55D1@vcaexch06.hq.corp.viasat.com> <E48B962F2B71EC4C97EF42A839D0F2DE05875E7384@IMCMBX1.MITRE.ORG>
Date: Tue, 17 May 2011 13:31:08 -0400
Message-ID: <BANLkTi=v0M1A_tLu6z7jCvMBVLq2tAMU-g@mail.gmail.com>
From: "Kevin W. Wall" <kevin.w.wall@gmail.com>
To: CICM Discussion List <cicm@ietf.org>
Content-Type: multipart/alternative; boundary=002215b02fba2e233504a37c2364
Subject: Re: [cicm] BoF Request for CICM at IETF 81
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: Tue, 17 May 2011 17:31:11 -0000

--002215b02fba2e233504a37c2364
Content-Type: text/plain; charset=ISO-8859-1

And while we're picking nits, should read "vendor NEUTRAL", not "vendor
agnostic"...unless you believe that nothing can be known / proven wrt the
existance of vendors. ;-)

-kevin
--
Kevin W. Wall
Sent from DroidX; please excuse typos.
On May 17, 2011 11:06 AM, "Cottrell Jr., James R." <jxc@mitre.org> wrote:
> Sound good.
>
> -----Original Message-----
> From: cicm-bounces@ietf.org [mailto:cicm-bounces@ietf.org] On Behalf Of
Bourget, Dennis
> Sent: Monday, May 16, 2011 9:11 PM
> To: CICM Discussion List
> Subject: Re: [cicm] BoF Request for CICM at IETF 81
>
> Again, I may be picking nits, but I still don't believe that the API
> offers any security domain separation.
> I would just delete "and thus offers".
>
> It would then read:
> "The API is intended to support high assurance cryptography, security
> domain separation, and
> enhanced module, key, and channel management capabilities that are
> vendor agnostic."
>
> -----Original Message-----
> From: cicm-bounces@ietf.org [mailto:cicm-bounces@ietf.org] On Behalf Of
> Novikov, Lev
> Sent: Monday, May 16, 2011 5:54 PM
> To: CICM Discussion List
> Subject: Re: [cicm] BoF Request for CICM at IETF 81
>
> On 2011-05-13 at 13:34, John Davidson wrote:
>> I am wondering if we need to (or even can) clarify what we mean by
>> High Assurance.
>
> On 2011-05-13 at 17:56, John Fitton wrote:
>> I would suggest defining High Assurance in terms of FIPS-140-2
>> Level 4. Of course FIPS 140-2 refers to the Common Criteria AL4 or
>> higher, but does offer specific criteria to be used in the evaluation.
>> That being said, however, while the stated goal is for a high
>> assurance API, there is nothing in principal which limits the API to
>> high assurance applications.
>
> On 2011-05-14 at 18:12, Dennis Bourget wrote:
>> I just don't see how any API can provide "high assurance", it is the
>> implementation of the API, host platform and operating system that
>> would need to be evaluated to FIPS 140-2 or Common Criteria. For
>> example, the API does not and cannot provide domain separation, I
>> suggest that we strike that text from the charter.
>
> On 2011-05-16 at 13:08, Jim Cottrell wrote:
>> I agree that the API by itself cannot provide "high assurance" but
>> this API has been designed to be targeted for use in high assurance
>> applications.
>
> Interesting discussion.
>
> What do people think of the following? It is based on Dennis's
> suggestion,
> but emphasizes that the API targets high assurance environments.
>
> The Common Interface to Cryptographic Modules (CICM) defines an
> application
> programming interface for the security services provided by
> cryptographic
> modules developed by multiple vendors. The API is intended to support
> high
> assurance cryptography, and thus offers security domain separation,
> and
> enhanced module, key, and channel management capabilities that are
> vendor
> agnostic.
>
> Lev
> _______________________________________________
> cicm mailing list
> cicm@ietf.org
> https://www.ietf.org/mailman/listinfo/cicm
> _______________________________________________
> cicm mailing list
> cicm@ietf.org
> https://www.ietf.org/mailman/listinfo/cicm
> _______________________________________________
> cicm mailing list
> cicm@ietf.org
> https://www.ietf.org/mailman/listinfo/cicm

--002215b02fba2e233504a37c2364
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<p>And while we&#39;re picking nits, should read &quot;vendor NEUTRAL&quot;=
, not &quot;vendor agnostic&quot;...unless you believe that nothing can be =
known / proven wrt the existance of vendors. ;-)</p>
<p>-kevin<br>
--<br>
Kevin W. Wall<br>
Sent from DroidX; please excuse typos.</p>
<div class=3D"gmail_quote">On May 17, 2011 11:06 AM, &quot;Cottrell Jr., Ja=
mes R.&quot; &lt;<a href=3D"mailto:jxc@mitre.org">jxc@mitre.org</a>&gt; wro=
te:<br type=3D"attribution">&gt; Sound good.<br>&gt; <br>&gt; -----Original=
 Message-----<br>
&gt; From: <a href=3D"mailto:cicm-bounces@ietf.org">cicm-bounces@ietf.org</=
a> [mailto:<a href=3D"mailto:cicm-bounces@ietf.org">cicm-bounces@ietf.org</=
a>] On Behalf Of Bourget, Dennis<br>&gt; Sent: Monday, May 16, 2011 9:11 PM=
<br>
&gt; To: CICM Discussion List<br>&gt; Subject: Re: [cicm] BoF Request for C=
ICM at IETF 81<br>&gt; <br>&gt; Again, I may be picking nits, but I still d=
on&#39;t believe that the API<br>&gt; offers any security domain separation=
.  <br>
&gt; I would just delete &quot;and thus offers&quot;.<br>&gt; <br>&gt; It w=
ould then read: <br>&gt; &quot;The API is intended to support high assuranc=
e cryptography, security<br>&gt; domain separation, and <br>&gt;  enhanced =
module, key, and channel management capabilities that are<br>
&gt; vendor agnostic.&quot;<br>&gt; <br>&gt; -----Original Message-----<br>=
&gt; From: <a href=3D"mailto:cicm-bounces@ietf.org">cicm-bounces@ietf.org</=
a> [mailto:<a href=3D"mailto:cicm-bounces@ietf.org">cicm-bounces@ietf.org</=
a>] On Behalf Of<br>
&gt; Novikov, Lev<br>&gt; Sent: Monday, May 16, 2011 5:54 PM<br>&gt; To: CI=
CM Discussion List<br>&gt; Subject: Re: [cicm] BoF Request for CICM at IETF=
 81<br>&gt; <br>&gt; On 2011-05-13 at 13:34, John Davidson wrote:<br>&gt;&g=
t; I am wondering if we need to (or even can) clarify what we mean by <br>
&gt;&gt; High Assurance.<br>&gt; <br>&gt; On 2011-05-13 at 17:56, John Fitt=
on wrote:<br>&gt;&gt; I would suggest defining High Assurance in terms of  =
FIPS-140-2 <br>&gt;&gt; Level 4. Of course FIPS 140-2 refers to the Common =
Criteria AL4 or <br>
&gt;&gt; higher, but does offer specific criteria to be used in the evaluat=
ion.<br>&gt;&gt; That being said, however, while the stated goal is for a h=
igh <br>&gt;&gt; assurance API, there is nothing in principal which limits =
the API to <br>
&gt;&gt; high assurance applications.<br>&gt; <br>&gt; On 2011-05-14 at 18:=
12, Dennis Bourget wrote:<br>&gt;&gt; I just don&#39;t see how any API can =
provide &quot;high assurance&quot;, it is the<br>&gt;&gt; implementation of=
 the API, host platform and operating system that <br>
&gt;&gt; would need to be evaluated to FIPS 140-2 or Common Criteria.  For =
<br>&gt;&gt; example, the API does not and cannot provide domain separation=
, I <br>&gt;&gt; suggest that we strike that text from the charter.<br>
&gt; <br>&gt; On 2011-05-16 at 13:08, Jim Cottrell wrote:<br>&gt;&gt; I agr=
ee that the API by itself cannot provide &quot;high assurance&quot; but <br=
>&gt;&gt; this API has been designed to be targeted for use in high assuran=
ce <br>
&gt;&gt; applications.<br>&gt; <br>&gt; Interesting discussion. <br>&gt; <b=
r>&gt; What do people think of the following? It is based on Dennis&#39;s<b=
r>&gt; suggestion, <br>&gt; but emphasizes that the API targets high assura=
nce environments.<br>
&gt; <br>&gt;   The Common Interface to Cryptographic Modules (CICM) define=
s an<br>&gt; application <br>&gt;   programming interface for the security =
services provided by<br>&gt; cryptographic <br>&gt;   modules developed by =
multiple vendors. The API is intended to support<br>
&gt; high <br>&gt;   assurance cryptography, and thus offers security domai=
n separation,<br>&gt; and <br>&gt;   enhanced module, key, and channel mana=
gement capabilities that are<br>&gt; vendor <br>&gt;   agnostic.<br>&gt; <b=
r>
&gt; Lev<br>&gt; _______________________________________________<br>&gt; ci=
cm mailing list<br>&gt; <a href=3D"mailto:cicm@ietf.org">cicm@ietf.org</a><=
br>&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/cicm">https://www.=
ietf.org/mailman/listinfo/cicm</a><br>
&gt; _______________________________________________<br>&gt; cicm mailing l=
ist<br>&gt; <a href=3D"mailto:cicm@ietf.org">cicm@ietf.org</a><br>&gt; <a h=
ref=3D"https://www.ietf.org/mailman/listinfo/cicm">https://www.ietf.org/mai=
lman/listinfo/cicm</a><br>
&gt; _______________________________________________<br>&gt; cicm mailing l=
ist<br>&gt; <a href=3D"mailto:cicm@ietf.org">cicm@ietf.org</a><br>&gt; <a h=
ref=3D"https://www.ietf.org/mailman/listinfo/cicm">https://www.ietf.org/mai=
lman/listinfo/cicm</a><br>
</div>

--002215b02fba2e233504a37c2364--

From lnovikov@mitre.org  Tue May 17 16:13:11 2011
Return-Path: <lnovikov@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 9D6E7E0792 for <cicm@ietfa.amsl.com>; Tue, 17 May 2011 16:13:11 -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 qSXcicWgcb4B for <cicm@ietfa.amsl.com>; Tue, 17 May 2011 16:13:11 -0700 (PDT)
Received: from smtpksrv1.mitre.org (smtpksrv1.mitre.org [198.49.146.77]) by ietfa.amsl.com (Postfix) with ESMTP id E6E30E068E for <cicm@ietf.org>; Tue, 17 May 2011 16:13:10 -0700 (PDT)
Received: from smtpksrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 9CB2A21B1243 for <cicm@ietf.org>; Tue, 17 May 2011 19:13:09 -0400 (EDT)
Received: from imchub1.MITRE.ORG (imchub1.mitre.org [129.83.29.73]) by smtpksrv1.mitre.org (Postfix) with ESMTP id 987B821B0640 for <cicm@ietf.org>; Tue, 17 May 2011 19:13:09 -0400 (EDT)
Received: from IMCMBX3.MITRE.ORG ([129.83.29.206]) by imchub1.MITRE.ORG ([129.83.29.73]) with mapi; Tue, 17 May 2011 19:13:09 -0400
From: "Novikov, Lev" <lnovikov@mitre.org>
To: CICM Discussion List <cicm@ietf.org>
Date: Tue, 17 May 2011 19:11:12 -0400
Thread-Topic: Ports
Thread-Index: AcwU57Xd8TBHgVd0Tl6sySOkZxy6CQ==
Message-ID: <F9AB58FA72BAE7449E7723791F6993ED05D308FCEE@IMCMBX3.MITRE.ORG>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [cicm] Ports
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: Tue, 17 May 2011 23:13:11 -0000

Hema,

On 2011-05-17 at 11:32, Hema Krishnamurthy wrote:
> Could you provide me some info on the usage of ports(remote/local) in the=
 channel manager?

Sure. I highly recommend you look at Figure 6 in the CICM Logical Model:
http://tools.ietf.org/html/draft-lanz-cicm-lm-00#section-5

I've reproduced it here.

                  Security Domain         Security Domain
                     Boundary                Boundary
                        .                       .
               +--------.--------+     +--------.--------+
    Client  --(a) Cryptographic (b)---(c) Cryptographic (d) -- Client
   Program X   |      Module     |     |      Module     |    Program Y
               +--------.--------+     +--------.--------+
                        .                       .

               X local    X remote     Y remote    Y local
               port (a)   port (b)     port (c)   port (d)

   Figure 6.  Local and Remote Port Nomenclature for Channels that
   Operate in Two Security Domains


The terms remote/local are relative to the client program. We chose these t=
erms to avoid directionality (e.g., input / output) because the direction d=
epends on the operation (e.g., encrypt / decrypt), but we need to specify t=
he ports consistently (regardless of the operation).

Let me know if this needs more elaboration.

Lev

From lnovikov@mitre.org  Wed May 18 05:07:23 2011
Return-Path: <lnovikov@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 24A64E06DC for <cicm@ietfa.amsl.com>; Wed, 18 May 2011 05:07:23 -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 sT5NMNZSX+my for <cicm@ietfa.amsl.com>; Wed, 18 May 2011 05:07:22 -0700 (PDT)
Received: from smtpksrv1.mitre.org (smtpksrv1.mitre.org [198.49.146.77]) by ietfa.amsl.com (Postfix) with ESMTP id 858F8E06BC for <cicm@ietf.org>; Wed, 18 May 2011 05:07:21 -0700 (PDT)
Received: from smtpksrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 584A121B1BEC for <cicm@ietf.org>; Wed, 18 May 2011 08:07:21 -0400 (EDT)
Received: from imchub1.MITRE.ORG (imchub1.mitre.org [129.83.29.73]) by smtpksrv1.mitre.org (Postfix) with ESMTP id 5340821B1BDC for <cicm@ietf.org>; Wed, 18 May 2011 08:07:21 -0400 (EDT)
Received: from IMCMBX3.MITRE.ORG ([129.83.29.206]) by imchub1.MITRE.ORG ([129.83.29.73]) with mapi; Wed, 18 May 2011 08:07:21 -0400
From: "Novikov, Lev" <lnovikov@mitre.org>
To: CICM Discussion List <cicm@ietf.org>
Date: Wed, 18 May 2011 08:07:20 -0400
Thread-Topic: [cicm] BoF Request for CICM at IETF 81
Thread-Index: AcwVVCMTkOAA39kjS2mWGlMpvXvrng==
Message-ID: <F9AB58FA72BAE7449E7723791F6993ED05D308FD4C@IMCMBX3.MITRE.ORG>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [cicm] BoF Request for CICM at IETF 81
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: Wed, 18 May 2011 12:07:23 -0000

On 2011-05-16 at 21:11, Dennis Bourget wrote:
> Again, I may be picking nits, but I still don't believe that the API
> offers any security domain separation.=20
> I would just delete "and thus offers".

On 2011-05-16 at 23:36, John Davidson wrote:
> Dennis wrote:  ...I still don't believe that the API offers any security=
=20
> domain separation. I wish I had written that!  Policy enforcement is not =
an=20
> API's thing, IMHO.

On 2011-05-17 at 13:31, Kevin Wall wrote:
> And while we're picking nits, should read "vendor NEUTRAL", not=20
> "vendor agnostic"...unless you believe that nothing can be known / proven=
=20
> wrt the existance of vendors. ;-)

Good points all. Updated.
http://code.google.com/p/ietf-cicm/wiki/WGCharter

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

On 2011-05-17 at 10:28, John Davidson wrote:
> This may be a case for just leaving out the "high assurance" (HA) part.
> [...]
> Isn't our API more about being generic and allowing the user to make desi=
gn=20
> choices between best effort and rigorous HA? =20

The reason we're referring to high assurance is because it is an important
differentiating factor between CICM and current commercial crypto APIs=20
(e.g., PKCS#11). CICM allows users to make a design choice that is not=20
available in other APIs-- a point that we need to stress to create this=20
Working Group. Otherwise, we are just a very large, generic API (and the IE=
TF
already has GSS-API: Generic Security Services API).

Thank you all for your feedback. Any other points we should clarify?
We'll be asking the Security Area Directors for permission to hold the BoF=
=20
next week (Friday), so let's make sure the charter is ironed out before the=
n.

Thanks,
Lev

From JOHN.A.DAVIDSON@saic.com  Wed May 18 06:53:12 2011
Return-Path: <JOHN.A.DAVIDSON@saic.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 BC798E0704 for <cicm@ietfa.amsl.com>; Wed, 18 May 2011 06:53:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
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 9zAcZJrSKMed for <cicm@ietfa.amsl.com>; Wed, 18 May 2011 06:53:12 -0700 (PDT)
Received: from cpmx.mail.saic.com (cpmx.mail.saic.com [139.121.17.160]) by ietfa.amsl.com (Postfix) with ESMTP id 24541E073A for <cicm@ietf.org>; Wed, 18 May 2011 06:53:11 -0700 (PDT)
Received: from 0599-its-sbg01.saic.com ([139.121.20.253] [139.121.20.253]) by cpmx.mail.saic.com with ESMTP id BT-MMP-96143 for cicm@ietf.org; Wed, 18 May 2011 06:52:57 -0700
X-AuditID: 8b791438-b7b0bae0000004fc-1c-4dd3cf39b534
Received: from 0599-its-exbh01.us.saic.com (cpe-z7-si-srcnat.sw.saic.com [139.121.20.253]) by 0599-its-sbg01.saic.com (Symantec Brightmail Gateway) with SMTP id 71.84.01276.93FC3DD4; Wed, 18 May 2011 06:52:57 -0700 (PDT)
Received: from 0461-its-exmb09.us.saic.com ([10.8.67.20]) by 0599-its-exbh01.us.saic.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 18 May 2011 06:52:57 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 18 May 2011 06:52:56 -0700
Message-Id: <7EDDD87A9A1D7F4DB6F78BC55AA495502B775C@0461-its-exmb09.us.saic.com>
In-Reply-To: <F9AB58FA72BAE7449E7723791F6993ED05D308FD4C@IMCMBX3.MITRE.ORG>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [cicm] BoF Request for CICM at IETF 81
Thread-Index: AcwVVCMTkOAA39kjS2mWGlMpvXvrngADfklA
References: <F9AB58FA72BAE7449E7723791F6993ED05D308FD4C@IMCMBX3.MITRE.ORG>
From: "Davidson, John A." <JOHN.A.DAVIDSON@saic.com>
To: "CICM Discussion List" <cicm@ietf.org>
X-OriginalArrivalTime: 18 May 2011 13:52:57.0158 (UTC) FILETIME=[E4819E60:01CC1562]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [cicm] BoF Request for CICM at IETF 81
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: Wed, 18 May 2011 13:53:12 -0000

Wow, what an important point, Lev. =20
Could you provide a brief list of features present in our APIs and
missing elsewhere?=20

-----Original Message-----
From: cicm-bounces@ietf.org [mailto:cicm-bounces@ietf.org] On Behalf Of
Novikov, Lev
Sent: Wednesday, May 18, 2011 5:07 AM
To: CICM Discussion List
Subject: Re: [cicm] BoF Request for CICM at IETF 81

On 2011-05-16 at 21:11, Dennis Bourget wrote:
> Again, I may be picking nits, but I still don't believe that the API
> offers any security domain separation.=20
> I would just delete "and thus offers".

On 2011-05-16 at 23:36, John Davidson wrote:
> Dennis wrote:  ...I still don't believe that the API offers any
security=20
> domain separation. I wish I had written that!  Policy enforcement is
not an=20
> API's thing, IMHO.

On 2011-05-17 at 13:31, Kevin Wall wrote:
> And while we're picking nits, should read "vendor NEUTRAL", not=20
> "vendor agnostic"...unless you believe that nothing can be known /
proven=20
> wrt the existance of vendors. ;-)

Good points all. Updated.
http://code.google.com/p/ietf-cicm/wiki/WGCharter

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

On 2011-05-17 at 10:28, John Davidson wrote:
> This may be a case for just leaving out the "high assurance" (HA)
part.
> [...]
> Isn't our API more about being generic and allowing the user to make
design=20
> choices between best effort and rigorous HA? =20

The reason we're referring to high assurance is because it is an
important
differentiating factor between CICM and current commercial crypto APIs=20
(e.g., PKCS#11). CICM allows users to make a design choice that is not=20
available in other APIs-- a point that we need to stress to create this=20
Working Group. Otherwise, we are just a very large, generic API (and the
IETF
already has GSS-API: Generic Security Services API).

Thank you all for your feedback. Any other points we should clarify?
We'll be asking the Security Area Directors for permission to hold the
BoF=20
next week (Friday), so let's make sure the charter is ironed out before
then.

Thanks,
Lev
_______________________________________________
cicm mailing list
cicm@ietf.org
https://www.ietf.org/mailman/listinfo/cicm

From dennis.bourget@viasat.com  Wed May 18 10:05:52 2011
Return-Path: <dennis.bourget@viasat.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 853CEE074C for <cicm@ietfa.amsl.com>; Wed, 18 May 2011 10:05:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 xUnPsRTQAkPB for <cicm@ietfa.amsl.com>; Wed, 18 May 2011 10:05:51 -0700 (PDT)
Received: from viasat.com (bateleur.viasat.com [199.106.52.160]) by ietfa.amsl.com (Postfix) with ESMTP id A6F94E0665 for <cicm@ietf.org>; Wed, 18 May 2011 10:05:51 -0700 (PDT)
Received: from ([172.20.1.71]) by bateleur.viasat.com with ESMTP  id H6GMFJ1.44500855; Wed, 18 May 2011 10:05:48 -0700
Received: from vcaexch06.hq.corp.viasat.com ([172.18.46.74]) by VCAEXCH02.hq.corp.viasat.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 18 May 2011 10:05:48 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 18 May 2011 10:05:05 -0700
Message-ID: <9742CF2025F5FD41AAF6D9B8679F806201FA66E7@vcaexch06.hq.corp.viasat.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [cicm] BoF Request for CICM at IETF 81
Thread-Index: AcwVVCMTkOAA39kjS2mWGlMpvXvrngAKYnRw
References: <F9AB58FA72BAE7449E7723791F6993ED05D308FD4C@IMCMBX3.MITRE.ORG>
From: "Bourget, Dennis" <dennis.bourget@viasat.com>
To: "CICM Discussion List" <cicm@ietf.org>
X-OriginalArrivalTime: 18 May 2011 17:05:48.0492 (UTC) FILETIME=[D58F10C0:01CC157D]
Subject: Re: [cicm] BoF Request for CICM at IETF 81
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: Wed, 18 May 2011 17:05:52 -0000

Lev, I am OK with the new wording.

-----Original Message-----
From: cicm-bounces@ietf.org [mailto:cicm-bounces@ietf.org] On Behalf Of
Novikov, Lev
Sent: Wednesday, May 18, 2011 5:07 AM
To: CICM Discussion List
Subject: Re: [cicm] BoF Request for CICM at IETF 81

On 2011-05-16 at 21:11, Dennis Bourget wrote:
> Again, I may be picking nits, but I still don't believe that the API
> offers any security domain separation.=20
> I would just delete "and thus offers".

On 2011-05-16 at 23:36, John Davidson wrote:
> Dennis wrote:  ...I still don't believe that the API offers any
security=20
> domain separation. I wish I had written that!  Policy enforcement is
not an=20
> API's thing, IMHO.

On 2011-05-17 at 13:31, Kevin Wall wrote:
> And while we're picking nits, should read "vendor NEUTRAL", not=20
> "vendor agnostic"...unless you believe that nothing can be known /
proven=20
> wrt the existance of vendors. ;-)

Good points all. Updated.
http://code.google.com/p/ietf-cicm/wiki/WGCharter

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

On 2011-05-17 at 10:28, John Davidson wrote:
> This may be a case for just leaving out the "high assurance" (HA)
part.
> [...]
> Isn't our API more about being generic and allowing the user to make
design=20
> choices between best effort and rigorous HA? =20

The reason we're referring to high assurance is because it is an
important
differentiating factor between CICM and current commercial crypto APIs=20
(e.g., PKCS#11). CICM allows users to make a design choice that is not=20
available in other APIs-- a point that we need to stress to create this=20
Working Group. Otherwise, we are just a very large, generic API (and the
IETF
already has GSS-API: Generic Security Services API).

Thank you all for your feedback. Any other points we should clarify?
We'll be asking the Security Area Directors for permission to hold the
BoF=20
next week (Friday), so let's make sure the charter is ironed out before
then.

Thanks,
Lev
_______________________________________________
cicm mailing list
cicm@ietf.org
https://www.ietf.org/mailman/listinfo/cicm

From jfitton@harris.com  Wed May 18 12:17:36 2011
Return-Path: <jfitton@harris.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 26FB3E06BB for <cicm@ietfa.amsl.com>; Wed, 18 May 2011 12:17:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 4h-QFTCayW2e for <cicm@ietfa.amsl.com>; Wed, 18 May 2011 12:17:35 -0700 (PDT)
Received: from mlbe2k1.cs.myharris.net (mlbe2k1.cs.myharris.net [137.237.90.88]) by ietfa.amsl.com (Postfix) with ESMTP id 04374E06B0 for <cicm@ietf.org>; Wed, 18 May 2011 12:17:33 -0700 (PDT)
Received: from mail pickup service by mlbe2k1.cs.myharris.net with Microsoft SMTPSVC; Wed, 18 May 2011 15:17:29 -0400
Received: from mlbrst2.cs.myharris.net ([137.237.89.11]) by mlbe2k1.cs.myharris.net with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 18 May 2011 15:17:24 -0400
Received: from MLBMXHTUS1.cs.myharris.net ([137.237.89.77]) by mlbrst2.cs.myharris.net with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 18 May 2011 15:17:23 -0400
Received: from ROCMXCAHT22.cs.myharris.net (10.64.228.25) by MLBMXHTUS1.cs.myharris.net (137.237.89.77) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 18 May 2011 15:17:22 -0400
Received: from ROCMXUS21.cs.myharris.net ([fe80::1161:8dee:2d75:5ac]) by ROCMXCAHT22.cs.myharris.net ([::1]) with mapi id 14.01.0270.001; Wed, 18 May 2011 15:17:21 -0400
From: "Fitton, John" <jfitton@harris.com>
To: CICM Discussion List <cicm@ietf.org>
Thread-Topic: [cicm] BoF Request for CICM at IETF 81
Thread-Index: AQHMFY4V7Om8i3qNBEKAIbc8ql6/r5SS9RyA
Date: Wed, 18 May 2011 19:17:21 +0000
Message-ID: <06D46EAFF7D0C946BEC108DB7CCDC9A608B32FD6@ROCMXUS21.cs.myharris.net>
References: <F9AB58FA72BAE7449E7723791F6993ED05D308FD4C@IMCMBX3.MITRE.ORG>
In-Reply-To: <F9AB58FA72BAE7449E7723791F6993ED05D308FD4C@IMCMBX3.MITRE.ORG>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.64.228.56]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 18 May 2011 19:17:23.0095 (UTC) FILETIME=[371BE270:01CC1590]
Subject: Re: [cicm] BoF Request for CICM at IETF 81
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: Wed, 18 May 2011 19:17:36 -0000

Lev, I am OK with your latest version.

-----Original Message-----
From: Novikov, Lev [mailto:lnovikov@mitre.org]=20
Sent: Wednesday, May 18, 2011 8:07 AM
To: CICM Discussion List
Subject: Re: [cicm] BoF Request for CICM at IETF 81

On 2011-05-16 at 21:11, Dennis Bourget wrote:
> Again, I may be picking nits, but I still don't believe that the API
> offers any security domain separation.=20
> I would just delete "and thus offers".

On 2011-05-16 at 23:36, John Davidson wrote:
> Dennis wrote:  ...I still don't believe that the API offers any security=
=20
> domain separation. I wish I had written that!  Policy enforcement is not =
an=20
> API's thing, IMHO.

On 2011-05-17 at 13:31, Kevin Wall wrote:
> And while we're picking nits, should read "vendor NEUTRAL", not=20
> "vendor agnostic"...unless you believe that nothing can be known / proven=
=20
> wrt the existance of vendors. ;-)

Good points all. Updated.
http://code.google.com/p/ietf-cicm/wiki/WGCharter

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

On 2011-05-17 at 10:28, John Davidson wrote:
> This may be a case for just leaving out the "high assurance" (HA) part.
> [...]
> Isn't our API more about being generic and allowing the user to make desi=
gn=20
> choices between best effort and rigorous HA? =20

The reason we're referring to high assurance is because it is an important
differentiating factor between CICM and current commercial crypto APIs=20
(e.g., PKCS#11). CICM allows users to make a design choice that is not=20
available in other APIs-- a point that we need to stress to create this=20
Working Group. Otherwise, we are just a very large, generic API (and the IE=
TF
already has GSS-API: Generic Security Services API).

Thank you all for your feedback. Any other points we should clarify?
We'll be asking the Security Area Directors for permission to hold the BoF=
=20
next week (Friday), so let's make sure the charter is ironed out before the=
n.

Thanks,
Lev


From lnovikov@mitre.org  Wed May 18 18:35:02 2011
Return-Path: <lnovikov@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 0AB81E06C2 for <cicm@ietfa.amsl.com>; Wed, 18 May 2011 18:35:02 -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=[AWL=0.000,  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 fdXdD25-DKZJ for <cicm@ietfa.amsl.com>; Wed, 18 May 2011 18:35:01 -0700 (PDT)
Received: from smtpksrv1.mitre.org (smtpksrv1.mitre.org [198.49.146.77]) by ietfa.amsl.com (Postfix) with ESMTP id 8962CE0674 for <cicm@ietf.org>; Wed, 18 May 2011 18:35:00 -0700 (PDT)
Received: from smtpksrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 0082D21B133F for <cicm@ietf.org>; Wed, 18 May 2011 21:35:00 -0400 (EDT)
Received: from imchub2.MITRE.ORG (imchub2.mitre.org [129.83.29.74]) by smtpksrv1.mitre.org (Postfix) with ESMTP id F018021B1333 for <cicm@ietf.org>; Wed, 18 May 2011 21:34:59 -0400 (EDT)
Received: from IMCMBX3.MITRE.ORG ([129.83.29.206]) by imchub2.MITRE.ORG ([129.83.29.74]) with mapi; Wed, 18 May 2011 21:34:59 -0400
From: "Novikov, Lev" <lnovikov@mitre.org>
To: CICM Discussion List <cicm@ietf.org>
Date: Wed, 18 May 2011 21:33:36 -0400
Thread-Topic: [cicm] BoF Request for CICM at IETF 81
Thread-Index: AcwVVCMTkOAA39kjS2mWGlMpvXvrngADfklAABSKvlA=
Message-ID: <F9AB58FA72BAE7449E7723791F6993ED05D30901B2@IMCMBX3.MITRE.ORG>
References: <F9AB58FA72BAE7449E7723791F6993ED05D308FD4C@IMCMBX3.MITRE.ORG> <7EDDD87A9A1D7F4DB6F78BC55AA495502B775C@0461-its-exmb09.us.saic.com>
In-Reply-To: <7EDDD87A9A1D7F4DB6F78BC55AA495502B775C@0461-its-exmb09.us.saic.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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [cicm] BoF Request for CICM at IETF 81
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: Thu, 19 May 2011 01:35:02 -0000

John,

On 2011-05-18 at 09:53 John Davidson wrote:
> Could you provide a brief list of features present in our APIs and
> missing elsewhere?

Clearly the biggest difference is the concept of domain separation; it impa=
cts the entire logical model, especially channel management.

Additionally, CICM defines more key and module management APIs than other c=
rypto APIs because of the more extensive management available in high assur=
ance devices.=20

See: http://tools.ietf.org/html/draft-lanz-cicm-lm-00#section-2

Lev

From prvs=113e76e90=Hema.Krishnamurthy@itt.com  Thu May 19 06:56:58 2011
Return-Path: <prvs=113e76e90=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 30EE9E07CB for <cicm@ietfa.amsl.com>; Thu, 19 May 2011 06:56:58 -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 rDcXF5AOVUD3 for <cicm@ietfa.amsl.com>; Thu, 19 May 2011 06:56:57 -0700 (PDT)
Received: from cip-fwa-c2.itt.com (cip-fwa-c2.itt.com [151.190.252.22]) by ietfa.amsl.com (Postfix) with ESMTP id 45107E07B0 for <cicm@ietf.org>; Thu, 19 May 2011 06:56:56 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AuwAADAg1U0KHOwH/2dsb2JhbACXUY80yXWGGQSUSYpZ
X-IronPort-AV: E=Sophos;i="4.65,237,1304294400"; d="scan'208";a="80847325"
Received: from usfwa1exhub3.itt.net ([10.28.236.7]) by cip-fwa-c2.itt.com with ESMTP/TLS/AES128-SHA; 19 May 2011 13:56:56 +0000
Received: from fwexhub5.itt.net (10.32.76.115) by USFWA1EXHUB3.itt.net (10.28.236.7) with Microsoft SMTP Server (TLS) id 8.2.255.0; Thu, 19 May 2011 09:56:55 -0400
Received: from CSFWCAS1.cs.de.ittind.com (10.32.129.151) by fwexhub5.itt.net (10.32.76.115) with Microsoft SMTP Server (TLS) id 8.2.255.0; Thu, 19 May 2011 09:56:55 -0400
Received: from CSFWMAIL1.cs.de.ittind.com ([10.32.129.153]) by CSFWCAS1.cs.de.ittind.com ([10.32.129.151]) with mapi; Thu, 19 May 2011 09:56:54 -0400
From: "Krishnamurthy, Hema - ES" <Hema.Krishnamurthy@itt.com>
To: CICM Discussion List <cicm@ietf.org>
Date: Thu, 19 May 2011 09:56:52 -0400
Thread-Topic: Ports
Thread-Index: AcwU57Xd8TBHgVd0Tl6sySOkZxy6CQBRN/NA
Message-ID: <86150541B533894DAD5CB2DB3F4788520C669C33BE@CSFWMAIL1.cs.de.ittind.com>
References: <F9AB58FA72BAE7449E7723791F6993ED05D308FCEE@IMCMBX3.MITRE.ORG>
In-Reply-To: <F9AB58FA72BAE7449E7723791F6993ED05D308FCEE@IMCMBX3.MITRE.ORG>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [cicm] Ports
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: Thu, 19 May 2011 13:56:58 -0000

Thanks Lev. That's helpful.

-----Original Message-----
From: cicm-bounces@ietf.org [mailto:cicm-bounces@ietf.org] On Behalf Of Nov=
ikov, Lev
Sent: Tuesday, May 17, 2011 4:11 PM
To: CICM Discussion List
Subject: Re: [cicm] Ports

Hema,

On 2011-05-17 at 11:32, Hema Krishnamurthy wrote:
> Could you provide me some info on the usage of ports(remote/local) in the=
 channel manager?

Sure. I highly recommend you look at Figure 6 in the CICM Logical Model:
http://tools.ietf.org/html/draft-lanz-cicm-lm-00#section-5

I've reproduced it here.

                  Security Domain         Security Domain
                     Boundary                Boundary
                        .                       .
               +--------.--------+     +--------.--------+
    Client  --(a) Cryptographic (b)---(c) Cryptographic (d) -- Client
   Program X   |      Module     |     |      Module     |    Program Y
               +--------.--------+     +--------.--------+
                        .                       .

               X local    X remote     Y remote    Y local
               port (a)   port (b)     port (c)   port (d)

   Figure 6.  Local and Remote Port Nomenclature for Channels that
   Operate in Two Security Domains


The terms remote/local are relative to the client program. We chose these t=
erms to avoid directionality (e.g., input / output) because the direction d=
epends on the operation (e.g., encrypt / decrypt), but we need to specify t=
he ports consistently (regardless of the operation).

Let me know if this needs more elaboration.

Lev
_______________________________________________
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 in=
tended solely for the use of the individual or entity to whom they are addr=
essed. 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 Corporati=
on. The recipient should check this e-mail and any attachments for the pres=
ence of viruses. ITT accepts no liability for any damage caused by any viru=
s transmitted by this e-mail.

From JOHN.A.DAVIDSON@saic.com  Thu May 19 07:49:28 2011
Return-Path: <JOHN.A.DAVIDSON@saic.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 8A3CBE06DD for <cicm@ietfa.amsl.com>; Thu, 19 May 2011 07:49:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 Dy6VGJ6Ed8L9 for <cicm@ietfa.amsl.com>; Thu, 19 May 2011 07:49:27 -0700 (PDT)
Received: from cpmx2.mail.saic.com (cpmx2.mail.saic.com [139.121.17.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6E618E06A1 for <cicm@ietf.org>; Thu, 19 May 2011 07:49:27 -0700 (PDT)
Received: from 0599-its-sbg03.saic.com ([139.121.20.253] [139.121.20.253]) by cpmx2.mail.saic.com with ESMTP id BT-MMP-308547 for cicm@ietf.org; Thu, 19 May 2011 07:49:23 -0700
X-AuditID: 8b79132a-b7bc1ae000006a6c-74-4dd52df33613
Received: from 0599-its-exbh01.us.saic.com (cpe-z7-si-srcnat.sw.saic.com [139.121.20.253]) by 0599-its-sbg03.saic.com (Symantec Brightmail Gateway) with SMTP id 16.CB.27244.3FD25DD4; Thu, 19 May 2011 07:49:23 -0700 (PDT)
Received: from 0461-its-exmb09.us.saic.com ([10.8.67.20]) by 0599-its-exbh01.us.saic.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 19 May 2011 07:49:23 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 19 May 2011 07:49:23 -0700
Message-Id: <7EDDD87A9A1D7F4DB6F78BC55AA495502B7769@0461-its-exmb09.us.saic.com>
In-Reply-To: <F9AB58FA72BAE7449E7723791F6993ED05D30901B2@IMCMBX3.MITRE.ORG>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [cicm] BoF Request for CICM at IETF 81
Thread-Index: AcwVVCMTkOAA39kjS2mWGlMpvXvrngADfklAABSKvlAAH4Mb4A==
References: <F9AB58FA72BAE7449E7723791F6993ED05D308FD4C@IMCMBX3.MITRE.ORG><7EDDD87A9A1D7F4DB6F78BC55AA495502B775C@0461-its-exmb09.us.saic.com> <F9AB58FA72BAE7449E7723791F6993ED05D30901B2@IMCMBX3.MITRE.ORG>
From: "Davidson, John A." <JOHN.A.DAVIDSON@saic.com>
To: "CICM Discussion List" <cicm@ietf.org>
X-OriginalArrivalTime: 19 May 2011 14:49:23.0554 (UTC) FILETIME=[F15E6420:01CC1633]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [cicm] BoF Request for CICM at IETF 81
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: Thu, 19 May 2011 14:49:28 -0000

Lev, et al,=20
I would vote for it as it is now, but I might even be pinch more
satisfied if it said some of this kind of stuff: =20

The Common Interface to Cryptographic Modules (CICM) defines an
application programming interface for the security services provided by
cryptographic modules developed by multiple vendors. It provides
enhanced module, key and channel capabilities that are intended to be
vendor neutral.  The API is structured to enable it to operate in IA
environments that enforce domain separation.  This enables it to be
adaptable to high assurance IA applications. =20

-John

-----Original Message-----
From: cicm-bounces@ietf.org [mailto:cicm-bounces@ietf.org] On Behalf Of
Novikov, Lev
Sent: Wednesday, May 18, 2011 6:34 PM
To: CICM Discussion List
Subject: Re: [cicm] BoF Request for CICM at IETF 81

John,

On 2011-05-18 at 09:53 John Davidson wrote:
> Could you provide a brief list of features present in our APIs and
> missing elsewhere?

Clearly the biggest difference is the concept of domain separation; it
impacts the entire logical model, especially channel management.

Additionally, CICM defines more key and module management APIs than
other crypto APIs because of the more extensive management available in
high assurance devices.=20

See: http://tools.ietf.org/html/draft-lanz-cicm-lm-00#section-2

Lev
_______________________________________________
cicm mailing list
cicm@ietf.org
https://www.ietf.org/mailman/listinfo/cicm

From lnovikov@mitre.org  Sat May 21 19:31:53 2011
Return-Path: <lnovikov@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 C0F7CE0665 for <cicm@ietfa.amsl.com>; Sat, 21 May 2011 19:31:53 -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 hxo5yEibAfl5 for <cicm@ietfa.amsl.com>; Sat, 21 May 2011 19:31:52 -0700 (PDT)
Received: from smtpksrv1.mitre.org (smtpksrv1.mitre.org [198.49.146.77]) by ietfa.amsl.com (Postfix) with ESMTP id 7A09CE062B for <cicm@ietf.org>; Sat, 21 May 2011 19:31:51 -0700 (PDT)
Received: from smtpksrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 039E121B10F3 for <cicm@ietf.org>; Sat, 21 May 2011 22:31:51 -0400 (EDT)
Received: from imchub1.MITRE.ORG (imchub1.mitre.org [129.83.29.73]) by smtpksrv1.mitre.org (Postfix) with ESMTP id E6ADF21B0F28 for <cicm@ietf.org>; Sat, 21 May 2011 22:31:50 -0400 (EDT)
Received: from IMCMBX3.MITRE.ORG ([129.83.29.206]) by imchub1.MITRE.ORG ([129.83.29.73]) with mapi; Sat, 21 May 2011 22:31:51 -0400
From: "Novikov, Lev" <lnovikov@mitre.org>
To: CICM Discussion List <cicm@ietf.org>
Date: Sat, 21 May 2011 22:30:46 -0400
Thread-Topic: [cicm] BoF Request for CICM at IETF 81
Thread-Index: AcwVVCMTkOAA39kjS2mWGlMpvXvrngADfklAABSKvlAAH4Mb4AB8daJA
Message-ID: <F9AB58FA72BAE7449E7723791F6993ED05D3141508@IMCMBX3.MITRE.ORG>
References: <F9AB58FA72BAE7449E7723791F6993ED05D308FD4C@IMCMBX3.MITRE.ORG><7EDDD87A9A1D7F4DB6F78BC55AA495502B775C@0461-its-exmb09.us.saic.com> <F9AB58FA72BAE7449E7723791F6993ED05D30901B2@IMCMBX3.MITRE.ORG> <7EDDD87A9A1D7F4DB6F78BC55AA495502B7769@0461-its-exmb09.us.saic.com>
In-Reply-To: <7EDDD87A9A1D7F4DB6F78BC55AA495502B7769@0461-its-exmb09.us.saic.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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [cicm] BoF Request for CICM at IETF 81
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: Sun, 22 May 2011 02:31:53 -0000

John,

On 2011-05-19 at 10:49, John Davidson wrote:
> I would vote for it as it is now, but I might even be pinch more
> satisfied if it said some of this kind of stuff: =20
>=20
> The Common Interface to Cryptographic Modules (CICM) defines an
> application programming interface for the security services provided by
> cryptographic modules developed by multiple vendors. It provides
> enhanced module, key and channel capabilities that are intended to be
> vendor neutral.  The API is structured to enable it to operate in IA
> environments that enforce domain separation.  This enables it to be
> adaptable to high assurance IA applications. =20

It seems that you are trying to distinguish between environments that=20
enforce domain separation and high assurance environments. I've been thinki=
ng=20
about how to incorporate that point into our existing text.

What do people think about the following?

  The Common Interface to Cryptographic Modules (CICM) defines a=20
  vendor-neutral application programming interface for security services=20
  provided by cryptographic modules developed by multiple vendors. The API=
=20
  defines enhanced module, key, and channel capabilities and is structured =
to=20
  to enable applications to operate in environments that enforce security=20
  domain separation, such as high assurance environments.

While I can see the point being made, it might make it harder for people wh=
o=20
are not familiar with our fine distinctions (i.e. the rest of the IETF) to=
=20
understand why CICM is important.

I'm open to other suggestions.

Thanks,
Lev

From rfgraveman@gmail.com  Sun May 22 03:36:15 2011
Return-Path: <rfgraveman@gmail.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 E8185E071D for <cicm@ietfa.amsl.com>; Sun, 22 May 2011 03:36:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 6KdZc+-f0Icq for <cicm@ietfa.amsl.com>; Sun, 22 May 2011 03:36:15 -0700 (PDT)
Received: from mail-px0-f179.google.com (mail-px0-f179.google.com [209.85.212.179]) by ietfa.amsl.com (Postfix) with ESMTP id EA714E0719 for <cicm@ietf.org>; Sun, 22 May 2011 03:36:14 -0700 (PDT)
Received: by pxi2 with SMTP id 2so2990505pxi.38 for <cicm@ietf.org>; Sun, 22 May 2011 03:36:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=cNBbDtw5MZ5ZrdTOQ+Dz6Kx35YTkcGBz1YiCVEeB47o=; b=sSBxbcftFRnY+QgSXb3Hg16F6B3yaJnurXB+l/C87cNEseptWgrgZBfCt16nY67vKe gmrc1s5+fR1sXvPomUN1w1FBjQuVe+Am632OOBS1JiXO9qDKO76rO/etBRf57OxDtY3D aaFftNY/8RH8nP/ST3quahAjDxDa/RWPz5E9U=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=e+ZWf4BlxiarqEH4hMIQfLcK/i5zv4U6QwUPIfCkbD677AC3TjbaMdxRCEU8LDBwkJ s5swv+doF/ziCVFgNO+ydL/W0yoZgNT/K6umh/Eqb/sto+OlU+hiYvGv6IEbE6AKbo5e 9AToiTLRXBbmwnZocjeJllQ1fwwiwXM0jAPzo=
MIME-Version: 1.0
Received: by 10.68.0.105 with SMTP id 9mr138839pbd.346.1306060574423; Sun, 22 May 2011 03:36:14 -0700 (PDT)
Received: by 10.68.56.42 with HTTP; Sun, 22 May 2011 03:36:14 -0700 (PDT)
In-Reply-To: <F9AB58FA72BAE7449E7723791F6993ED05D3141508@IMCMBX3.MITRE.ORG>
References: <F9AB58FA72BAE7449E7723791F6993ED05D308FD4C@IMCMBX3.MITRE.ORG> <7EDDD87A9A1D7F4DB6F78BC55AA495502B775C@0461-its-exmb09.us.saic.com> <F9AB58FA72BAE7449E7723791F6993ED05D30901B2@IMCMBX3.MITRE.ORG> <7EDDD87A9A1D7F4DB6F78BC55AA495502B7769@0461-its-exmb09.us.saic.com> <F9AB58FA72BAE7449E7723791F6993ED05D3141508@IMCMBX3.MITRE.ORG>
Date: Sun, 22 May 2011 06:36:14 -0400
Message-ID: <BANLkTin+LN-7oN9zo4X1o7zPP49_komWrg@mail.gmail.com>
From: Richard Graveman <rfgraveman@gmail.com>
To: CICM Discussion List <cicm@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Mon, 23 May 2011 05:23:08 -0700
Subject: Re: [cicm] BoF Request for CICM at IETF 81
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: Sun, 22 May 2011 10:36:16 -0000

It seems to me that high assurance may well be needed in cases with
only one domain. Is that out of scope?

Richard Graveman

On Sat, May 21, 2011 at 10:30 PM, Novikov, Lev <lnovikov@mitre.org> wrote:
> John,
>
> On 2011-05-19 at 10:49, John Davidson wrote:
>> I would vote for it as it is now, but I might even be pinch more
>> satisfied if it said some of this kind of stuff:
>>
>> The Common Interface to Cryptographic Modules (CICM) defines an
>> application programming interface for the security services provided by
>> cryptographic modules developed by multiple vendors. It provides
>> enhanced module, key and channel capabilities that are intended to be
>> vendor neutral. =A0The API is structured to enable it to operate in IA
>> environments that enforce domain separation. =A0This enables it to be
>> adaptable to high assurance IA applications.
>
> It seems that you are trying to distinguish between environments that
> enforce domain separation and high assurance environments. I've been thin=
king
> about how to incorporate that point into our existing text.
>
> What do people think about the following?
>
> =A0The Common Interface to Cryptographic Modules (CICM) defines a
> =A0vendor-neutral application programming interface for security services
> =A0provided by cryptographic modules developed by multiple vendors. The A=
PI
> =A0defines enhanced module, key, and channel capabilities and is structur=
ed to
> =A0to enable applications to operate in environments that enforce securit=
y
> =A0domain separation, such as high assurance environments.
>
> While I can see the point being made, it might make it harder for people =
who
> are not familiar with our fine distinctions (i.e. the rest of the IETF) t=
o
> understand why CICM is important.
>
> I'm open to other suggestions.
>
> Thanks,
> Lev
> _______________________________________________
> cicm mailing list
> cicm@ietf.org
> https://www.ietf.org/mailman/listinfo/cicm
>

From lnovikov@mitre.org  Mon May 23 05:35:07 2011
Return-Path: <lnovikov@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 42427E077D for <cicm@ietfa.amsl.com>; Mon, 23 May 2011 05:35:07 -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=[AWL=0.000,  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 B8BBXZJLlPhX for <cicm@ietfa.amsl.com>; Mon, 23 May 2011 05:35:06 -0700 (PDT)
Received: from smtpksrv1.mitre.org (smtpksrv1.mitre.org [198.49.146.77]) by ietfa.amsl.com (Postfix) with ESMTP id BFF8DE0778 for <cicm@ietf.org>; Mon, 23 May 2011 05:35:06 -0700 (PDT)
Received: from smtpksrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id BF40021B16B4 for <cicm@ietf.org>; Mon, 23 May 2011 08:28:32 -0400 (EDT)
Received: from imchub1.MITRE.ORG (imchub1.mitre.org [129.83.29.73]) by smtpksrv1.mitre.org (Postfix) with ESMTP id BABA921B0CAE for <cicm@ietf.org>; Mon, 23 May 2011 08:28:32 -0400 (EDT)
Received: from IMCMBX3.MITRE.ORG ([129.83.29.206]) by imchub1.MITRE.ORG ([129.83.29.73]) with mapi; Mon, 23 May 2011 08:28:32 -0400
From: "Novikov, Lev" <lnovikov@mitre.org>
To: CICM Discussion List <cicm@ietf.org>
Date: Mon, 23 May 2011 08:27:45 -0400
Thread-Topic: [cicm] BoF Request for CICM at IETF 81
Thread-Index: AcwZRC6Pob1b0lJ0Ra+ifi8a4a6LwwAABowg
Message-ID: <F9AB58FA72BAE7449E7723791F6993ED05D314158A@IMCMBX3.MITRE.ORG>
References: <F9AB58FA72BAE7449E7723791F6993ED05D308FD4C@IMCMBX3.MITRE.ORG> <7EDDD87A9A1D7F4DB6F78BC55AA495502B775C@0461-its-exmb09.us.saic.com> <F9AB58FA72BAE7449E7723791F6993ED05D30901B2@IMCMBX3.MITRE.ORG> <7EDDD87A9A1D7F4DB6F78BC55AA495502B7769@0461-its-exmb09.us.saic.com> <F9AB58FA72BAE7449E7723791F6993ED05D3141508@IMCMBX3.MITRE.ORG> <BANLkTin+LN-7oN9zo4X1o7zPP49_komWrg@mail.gmail.com>
In-Reply-To: <BANLkTin+LN-7oN9zo4X1o7zPP49_komWrg@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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [cicm] BoF Request for CICM at IETF 81
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, 23 May 2011 12:35:07 -0000

Richard,

On 2011-05-22 at 06:36, Richard Graveman wrote:
> It seems to me that high assurance may well be needed in cases with
> only one domain. Is that out of scope?

Single domain use cases are definitely in scope; but they are very similar=
=20
(conceptually) to existing commercial crypto APIs. The ability to separate=
=20
domains is what sets CICM apart.

See:=20
"2.3. Single Security Domain" in CICM Logical Model
http://tools.ietf.org/html/draft-lanz-cicm-lm-00#section-2.3

"18. Single-Domain" in CICM Channel Management
http://tools.ietf.org/html/draft-lanz-cicm-cm-00#section-18

Lev

From JOHN.A.DAVIDSON@saic.com  Mon May 23 09:13:33 2011
Return-Path: <JOHN.A.DAVIDSON@saic.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 03016E06C0 for <cicm@ietfa.amsl.com>; Mon, 23 May 2011 09:13:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 VaeFtaLQgh3n for <cicm@ietfa.amsl.com>; Mon, 23 May 2011 09:13:32 -0700 (PDT)
Received: from cpmx.mail.saic.com (cpmx.mail.saic.com [139.121.17.160]) by ietfa.amsl.com (Postfix) with ESMTP id 52D39E069E for <cicm@ietf.org>; Mon, 23 May 2011 09:13:31 -0700 (PDT)
Received: from 0599-its-sbg01.saic.com ([139.121.20.253] [139.121.20.253]) by cpmx.mail.saic.com with ESMTP id BT-MMP-726163 for cicm@ietf.org; Mon, 23 May 2011 06:58:23 -0700
X-AuditID: 8b791438-b7b0bae0000004fc-77-4dda67fe7a6e
Received: from 0599-its-exbh01.us.saic.com (cpe-z7-si-srcnat.sw.saic.com [139.121.20.253]) by 0599-its-sbg01.saic.com (Symantec Brightmail Gateway) with SMTP id 0C.26.01276.EF76ADD4; Mon, 23 May 2011 06:58:22 -0700 (PDT)
Received: from 0461-its-exmb09.us.saic.com ([10.8.67.20]) by 0599-its-exbh01.us.saic.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 23 May 2011 06:58:22 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CC1951.7A3C1AA1"
Date: Mon, 23 May 2011 06:58:21 -0700
Message-Id: <7EDDD87A9A1D7F4DB6F78BC55AA495502B7778@0461-its-exmb09.us.saic.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [cicm] BoF Request for CICM at IETF 81
Thread-Index: AcwVVCMTkOAA39kjS2mWGlMpvXvrngADfklAABSKvlAAH4Mb4AB8daJAAEtT9m8=
From: "Davidson, John A." <JOHN.A.DAVIDSON@saic.com>
To: <cicm@ietf.org>
X-OriginalArrivalTime: 23 May 2011 13:58:22.0467 (UTC) FILETIME=[7A789530:01CC1951]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [cicm] BoF Request for CICM at IETF 81
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, 23 May 2011 16:13:33 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CC1951.7A3C1AA1
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: base64

VGhhdCBpcyB2ZXJ5IGdvb2QgaW4gbXkgb3Bpbmlvbi4NCg0KDQotLS0tLSBPcmlnaW5hbCBNZXNz
YWdlIC0tLS0tDQpGcm9tOiBjaWNtLWJvdW5jZXNAaWV0Zi5vcmcgPGNpY20tYm91bmNlc0BpZXRm
Lm9yZz4NClRvOiBDSUNNIERpc2N1c3Npb24gTGlzdCA8Y2ljbUBpZXRmLm9yZz4NClNlbnQ6IFNh
dCBNYXkgMjEgMTk6MzA6NDYgMjAxMQ0KU3ViamVjdDogUmU6IFtjaWNtXSBCb0YgUmVxdWVzdCBm
b3IgQ0lDTSBhdCBJRVRGIDgxDQoNCkpvaG4sDQoNCk9uIDIwMTEtMDUtMTkgYXQgMTA6NDksIEpv
aG4gRGF2aWRzb24gd3JvdGU6DQo+IEkgd291bGQgdm90ZSBmb3IgaXQgYXMgaXQgaXMgbm93LCBi
dXQgSSBtaWdodCBldmVuIGJlIHBpbmNoIG1vcmUNCj4gc2F0aXNmaWVkIGlmIGl0IHNhaWQgc29t
ZSBvZiB0aGlzIGtpbmQgb2Ygc3R1ZmY6ICANCj4gDQo+IFRoZSBDb21tb24gSW50ZXJmYWNlIHRv
IENyeXB0b2dyYXBoaWMgTW9kdWxlcyAoQ0lDTSkgZGVmaW5lcyBhbg0KPiBhcHBsaWNhdGlvbiBw
cm9ncmFtbWluZyBpbnRlcmZhY2UgZm9yIHRoZSBzZWN1cml0eSBzZXJ2aWNlcyBwcm92aWRlZCBi
eQ0KPiBjcnlwdG9ncmFwaGljIG1vZHVsZXMgZGV2ZWxvcGVkIGJ5IG11bHRpcGxlIHZlbmRvcnMu
IEl0IHByb3ZpZGVzDQo+IGVuaGFuY2VkIG1vZHVsZSwga2V5IGFuZCBjaGFubmVsIGNhcGFiaWxp
dGllcyB0aGF0IGFyZSBpbnRlbmRlZCB0byBiZQ0KPiB2ZW5kb3IgbmV1dHJhbC4gIFRoZSBBUEkg
aXMgc3RydWN0dXJlZCB0byBlbmFibGUgaXQgdG8gb3BlcmF0ZSBpbiBJQQ0KPiBlbnZpcm9ubWVu
dHMgdGhhdCBlbmZvcmNlIGRvbWFpbiBzZXBhcmF0aW9uLiAgVGhpcyBlbmFibGVzIGl0IHRvIGJl
DQo+IGFkYXB0YWJsZSB0byBoaWdoIGFzc3VyYW5jZSBJQSBhcHBsaWNhdGlvbnMuICANCg0KSXQg
c2VlbXMgdGhhdCB5b3UgYXJlIHRyeWluZyB0byBkaXN0aW5ndWlzaCBiZXR3ZWVuIGVudmlyb25t
ZW50cyB0aGF0IA0KZW5mb3JjZSBkb21haW4gc2VwYXJhdGlvbiBhbmQgaGlnaCBhc3N1cmFuY2Ug
ZW52aXJvbm1lbnRzLiBJJ3ZlIGJlZW4gdGhpbmtpbmcgDQphYm91dCBob3cgdG8gaW5jb3Jwb3Jh
dGUgdGhhdCBwb2ludCBpbnRvIG91ciBleGlzdGluZyB0ZXh0Lg0KDQpXaGF0IGRvIHBlb3BsZSB0
aGluayBhYm91dCB0aGUgZm9sbG93aW5nPw0KDQogIFRoZSBDb21tb24gSW50ZXJmYWNlIHRvIENy
eXB0b2dyYXBoaWMgTW9kdWxlcyAoQ0lDTSkgZGVmaW5lcyBhIA0KICB2ZW5kb3ItbmV1dHJhbCBh
cHBsaWNhdGlvbiBwcm9ncmFtbWluZyBpbnRlcmZhY2UgZm9yIHNlY3VyaXR5IHNlcnZpY2VzIA0K
ICBwcm92aWRlZCBieSBjcnlwdG9ncmFwaGljIG1vZHVsZXMgZGV2ZWxvcGVkIGJ5IG11bHRpcGxl
IHZlbmRvcnMuIFRoZSBBUEkgDQogIGRlZmluZXMgZW5oYW5jZWQgbW9kdWxlLCBrZXksIGFuZCBj
aGFubmVsIGNhcGFiaWxpdGllcyBhbmQgaXMgc3RydWN0dXJlZCB0byANCiAgdG8gZW5hYmxlIGFw
cGxpY2F0aW9ucyB0byBvcGVyYXRlIGluIGVudmlyb25tZW50cyB0aGF0IGVuZm9yY2Ugc2VjdXJp
dHkgDQogIGRvbWFpbiBzZXBhcmF0aW9uLCBzdWNoIGFzIGhpZ2ggYXNzdXJhbmNlIGVudmlyb25t
ZW50cy4NCg0KV2hpbGUgSSBjYW4gc2VlIHRoZSBwb2ludCBiZWluZyBtYWRlLCBpdCBtaWdodCBt
YWtlIGl0IGhhcmRlciBmb3IgcGVvcGxlIHdobyANCmFyZSBub3QgZmFtaWxpYXIgd2l0aCBvdXIg
ZmluZSBkaXN0aW5jdGlvbnMgKGkuZS4gdGhlIHJlc3Qgb2YgdGhlIElFVEYpIHRvIA0KdW5kZXJz
dGFuZCB3aHkgQ0lDTSBpcyBpbXBvcnRhbnQuDQoNCkknbSBvcGVuIHRvIG90aGVyIHN1Z2dlc3Rp
b25zLg0KDQpUaGFua3MsDQpMZXYNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fDQpjaWNtIG1haWxpbmcgbGlzdA0KY2ljbUBpZXRmLm9yZw0KaHR0cHM6Ly93
d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9jaWNtDQo=

------_=_NextPart_001_01CC1951.7A3C1AA1
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDMuMi8vRU4iPg0KPEhUTUw+
DQo8SEVBRD4NCjxNRVRBIEhUVFAtRVFVSVY9IkNvbnRlbnQtVHlwZSIgQ09OVEVOVD0idGV4dC9o
dG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxNRVRBIE5BTUU9IkdlbmVyYXRvciIgQ09OVEVOVD0iTVMg
RXhjaGFuZ2UgU2VydmVyIHZlcnNpb24gNi41Ljc2NTQuMTIiPg0KPFRJVExFPlJlOiBbY2ljbV0g
Qm9GIFJlcXVlc3QgZm9yIENJQ00gYXQgSUVURiA4MTwvVElUTEU+DQo8L0hFQUQ+DQo8Qk9EWT4N
CjwhLS0gQ29udmVydGVkIGZyb20gdGV4dC9wbGFpbiBmb3JtYXQgLS0+DQoNCjxQPjxGT05UIFNJ
WkU9Mj5UaGF0IGlzIHZlcnkgZ29vZCBpbiBteSBvcGluaW9uLjxCUj4NCjxCUj4NCjxCUj4NCi0t
LS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS08QlI+DQpGcm9tOiBjaWNtLWJvdW5jZXNAaWV0Zi5v
cmcgJmx0O2NpY20tYm91bmNlc0BpZXRmLm9yZyZndDs8QlI+DQpUbzogQ0lDTSBEaXNjdXNzaW9u
IExpc3QgJmx0O2NpY21AaWV0Zi5vcmcmZ3Q7PEJSPg0KU2VudDogU2F0IE1heSAyMSAxOTozMDo0
NiAyMDExPEJSPg0KU3ViamVjdDogUmU6IFtjaWNtXSBCb0YgUmVxdWVzdCBmb3IgQ0lDTSBhdCBJ
RVRGIDgxPEJSPg0KPEJSPg0KSm9obiw8QlI+DQo8QlI+DQpPbiAyMDExLTA1LTE5IGF0IDEwOjQ5
LCBKb2huIERhdmlkc29uIHdyb3RlOjxCUj4NCiZndDsgSSB3b3VsZCB2b3RlIGZvciBpdCBhcyBp
dCBpcyBub3csIGJ1dCBJIG1pZ2h0IGV2ZW4gYmUgcGluY2ggbW9yZTxCUj4NCiZndDsgc2F0aXNm
aWVkIGlmIGl0IHNhaWQgc29tZSBvZiB0aGlzIGtpbmQgb2Ygc3R1ZmY6Jm5ic3A7PEJSPg0KJmd0
OzxCUj4NCiZndDsgVGhlIENvbW1vbiBJbnRlcmZhY2UgdG8gQ3J5cHRvZ3JhcGhpYyBNb2R1bGVz
IChDSUNNKSBkZWZpbmVzIGFuPEJSPg0KJmd0OyBhcHBsaWNhdGlvbiBwcm9ncmFtbWluZyBpbnRl
cmZhY2UgZm9yIHRoZSBzZWN1cml0eSBzZXJ2aWNlcyBwcm92aWRlZCBieTxCUj4NCiZndDsgY3J5
cHRvZ3JhcGhpYyBtb2R1bGVzIGRldmVsb3BlZCBieSBtdWx0aXBsZSB2ZW5kb3JzLiBJdCBwcm92
aWRlczxCUj4NCiZndDsgZW5oYW5jZWQgbW9kdWxlLCBrZXkgYW5kIGNoYW5uZWwgY2FwYWJpbGl0
aWVzIHRoYXQgYXJlIGludGVuZGVkIHRvIGJlPEJSPg0KJmd0OyB2ZW5kb3IgbmV1dHJhbC4mbmJz
cDsgVGhlIEFQSSBpcyBzdHJ1Y3R1cmVkIHRvIGVuYWJsZSBpdCB0byBvcGVyYXRlIGluIElBPEJS
Pg0KJmd0OyBlbnZpcm9ubWVudHMgdGhhdCBlbmZvcmNlIGRvbWFpbiBzZXBhcmF0aW9uLiZuYnNw
OyBUaGlzIGVuYWJsZXMgaXQgdG8gYmU8QlI+DQomZ3Q7IGFkYXB0YWJsZSB0byBoaWdoIGFzc3Vy
YW5jZSBJQSBhcHBsaWNhdGlvbnMuJm5ic3A7PEJSPg0KPEJSPg0KSXQgc2VlbXMgdGhhdCB5b3Ug
YXJlIHRyeWluZyB0byBkaXN0aW5ndWlzaCBiZXR3ZWVuIGVudmlyb25tZW50cyB0aGF0PEJSPg0K
ZW5mb3JjZSBkb21haW4gc2VwYXJhdGlvbiBhbmQgaGlnaCBhc3N1cmFuY2UgZW52aXJvbm1lbnRz
LiBJJ3ZlIGJlZW4gdGhpbmtpbmc8QlI+DQphYm91dCBob3cgdG8gaW5jb3Jwb3JhdGUgdGhhdCBw
b2ludCBpbnRvIG91ciBleGlzdGluZyB0ZXh0LjxCUj4NCjxCUj4NCldoYXQgZG8gcGVvcGxlIHRo
aW5rIGFib3V0IHRoZSBmb2xsb3dpbmc/PEJSPg0KPEJSPg0KJm5ic3A7IFRoZSBDb21tb24gSW50
ZXJmYWNlIHRvIENyeXB0b2dyYXBoaWMgTW9kdWxlcyAoQ0lDTSkgZGVmaW5lcyBhPEJSPg0KJm5i
c3A7IHZlbmRvci1uZXV0cmFsIGFwcGxpY2F0aW9uIHByb2dyYW1taW5nIGludGVyZmFjZSBmb3Ig
c2VjdXJpdHkgc2VydmljZXM8QlI+DQombmJzcDsgcHJvdmlkZWQgYnkgY3J5cHRvZ3JhcGhpYyBt
b2R1bGVzIGRldmVsb3BlZCBieSBtdWx0aXBsZSB2ZW5kb3JzLiBUaGUgQVBJPEJSPg0KJm5ic3A7
IGRlZmluZXMgZW5oYW5jZWQgbW9kdWxlLCBrZXksIGFuZCBjaGFubmVsIGNhcGFiaWxpdGllcyBh
bmQgaXMgc3RydWN0dXJlZCB0bzxCUj4NCiZuYnNwOyB0byBlbmFibGUgYXBwbGljYXRpb25zIHRv
IG9wZXJhdGUgaW4gZW52aXJvbm1lbnRzIHRoYXQgZW5mb3JjZSBzZWN1cml0eTxCUj4NCiZuYnNw
OyBkb21haW4gc2VwYXJhdGlvbiwgc3VjaCBhcyBoaWdoIGFzc3VyYW5jZSBlbnZpcm9ubWVudHMu
PEJSPg0KPEJSPg0KV2hpbGUgSSBjYW4gc2VlIHRoZSBwb2ludCBiZWluZyBtYWRlLCBpdCBtaWdo
dCBtYWtlIGl0IGhhcmRlciBmb3IgcGVvcGxlIHdobzxCUj4NCmFyZSBub3QgZmFtaWxpYXIgd2l0
aCBvdXIgZmluZSBkaXN0aW5jdGlvbnMgKGkuZS4gdGhlIHJlc3Qgb2YgdGhlIElFVEYpIHRvPEJS
Pg0KdW5kZXJzdGFuZCB3aHkgQ0lDTSBpcyBpbXBvcnRhbnQuPEJSPg0KPEJSPg0KSSdtIG9wZW4g
dG8gb3RoZXIgc3VnZ2VzdGlvbnMuPEJSPg0KPEJSPg0KVGhhbmtzLDxCUj4NCkxldjxCUj4NCl9f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPEJSPg0KY2ljbSBt
YWlsaW5nIGxpc3Q8QlI+DQpjaWNtQGlldGYub3JnPEJSPg0KPEEgSFJFRj0iaHR0cHM6Ly93d3cu
aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9jaWNtIj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWls
bWFuL2xpc3RpbmZvL2NpY208L0E+PEJSPg0KPC9GT05UPg0KPC9QPg0KDQo8L0JPRFk+DQo8L0hU
TUw+

------_=_NextPart_001_01CC1951.7A3C1AA1--

From JOHN.A.DAVIDSON@saic.com  Mon May 23 09:22:04 2011
Return-Path: <JOHN.A.DAVIDSON@saic.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 63C3CE06CD for <cicm@ietfa.amsl.com>; Mon, 23 May 2011 09:22:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 KMkX3TOafjRB for <cicm@ietfa.amsl.com>; Mon, 23 May 2011 09:22:03 -0700 (PDT)
Received: from cpmx.mail.saic.com (cpmx.mail.saic.com [139.121.17.160]) by ietfa.amsl.com (Postfix) with ESMTP id 7D1F4E0658 for <cicm@ietf.org>; Mon, 23 May 2011 09:22:03 -0700 (PDT)
Received: from 0599-its-sbg03.saic.com ([139.121.20.253] [139.121.20.253]) by cpmx.mail.saic.com with ESMTP id BT-MMP-728261 for cicm@ietf.org; Mon, 23 May 2011 07:06:43 -0700
X-AuditID: 8b79132a-b7bc1ae000006a6c-cb-4dda69f391eb
Received: from 0599-its-exbh01.us.saic.com (cpe-z7-si-srcnat.sw.saic.com [139.121.20.253]) by 0599-its-sbg03.saic.com (Symantec Brightmail Gateway) with SMTP id EF.60.27244.3F96ADD4; Mon, 23 May 2011 07:06:43 -0700 (PDT)
Received: from 0461-its-exmb09.us.saic.com ([10.8.67.20]) by 0599-its-exbh01.us.saic.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 23 May 2011 07:06:43 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CC1952.A505205F"
Date: Mon, 23 May 2011 07:06:43 -0700
Message-Id: <7EDDD87A9A1D7F4DB6F78BC55AA495502B7779@0461-its-exmb09.us.saic.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [cicm] BoF Request for CICM at IETF 81
Thread-Index: AcwZRC6Pob1b0lJ0Ra+ifi8a4a6LwwAABowgAAOW/jI=
From: "Davidson, John A." <JOHN.A.DAVIDSON@saic.com>
To: <cicm@ietf.org>
X-OriginalArrivalTime: 23 May 2011 14:06:43.0789 (UTC) FILETIME=[A5483FD0:01CC1952]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [cicm] BoF Request for CICM at IETF 81
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, 23 May 2011 16:22:04 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CC1952.A505205F
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: base64

VGhlIGNvbnZlbnRpb25hbCBDT01QVVNFQyB2aWV3IG9mIGhpZ2ggYXNzdXJhbmNlIHdhcyB0aGF0
IC0gaXQgd2FzIGluZGljYXRlZCB3aGVyZSB0aGUgUG9saWN5IGhhZCB0byBiZSBlbmZvcmNlZCBm
b3IgY2VydGFpbiAobWFuZGF0b3J5KSBlLmcuIG5vIGZsb3cgZG93biB0b2xlcmF0ZWQuDQoNCi0t
LS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0NCkZyb206IGNpY20tYm91bmNlc0BpZXRmLm9yZyA8
Y2ljbS1ib3VuY2VzQGlldGYub3JnPg0KVG86IENJQ00gRGlzY3Vzc2lvbiBMaXN0IDxjaWNtQGll
dGYub3JnPg0KU2VudDogTW9uIE1heSAyMyAwNToyNzo0NSAyMDExDQpTdWJqZWN0OiBSZTogW2Np
Y21dIEJvRiBSZXF1ZXN0IGZvciBDSUNNIGF0IElFVEYgODENCg0KUmljaGFyZCwNCg0KT24gMjAx
MS0wNS0yMiBhdCAwNjozNiwgUmljaGFyZCBHcmF2ZW1hbiB3cm90ZToNCj4gSXQgc2VlbXMgdG8g
bWUgdGhhdCBoaWdoIGFzc3VyYW5jZSBtYXkgd2VsbCBiZSBuZWVkZWQgaW4gY2FzZXMgd2l0aA0K
PiBvbmx5IG9uZSBkb21haW4uIElzIHRoYXQgb3V0IG9mIHNjb3BlPw0KDQpTaW5nbGUgZG9tYWlu
IHVzZSBjYXNlcyBhcmUgZGVmaW5pdGVseSBpbiBzY29wZTsgYnV0IHRoZXkgYXJlIHZlcnkgc2lt
aWxhciANCihjb25jZXB0dWFsbHkpIHRvIGV4aXN0aW5nIGNvbW1lcmNpYWwgY3J5cHRvIEFQSXMu
IFRoZSBhYmlsaXR5IHRvIHNlcGFyYXRlIA0KZG9tYWlucyBpcyB3aGF0IHNldHMgQ0lDTSBhcGFy
dC4NCg0KU2VlOiANCiIyLjMuIFNpbmdsZSBTZWN1cml0eSBEb21haW4iIGluIENJQ00gTG9naWNh
bCBNb2RlbA0KaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtbGFuei1jaWNtLWxtLTAw
I3NlY3Rpb24tMi4zDQoNCiIxOC4gU2luZ2xlLURvbWFpbiIgaW4gQ0lDTSBDaGFubmVsIE1hbmFn
ZW1lbnQNCmh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWxhbnotY2ljbS1jbS0wMCNz
ZWN0aW9uLTE4DQoNCkxldg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX18NCmNpY20gbWFpbGluZyBsaXN0DQpjaWNtQGlldGYub3JnDQpodHRwczovL3d3dy5p
ZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2NpY20NCg==

------_=_NextPart_001_01CC1952.A505205F
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDMuMi8vRU4iPg0KPEhUTUw+
DQo8SEVBRD4NCjxNRVRBIEhUVFAtRVFVSVY9IkNvbnRlbnQtVHlwZSIgQ09OVEVOVD0idGV4dC9o
dG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxNRVRBIE5BTUU9IkdlbmVyYXRvciIgQ09OVEVOVD0iTVMg
RXhjaGFuZ2UgU2VydmVyIHZlcnNpb24gNi41Ljc2NTQuMTIiPg0KPFRJVExFPlJlOiBbY2ljbV0g
Qm9GIFJlcXVlc3QgZm9yIENJQ00gYXQgSUVURiA4MTwvVElUTEU+DQo8L0hFQUQ+DQo8Qk9EWT4N
CjwhLS0gQ29udmVydGVkIGZyb20gdGV4dC9wbGFpbiBmb3JtYXQgLS0+DQoNCjxQPjxGT05UIFNJ
WkU9Mj5UaGUgY29udmVudGlvbmFsIENPTVBVU0VDIHZpZXcgb2YgaGlnaCBhc3N1cmFuY2Ugd2Fz
IHRoYXQgLSBpdCB3YXMgaW5kaWNhdGVkIHdoZXJlIHRoZSBQb2xpY3kgaGFkIHRvIGJlIGVuZm9y
Y2VkIGZvciBjZXJ0YWluIChtYW5kYXRvcnkpIGUuZy4gbm8gZmxvdyBkb3duIHRvbGVyYXRlZC48
QlI+DQo8QlI+DQotLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tPEJSPg0KRnJvbTogY2ljbS1i
b3VuY2VzQGlldGYub3JnICZsdDtjaWNtLWJvdW5jZXNAaWV0Zi5vcmcmZ3Q7PEJSPg0KVG86IENJ
Q00gRGlzY3Vzc2lvbiBMaXN0ICZsdDtjaWNtQGlldGYub3JnJmd0OzxCUj4NClNlbnQ6IE1vbiBN
YXkgMjMgMDU6Mjc6NDUgMjAxMTxCUj4NClN1YmplY3Q6IFJlOiBbY2ljbV0gQm9GIFJlcXVlc3Qg
Zm9yIENJQ00gYXQgSUVURiA4MTxCUj4NCjxCUj4NClJpY2hhcmQsPEJSPg0KPEJSPg0KT24gMjAx
MS0wNS0yMiBhdCAwNjozNiwgUmljaGFyZCBHcmF2ZW1hbiB3cm90ZTo8QlI+DQomZ3Q7IEl0IHNl
ZW1zIHRvIG1lIHRoYXQgaGlnaCBhc3N1cmFuY2UgbWF5IHdlbGwgYmUgbmVlZGVkIGluIGNhc2Vz
IHdpdGg8QlI+DQomZ3Q7IG9ubHkgb25lIGRvbWFpbi4gSXMgdGhhdCBvdXQgb2Ygc2NvcGU/PEJS
Pg0KPEJSPg0KU2luZ2xlIGRvbWFpbiB1c2UgY2FzZXMgYXJlIGRlZmluaXRlbHkgaW4gc2NvcGU7
IGJ1dCB0aGV5IGFyZSB2ZXJ5IHNpbWlsYXI8QlI+DQooY29uY2VwdHVhbGx5KSB0byBleGlzdGlu
ZyBjb21tZXJjaWFsIGNyeXB0byBBUElzLiBUaGUgYWJpbGl0eSB0byBzZXBhcmF0ZTxCUj4NCmRv
bWFpbnMgaXMgd2hhdCBzZXRzIENJQ00gYXBhcnQuPEJSPg0KPEJSPg0KU2VlOjxCUj4NCiZxdW90
OzIuMy4gU2luZ2xlIFNlY3VyaXR5IERvbWFpbiZxdW90OyBpbiBDSUNNIExvZ2ljYWwgTW9kZWw8
QlI+DQo8QSBIUkVGPSJodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1sYW56LWNpY20t
bG0tMDAjc2VjdGlvbi0yLjMiPmh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWxhbnot
Y2ljbS1sbS0wMCNzZWN0aW9uLTIuMzwvQT48QlI+DQo8QlI+DQomcXVvdDsxOC4gU2luZ2xlLURv
bWFpbiZxdW90OyBpbiBDSUNNIENoYW5uZWwgTWFuYWdlbWVudDxCUj4NCjxBIEhSRUY9Imh0dHA6
Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWxhbnotY2ljbS1jbS0wMCNzZWN0aW9uLTE4Ij5o
dHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1sYW56LWNpY20tY20tMDAjc2VjdGlvbi0x
ODwvQT48QlI+DQo8QlI+DQpMZXY8QlI+DQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fXzxCUj4NCmNpY20gbWFpbGluZyBsaXN0PEJSPg0KY2ljbUBpZXRmLm9y
ZzxCUj4NCjxBIEhSRUY9Imh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vY2lj
bSI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9jaWNtPC9BPjxCUj4NCjwv
Rk9OVD4NCjwvUD4NCg0KPC9CT0RZPg0KPC9IVE1MPg==

------_=_NextPart_001_01CC1952.A505205F--

From JOHN.A.DAVIDSON@saic.com  Mon May 23 09:32:09 2011
Return-Path: <JOHN.A.DAVIDSON@saic.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 4E561E07AD for <cicm@ietfa.amsl.com>; Mon, 23 May 2011 09:32:09 -0700 (PDT)
X-Quarantine-ID: <Z77CKosKy6n6>
X-Amavis-Modified: Mail body modified (defanged) by ietfa.amsl.com
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BANNED, message contains part: multipart/mixed | application/ms-tnef,.tnef,winmail.dat
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
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 Z77CKosKy6n6 for <cicm@ietfa.amsl.com>; Mon, 23 May 2011 09:32:08 -0700 (PDT)
Content-Type: multipart/mixed; boundary="----------=_1306168329-32363-1"
Content-Transfer-Encoding: binary
MIME-Version: 1.0
Received: from cpmx2.mail.saic.com (cpmx2.mail.saic.com [139.121.17.172]) by ietfa.amsl.com (Postfix) with ESMTP id A0502E077A for <cicm@ietf.org>; Mon, 23 May 2011 09:32:08 -0700 (PDT)
Received: from 0599-its-sbg03.saic.com ([139.121.20.253] [139.121.20.253]) by cpmx2.mail.saic.com with ESMTP id BT-MMP-786085 for cicm@ietf.org; Mon, 23 May 2011 09:31:57 -0700
Received: from 0599-its-exbh01.us.saic.com (cpe-z7-si-srcnat.sw.saic.com [139.121.20.253]) by 0599-its-sbg03.saic.com (Symantec Brightmail Gateway) with SMTP id 85.5E.27244.DFB8ADD4; Mon, 23 May 2011 09:31:57 -0700 (PDT)
Received: from 0461-its-exmb09.us.saic.com ([10.8.67.20]) by 0599-its-exbh01.us.saic.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 23 May 2011 09:31:57 -0700
Date: Mon, 23 May 2011 09:31:57 -0700
Message-Id: <7EDDD87A9A1D7F4DB6F78BC55AA495502F733D@0461-its-exmb09.us.saic.com>
References: <7EDDD87A9A1D7F4DB6F78BC55AA495502B7779@0461-its-exmb09.us.saic.com>
From: "Davidson, John A." <JOHN.A.DAVIDSON@saic.com>
To: "CICM Discussion List" <cicm@ietf.org>
Subject: Re: [cicm] BoF Request for CICM at IETF 81
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, 23 May 2011 16:32:09 -0000

This is a multi-part message in MIME format...

------------=_1306168329-32363-1
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

WARNING: contains banned part

------------=_1306168329-32363-1
Content-Type: message/rfc822; x-spam-type=original; name="message"
Content-Disposition: attachment; filename="message"
Content-Transfer-Encoding: 7bit
Content-Description: Original message

Return-Path: <JOHN.A.DAVIDSON@saic.com>
Received: from cpmx2.mail.saic.com (cpmx2.mail.saic.com [139.121.17.172])
	by ietfa.amsl.com (Postfix) with ESMTP id A0502E077A
	for <cicm@ietf.org>; Mon, 23 May 2011 09:32:08 -0700 (PDT)
Received: from 0599-its-sbg03.saic.com ([139.121.20.253] [139.121.20.253]) by cpmx2.mail.saic.com with ESMTP id BT-MMP-786085 for cicm@ietf.org; Mon, 23 May 2011 09:31:57 -0700
X-AuditID: 8b79132a-b7bc1ae000006a6c-20-4dda8bfd842d
Received: from 0599-its-exbh01.us.saic.com (cpe-z7-si-srcnat.sw.saic.com [139.121.20.253])
	by 0599-its-sbg03.saic.com (Symantec Brightmail Gateway) with SMTP id 85.5E.27244.DFB8ADD4; Mon, 23 May 2011 09:31:57 -0700 (PDT)
Received: from 0461-its-exmb09.us.saic.com ([10.8.67.20]) by 0599-its-exbh01.us.saic.com with Microsoft SMTPSVC(6.0.3790.4675);
	 Mon, 23 May 2011 09:31:57 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_001_01CC1966.EEF647DD"
Subject: RE: [cicm] BoF Request for CICM at IETF 81
Date: Mon, 23 May 2011 09:31:57 -0700
Message-Id: <7EDDD87A9A1D7F4DB6F78BC55AA495502F733D@0461-its-exmb09.us.saic.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: <7EDDD87A9A1D7F4DB6F78BC55AA495502F733D@0461-its-exmb09.us.saic.com>
Thread-Topic: [cicm] BoF Request for CICM at IETF 81
Thread-Index: AcwZRC6Pob1b0lJ0Ra+ifi8a4a6LwwAABowgAAOW/jIABNqFng==
References: <7EDDD87A9A1D7F4DB6F78BC55AA495502B7779@0461-its-exmb09.us.saic.com>
From: "Davidson, John A." <JOHN.A.DAVIDSON@saic.com>
To: "CICM Discussion List" <cicm@ietf.org>
X-OriginalArrivalTime: 23 May 2011 16:31:57.0675 (UTC) FILETIME=[EF29BBB0:01CC1966]
X-Brightmail-Tracker: AAAAAQPmCRA=

This is a multi-part message in MIME format.

------_=_NextPart_001_01CC1966.EEF647DD
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Someone suggested I should have pointed out that in my experience there =
exists policies that do not typically indicate a requirement for "high =
assurance," not because we aren't serious about them, but because IA =
technology does not yet offer a known good strategy to enforce them with =
any degree of certainty, like we can with military-oriented "No Flow =
Down."  Examples are so-called "Integrity" (whatever that is) and =
"Availability".  -John


-----Original Message-----
From: cicm-bounces@ietf.org on behalf of Davidson, John A.
Sent: Mon 5/23/2011 7:06 AM
To: cicm@ietf.org
Subject: Re: [cicm] BoF Request for CICM at IETF 81
=20
The conventional COMPUSEC view of high assurance was that - it was =
indicated where the Policy had to be enforced for certain (mandatory) =
e.g. no flow down tolerated.

----- Original Message -----
From: cicm-bounces@ietf.org <cicm-bounces@ietf.org>
To: CICM Discussion List <cicm@ietf.org>
Sent: Mon May 23 05:27:45 2011
Subject: Re: [cicm] BoF Request for CICM at IETF 81

Richard,

On 2011-05-22 at 06:36, Richard Graveman wrote:
> It seems to me that high assurance may well be needed in cases with
> only one domain. Is that out of scope?

Single domain use cases are definitely in scope; but they are very =
similar
(conceptually) to existing commercial crypto APIs. The ability to =
separate
domains is what sets CICM apart.

See:
"2.3. Single Security Domain" in CICM Logical Model
http://tools.ietf.org/html/draft-lanz-cicm-lm-00#section-2.3

"18. Single-Domain" in CICM Channel Management
http://tools.ietf.org/html/draft-lanz-cicm-cm-00#section-18

Lev
_______________________________________________
cicm mailing list
cicm@ietf.org
https://www.ietf.org/mailman/listinfo/cicm




------_=_NextPart_001_01CC1966.EEF647DD
Content-Type: application/ms-tnef;
	name="winmail.dat"
Content-Transfer-Encoding: base64

eJ8+IjoQAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy
b3NvZnQgTWFpbC5Ob3RlADEIAQ2ABAACAAAAAgACAAEEgAEAKwAAAFJFOiBbY2ljbV0gQm9GIFJl
cXVlc3QgZm9yIENJQ00gYXQgSUVURiA4MQDODAEFgAMADgAAANsHBQAXAAkAHwA5AAEAYAEBIIAD
AA4AAADbBwUAFwAJAB8AOQABAGABAQmAAQAhAAAAQ0Y3NTI3RjYzODc1MDg0N0FDQUMwMzBEQkU2
REJGRkEAcwcBA5AGALwMAAA5AAAAAwAmAAAAAAADADYAAAAAAEAAOQDdR/buZhnMAR4APQABAAAA
BQAAAFJFOiAAAAAAAgFHAAEAAAAzAAAAYz1VUzthPSA7cD1TQUlDO2w9MDQ2MS1JVFMtRVhNLTEx
MDUyMzE2MzE1N1otNzE4OTYAAB4ASQABAAAAKwAAAFJlOiBbY2ljbV0gQm9GIFJlcXVlc3QgZm9y
IENJQ00gYXQgSUVURiA4MQAAQABOAIDbz6RSGcwBHgBaAAEAAAAWAAAAY2ljbS1ib3VuY2VzQGll
dGYub3JnAAAAAgFbAAEAAABJAAAAAAAAAIErH6S+oxAZnW4A3QEPVAIAAAAAY2ljbS1ib3VuY2Vz
QGlldGYub3JnAFNNVFAAY2ljbS1ib3VuY2VzQGlldGYub3JnAAAAAAIBXAABAAAAGwAAAFNNVFA6
Q0lDTS1CT1VOQ0VTQElFVEYuT1JHAAAeAF0AAQAAABIAAABEYXZpZHNvbiwgSm9obiBBLgAAAAIB
XgABAAAASAAAAAAAAACBKx+kvqMQGZ1uAN0BD1QCAAAAAERhdmlkc29uLCBKb2huIEEuAFNNVFAA
Sk9ITi5BLkRBVklEU09OQHNhaWMuY29tAAIBXwABAAAAHgAAAFNNVFA6Sk9ITi5BLkRBVklEU09O
QFNBSUMuQ09NAAAAHgBmAAEAAAAFAAAAU01UUAAAAAAeAGcAAQAAABYAAABjaWNtLWJvdW5jZXNA
aWV0Zi5vcmcAAAAeAGgAAQAAAAUAAABTTVRQAAAAAB4AaQABAAAAGQAAAEpPSE4uQS5EQVZJRFNP
TkBzYWljLmNvbQAAAAAeAHAAAQAAACcAAABbY2ljbV0gQm9GIFJlcXVlc3QgZm9yIENJQ00gYXQg
SUVURiA4MQAAAgFxAAEAAAAlAAAAAcwZRC6Pob1b0lJ0Ra+ifi8a4a6LwwAABowgAAOW/jIABNqF
ngAAAB4AdAABAAAADgAAAGNpY21AaWV0Zi5vcmcAAAAeABoMAQAAABIAAABEYXZpZHNvbiwgSm9o
biBBLgAAAB4AHQ4BAAAAJwAAAFtjaWNtXSBCb0YgUmVxdWVzdCBmb3IgQ0lDTSBhdCBJRVRGIDgx
AAACAQkQAQAAAGQFAABgBQAAhggAAExaRnVtqBwnAwAKAHJjcGcxMjXiMgNDdGV4BUEBAwH3/wqA
AqQD5AcTAoAP8wBQBFY/CFUHshElDlEDAQIAY2jhCsBzZXQyBgAGwxEl9jMERhO3MBIsETMI7wn3
tjsYHw4wNREiDGBjAFDzCwkBZDM2FlALpgYAA3ACZQIgZSBzdWdnoweQDrBkIEkdYGgIYJZsHfAT
4HYdUHBvC4B3HdIIYAVAdBPgBUALgCBobXkgDsBwBnEJ8GO/HVAfsASQHVAOwAQAdAQgPR7wbA3g
CJAEIB+zZG/IIG5vH5F5cA3gB0A2bCBAC4BkI2EOsCBh4iAYIHF1aRggB4ACMAYgAhAFwCJoaWdo
nyRQBBAIcABwIOAsIiLjkmIFkGF1FBAgdyRB+RggbicFQBQQBRAIYAQgdwGgH3Qk4Cwm0B+BJuZJ
tkEfoAWQaCLwF7BnIED3IsAHkSLyeRQgH2ABIBKBlSRgayLwdwOgZ28EcN0dYHQmIA6wKrF0ItAJ
8GslQSDkbSdQaR+wJFBu7yrBLTAJ0SuhICDgACALcfcjMCkgIgBrJ0MjcAOgLnPObQMQLoAKwHkt
BbAgsWkd0iJOItBGF7AH4EQFLFEuJoAgRXhhbc8LUAeRJ5EdYG8tI3IyUi5JHyEJwC6AeSaAKHed
H8FlHsAFwB+0cykusdkyYUF2C3ALYGIxcjWQ4i4zcC1KbypgCqIKhNU41i05sk8FEGcLgAdAcwXQ
B5BzYR2gObM4lEbNA2E6L5AN4G0tKJEg0axzQAiQADAuBbBnH2C3A6Am4BPgbC+AL3FEHrB0aWQ0
YG4pIDhSEMAuLziUBmACMDvwTT1xNS8EMjNAYDAxMSA3KDowNhDATTiUVG/HO/Q81z9VdWJqBZA/
4RRSZTvwWzwSXSBCPG9GQ7EkoB2xJTNDSYxDTSRQBUBJRVREkP44GvMKgArjQaEhIC+QAiAPHsAC
MCgwOlJDT01Q4FVTRUMgPmAH0S9x7yWcJ1Al4B+kLR/wBUBKQp8j1h3wNdAhMiERIFAh8v8gQBPg
HfAtcSbgLZYd8CVCty+lNbADgWQf0AWweTbQ+GUuZzgQIvAlMDLSIsBvLGEtcDPgLQJkP0U5WSDf
Og44MDsfPC89MjxUzz0i1j5BaEVzRAQAYycgAJA9PXFMIZFWFFb+P7hNYYMgQEBwIDA1OjJA8Pw0
NVugQLFC30PvRP9GCk04lFIN4BPhZCw4mk/LA6BAoi1b4C0yFEAf0Z1BEDocICkgYQUgRyYgWx7A
A4J3A2AOsDo4lD7/HgAn4iTgIlEi0AeAH6RJXf8AwCBAJ2AjkE1yHUAJgB3h/yABI3AUEAQgLnJl
NgIgI6HfHTIiwADAC4A4EEkiVR9yqy9xBPBvIIA/OJpTC4D2ZzPgauUgJyJpRDQiAQHfC4AugGgw
I7JsVDspMyER/yBANCI2ISBAAJAxYQrAOJTuKEdxIOAFMHUjgjbQLXL3IYJtkUdhbQeALeAHMS+Q
5zHABTAi0EFQa3A4EEcy/zeVLWIUEAqxJCE4lGr0S0G/aYEfwhQRBCBfVAqxdFF7wwZgZRYiMi4z
OBBthf8GYFiwNWIzAWsSJoAgAV9TfkwqoCNiQAEBABgAOKNo4QJAcDovLy1wBvB1gIU85i9+cG1s
L2QmIGUBgC0LYG56NIBWQmzxVmAwMCMUEF1gR+Fi4KN7ADiaIjE4eyYtfE76QxPgbh1AOnEAcDrR
JPJ/fh9/L4A9VlGBWYMAOJpM+zYQOJRfiz+MT40aOJRWMv9n0TFxdAEiAB3AjihCTYYyenOGcXeR
oIb4jtIDgS93j1ILgAIQL1YyOJ845X0BlVAeADUQAQAAAEUAAAA8N0VEREQ4N0E5QTFEN0Y0REI2
Rjc4QkM1NUFBNDk1NTAyRjczM0RAMDQ2MS1pdHMtZXhtYjA5LnVzLnNhaWMuY29tPgAAAAAeADkQ
AQAAAEUAAAA8N0VEREQ4N0E5QTFEN0Y0REI2Rjc4QkM1NUFBNDk1NTAyQjc3NzlAMDQ2MS1pdHMt
ZXhtYjA5LnVzLnNhaWMuY29tPgAAAAAeAEcQAQAAAA8AAABtZXNzYWdlL3JmYzgyMgAACwDyEAEA
AAAfAPMQAQAAAGIAAABSAEUAJQAzAEEAIABbAGMAaQBjAG0AXQAgAEIAbwBGACAAUgBlAHEAdQBl
AHMAdAAgAGYAbwByACAAQwBJAEMATQAgAGEAdAAgAEkARQBUAEYAIAA4ADEALgBFAE0ATAAAAAAA
CwD2EAAAAABAAAcwZTrODmYZzAFAAAgwzVoJ72YZzAEDAN4/r28AAAMA8T8JBAAAHgD4PwEAAAAS
AAAARGF2aWRzb24sIEpvaG4gQS4AAAACAfk/AQAAAE4AAAAAAAAA3KdAyMBCEBq0uQgAKy/hggEA
AAAAAAAAL089U0FJQy9PVT1VUy1TRC1QTFRDL0NOPVJFQ0lQSUVOVFMvQ049REFWSURTT05KQQAA
AB4A+j8BAAAAFQAAAFN5c3RlbSBBZG1pbmlzdHJhdG9yAAAAAAIB+z8BAAAAHgAAAAAAAADcp0DI
wEIQGrS5CAArL+GCAQAAAAAAAAAuAAAAAwD9P+QEAAADABlAAAAAAAMAGkAAAAAAAwAdQAAAAAAD
AB5AAAAAAB4AMEABAAAACwAAAERBVklEU09OSkEAAB4AMUABAAAACwAAAERBVklEU09OSkEAAB4A
MkABAAAAFgAAAGNpY20tYm91bmNlc0BpZXRmLm9yZwAAAB4AM0ABAAAAGQAAAEpPSE4uQS5EQVZJ
RFNPTkBzYWljLmNvbQAAAAAeADhAAQAAAAsAAABEQVZJRFNPTkpBAAAeADlAAQAAAAIAAAAuAAAA
AwB2QP////8LACkAAAAAAAsAIwAAAAAAAwAGEJzLYWEDAAcQZQUAAAMAEBAAAAAAAwAREAAAAAAe
AAgQAQAAAGUAAABTT01FT05FU1VHR0VTVEVESVNIT1VMREhBVkVQT0lOVEVET1VUVEhBVElOTVlF
WFBFUklFTkNFVEhFUkVFWElTVFNQT0xJQ0lFU1RIQVRET05PVFRZUElDQUxMWUlORElDQVRFAAAA
AAIBfwABAAAARQAAADw3RURERDg3QTlBMUQ3RjREQjZGNzhCQzU1QUE0OTU1MDJGNzMzREAwNDYx
LWl0cy1leG1iMDkudXMuc2FpYy5jb20+AAAAADVV

------_=_NextPart_001_01CC1966.EEF647DD--

------------=_1306168329-32363-1--

From jfitton@harris.com  Mon May 23 17:52:50 2011
Return-Path: <jfitton@harris.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 D0957E07A4 for <cicm@ietfa.amsl.com>; Mon, 23 May 2011 17:52:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
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 O7GOLUQMmsJW for <cicm@ietfa.amsl.com>; Mon, 23 May 2011 17:52:50 -0700 (PDT)
Received: from mlbe2k2.cs.myharris.net (mlbe2k2.cs.myharris.net [137.237.90.89]) by ietfa.amsl.com (Postfix) with ESMTP id CDAC9E06E2 for <cicm@ietf.org>; Mon, 23 May 2011 17:52:49 -0700 (PDT)
Received: from mail pickup service by mlbe2k2.cs.myharris.net with Microsoft SMTPSVC; Mon, 23 May 2011 20:52:48 -0400
Received: from mlbrst2.cs.myharris.net ([137.237.89.11]) by mlbe2k2.cs.myharris.net with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 23 May 2011 20:52:47 -0400
Received: from MLBMXHT1.cs.myharris.net ([137.237.89.19]) by mlbrst2.cs.myharris.net with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 23 May 2011 20:52:47 -0400
Received: from ROCMXCAHT22.cs.myharris.net (10.64.228.25) by MLBMXHT1.cs.myharris.net (137.237.89.19) with Microsoft SMTP Server (TLS) id 8.2.254.0; Mon, 23 May 2011 20:52:47 -0400
Received: from ROCMXUS21.cs.myharris.net ([fe80::1161:8dee:2d75:5ac]) by ROCMXCAHT22.cs.myharris.net ([::1]) with mapi id 14.01.0270.001; Mon, 23 May 2011 20:52:46 -0400
From: "Fitton, John" <jfitton@harris.com>
To: CICM Discussion List <cicm@ietf.org>
Thread-Topic: [cicm] BoF Request for CICM at IETF 81
Thread-Index: AQHMGWhrWYa5rmedwkWeZn8qfUYp4ZSbI8Tf
Date: Tue, 24 May 2011 00:52:45 +0000
Message-ID: <06D46EAFF7D0C946BEC108DB7CCDC9A608B43534@ROCMXUS21.cs.myharris.net>
References: <7EDDD87A9A1D7F4DB6F78BC55AA495502B7779@0461-its-exmb09.us.saic.com>
In-Reply-To: <7EDDD87A9A1D7F4DB6F78BC55AA495502B7779@0461-its-exmb09.us.saic.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.64.228.53]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 24 May 2011 00:52:47.0272 (UTC) FILETIME=[E61E5A80:01CC19AC]
Subject: Re: [cicm] BoF Request for CICM at IETF 81
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: Tue, 24 May 2011 00:52:50 -0000

John, I don't believe that was quite true. I believe you are interpreting B=
ell-LaPadua as an overall security policy, when in fact is was strictly an =
access control policy as were most COMPUSEC policies.  The US Government's =
classification system is in fact part of an access control policy.  High As=
surance is achieved when it can be shown that the security policy for a pla=
tform is rigorously enforced by the security mechanisms...regardless what t=
hat security policy may be.  Even the access control policy which says "no =
flow down" can be "bent" in real world situations when the situation demand=
s.  Things are never just black and white (or perhaps I should say black an=
d red).

________________________________
From: Davidson, John A. [JOHN.A.DAVIDSON@saic.com]
Sent: Monday, May 23, 2011 10:06 AM
To: cicm@ietf.org
Subject: Re: [cicm] BoF Request for CICM at IETF 81


The conventional COMPUSEC view of high assurance was that - it was indicate=
d where the Policy had to be enforced for certain (mandatory) e.g. no flow =
down tolerated.

----- Original Message -----
From: cicm-bounces@ietf.org <cicm-bounces@ietf.org>
To: CICM Discussion List <cicm@ietf.org>
Sent: Mon May 23 05:27:45 2011
Subject: Re: [cicm] BoF Request for CICM at IETF 81

Richard,

On 2011-05-22 at 06:36, Richard Graveman wrote:
> It seems to me that high assurance may well be needed in cases with
> only one domain. Is that out of scope?

Single domain use cases are definitely in scope; but they are very similar
(conceptually) to existing commercial crypto APIs. The ability to separate
domains is what sets CICM apart.

See:
"2.3. Single Security Domain" in CICM Logical Model
http://tools.ietf.org/html/draft-lanz-cicm-lm-00#section-2.3

"18. Single-Domain" in CICM Channel Management
http://tools.ietf.org/html/draft-lanz-cicm-cm-00#section-18

Lev
_______________________________________________
cicm mailing list
cicm@ietf.org
https://www.ietf.org/mailman/listinfo/cicm

From JOHN.A.DAVIDSON@saic.com  Tue May 24 09:16:19 2011
Return-Path: <JOHN.A.DAVIDSON@saic.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 4E33BE073C for <cicm@ietfa.amsl.com>; Tue, 24 May 2011 09:16:19 -0700 (PDT)
X-Quarantine-ID: <tttWmTk5A1T0>
X-Amavis-Modified: Mail body modified (defanged) by ietfa.amsl.com
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BANNED, message contains part: multipart/mixed | application/ms-tnef,.tnef,winmail.dat
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
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 tttWmTk5A1T0 for <cicm@ietfa.amsl.com>; Tue, 24 May 2011 09:16:18 -0700 (PDT)
Content-Type: multipart/mixed; boundary="----------=_1306253779-27929-1"
Content-Transfer-Encoding: binary
MIME-Version: 1.0
Received: from cpmx2.mail.saic.com (cpmx2.mail.saic.com [139.121.17.172]) by ietfa.amsl.com (Postfix) with ESMTP id A4CB6E0671 for <cicm@ietf.org>; Tue, 24 May 2011 09:16:18 -0700 (PDT)
Received: from 0599-its-sbg03.saic.com ([139.121.20.253] [139.121.20.253]) by cpmx2.mail.saic.com with ESMTP id BT-MMP-985379 for cicm@ietf.org; Tue, 24 May 2011 09:16:03 -0700
Received: from 0599-its-exbh01.us.saic.com (cpe-z7-si-srcnat.sw.saic.com [139.121.20.253]) by 0599-its-sbg03.saic.com (Symantec Brightmail Gateway) with SMTP id F4.85.27244.3C9DBDD4; Tue, 24 May 2011 09:16:03 -0700 (PDT)
Received: from 0461-its-exmb09.us.saic.com ([10.8.67.20]) by 0599-its-exbh01.us.saic.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 24 May 2011 09:16:03 -0700
Date: Tue, 24 May 2011 09:14:05 -0700
Message-Id: <7EDDD87A9A1D7F4DB6F78BC55AA495502F733F@0461-its-exmb09.us.saic.com>
References: <7EDDD87A9A1D7F4DB6F78BC55AA495502B7779@0461-its-exmb09.us.saic.com> <06D46EAFF7D0C946BEC108DB7CCDC9A608B43534@ROCMXUS21.cs.myharris.net>
From: "Davidson, John A." <JOHN.A.DAVIDSON@saic.com>
To: "CICM Discussion List" <cicm@ietf.org>
Subject: Re: [cicm] BoF Request for CICM at IETF 81
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: Tue, 24 May 2011 16:16:19 -0000

This is a multi-part message in MIME format...

------------=_1306253779-27929-1
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

WARNING: contains banned part

------------=_1306253779-27929-1
Content-Type: message/rfc822; x-spam-type=original; name="message"
Content-Disposition: attachment; filename="message"
Content-Transfer-Encoding: 7bit
Content-Description: Original message

Return-Path: <JOHN.A.DAVIDSON@saic.com>
Received: from cpmx2.mail.saic.com (cpmx2.mail.saic.com [139.121.17.172])
	by ietfa.amsl.com (Postfix) with ESMTP id A4CB6E0671
	for <cicm@ietf.org>; Tue, 24 May 2011 09:16:18 -0700 (PDT)
Received: from 0599-its-sbg03.saic.com ([139.121.20.253] [139.121.20.253]) by cpmx2.mail.saic.com with ESMTP id BT-MMP-985379 for cicm@ietf.org; Tue, 24 May 2011 09:16:03 -0700
X-AuditID: 8b79132a-b7bc1ae000006a6c-63-4ddbd9c3d7ca
Received: from 0599-its-exbh01.us.saic.com (cpe-z7-si-srcnat.sw.saic.com [139.121.20.253])
	by 0599-its-sbg03.saic.com (Symantec Brightmail Gateway) with SMTP id F4.85.27244.3C9DBDD4; Tue, 24 May 2011 09:16:03 -0700 (PDT)
Received: from 0461-its-exmb09.us.saic.com ([10.8.67.20]) by 0599-its-exbh01.us.saic.com with Microsoft SMTPSVC(6.0.3790.4675);
	 Tue, 24 May 2011 09:16:03 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_001_01CC1A2D.E0DCA2A7"
Subject: RE: [cicm] BoF Request for CICM at IETF 81
Date: Tue, 24 May 2011 09:14:05 -0700
Message-Id: <7EDDD87A9A1D7F4DB6F78BC55AA495502F733F@0461-its-exmb09.us.saic.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: <7EDDD87A9A1D7F4DB6F78BC55AA495502F733F@0461-its-exmb09.us.saic.com>
Thread-Topic: [cicm] BoF Request for CICM at IETF 81
Thread-Index: AQHMGWhrWYa5rmedwkWeZn8qfUYp4ZSbI8TfgAEEoCs=
References: <7EDDD87A9A1D7F4DB6F78BC55AA495502B7779@0461-its-exmb09.us.saic.com> <06D46EAFF7D0C946BEC108DB7CCDC9A608B43534@ROCMXUS21.cs.myharris.net>
From: "Davidson, John A." <JOHN.A.DAVIDSON@saic.com>
To: "CICM Discussion List" <cicm@ietf.org>
X-OriginalArrivalTime: 24 May 2011 16:16:03.0843 (UTC) FILETIME=[E10C4530:01CC1A2D]
X-Brightmail-Tracker: AAAAAQPmCRA=

This is a multi-part message in MIME format.

------_=_NextPart_001_01CC1A2D.E0DCA2A7
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

John, That involves that thing we agree to disagree on.  Lets please =
take that continuing discussion off line.  Thanks, John


-----Original Message-----
From: cicm-bounces@ietf.org on behalf of Fitton, John
Sent: Mon 5/23/2011 5:52 PM
To: CICM Discussion List
Subject: Re: [cicm] BoF Request for CICM at IETF 81
=20
John, I don't believe that was quite true. I believe you are =
interpreting Bell-LaPadua as an overall security policy, when in fact is =
was strictly an access control policy as were most COMPUSEC policies.  =
The US Government's classification system is in fact part of an access =
control policy.  High Assurance is achieved when it can be shown that =
the security policy for a platform is rigorously enforced by the =
security mechanisms...regardless what that security policy may be.  Even =
the access control policy which says "no flow down" can be "bent" in =
real world situations when the situation demands.  Things are never just =
black and white (or perhaps I should say black and red).

________________________________
From: Davidson, John A. [JOHN.A.DAVIDSON@saic.com]
Sent: Monday, May 23, 2011 10:06 AM
To: cicm@ietf.org
Subject: Re: [cicm] BoF Request for CICM at IETF 81


The conventional COMPUSEC view of high assurance was that - it was =
indicated where the Policy had to be enforced for certain (mandatory) =
e.g. no flow down tolerated.

----- Original Message -----
From: cicm-bounces@ietf.org <cicm-bounces@ietf.org>
To: CICM Discussion List <cicm@ietf.org>
Sent: Mon May 23 05:27:45 2011
Subject: Re: [cicm] BoF Request for CICM at IETF 81

Richard,

On 2011-05-22 at 06:36, Richard Graveman wrote:
> It seems to me that high assurance may well be needed in cases with
> only one domain. Is that out of scope?

Single domain use cases are definitely in scope; but they are very =
similar
(conceptually) to existing commercial crypto APIs. The ability to =
separate
domains is what sets CICM apart.

See:
"2.3. Single Security Domain" in CICM Logical Model
http://tools.ietf.org/html/draft-lanz-cicm-lm-00#section-2.3

"18. Single-Domain" in CICM Channel Management
http://tools.ietf.org/html/draft-lanz-cicm-cm-00#section-18

Lev
_______________________________________________
cicm mailing list
cicm@ietf.org
https://www.ietf.org/mailman/listinfo/cicm
_______________________________________________
cicm mailing list
cicm@ietf.org
https://www.ietf.org/mailman/listinfo/cicm


------_=_NextPart_001_01CC1A2D.E0DCA2A7
Content-Type: application/ms-tnef;
	name="winmail.dat"
Content-Transfer-Encoding: base64

eJ8+IgQQAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy
b3NvZnQgTWFpbC5Ob3RlADEIAQ2ABAACAAAAAgACAAEEgAEAKwAAAFJFOiBbY2ljbV0gQm9GIFJl
cXVlc3QgZm9yIENJQ00gYXQgSUVURiA4MQDODAEFgAMADgAAANsHBQAYAAkADgAFAAIAHQEBIIAD
AA4AAADbBwUAGAAJABAAAwACAB0BAQmAAQAhAAAAMzA4MkE1NERDMUJDNEY0N0IyMDAwRjlFRTU1
RTBDMkYAQAcBA5AGAOgNAAA5AAAAAwAmAAAAAAADADYAAAAAAEAAOQAfV5CaLRrMAR4APQABAAAA
BQAAAFJFOiAAAAAAAgFHAAEAAAAzAAAAYz1VUzthPSA7cD1TQUlDO2w9MDQ2MS1JVFMtRVhNLTEx
MDUyNDE2MTYwM1otNzUxMjkAAB4ASQABAAAAKwAAAFJlOiBbY2ljbV0gQm9GIFJlcXVlc3QgZm9y
IENJQ00gYXQgSUVURiA4MQAAQABOAICsw+SsGcwBHgBaAAEAAAAWAAAAY2ljbS1ib3VuY2VzQGll
dGYub3JnAAAAAgFbAAEAAABJAAAAAAAAAIErH6S+oxAZnW4A3QEPVAIAAAAAY2ljbS1ib3VuY2Vz
QGlldGYub3JnAFNNVFAAY2ljbS1ib3VuY2VzQGlldGYub3JnAAAAAAIBXAABAAAAGwAAAFNNVFA6
Q0lDTS1CT1VOQ0VTQElFVEYuT1JHAAAeAF0AAQAAAA0AAABGaXR0b24sIEpvaG4AAAAAAgFeAAEA
AAA9AAAAAAAAAIErH6S+oxAZnW4A3QEPVAIAAAAARml0dG9uLCBKb2huAFNNVFAAamZpdHRvbkBo
YXJyaXMuY29tAAAAAAIBXwABAAAAGAAAAFNNVFA6SkZJVFRPTkBIQVJSSVMuQ09NAB4AZgABAAAA
BQAAAFNNVFAAAAAAHgBnAAEAAAAWAAAAY2ljbS1ib3VuY2VzQGlldGYub3JnAAAAHgBoAAEAAAAF
AAAAU01UUAAAAAAeAGkAAQAAABMAAABqZml0dG9uQGhhcnJpcy5jb20AAB4AcAABAAAAJwAAAFtj
aWNtXSBCb0YgUmVxdWVzdCBmb3IgQ0lDTSBhdCBJRVRGIDgxAAACAXEAAQAAACAAAAABAcwZaGtZ
hrmuZ53CRZ5mfyp9RinhlJsjxN+AAQSgKx4AdAABAAAAFQAAAENJQ00gRGlzY3Vzc2lvbiBMaXN0
AAAAAB4AGgwBAAAAEgAAAERhdmlkc29uLCBKb2huIEEuAAAAHgAdDgEAAAAnAAAAW2NpY21dIEJv
RiBSZXF1ZXN0IGZvciBDSUNNIGF0IElFVEYgODEAAAIBCRABAAAAbQYAAGkGAABmCwAATFpGdd+i
m8ADAAoAcmNwZzEyNeIyA0N0ZXgFQQEDAff/CoACpAPkBxMCgA/zAFAEVj8IVQeyESUOUQMBAgBj
aOEKwHNldDIGAAbDESX2MwRGE7cwEiwRMwjvCfe2OxgfDjA1ESIMYGMAUDMLCQFkMzYWUAumIErA
b2huLCBUE+AFQNULgHYG8HYHkXQdYh4wgQuAZyB3ZSBhCcJxHiBvIGQEAB8UAiAuOCAgTBQgBCAL
UGVh8xQQHiBhax9RHWIFoAIwTQuAdR6iH6FjdQQQaacCICAgASAgbAuAZSBR8R1RbmtzHTAc8gqi
CoTVJPYtJdJPBRBnC4AHQLcF0AeQH8FlJdMktEYDYSY6IdAN4G0tBuB1btpjB5BACJAAMC4FsB7A
aSMRYmUT4GwjYCNAIPxGaQJAAiAkWgZgAjAoEEJNIxE1LzIzLDAwFDExLBA6DkAgUE0JJLRUbygQ
Q0lDTVQgRCKoTAQAdCsldUxiagWQK7FSZSgQW0EoMl0gQm9GL/FxewpQLvAgAhAFwC3THXFJ9EVU
MNA4GvMKgArjCoDtHPRJH5ACICcFQCnAI4DWZR3wHiR3IQAgMRAqcL0fUXIKUCBQM9A0VnkIYM8f
ABggHZEOsHJwGCAiEQUewEI0YGwtTGFQcGFkdWEfAAQgA5FvfR3wcgdAAyAUECLABRB0LnkgwAbw
DeB5HTB3aP8J8B2RMWAA0B2BBCA1Ii7w+wUQL8BsOjADkQDQKMEEIP8h4gNgAyA6VDjSHuA3EQRg
ATFBQ09NUFVTRXZDOkQIkHMjwx7wP0Ag2kc5Qm4HgAIwJz0hC2CdIuFmDeAdcCMCc3ku8PxlbTuS
OyYKsQVAKjE8r+s6RSBRSCZAaBDABBAIcL8AcCjAO5IA0B6QNJFkOsWPIcEDkSnAObBob3cDoP8e
NUhBOdwxYzjAC1EAMAWw70LDJjEFsAhgczxxCfAxcfsowEdQYjowSRsHgBPRAwDcc21AAE5QGCBn
CxEg4P8EETrQHlMdcUleAMA6MCnA/SBRRR3wSKIe8URfPfI60I8N4EXwH8BCgCAibh+AXmYXsAfg
M/BIkCJH5iK/KcACMFTQOyEYICaBdwWw9mxHUACQdDiwQiJPElGF71a3H5BCsABwZEAEHqE48ec3
ESOgOVEgaiLQNDELYFxjazkBR1I1gigFsXC7BJAT4HAEIDPQSGF1VoKnUOJapxghKS4kul9e38Nf
zCd6RGF2aVjgKqYDEMAgUFtKT0hOLgFigERBVklEU0/sTkAfwA3gLgWgMIArLfZkUOAdME1Q4SxA
HTAsc+AxMDowNhDALSkoMv8o9y8fMC8xPzJKa+pAQiHh/1FxQiImgT8HYbAH0SoxHpDfReFBoUZF
NSIeMy1HsjUivwuAH6BCAUdENxFJElA91P8T4EdQH3FIMUwnarIowAAgnwtxW4BYsh1wBbB5KUwQ
/C5nIFBUGh9hIOA5cHGR+14LJdMgJi5wkCc/KE8pUvY8ep8pQj4tPy5Le+R8zhMriGWUIDAswDI3
Onw0NWYDaF9pb2p/a48K1lJTcQsRLGvqTwOgLHJyLYGwLTIUQB1xZpA6fxwgHTCG1UCgOXAd8AOC
d+sDYA6wOmvkPjIgT7JCsP8eER+AB4AeJG8tUNIe4DmR/0gxI6AJgEdBOyFCABQQO7H9KnBoiwYC
IDxxAiAe8DPwfwDAC4A2AR4VCGBDwwTwb3Vb0D9r6lMeoSDgkLUg/yLQbSGPIzcCAQELgDWBPHH7
OyGSMzspsJHRSRE8gTcRdzlROjAAkG0DEArAa+Qo/yHhKMAFMDiwODB1YR9xDsD/LuEeomQRB4BM
YAcxIdB1UPMFMB+AQVCRQCBQQEIBoP8DEDoSH3EUEAqxcYFr5JDE/0LxTxUUEQQghSRDkl4LBmDh
iuYiMi4zIFCTVQZgnTnlRJDTVbN+A0xvJlBfQgAmkQRxGABr82gCQHB4Oi8vH3AG8EAAKQYvYaRA
bWwvZDlwAYAtUQtgbnotfANsfDAwfDAjOcFCIoiwoNBr6iLUMTig9i2iHkMkASOg/yaRAHAm8UES
o++k/6YNfCHvpymo0GvqIIB2Xn+xr7K//2C2fAJQwZvhHrEjgC72Z4/1q+RzrEF3t3CsyLSiA4Hu
L7UiC4ACEC98ArCvup//u6+z37Tvtf+3D7gfuStr5AJ9w1AAAAAeADUQAQAAAEUAAAA8N0VEREQ4
N0E5QTFEN0Y0REI2Rjc4QkM1NUFBNDk1NTAyRjczM0ZAMDQ2MS1pdHMtZXhtYjA5LnVzLnNhaWMu
Y29tPgAAAAAeADkQAQAAAIoAAAA8N0VEREQ4N0E5QTFEN0Y0REI2Rjc4QkM1NUFBNDk1NTAyQjc3
NzlAMDQ2MS1pdHMtZXhtYjA5LnVzLnNhaWMuY29tPiA8MDZENDZFQUZGN0QwQzk0NkJFQzEwOERC
N0NDREM5QTYwOEI0MzUzNEBST0NNWFVTMjEuY3MubXloYXJyaXMubmV0PgAAAB4ARxABAAAADwAA
AG1lc3NhZ2UvcmZjODIyAAALAPIQAQAAAB8A8xABAAAAYgAAAFIARQAlADMAQQAgAFsAYwBpAGMA
bQBdACAAQgBvAEYAIABSAGUAcQB1AGUAcwB0ACAAZgBvAHIAIABDAEkAQwBNACAAYQB0ACAASQBF
AFQARgAgADgAMQAuAEUATQBMAAAAAAALAPYQAAAAAEAABzAfV5CaLRrMAUAACDA5U+3gLRrMAQMA
3j+vbwAAAwDxPwkEAAAeAPg/AQAAABIAAABEYXZpZHNvbiwgSm9obiBBLgAAAAIB+T8BAAAATgAA
AAAAAADcp0DIwEIQGrS5CAArL+GCAQAAAAAAAAAvTz1TQUlDL09VPVVTLVNELVBMVEMvQ049UkVD
SVBJRU5UUy9DTj1EQVZJRFNPTkpBAAAAHgD6PwEAAAAVAAAAU3lzdGVtIEFkbWluaXN0cmF0b3IA
AAAAAgH7PwEAAAAeAAAAAAAAANynQMjAQhAatLkIACsv4YIBAAAAAAAAAC4AAAADAP0/5AQAAAMA
GUAAAAAAAwAaQAAAAAADAB1AAAAAAAMAHkAAAAAAHgAwQAEAAAALAAAAREFWSURTT05KQQAAHgAx
QAEAAAALAAAAREFWSURTT05KQQAAHgAyQAEAAAAWAAAAY2ljbS1ib3VuY2VzQGlldGYub3JnAAAA
HgAzQAEAAAATAAAAamZpdHRvbkBoYXJyaXMuY29tAAAeADhAAQAAAAsAAABEQVZJRFNPTkpBAAAe
ADlAAQAAAAIAAAAuAAAAAwB2QP////8LACkAAAAAAAsAIwAAAAAAAwAGEGcKhOoDAAcQRgcAAAMA
EBAAAAAAAwAREAAAAAAeAAgQAQAAAGUAAABKT0hOLFRIQVRJTlZPTFZFU1RIQVRUSElOR1dFQUdS
RUVUT0RJU0FHUkVFT05MRVRTUExFQVNFVEFLRVRIQVRDT05USU5VSU5HRElTQ1VTU0lPTk9GRkxJ
TkVUSEFOS1MsSk9IAAAAAAIBfwABAAAARQAAADw3RURERDg3QTlBMUQ3RjREQjZGNzhCQzU1QUE0
OTU1MDJGNzMzRkAwNDYxLWl0cy1leG1iMDkudXMuc2FpYy5jb20+AAAAAJXP

------_=_NextPart_001_01CC1A2D.E0DCA2A7--

------------=_1306253779-27929-1--

From JOHN.A.DAVIDSON@saic.com  Tue May 24 10:44:33 2011
Return-Path: <JOHN.A.DAVIDSON@saic.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 91B6FE073D for <cicm@ietfa.amsl.com>; Tue, 24 May 2011 10:44:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 6p5yUrIstgxg for <cicm@ietfa.amsl.com>; Tue, 24 May 2011 10:44:32 -0700 (PDT)
Received: from cpmx2.mail.saic.com (cpmx2.mail.saic.com [139.121.17.172]) by ietfa.amsl.com (Postfix) with ESMTP id D6F8EE067F for <cicm@ietf.org>; Tue, 24 May 2011 10:44:32 -0700 (PDT)
Received: from 0599-its-sbg02.saic.com ([139.121.20.253] [139.121.20.253]) by cpmx2.mail.saic.com with ESMTP id BT-MMP-1012822 for cicm@ietf.org; Tue, 24 May 2011 10:44:18 -0700
X-AuditID: 8b7911db-b7c5bae0000051d3-c5-4ddbee726aaf
Received: from 0599-its-exbh01.us.saic.com (cpe-z7-si-srcnat.sw.saic.com [139.121.20.253]) by 0599-its-sbg02.saic.com (Symantec Brightmail Gateway) with SMTP id AC.5F.20947.27EEBDD4; Tue, 24 May 2011 10:44:18 -0700 (PDT)
Received: from 0461-its-exmb09.us.saic.com ([10.8.67.20]) by 0599-its-exbh01.us.saic.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 24 May 2011 10:44:18 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CC1A3A.347CAE97"
Date: Tue, 24 May 2011 10:44:17 -0700
Message-Id: <7EDDD87A9A1D7F4DB6F78BC55AA495502B777A@0461-its-exmb09.us.saic.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [cicm] BoF Request for CICM at IETF 81
Thread-Index: AQHMGWhrWYa5rmedwkWeZn8qfUYp4ZSbI8TfgAEd02Y=
From: "Davidson, John A." <JOHN.A.DAVIDSON@saic.com>
To: <cicm@ietf.org>
X-OriginalArrivalTime: 24 May 2011 17:44:18.0117 (UTC) FILETIME=[34AE5F50:01CC1A3A]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [cicm] BoF Request for CICM at IETF 81
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: Tue, 24 May 2011 17:44:33 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CC1A3A.347CAE97
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: base64

Sm9obiwgVGhhdCBpbnZvbHZlcyB0aGF0IHRoaW5nIHdlIGFncmVlIHRvIGRpc2FncmVlIG9uLiAg
TGV0cyBwbGVhc2UgdGFrZSB0aGF0IGNvbnRpbnVpbmcgZGlzY3Vzc2lvbiBvZmYgbGluZS4gIFRo
YW5rcywgSm9obg0KDQoNCi0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0NCkZyb206IGNpY20t
Ym91bmNlc0BpZXRmLm9yZyA8Y2ljbS1ib3VuY2VzQGlldGYub3JnPg0KVG86IENJQ00gRGlzY3Vz
c2lvbiBMaXN0IDxjaWNtQGlldGYub3JnPg0KU2VudDogTW9uIE1heSAyMyAxNzo1Mjo0NSAyMDEx
DQpTdWJqZWN0OiBSZTogW2NpY21dIEJvRiBSZXF1ZXN0IGZvciBDSUNNIGF0IElFVEYgODENCg0K
Sm9obiwgSSBkb24ndCBiZWxpZXZlIHRoYXQgd2FzIHF1aXRlIHRydWUuIEkgYmVsaWV2ZSB5b3Ug
YXJlIGludGVycHJldGluZyBCZWxsLUxhUGFkdWEgYXMgYW4gb3ZlcmFsbCBzZWN1cml0eSBwb2xp
Y3ksIHdoZW4gaW4gZmFjdCBpcyB3YXMgc3RyaWN0bHkgYW4gYWNjZXNzIGNvbnRyb2wgcG9saWN5
IGFzIHdlcmUgbW9zdCBDT01QVVNFQyBwb2xpY2llcy4gIFRoZSBVUyBHb3Zlcm5tZW50J3MgY2xh
c3NpZmljYXRpb24gc3lzdGVtIGlzIGluIGZhY3QgcGFydCBvZiBhbiBhY2Nlc3MgY29udHJvbCBw
b2xpY3kuICBIaWdoIEFzc3VyYW5jZSBpcyBhY2hpZXZlZCB3aGVuIGl0IGNhbiBiZSBzaG93biB0
aGF0IHRoZSBzZWN1cml0eSBwb2xpY3kgZm9yIGEgcGxhdGZvcm0gaXMgcmlnb3JvdXNseSBlbmZv
cmNlZCBieSB0aGUgc2VjdXJpdHkgbWVjaGFuaXNtcy4uLnJlZ2FyZGxlc3Mgd2hhdCB0aGF0IHNl
Y3VyaXR5IHBvbGljeSBtYXkgYmUuICBFdmVuIHRoZSBhY2Nlc3MgY29udHJvbCBwb2xpY3kgd2hp
Y2ggc2F5cyAibm8gZmxvdyBkb3duIiBjYW4gYmUgImJlbnQiIGluIHJlYWwgd29ybGQgc2l0dWF0
aW9ucyB3aGVuIHRoZSBzaXR1YXRpb24gZGVtYW5kcy4gIFRoaW5ncyBhcmUgbmV2ZXIganVzdCBi
bGFjayBhbmQgd2hpdGUgKG9yIHBlcmhhcHMgSSBzaG91bGQgc2F5IGJsYWNrIGFuZCByZWQpLg0K
DQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KRnJvbTogRGF2aWRzb24sIEpvaG4g
QS4gW0pPSE4uQS5EQVZJRFNPTkBzYWljLmNvbV0NClNlbnQ6IE1vbmRheSwgTWF5IDIzLCAyMDEx
IDEwOjA2IEFNDQpUbzogY2ljbUBpZXRmLm9yZw0KU3ViamVjdDogUmU6IFtjaWNtXSBCb0YgUmVx
dWVzdCBmb3IgQ0lDTSBhdCBJRVRGIDgxDQoNCg0KVGhlIGNvbnZlbnRpb25hbCBDT01QVVNFQyB2
aWV3IG9mIGhpZ2ggYXNzdXJhbmNlIHdhcyB0aGF0IC0gaXQgd2FzIGluZGljYXRlZCB3aGVyZSB0
aGUgUG9saWN5IGhhZCB0byBiZSBlbmZvcmNlZCBmb3IgY2VydGFpbiAobWFuZGF0b3J5KSBlLmcu
IG5vIGZsb3cgZG93biB0b2xlcmF0ZWQuDQoNCi0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0N
CkZyb206IGNpY20tYm91bmNlc0BpZXRmLm9yZyA8Y2ljbS1ib3VuY2VzQGlldGYub3JnPg0KVG86
IENJQ00gRGlzY3Vzc2lvbiBMaXN0IDxjaWNtQGlldGYub3JnPg0KU2VudDogTW9uIE1heSAyMyAw
NToyNzo0NSAyMDExDQpTdWJqZWN0OiBSZTogW2NpY21dIEJvRiBSZXF1ZXN0IGZvciBDSUNNIGF0
IElFVEYgODENCg0KUmljaGFyZCwNCg0KT24gMjAxMS0wNS0yMiBhdCAwNjozNiwgUmljaGFyZCBH
cmF2ZW1hbiB3cm90ZToNCj4gSXQgc2VlbXMgdG8gbWUgdGhhdCBoaWdoIGFzc3VyYW5jZSBtYXkg
d2VsbCBiZSBuZWVkZWQgaW4gY2FzZXMgd2l0aA0KPiBvbmx5IG9uZSBkb21haW4uIElzIHRoYXQg
b3V0IG9mIHNjb3BlPw0KDQpTaW5nbGUgZG9tYWluIHVzZSBjYXNlcyBhcmUgZGVmaW5pdGVseSBp
biBzY29wZTsgYnV0IHRoZXkgYXJlIHZlcnkgc2ltaWxhcg0KKGNvbmNlcHR1YWxseSkgdG8gZXhp
c3RpbmcgY29tbWVyY2lhbCBjcnlwdG8gQVBJcy4gVGhlIGFiaWxpdHkgdG8gc2VwYXJhdGUNCmRv
bWFpbnMgaXMgd2hhdCBzZXRzIENJQ00gYXBhcnQuDQoNClNlZToNCiIyLjMuIFNpbmdsZSBTZWN1
cml0eSBEb21haW4iIGluIENJQ00gTG9naWNhbCBNb2RlbA0KaHR0cDovL3Rvb2xzLmlldGYub3Jn
L2h0bWwvZHJhZnQtbGFuei1jaWNtLWxtLTAwI3NlY3Rpb24tMi4zDQoNCiIxOC4gU2luZ2xlLURv
bWFpbiIgaW4gQ0lDTSBDaGFubmVsIE1hbmFnZW1lbnQNCmh0dHA6Ly90b29scy5pZXRmLm9yZy9o
dG1sL2RyYWZ0LWxhbnotY2ljbS1jbS0wMCNzZWN0aW9uLTE4DQoNCkxldg0KX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCmNpY20gbWFpbGluZyBsaXN0DQpj
aWNtQGlldGYub3JnDQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2NpY20N
Cl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQpjaWNtIG1h
aWxpbmcgbGlzdA0KY2ljbUBpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9s
aXN0aW5mby9jaWNtDQo=

------_=_NextPart_001_01CC1A3A.347CAE97
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDMuMi8vRU4iPg0KPEhUTUw+
DQo8SEVBRD4NCjxNRVRBIEhUVFAtRVFVSVY9IkNvbnRlbnQtVHlwZSIgQ09OVEVOVD0idGV4dC9o
dG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxNRVRBIE5BTUU9IkdlbmVyYXRvciIgQ09OVEVOVD0iTVMg
RXhjaGFuZ2UgU2VydmVyIHZlcnNpb24gNi41Ljc2NTQuMTIiPg0KPFRJVExFPlJlOiBbY2ljbV0g
Qm9GIFJlcXVlc3QgZm9yIENJQ00gYXQgSUVURiA4MTwvVElUTEU+DQo8L0hFQUQ+DQo8Qk9EWT4N
CjwhLS0gQ29udmVydGVkIGZyb20gdGV4dC9wbGFpbiBmb3JtYXQgLS0+DQoNCjxQPjxGT05UIFNJ
WkU9Mj5Kb2huLCBUaGF0IGludm9sdmVzIHRoYXQgdGhpbmcgd2UgYWdyZWUgdG8gZGlzYWdyZWUg
b24uJm5ic3A7IExldHMgcGxlYXNlIHRha2UgdGhhdCBjb250aW51aW5nIGRpc2N1c3Npb24gb2Zm
IGxpbmUuJm5ic3A7IFRoYW5rcywgSm9objxCUj4NCjxCUj4NCjxCUj4NCi0tLS0tIE9yaWdpbmFs
IE1lc3NhZ2UgLS0tLS08QlI+DQpGcm9tOiBjaWNtLWJvdW5jZXNAaWV0Zi5vcmcgJmx0O2NpY20t
Ym91bmNlc0BpZXRmLm9yZyZndDs8QlI+DQpUbzogQ0lDTSBEaXNjdXNzaW9uIExpc3QgJmx0O2Np
Y21AaWV0Zi5vcmcmZ3Q7PEJSPg0KU2VudDogTW9uIE1heSAyMyAxNzo1Mjo0NSAyMDExPEJSPg0K
U3ViamVjdDogUmU6IFtjaWNtXSBCb0YgUmVxdWVzdCBmb3IgQ0lDTSBhdCBJRVRGIDgxPEJSPg0K
PEJSPg0KSm9obiwgSSBkb24ndCBiZWxpZXZlIHRoYXQgd2FzIHF1aXRlIHRydWUuIEkgYmVsaWV2
ZSB5b3UgYXJlIGludGVycHJldGluZyBCZWxsLUxhUGFkdWEgYXMgYW4gb3ZlcmFsbCBzZWN1cml0
eSBwb2xpY3ksIHdoZW4gaW4gZmFjdCBpcyB3YXMgc3RyaWN0bHkgYW4gYWNjZXNzIGNvbnRyb2wg
cG9saWN5IGFzIHdlcmUgbW9zdCBDT01QVVNFQyBwb2xpY2llcy4mbmJzcDsgVGhlIFVTIEdvdmVy
bm1lbnQncyBjbGFzc2lmaWNhdGlvbiBzeXN0ZW0gaXMgaW4gZmFjdCBwYXJ0IG9mIGFuIGFjY2Vz
cyBjb250cm9sIHBvbGljeS4mbmJzcDsgSGlnaCBBc3N1cmFuY2UgaXMgYWNoaWV2ZWQgd2hlbiBp
dCBjYW4gYmUgc2hvd24gdGhhdCB0aGUgc2VjdXJpdHkgcG9saWN5IGZvciBhIHBsYXRmb3JtIGlz
IHJpZ29yb3VzbHkgZW5mb3JjZWQgYnkgdGhlIHNlY3VyaXR5IG1lY2hhbmlzbXMuLi5yZWdhcmRs
ZXNzIHdoYXQgdGhhdCBzZWN1cml0eSBwb2xpY3kgbWF5IGJlLiZuYnNwOyBFdmVuIHRoZSBhY2Nl
c3MgY29udHJvbCBwb2xpY3kgd2hpY2ggc2F5cyAmcXVvdDtubyBmbG93IGRvd24mcXVvdDsgY2Fu
IGJlICZxdW90O2JlbnQmcXVvdDsgaW4gcmVhbCB3b3JsZCBzaXR1YXRpb25zIHdoZW4gdGhlIHNp
dHVhdGlvbiBkZW1hbmRzLiZuYnNwOyBUaGluZ3MgYXJlIG5ldmVyIGp1c3QgYmxhY2sgYW5kIHdo
aXRlIChvciBwZXJoYXBzIEkgc2hvdWxkIHNheSBibGFjayBhbmQgcmVkKS48QlI+DQo8QlI+DQpf
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxCUj4NCkZyb206IERhdmlkc29uLCBKb2hu
IEEuIFtKT0hOLkEuREFWSURTT05Ac2FpYy5jb21dPEJSPg0KU2VudDogTW9uZGF5LCBNYXkgMjMs
IDIwMTEgMTA6MDYgQU08QlI+DQpUbzogY2ljbUBpZXRmLm9yZzxCUj4NClN1YmplY3Q6IFJlOiBb
Y2ljbV0gQm9GIFJlcXVlc3QgZm9yIENJQ00gYXQgSUVURiA4MTxCUj4NCjxCUj4NCjxCUj4NClRo
ZSBjb252ZW50aW9uYWwgQ09NUFVTRUMgdmlldyBvZiBoaWdoIGFzc3VyYW5jZSB3YXMgdGhhdCAt
IGl0IHdhcyBpbmRpY2F0ZWQgd2hlcmUgdGhlIFBvbGljeSBoYWQgdG8gYmUgZW5mb3JjZWQgZm9y
IGNlcnRhaW4gKG1hbmRhdG9yeSkgZS5nLiBubyBmbG93IGRvd24gdG9sZXJhdGVkLjxCUj4NCjxC
Uj4NCi0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS08QlI+DQpGcm9tOiBjaWNtLWJvdW5jZXNA
aWV0Zi5vcmcgJmx0O2NpY20tYm91bmNlc0BpZXRmLm9yZyZndDs8QlI+DQpUbzogQ0lDTSBEaXNj
dXNzaW9uIExpc3QgJmx0O2NpY21AaWV0Zi5vcmcmZ3Q7PEJSPg0KU2VudDogTW9uIE1heSAyMyAw
NToyNzo0NSAyMDExPEJSPg0KU3ViamVjdDogUmU6IFtjaWNtXSBCb0YgUmVxdWVzdCBmb3IgQ0lD
TSBhdCBJRVRGIDgxPEJSPg0KPEJSPg0KUmljaGFyZCw8QlI+DQo8QlI+DQpPbiAyMDExLTA1LTIy
IGF0IDA2OjM2LCBSaWNoYXJkIEdyYXZlbWFuIHdyb3RlOjxCUj4NCiZndDsgSXQgc2VlbXMgdG8g
bWUgdGhhdCBoaWdoIGFzc3VyYW5jZSBtYXkgd2VsbCBiZSBuZWVkZWQgaW4gY2FzZXMgd2l0aDxC
Uj4NCiZndDsgb25seSBvbmUgZG9tYWluLiBJcyB0aGF0IG91dCBvZiBzY29wZT88QlI+DQo8QlI+
DQpTaW5nbGUgZG9tYWluIHVzZSBjYXNlcyBhcmUgZGVmaW5pdGVseSBpbiBzY29wZTsgYnV0IHRo
ZXkgYXJlIHZlcnkgc2ltaWxhcjxCUj4NCihjb25jZXB0dWFsbHkpIHRvIGV4aXN0aW5nIGNvbW1l
cmNpYWwgY3J5cHRvIEFQSXMuIFRoZSBhYmlsaXR5IHRvIHNlcGFyYXRlPEJSPg0KZG9tYWlucyBp
cyB3aGF0IHNldHMgQ0lDTSBhcGFydC48QlI+DQo8QlI+DQpTZWU6PEJSPg0KJnF1b3Q7Mi4zLiBT
aW5nbGUgU2VjdXJpdHkgRG9tYWluJnF1b3Q7IGluIENJQ00gTG9naWNhbCBNb2RlbDxCUj4NCjxB
IEhSRUY9Imh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWxhbnotY2ljbS1sbS0wMCNz
ZWN0aW9uLTIuMyI+aHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtbGFuei1jaWNtLWxt
LTAwI3NlY3Rpb24tMi4zPC9BPjxCUj4NCjxCUj4NCiZxdW90OzE4LiBTaW5nbGUtRG9tYWluJnF1
b3Q7IGluIENJQ00gQ2hhbm5lbCBNYW5hZ2VtZW50PEJSPg0KPEEgSFJFRj0iaHR0cDovL3Rvb2xz
LmlldGYub3JnL2h0bWwvZHJhZnQtbGFuei1jaWNtLWNtLTAwI3NlY3Rpb24tMTgiPmh0dHA6Ly90
b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWxhbnotY2ljbS1jbS0wMCNzZWN0aW9uLTE4PC9BPjxC
Uj4NCjxCUj4NCkxldjxCUj4NCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fPEJSPg0KY2ljbSBtYWlsaW5nIGxpc3Q8QlI+DQpjaWNtQGlldGYub3JnPEJSPg0K
PEEgSFJFRj0iaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9jaWNtIj5odHRw
czovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2NpY208L0E+PEJSPg0KX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188QlI+DQpjaWNtIG1haWxpbmcg
bGlzdDxCUj4NCmNpY21AaWV0Zi5vcmc8QlI+DQo8QSBIUkVGPSJodHRwczovL3d3dy5pZXRmLm9y
Zy9tYWlsbWFuL2xpc3RpbmZvL2NpY20iPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlz
dGluZm8vY2ljbTwvQT48QlI+DQo8L0ZPTlQ+DQo8L1A+DQoNCjwvQk9EWT4NCjwvSFRNTD4=

------_=_NextPart_001_01CC1A3A.347CAE97--

From jfitton@harris.com  Wed May 25 10:21:39 2011
Return-Path: <jfitton@harris.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 42619E0755 for <cicm@ietfa.amsl.com>; Wed, 25 May 2011 10:21:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 ItpbONCwmy+b for <cicm@ietfa.amsl.com>; Wed, 25 May 2011 10:21:38 -0700 (PDT)
Received: from mlbe2k2.cs.myharris.net (mlbe2k2.cs.myharris.net [137.237.90.89]) by ietfa.amsl.com (Postfix) with ESMTP id 63C77E075A for <cicm@ietf.org>; Wed, 25 May 2011 10:21:38 -0700 (PDT)
Received: from mail pickup service by mlbe2k2.cs.myharris.net with Microsoft SMTPSVC; Wed, 25 May 2011 13:21:29 -0400
Received: from mlbrst2.cs.myharris.net ([137.237.89.11]) by mlbe2k2.cs.myharris.net with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 25 May 2011 13:21:22 -0400
Received: from MLBMXHTUS1.cs.myharris.net ([137.237.89.77]) by mlbrst2.cs.myharris.net with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 25 May 2011 13:21:15 -0400
Received: from ROCMXCAHT22.cs.myharris.net (10.64.228.25) by MLBMXHTUS1.cs.myharris.net (137.237.89.77) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 25 May 2011 13:21:15 -0400
Received: from ROCMXUS21.cs.myharris.net ([fe80::1161:8dee:2d75:5ac]) by ROCMXCAHT22.cs.myharris.net ([::1]) with mapi id 14.01.0270.001; Wed, 25 May 2011 13:21:14 -0400
From: "Fitton, John" <jfitton@harris.com>
To: CICM Discussion List <cicm@ietf.org>
Thread-Topic: [cicm] BoF Request for CICM at IETF 81
Thread-Index: AQHMGkVXWYa5rmedwkWeZn8qfUYp4ZSdyDsz
Date: Wed, 25 May 2011 17:21:12 +0000
Message-ID: <06D46EAFF7D0C946BEC108DB7CCDC9A608B465F3@ROCMXUS21.cs.myharris.net>
References: <7EDDD87A9A1D7F4DB6F78BC55AA495502B777A@0461-its-exmb09.us.saic.com>
In-Reply-To: <7EDDD87A9A1D7F4DB6F78BC55AA495502B777A@0461-its-exmb09.us.saic.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.64.228.54]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 25 May 2011 17:21:15.0956 (UTC) FILETIME=[27431740:01CC1B00]
Subject: Re: [cicm] BoF Request for CICM at IETF 81
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: Wed, 25 May 2011 17:21:39 -0000

John



I don't believe this iis  an off-line subject. As I recall we agreed to def=
er discussion of "Bypass" to an off-line topic. The topic we are discussing=
 concerns what constitutes high assurance. I am simply pointing out that th=
e "COMPUSEC" policy you were referring to was an access control policy and =
that the specifics of a given policy have nothing to do with the definition=
 of what is or isn't high assurance.  Assurance has to do with the strength=
 or rubustness of the measures used to enforce any given set of security po=
licies.  As a practical matter, the security policy does have bearing becau=
se unless the assets being protected are considered valuable (either intrin=
sically or otherwise) it is unlikely that the related security policies wil=
l be very strong nor will it be considered as cost-effective to invest in m=
easures that would provide high assurance.



Another aspect of high assurance is that whatever is being certified/evalua=
ted will almost certainly involve one or more independent evaluation groups=
 as part of the process.



I'd be interested in other's views on this topic.



Thanks



John F.



________________________________

From: Davidson, John A. [JOHN.A.DAVIDSON@saic.com]
Sent: Tuesday, May 24, 2011 1:44 PM
To: cicm@ietf.org
Subject: Re: [cicm] BoF Request for CICM at IETF 81


John, That involves that thing we agree to disagree on.  Lets please take t=
hat continuing discussion off line.  Thanks, John


----- Original Message -----
From: cicm-bounces@ietf.org <cicm-bounces@ietf.org>
To: CICM Discussion List <cicm@ietf.org>
Sent: Mon May 23 17:52:45 2011
Subject: Re: [cicm] BoF Request for CICM at IETF 81

John, I don't believe that was quite true. I believe you are interpreting B=
ell-LaPadua as an overall security policy, when in fact is was strictly an =
access control policy as were most COMPUSEC policies.  The US Government's =
classification system is in fact part of an access control policy.  High As=
surance is achieved when it can be shown that the security policy for a pla=
tform is rigorously enforced by the security mechanisms...regardless what t=
hat security policy may be.  Even the access control policy which says "no =
flow down" can be "bent" in real world situations when the situation demand=
s.  Things are never just black and white (or perhaps I should say black an=
d red).

________________________________
From: Davidson, John A. [JOHN.A.DAVIDSON@saic.com]
Sent: Monday, May 23, 2011 10:06 AM
To: cicm@ietf.org
Subject: Re: [cicm] BoF Request for CICM at IETF 81


The conventional COMPUSEC view of high assurance was that - it was indicate=
d where the Policy had to be enforced for certain (mandatory) e.g. no flow =
down tolerated.

----- Original Message -----
From: cicm-bounces@ietf.org <cicm-bounces@ietf.org>
To: CICM Discussion List <cicm@ietf.org>
Sent: Mon May 23 05:27:45 2011
Subject: Re: [cicm] BoF Request for CICM at IETF 81

Richard,

On 2011-05-22 at 06:36, Richard Graveman wrote:
> It seems to me that high assurance may well be needed in cases with
> only one domain. Is that out of scope?

Single domain use cases are definitely in scope; but they are very similar
(conceptually) to existing commercial crypto APIs. The ability to separate
domains is what sets CICM apart.

See:
"2.3. Single Security Domain" in CICM Logical Model
http://tools.ietf.org/html/draft-lanz-cicm-lm-00#section-2.3

"18. Single-Domain" in CICM Channel Management
http://tools.ietf.org/html/draft-lanz-cicm-cm-00#section-18

Lev
_______________________________________________
cicm mailing list
cicm@ietf.org
https://www.ietf.org/mailman/listinfo/cicm
_______________________________________________
cicm mailing list
cicm@ietf.org
https://www.ietf.org/mailman/listinfo/cicm

From girish.nanjundiah@viasat.com  Fri May 27 11:50:07 2011
Return-Path: <girish.nanjundiah@viasat.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 28C63E06A2 for <cicm@ietfa.amsl.com>; Fri, 27 May 2011 11:50:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.109
X-Spam-Level: 
X-Spam-Status: No, score=-1.109 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, HTML_MESSAGE=0.001]
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 Fq6Dpx0WLZ26 for <cicm@ietfa.amsl.com>; Fri, 27 May 2011 11:50:06 -0700 (PDT)
Received: from viasat.com (bateleur.viasat.com [199.106.52.160]) by ietfa.amsl.com (Postfix) with ESMTP id EEC0CE0671 for <cicm@ietf.org>; Fri, 27 May 2011 11:50:05 -0700 (PDT)
Received: from ([172.20.1.71]) by bateleur.viasat.com with ESMTP  id H6GMFJ1.45073024; Fri, 27 May 2011 11:50:02 -0700
Received: from vcaexch06.hq.corp.viasat.com ([172.18.46.74]) by VCAEXCH02.hq.corp.viasat.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 27 May 2011 11:50:02 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CC1C9E.D643BED0"
Date: Fri, 27 May 2011 11:49:41 -0700
Message-ID: <E3337014FCBC034BBD725917528D5D7BD08CB3@vcaexch06.hq.corp.viasat.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: CICM Questions
Thread-Index: AcwcntZQPbfelPIIQ4CFOB8a3OzA+w==
From: "Nanjundiah, Girish" <Girish.Nanjundiah@viasat.com>
To: <cicm@ietf.org>
X-OriginalArrivalTime: 27 May 2011 18:50:02.0324 (UTC) FILETIME=[E2D9D940:01CC1C9E]
Subject: [cicm] CICM Questions
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, 27 May 2011 18:50:07 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CC1C9E.D643BED0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hello Everyone,

=20

We are in the midst of implementing the CICM driver at ViaSat and we had
the following issues with the code:

=20

1.       When the function encrypt() sends a packet to the Crypto, it
emerges on the black side encrypted and decrypt() is expected to decrypt
this encrypted packet. In order for the packet to be decrypted, there
needs to be some function that echoes the encrypted packet back through
the black side. Since this echoing back seems to be more of an
application level function than a driver function, what part of the code
should be responsible for echoing the encrypted packet back through the
Crypto?

2.       When create_en/decrypt_conduit is finished executing, it needs
to store an identifier (just a number really) to identify the conduit it
has created with the Crypto. Since both of these functions only return a
status and a CICM::En/Decrypt::Conduit pointer, the only way to store
the identifier for the conduit to use is to add it as a member variable
to the Conduit class. If the variable is to be private, we would also
need a simple public member function to access it. Is there a way to
update the CICM API so that we can store the conduit's identifier in one
of the ways I listed?

=20

Can we please get some clarification on these issues?

=20

Thanks,

-Girish Nanjundiah


------_=_NextPart_001_01CC1C9E.D643BED0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:a=3D"urn:schemas-microsoft-com:office:access" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" =
xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" =
xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" =
xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" =
xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" =
xmlns:odc=3D"urn:schemas-microsoft-com:office:odc" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" =
xmlns:rtc=3D"http://microsoft.com/officenet/conferencing" =
xmlns:D=3D"DAV:" xmlns:Repl=3D"http://schemas.microsoft.com/repl/" =
xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" =
xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" =
xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" =
xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" =
xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" =
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" =
xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" =
xmlns:udc=3D"http://schemas.microsoft.com/data/udc" =
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" =
xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"=
 xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" =
xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" =
xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" =
xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" =
xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/parttopart" =
xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" =
xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup" =
xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" =
xmlns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-sig=
nature" =
xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006=
" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relationshi=
ps" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" =
xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"=
 =
xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag=
es" =
xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/=
" =
xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Pub=
lishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" =
xmlns:st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1696806520;
	mso-list-type:hybrid;
	mso-list-template-ids:244850786 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.25in;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>Hello =
Everyone,<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>We are in the midst of implementing the CICM driver at =
ViaSat and we had the following issues with the code:<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoListParagraph =
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span style=3D'color:#1F497D'><span =
style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span style=3D'color:#1F497D'>When the =
function encrypt() sends a packet to the Crypto, it emerges on the black =
side encrypted and decrypt() is expected to decrypt this encrypted =
packet. In order for the packet to be decrypted, there needs to be some =
function that echoes the encrypted packet back through the black side. =
Since this echoing back seems to be more of an application level =
function than a driver function, what part of the code should be =
responsible for echoing the encrypted packet back through the =
Crypto?<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span style=3D'color:#1F497D'><span =
style=3D'mso-list:Ignore'>2.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span style=3D'color:#1F497D'>When =
create_en/decrypt_conduit is finished executing, it needs to store an =
identifier (just a number really) to identify the conduit it has created =
with the Crypto. Since both of these functions only return a status and =
a CICM::En/Decrypt::Conduit pointer, the only way to store the =
identifier for the conduit to use is to add it as a member variable to =
the Conduit class. If the variable is to be private, we would also need =
a simple public member function to access it. Is there a way to update =
the CICM API so that we can store the conduit&#8217;s identifier in one =
of the ways I listed?<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:.5in'><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Can =
we please get some clarification on these issues?<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Thanks,<o:p></o:p></p><p class=3DMsoNormal>-Girish =
Nanjundiah<o:p></o:p></p></div></body></html>
------_=_NextPart_001_01CC1C9E.D643BED0--

From lnovikov@mitre.org  Fri May 27 12:47:10 2011
Return-Path: <lnovikov@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 30060E0769 for <cicm@ietfa.amsl.com>; Fri, 27 May 2011 12:47:10 -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 1-Lft0feITXA for <cicm@ietfa.amsl.com>; Fri, 27 May 2011 12:47:07 -0700 (PDT)
Received: from smtpksrv1.mitre.org (smtpksrv1.mitre.org [198.49.146.77]) by ietfa.amsl.com (Postfix) with ESMTP id C9BEEE077B for <cicm@ietf.org>; Fri, 27 May 2011 12:47:07 -0700 (PDT)
Received: from smtpksrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 9F6DD21B1985 for <cicm@ietf.org>; Fri, 27 May 2011 15:47:06 -0400 (EDT)
Received: from imchub1.MITRE.ORG (imchub1.mitre.org [129.83.29.73]) by smtpksrv1.mitre.org (Postfix) with ESMTP id 9C1EA21B17C3 for <cicm@ietf.org>; Fri, 27 May 2011 15:47:06 -0400 (EDT)
Received: from IMCMBX3.MITRE.ORG ([129.83.29.206]) by imchub1.MITRE.ORG ([129.83.29.73]) with mapi; Fri, 27 May 2011 15:47:06 -0400
From: "Novikov, Lev" <lnovikov@mitre.org>
To: CICM Discussion List <cicm@ietf.org>
Date: Fri, 27 May 2011 15:46:32 -0400
Thread-Topic: Moving Packets and Storing Identifiers (was RE: CICM Questions)
Thread-Index: AcwcpsTkd/0hRpvdRrCyJDEF6zWhTw==
Message-ID: <F9AB58FA72BAE7449E7723791F6993ED05D32435B2@IMCMBX3.MITRE.ORG>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [cicm] Moving Packets and Storing Identifiers (was RE: CICM Questions)
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, 27 May 2011 19:47:10 -0000

Hi Girish,

On 2011-05-27 at 14:50, Girish Nanjundiah wrote:
> 1. When the function encrypt() sends a packet to the Crypto, it emerges o=
n=20
> the black side encrypted and decrypt() is expected to decrypt this encryp=
ted
> packet. In order for the packet to be decrypted, there needs to be some=20
> function that echoes the encrypted packet back through the black side. Si=
nce
> this echoing back seems to be more of an application level function than =
a=20
> driver function, what part of the code should be responsible for echoing =
the
> encrypted packet back through the Crypto?

Another way of asking this question is: What functions move data from the=20
remote (unprotected) side of a crypto into the local (protected) side?

See also:
"Does CICM only provide (specify) the "red" side API in a multilevel system=
?"
http://www.ietf.org/mail-archive/web/cicm/current/msg00014.html
http://www.ietf.org/mail-archive/web/cicm/current/msg00028.html

You correctly point out that this is not a driver-level function. In fact,
CICM does not define functions for simply moving data into the crypto.=20
Therefore, you are free to use whatever transport mechanism works for you=20
(e.g., POSIX socket).

> 2. When create_en/decrypt_conduit is finished executing, it needs to stor=
e=20
> an identifier (just a number really) to identify the conduit it has creat=
ed=20
> with the Crypto. Since both of these functions only return a status and a=
=20
> CICM::En/Decrypt::Conduit pointer, the only way to store the identifier f=
or=20
> the conduit to use is to add it as a member variable to the Conduit class=
.=20
> If the variable is to be private, we would also need a simple public memb=
er=20
> function to access it. Is there a way to update the CICM API so that we c=
an=20
> store the conduit's identifier in one of the ways I listed?

This is an interesting suggestion. We define KeyId for key identifiers, but=
=20
we do not define a ChannelId for channel identifiers. This is because there
isn't currently a way to lookup a channel by its identifier (like there is=
=20
for keys, modules, and tokens).

This is going to require some discussion. Normally, vendor-specific attribu=
tes
are defined by extending the CICM base object and adding those properties.=
=20
However, it seems like a common operation to store a vendor-specific=20
identifier in a CICM object to make it easy to reference the underlying obj=
ect
later on.

** What do people think about extending the API to allow vendors to store a=
=20
   single numeric value to uniquely identify the objects to the underlying=
=20
   system?
  =20
Lev

From girish.nanjundiah@viasat.com  Fri May 27 15:35:09 2011
Return-Path: <girish.nanjundiah@viasat.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 05BFFE06E2 for <cicm@ietfa.amsl.com>; Fri, 27 May 2011 15:35:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.854
X-Spam-Level: 
X-Spam-Status: No, score=-1.854 tagged_above=-999 required=5 tests=[AWL=0.745,  BAYES_00=-2.599]
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 GOGO+yewCIfe for <cicm@ietfa.amsl.com>; Fri, 27 May 2011 15:35:08 -0700 (PDT)
Received: from viasat.com (bateleur.viasat.com [199.106.52.160]) by ietfa.amsl.com (Postfix) with ESMTP id 47F95E0678 for <cicm@ietf.org>; Fri, 27 May 2011 15:35:08 -0700 (PDT)
Received: from ([172.20.1.71]) by bateleur.viasat.com with ESMTP  id H6GMFJ1.45087138; Fri, 27 May 2011 15:35:05 -0700
Received: from vcaexch06.hq.corp.viasat.com ([172.18.46.74]) by VCAEXCH02.hq.corp.viasat.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 27 May 2011 15:35:04 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 27 May 2011 15:34:43 -0700
Message-ID: <E3337014FCBC034BBD725917528D5D7BD08CB5@vcaexch06.hq.corp.viasat.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [cicm] Moving Packets and Storing Identifiers (was RE: CICMQuestions)
Thread-Index: AcwcpsTkd/0hRpvdRrCyJDEF6zWhTwAFtHkw
References: <F9AB58FA72BAE7449E7723791F6993ED05D32435B2@IMCMBX3.MITRE.ORG>
From: "Nanjundiah, Girish" <Girish.Nanjundiah@viasat.com>
To: "CICM Discussion List" <cicm@ietf.org>
X-OriginalArrivalTime: 27 May 2011 22:35:04.0972 (UTC) FILETIME=[530E6CC0:01CC1CBE]
Subject: Re: [cicm] Moving Packets and Storing Identifiers (was RE: CICMQuestions)
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, 27 May 2011 22:35:09 -0000

Hi Lev,

Thanks for the answers. In regards to the answer to the first question,
while we can define the actual mechanism to reflect back the packets
outside of the driver, the driver still needs to call the
function/mechanism that we define within its decrypt() function before
it can expect the packet to appear. Technically, this is still not
completely separated from the driver functionality. Is this still an
appropriate place to echo back black packets?

Thanks,
-Girish=20

-----Original Message-----
From: cicm-bounces@ietf.org [mailto:cicm-bounces@ietf.org] On Behalf Of
Novikov, Lev
Sent: Friday, May 27, 2011 12:47 PM
To: CICM Discussion List
Subject: [cicm] Moving Packets and Storing Identifiers (was RE:
CICMQuestions)

Hi Girish,

On 2011-05-27 at 14:50, Girish Nanjundiah wrote:
> 1. When the function encrypt() sends a packet to the Crypto, it
emerges on=20
> the black side encrypted and decrypt() is expected to decrypt this
encrypted
> packet. In order for the packet to be decrypted, there needs to be
some=20
> function that echoes the encrypted packet back through the black side.
Since
> this echoing back seems to be more of an application level function
than a=20
> driver function, what part of the code should be responsible for
echoing the
> encrypted packet back through the Crypto?

Another way of asking this question is: What functions move data from
the=20
remote (unprotected) side of a crypto into the local (protected) side?

See also:
"Does CICM only provide (specify) the "red" side API in a multilevel
system?"
http://www.ietf.org/mail-archive/web/cicm/current/msg00014.html
http://www.ietf.org/mail-archive/web/cicm/current/msg00028.html

You correctly point out that this is not a driver-level function. In
fact,
CICM does not define functions for simply moving data into the crypto.=20
Therefore, you are free to use whatever transport mechanism works for
you=20
(e.g., POSIX socket).

> 2. When create_en/decrypt_conduit is finished executing, it needs to
store=20
> an identifier (just a number really) to identify the conduit it has
created=20
> with the Crypto. Since both of these functions only return a status
and a=20
> CICM::En/Decrypt::Conduit pointer, the only way to store the
identifier for=20
> the conduit to use is to add it as a member variable to the Conduit
class.=20
> If the variable is to be private, we would also need a simple public
member=20
> function to access it. Is there a way to update the CICM API so that
we can=20
> store the conduit's identifier in one of the ways I listed?

This is an interesting suggestion. We define KeyId for key identifiers,
but=20
we do not define a ChannelId for channel identifiers. This is because
there
isn't currently a way to lookup a channel by its identifier (like there
is=20
for keys, modules, and tokens).

This is going to require some discussion. Normally, vendor-specific
attributes
are defined by extending the CICM base object and adding those
properties.=20
However, it seems like a common operation to store a vendor-specific=20
identifier in a CICM object to make it easy to reference the underlying
object
later on.

** What do people think about extending the API to allow vendors to
store a=20
   single numeric value to uniquely identify the objects to the
underlying=20
   system?
  =20
Lev
_______________________________________________
cicm mailing list
cicm@ietf.org
https://www.ietf.org/mailman/listinfo/cicm

From prvs=125c2e4c7=Hema.Krishnamurthy@itt.com  Tue May 31 08:22:16 2011
Return-Path: <prvs=125c2e4c7=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 E7BBAE0701 for <cicm@ietfa.amsl.com>; Tue, 31 May 2011 08:22:16 -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 5t4y+gNTyg0X for <cicm@ietfa.amsl.com>; Tue, 31 May 2011 08:22:16 -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 BFD2DE06D5 for <cicm@ietf.org>; Tue, 31 May 2011 08:22:15 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvIAADoH5U0KHOwG/2dsb2JhbABFDpdLj0mIcb1FgxeDBwSVFopv
X-IronPort-AV: E=Sophos;i="4.65,297,1304294400"; d="scan'208";a="99961635"
Received: from usfwa1exhub2.itt.net ([10.28.236.6]) by cip-fwa-c1.itt.com with ESMTP/TLS/AES128-SHA; 31 May 2011 15:21:50 +0000
Received: from USFWA1EXCAS5.itt.net (10.28.236.33) by USFWA1EXHUB2.itt.net (10.28.236.6) with Microsoft SMTP Server (TLS) id 8.2.255.0; Tue, 31 May 2011 11:21:50 -0400
Received: from CSFWCAS2.cs.de.ittind.com (10.32.129.152) by USFWA1EXCAS5.itt.net (10.28.236.33) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 31 May 2011 11:21:49 -0400
Received: from CSFWMAIL1.cs.de.ittind.com ([10.32.129.154]) by CSFWCAS2.cs.de.ittind.com ([10.32.129.152]) with mapi; Tue, 31 May 2011 11:21:49 -0400
From: "Krishnamurthy, Hema - ES" <Hema.Krishnamurthy@itt.com>
To: CICM Discussion List <cicm@ietf.org>
Date: Tue, 31 May 2011 11:21:48 -0400
Thread-Topic: [cicm] Moving Packets and Storing Identifiers (was RE: CICM Questions)
Thread-Index: AcwcpsTkd/0hRpvdRrCyJDEF6zWhTwC/6czA
Message-ID: <86150541B533894DAD5CB2DB3F4788520C677C81FF@CSFWMAIL1.cs.de.ittind.com>
References: <F9AB58FA72BAE7449E7723791F6993ED05D32435B2@IMCMBX3.MITRE.ORG>
In-Reply-To: <F9AB58FA72BAE7449E7723791F6993ED05D32435B2@IMCMBX3.MITRE.ORG>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [cicm] Moving Packets and Storing Identifiers (was RE: CICM	Questions)
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: Tue, 31 May 2011 15:22:17 -0000

I think providing a means to specify the channel ID would be useful.

-----Original Message-----
From: cicm-bounces@ietf.org [mailto:cicm-bounces@ietf.org] On Behalf Of Nov=
ikov, Lev
Sent: Friday, May 27, 2011 12:47 PM
To: CICM Discussion List
Subject: [cicm] Moving Packets and Storing Identifiers (was RE: CICM Questi=
ons)

Hi Girish,

On 2011-05-27 at 14:50, Girish Nanjundiah wrote:
> 1. When the function encrypt() sends a packet to the Crypto, it emerges o=
n
> the black side encrypted and decrypt() is expected to decrypt this encryp=
ted
> packet. In order for the packet to be decrypted, there needs to be some
> function that echoes the encrypted packet back through the black side. Si=
nce
> this echoing back seems to be more of an application level function than =
a
> driver function, what part of the code should be responsible for echoing =
the
> encrypted packet back through the Crypto?

Another way of asking this question is: What functions move data from the
remote (unprotected) side of a crypto into the local (protected) side?

See also:
"Does CICM only provide (specify) the "red" side API in a multilevel system=
?"
http://www.ietf.org/mail-archive/web/cicm/current/msg00014.html
http://www.ietf.org/mail-archive/web/cicm/current/msg00028.html

You correctly point out that this is not a driver-level function. In fact,
CICM does not define functions for simply moving data into the crypto.
Therefore, you are free to use whatever transport mechanism works for you
(e.g., POSIX socket).

> 2. When create_en/decrypt_conduit is finished executing, it needs to stor=
e
> an identifier (just a number really) to identify the conduit it has creat=
ed
> with the Crypto. Since both of these functions only return a status and a
> CICM::En/Decrypt::Conduit pointer, the only way to store the identifier f=
or
> the conduit to use is to add it as a member variable to the Conduit class=
.
> If the variable is to be private, we would also need a simple public memb=
er
> function to access it. Is there a way to update the CICM API so that we c=
an
> store the conduit's identifier in one of the ways I listed?

This is an interesting suggestion. We define KeyId for key identifiers, but
we do not define a ChannelId for channel identifiers. This is because there
isn't currently a way to lookup a channel by its identifier (like there is
for keys, modules, and tokens).

This is going to require some discussion. Normally, vendor-specific attribu=
tes
are defined by extending the CICM base object and adding those properties.
However, it seems like a common operation to store a vendor-specific
identifier in a CICM object to make it easy to reference the underlying obj=
ect
later on.

** What do people think about extending the API to allow vendors to store a
   single numeric value to uniquely identify the objects to the underlying
   system?

Lev
_______________________________________________
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 in=
tended solely for the use of the individual or entity to whom they are addr=
essed. 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 Corporati=
on. The recipient should check this e-mail and any attachments for the pres=
ence of viruses. ITT accepts no liability for any damage caused by any viru=
s transmitted by this e-mail.

From Steven.DiMedio@L-3Com.com  Tue May 31 08:43:12 2011
Return-Path: <Steven.DiMedio@L-3Com.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 DEE76E0739 for <cicm@ietfa.amsl.com>; Tue, 31 May 2011 08:43:12 -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 0VGqvWvuu+-O for <cicm@ietfa.amsl.com>; Tue, 31 May 2011 08:43:12 -0700 (PDT)
Received: from smtp4out.l-3com.com (smtp4out.l-3com.com [128.170.207.112]) by ietfa.amsl.com (Postfix) with ESMTP id 4CB30E0701 for <cicm@ietf.org>; Tue, 31 May 2011 08:43:12 -0700 (PDT)
X-filenames: None
X-filesizes: None
X-filetypes: None
X-IronPort-AV: E=Sophos;i="4.65,297,1304294400"; d="scan'208";a="276018817"
From: Steven.DiMedio@L-3Com.com
Received: from host-166-20-16-165.l-3com.com (HELO csemail02.cse.l-3com.com) ([166.20.16.165]) by smtp4out.l-3com.com with ESMTP; 31 May 2011 15:43:11 +0000
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Tue, 31 May 2011 11:43:10 -0400
Message-ID: <BB991CD915E5884B9E4D087F2C63EE0BD32DB1@csemail02.cse.l-3com.com>
In-Reply-To: <F9AB58FA72BAE7449E7723791F6993ED05D32435B2@IMCMBX3.MITRE.ORG>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [cicm] Moving Packets and Storing Identifiers (was RE: CICMQuestions)
Thread-Index: AcwcpsTkd/0hRpvdRrCyJDEF6zWhTwC7DKNA
References: <F9AB58FA72BAE7449E7723791F6993ED05D32435B2@IMCMBX3.MITRE.ORG>
To: "CICM Discussion List" <cicm@ietf.org>
Subject: Re: [cicm] Moving Packets and Storing Identifiers (was RE: CICMQuestions)
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: Tue, 31 May 2011 15:43:13 -0000

Lev (and group),=20

I'm implementing the CICM driver here at L3. I'd support the concept of
extending the API to allow vendors to store a conduit identifier as a
numeric value, such as channel ID.  This allows vendors to link the
conduits created through the API to their own internal hardware-specific
attributes for the conduits.

Regards,
  Steve DiMedio
  L-3 Communications
  856-338-4204



>> 2. When create_en/decrypt_conduit is finished executing, it needs to
store=20
>> an identifier (just a number really) to identify the conduit it has
created=20
>> with the Crypto. Since both of these functions only return a status
and a=20
>> CICM::En/Decrypt::Conduit pointer, the only way to store the
identifier for=20
>> the conduit to use is to add it as a member variable to the Conduit
class.=20
>> If the variable is to be private, we would also need a simple public
member=20
>> function to access it. Is there a way to update the CICM API so that
we can=20
>> store the conduit's identifier in one of the ways I listed?
>
>This is an interesting suggestion. We define KeyId for key identifiers,
but=20
>we do not define a ChannelId for channel identifiers. This is because
there
>isn't currently a way to lookup a channel by its identifier (like there
is=20
>for keys, modules, and tokens).
>
>This is going to require some discussion. Normally, vendor-specific
attributes
>are defined by extending the CICM base object and adding those
properties.=20
>However, it seems like a common operation to store a vendor-specific=20
>identifier in a CICM object to make it easy to reference the underlying
object
>later on.
>
>** What do people think about extending the API to allow vendors to
store a=20
>   single numeric value to uniquely identify the objects to the
underlying=20
>   system?
>  =20
>Lev



From JOHN.A.DAVIDSON@saic.com  Tue May 31 09:37:36 2011
Return-Path: <JOHN.A.DAVIDSON@saic.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 A7AE1E0795 for <cicm@ietfa.amsl.com>; Tue, 31 May 2011 09:37:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
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 ca0GibxRtmVG for <cicm@ietfa.amsl.com>; Tue, 31 May 2011 09:37:32 -0700 (PDT)
Received: from cpmx2.mail.saic.com (cpmx2.mail.saic.com [139.121.17.172]) by ietfa.amsl.com (Postfix) with ESMTP id 13559E07C9 for <cicm@ietf.org>; Tue, 31 May 2011 09:37:28 -0700 (PDT)
Received: from 0599-its-sbg03.saic.com ([139.121.20.253] [139.121.20.253]) by cpmx2.mail.saic.com with ESMTP id BT-MMP-1906678 for cicm@ietf.org; Tue, 31 May 2011 09:37:15 -0700
X-AuditID: 8b79132a-b7bf1ae00000097a-8b-4de5193b9901
Received: from 0599-its-exbh01.us.saic.com (cpe-z7-si-srcnat.sw.saic.com [139.121.20.253]) by 0599-its-sbg03.saic.com (Symantec Brightmail Gateway) with SMTP id 5D.83.02426.B3915ED4; Tue, 31 May 2011 09:37:15 -0700 (PDT)
Received: from 0461-its-exmb09.us.saic.com ([10.8.67.20]) by 0599-its-exbh01.us.saic.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 31 May 2011 09:37:15 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 31 May 2011 09:37:15 -0700
Message-Id: <7EDDD87A9A1D7F4DB6F78BC55AA495502B7785@0461-its-exmb09.us.saic.com>
In-Reply-To: <E3337014FCBC034BBD725917528D5D7BD08CB5@vcaexch06.hq.corp.viasat.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [cicm] Moving Packets and Storing Identifiers (was RE:CICMQuestions)
Thread-Index: AcwcpsTkd/0hRpvdRrCyJDEF6zWhTwAFtHkwALkzpTA=
References: <F9AB58FA72BAE7449E7723791F6993ED05D32435B2@IMCMBX3.MITRE.ORG> <E3337014FCBC034BBD725917528D5D7BD08CB5@vcaexch06.hq.corp.viasat.com>
From: "Davidson, John A." <JOHN.A.DAVIDSON@saic.com>
To: "CICM Discussion List" <cicm@ietf.org>
X-OriginalArrivalTime: 31 May 2011 16:37:15.0900 (UTC) FILETIME=[002503C0:01CC1FB1]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [cicm] Moving Packets and Storing Identifiers (was RE:CICMQuestions)
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: Tue, 31 May 2011 16:37:36 -0000

All,=20

This question is interesting an esoteric way, as it illustrates a point
about CICM support for high assurance (HA*).  Encrypted objects possess
security properties that are not compatible with unencrypted (or
decrypted) objects.  There are numerous other examples of objects in a
generic SDR that have security properties that are not compatible with
other objects. =20

To ensure secure operation (in general) I know of at least two
alternatives.  1. Trust the application software to do right (whatever
that is), and this is repeatedly debunked, (but we still pursue it
anyway) and 2. Define "secure behavior" in a Security Policy and enforce
it by a HA OE from beneath the application SW (the only way that has
really ever really worked for HA in practice). =20

Alternative 2 above implies objects with compatible security properties
need to be grouped in security domains and isolated from other
incompatible security domains by a HA OE, and the HA OE must prevent
some of the flow in some directions between some of these domains,
(allowable flow being defined by a Security Policy) including precluding
some of the "echoing" suggested by the question.  I claim there exist a
structure for security domains in generic secure SDRs that does not
require harmful flow (obviating the need to "bend rules" with CDS
guards) among security domains and this structure is required for secure
behavior.  We have a science that produces this structure.  Furthermore,
I claim guards that "sanitize" objects are not logically sound in these
cases.  (These admittedly controversial claims are supported in an IEEE
paper "On The Architecture of Secure SDRs"
<http://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=3D04753440>. )=20

It seems to me our APIs support flow that we do not need in a securely
structured SDR and should not really be allowable in secure SDR OE,
whether or not it is HA.  (*HA is just a term that implies a
successfully enforced security policy.)  My concern is that when we
assume the HW view of a crypto, that is red side / black side, we lack
enough "sides" to get the SDR job done without bending the rules.  It
worked in HW cryptos that connected physically isolated functions with
physical wires but when we emulate that in SW along with additional
radio functions with APIs, we really do need APIs that bend rules.  This
gives rise to questions like this.  I am still hoping to propose a
"guidance" section for CICM on how to structure an SDR to avoid these
issues. =20

So that is my opinion.=20
Thanks,=20
John =20

-----Original Message-----
From: cicm-bounces@ietf.org [mailto:cicm-bounces@ietf.org] On Behalf Of
Nanjundiah, Girish
Sent: Friday, May 27, 2011 3:35 PM
To: CICM Discussion List
Subject: Re: [cicm] Moving Packets and Storing Identifiers (was
RE:CICMQuestions)

Hi Lev,

Thanks for the answers. In regards to the answer to the first question,
while we can define the actual mechanism to reflect back the packets
outside of the driver, the driver still needs to call the
function/mechanism that we define within its decrypt() function before
it can expect the packet to appear. Technically, this is still not
completely separated from the driver functionality. Is this still an
appropriate place to echo back black packets?

Thanks,
-Girish=20

-----Original Message-----
From: cicm-bounces@ietf.org [mailto:cicm-bounces@ietf.org] On Behalf Of
Novikov, Lev
Sent: Friday, May 27, 2011 12:47 PM
To: CICM Discussion List
Subject: [cicm] Moving Packets and Storing Identifiers (was RE:
CICMQuestions)

Hi Girish,

On 2011-05-27 at 14:50, Girish Nanjundiah wrote:
> 1. When the function encrypt() sends a packet to the Crypto, it
emerges on=20
> the black side encrypted and decrypt() is expected to decrypt this
encrypted
> packet. In order for the packet to be decrypted, there needs to be
some=20
> function that echoes the encrypted packet back through the black side.
Since
> this echoing back seems to be more of an application level function
than a=20
> driver function, what part of the code should be responsible for
echoing the
> encrypted packet back through the Crypto?

Another way of asking this question is: What functions move data from
the=20
remote (unprotected) side of a crypto into the local (protected) side?

See also:
"Does CICM only provide (specify) the "red" side API in a multilevel
system?"
http://www.ietf.org/mail-archive/web/cicm/current/msg00014.html
http://www.ietf.org/mail-archive/web/cicm/current/msg00028.html

You correctly point out that this is not a driver-level function. In
fact,
CICM does not define functions for simply moving data into the crypto.=20
Therefore, you are free to use whatever transport mechanism works for
you=20
(e.g., POSIX socket).

> 2. When create_en/decrypt_conduit is finished executing, it needs to
store=20
> an identifier (just a number really) to identify the conduit it has
created=20
> with the Crypto. Since both of these functions only return a status
and a=20
> CICM::En/Decrypt::Conduit pointer, the only way to store the
identifier for=20
> the conduit to use is to add it as a member variable to the Conduit
class.=20
> If the variable is to be private, we would also need a simple public
member=20
> function to access it. Is there a way to update the CICM API so that
we can=20
> store the conduit's identifier in one of the ways I listed?

This is an interesting suggestion. We define KeyId for key identifiers,
but we do not define a ChannelId for channel identifiers. This is
because isn't currently a way to lookup a channel by its identifier
(like there is for keys, modules, and tokens).

This is going to require some discussion. Normally, vendor-specific
attributes are defined by extending the CICM base object and adding
those properties. However, it seems like a common operation to store a
vendor-specific identifier in a CICM object to make it easy to reference
the underlying object later on.

** What do people think about extending the API to allow vendors to
store a=20
   single numeric value to uniquely identify the objects to the
underlying=20
   system?
  =20
Lev
_______________________________________________
cicm mailing list
cicm@ietf.org
https://www.ietf.org/mailman/listinfo/cicm
_______________________________________________
cicm mailing list
cicm@ietf.org
https://www.ietf.org/mailman/listinfo/cicm
