Re: [cicm] Use Cases
"Kevin W. Wall" <kevin.w.wall@gmail.com> Fri, 26 August 2011 22:23 UTC
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 0540A21F8C72 for <cicm@ietfa.amsl.com>; Fri, 26 Aug 2011 15:23:27 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gpkru1lMw+1i for <cicm@ietfa.amsl.com>; Fri, 26 Aug 2011 15:23:26 -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 393BD21F8C6E for <cicm@ietf.org>; Fri, 26 Aug 2011 15:23:26 -0700 (PDT)
Received: by wyg8 with SMTP id 8so3180720wyg.31 for <cicm@ietf.org>; Fri, 26 Aug 2011 15:24:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=+NB7PpchK4INFjFVheRwAisSis4XPyE30cuR6xLuj+k=; b=IsVe2qCbaqBx9xbdkl3HboSaEU4Ioep5/B2j80T2f2JLqzdXzyevxp3IG6ejz2iyjr r3buO6XNdMgTF1Xsr2VkyTPENIvxV5fiDHgsTCZ9HCMHFU0g8SxTMdDeWfN+09/xkIV1 LnhVgjOxzROJOjxx4gzeMG3dt3e1vBHU8EMuw=
MIME-Version: 1.0
Received: by 10.216.202.136 with SMTP id d8mr941624weo.52.1314397481500; Fri, 26 Aug 2011 15:24:41 -0700 (PDT)
Received: by 10.216.55.208 with HTTP; Fri, 26 Aug 2011 15:24:41 -0700 (PDT)
In-Reply-To: <F9AB58FA72BAE7449E7723791F6993ED0630EDD3B8@IMCMBX3.MITRE.ORG>
References: <F9AB58FA72BAE7449E7723791F6993ED0630EDD3B8@IMCMBX3.MITRE.ORG>
Date: Fri, 26 Aug 2011 18:24:41 -0400
Message-ID: <CAOPE6Phjw8Acd9x=rQmCyxVfRgH+ORgfkFdcHmJwTffWRUVE_Q@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] Use Cases
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, 26 Aug 2011 22:23:27 -0000
On Fri, Aug 26, 2011 at 4:17 PM, Novikov, Lev <lnovikov@mitre.org> wrote: > I started a rewrite of draft-lanz-cicm-lm and want to discuss the use > cases we want included in the Logical Model. > > Here's a short list I've got so far: > 1. Two networks each in their own security domain (archetypal > high assurance data-in-transit case) > > 2. Traditional data-in-transit and -at-reset case (cf. PKCS#11) I presume that you meant 'at-rest' rather than 'at-reset' here? > 3. One network with two security domains (cf. network storage; > data-in-transit and -at-rest ) > > 4. One machine with two security domains in software (cf. Vincent > Roca's slides http://www.ietf.org/proceedings/81/slides/cicm-1.pdf) > > The resulting model will be used to analyze the impact on existing > protocols where, for example, there might not be separate security > domains. > > ** Anything else to add to the use case list? What are your assumptions about crypto keys? Are you assuming that 2 parties have already met and shared keys (probably out of band)? If not, then I could see maybe use cases involving secure key exchange. However, I suspect that is considered out of scope. -kevin -- Blog: http://off-the-wall-security.blogspot.com/ "The most likely way for the world to be destroyed, most experts agree, is by accident. That's where we come in; we're computer professionals. We *cause* accidents." -- Nathaniel Borenstein
- [cicm] Use Cases Novikov, Lev
- Re: [cicm] Use Cases Kevin W. Wall
- Re: [cicm] Use Cases Davidson, John A.
- Re: [cicm] Use Cases Novikov, Lev
- Re: [cicm] Use Cases Kevin W. Wall
- Re: [cicm] Use Cases Novikov, Lev
- Re: [cicm] Use Cases Krishnamurthy, Hema - ES
- Re: [cicm] Use Cases Davidson, John A.
- Re: [cicm] Use Cases Fitton, John
- Re: [cicm] Use Cases Novikov, Lev
- Re: [cicm] Use Cases Davidson, John A.
- Re: [cicm] Use Cases Cottrell Jr., James R.
- Re: [cicm] Use Cases Davidson, John A.
- Re: [cicm] Use Cases Fitton, John
- Re: [cicm] Use Cases Fitton, John
- Re: [cicm] Use Cases Davidson, John A.
- Re: [cicm] Use Cases Davidson, John A.
- Re: [cicm] Use Cases Fitton, John