Re: [cicm] Why do we need a high assurance API?
"Otaway Thomas" <othomas@arkhamtechnology.com> Thu, 21 July 2011 22:04 UTC
Return-Path: <othomas@arkhamtechnology.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 AEC7F21F8A1A for <cicm@ietfa.amsl.com>; Thu, 21 Jul 2011 15:04:49 -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 70Ct5v7FtvUI for <cicm@ietfa.amsl.com>; Thu, 21 Jul 2011 15:04:49 -0700 (PDT)
Received: from oproxy1-pub.bluehost.com (oproxy1-pub.bluehost.com [66.147.249.253]) by ietfa.amsl.com (Postfix) with SMTP id 073B421F8764 for <cicm@ietf.org>; Thu, 21 Jul 2011 15:04:48 -0700 (PDT)
Received: (qmail 29848 invoked by uid 0); 21 Jul 2011 22:04:48 -0000
Received: from unknown (HELO host236.hostmonster.com) (74.220.215.236) by oproxy1.bluehost.com with SMTP; 21 Jul 2011 22:04:48 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=arkhamtechnology.com; h=Received:Reply-To:From:To:References:In-Reply-To:Subject:Date:Organization:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:Thread-Index:Content-Language:X-Identified-User; b=REBs5X/IdZOSt6+qScGKEzGt0/1gEip6oiWT0jI+wPmKLkjLbgnFftVgMl5z1qrB/1OluIl19fJq7VR/cY/2RUQl4P8Xl1kbHTL3ffIMoAmSIEjHZfdhgU+g6Wqbdc5R;
Received: from [12.132.228.130] (helo=WIN91J4A5AH5KS) by host236.hostmonster.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <othomas@arkhamtechnology.com>) id 1Qk1MO-0002D6-8o for cicm@ietf.org; Thu, 21 Jul 2011 16:04:48 -0600
From: Otaway Thomas <othomas@arkhamtechnology.com>
To: 'CICM Discussion List' <cicm@ietf.org>
References: <F9AB58FA72BAE7449E7723791F6993ED062D1AB1D7@IMCMBX3.MITRE.ORG>
In-Reply-To: <F9AB58FA72BAE7449E7723791F6993ED062D1AB1D7@IMCMBX3.MITRE.ORG>
Date: Thu, 21 Jul 2011 18:04:47 -0400
Organization: Arkham Technology
Message-ID: <01b301cc47f2$34f6d0b0$9ee47210$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcxHv4MOnqbUp0XFQk+e3rJi5RL8IwAMQGGg
Content-Language: en-us
X-Identified-User: {2111:host236.hostmonster.com:arkhamte:arkhamtechnology.com} {sentby:smtp auth 12.132.228.130 authed with othomas+arkhamtechnology.com}
Subject: Re: [cicm] Why do we need a high assurance API?
X-BeenThere: cicm@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: othomas@arkhamtechnology.com, 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, 21 Jul 2011 22:04:49 -0000
CICM Distro List, One application in which this API is needed in the development of high assurance software definable radios. In JTRS this is handled by the "closed" JTRS Red Security Services (RSS) API which is under need-to-know distribution control of the U.S. DoD. An equivalent open standard would provide reduced development costs through commercial competition and a wider global market. The API would also be helpful in the wider range of communications systems, such as terminals and crypto devices (ECUs), that are becoming increasingly "software definable." Thanks, Otaway Otaway Thomas, CISSP, ISSEP, IAM Chief Engineer Arkham Technology Ltd. 20 Pacifica, Suite 670 Irvine, CA 92618 949-228-6677 -----Original Message----- From: Novikov, Lev [mailto:lnovikov@mitre.org] Sent: Thursday, July 21, 2011 12:02 PM To: CICM Discussion List (cicm@ietf.org) Subject: [cicm] Why do we need a high assurance API? For the benefit of IETF folks who are unfamiliar with this area who will be reading this list during and after the BOF: Why do we need a high assurance crypto API? Please write a brief response that relates to your (or your organization's) experience. Thank you, Lev
- Re: [cicm] Why do we need a high assurance API? Cottrell Jr., James R.
- Re: [cicm] Why do we need a high assurance API? Davidson, John A.
- [cicm] Why do we need a high assurance API? Novikov, Lev
- Re: [cicm] Why do we need a high assurance API? Otaway Thomas
- Re: [cicm] Why do we need a high assurance API? Davidson, John A.